Audit: gitlab.com
Checking…
- Reachable 1% of the last 24 hours
- Last time we couldn't reach it: 5d ago
- Outages cost you traffic and rankings while they last, and they rarely happen while you are watching.
On-page SEO
Crawlability
TLS & security
Network
100/100- Hostname resolves to an A record 172.65.251.78
- MX records valid + reachable
- SPF record present v=spf1 include:mail.zendesk.com include:_spf.google.com include:mktomail.com include:_spf.salesforce.com include:_spf-ip.gitlab.com a:zgateway.zuora.com include:mailgun.org include:_spf.sendergen.com ip4:35.80.141.6/32 ip4:44.229.121.55/32 -all
- DMARC record present
- DMARC policy enforced p=reject
- DKIM key published selector=google, ~1296-bit
DNS
100/100- A records resolve
- NS records present
- MX records present
- DNS resolvers agree on the same A record 100% of 12 resolvers agree
- Domain registration not expiring soon 116 days left
- Domain is established 22y 7m 21d (2004-01-15)
What changed
Nothing has changed on gitlab.com since we started watching it.
Certificates expire, DNS gets edited, a header goes missing in a deploy. Prove the domain is yours and we watch it on a schedule — free — and email you the moment something moves, so you hear it from us instead of from a customer.
Subdomains discovered 🔒 Pro
502 via Certificate Transparency · 500+ truncated
We found 502 subdomains for
gitlab.com via Certificate Transparency logs.
Unlock the subdomain list
- See every subdomain discovered via crt.sh CT logs
- Click any subdomain to audit it (separate report)
- Useful for security recon + asset inventory
A certificate that expires on Tuesday should not wait until Friday. Prove a domain is yours and we check it free, once a week, emailing you anything that changed. Pro checks it once a day, looks at every host on the domain, and keeps 365 days of history — so you hear about a problem in hours rather than days.
Compare plans →