Verify Your Infrastructure
Declare the domains, IP networks, S3 buckets and Microsoft 365 tenant your organization operates, and prove you own them to unlock RedKit audits and scheduled scans.
Your organization's infrastructure lists what it operates: domains, IP networks, S3 buckets and its Microsoft 365 tenant. Each asset has to be proven before it counts as yours. Proven assets unlock RedKit audits, scheduled scans and sign-ups from your company domain.
Assets belong to the organization. Every member can see them in Organization → Infrastructure; the owner and admins add, prove and remove them.
| Asset | How it is proven |
|---|---|
| Domain | A DNS TXT record you add |
| Bucket (Amazon S3, Scaleway Object Storage) | A .mlab object in the bucket |
| IP network | Validated by the mlab.sh team |
| Microsoft 365 / Entra ID tenant (beta) | Admin consent, tied to a domain you already proved |
Domains
Add your domain
In Organization → Infrastructure, click Add an asset, choose Domain and enter it (for example example.com).
Add a DNS TXT record
The asset page shows a token like mlab-domain-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. In your DNS provider (Cloudflare, OVH, AWS Route 53...), add it as a TXT record on the root of the domain.
Example DNS record
Type: TXT - Name: @ - Value: mlab-domain-abc123...
Check
Back on the asset page, click Check the DNS record. DNS can take a few minutes to propagate.
The .mlab file
Buckets are proven with a plain text file named .mlab, holding a line VERIF_CODE=<token>. The token is shown on the asset's page. The file can hold other KEY=value lines and # comments for other tools; only VERIF_CODE is read, and you can keep the line after the check.
# .mlab
VERIF_CODE=mlab-s3-3f2a9c1e-5b7d-4e2a-9c1f-0a8b7d6e5f43Buckets
Amazon S3 and Scaleway Object Storage are supported. Another provider (Google Cloud Storage, Azure Blob, OVHcloud, Cloudflare R2, MinIO...)? Ask for it on GitHub Discussions.
Add the bucket
Choose S3 bucket and enter it:
- Amazon S3: its name, or its
s3://orhttps://address. - Scaleway: its address, which carries the region, for example
my-bucket.s3.fr-par.scw.cloudorhttps://s3.fr-par.scw.cloud/my-bucket.
Upload a public .mlab object
Put .mlab with your VERIF_CODE= line at the root of the bucket, readable by anyone. Only that one object has to be public; the rest of the bucket stays private.
aws s3 cp .mlab s3://acme-public-assets/.mlab --content-type text/plainOn Amazon S3, allow public read on that single key with a bucket policy statement:
{
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::acme-public-assets/.mlab"
}On Scaleway, an object ACL is enough:
aws s3 cp .mlab s3://acme-public-assets/.mlab --acl public-read --content-type text/plain \
--endpoint-url https://s3.fr-par.scw.cloudCheck
Click Check the .mlab file. Every Amazon S3 region is supported. If the check fails, the message says why: no such bucket (on Scaleway, check the region in the address), no .mlab object, or an object that is not publicly readable.
IP networks
An IP address or range cannot prove itself with a record, so each IP network is validated by hand by the mlab.sh team.
- Declare one public IPv4 or IPv6 address, or a CIDR range up to
/16(IPv4) or/32(IPv6). A host inside a range is saved as its network (203.0.113.7/24becomes203.0.113.0/24). Private and reserved ranges are refused. - The network stays Pending mlab review until it is validated.
- Contact us and show that your organization owns or operates it: the RIR or WHOIS allocation, your own ASN, or a hosting contract naming the range.
Microsoft 365 (beta)
Connect your Microsoft 365 / Entra ID tenant so RedKit can scan it against the CIS Microsoft 365 benchmark. See Microsoft 365 tenant scans.
Prove a domain of the tenant first
The tenant is tied to your organization through its domains: one of the tenant's verified domains in Entra ID has to be a domain you proved on mlab.
Connect
In Organization → Infrastructure, click Connect Microsoft 365. You are sent to Microsoft's own consent page.
Grant admin consent
A Global Administrator of the tenant (or a Privileged Role or Cloud Application
Administrator) accepts the read-only permissions requested by the mlab-scan
app. Grant all of them: without the permission to read the tenant's organization,
mlab cannot check its domains and the connection is refused.
Back on mlab, the tenant shows as Connected with the number of permissions granted.
- One organization per tenant. A tenant already connected to another organization on mlab is refused.
- Checked daily. mlab checks every day that the consent is still there and which permissions it grants. A tenant whose consent was removed shows Consent removed, and a check that fails says why.
- Owners and Admins can connect a tenant, check it on demand or disconnect it. Members and Viewers see it.
Disconnecting does not withdraw the access. It removes the tenant from mlab. To
revoke the consent itself, also remove the mlab-scan app in Entra ID, under
Enterprise applications.