Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BDNS Records4 A records, 207 ms lookupREVIEW
| A | 13.249.74.73, 13.249.74.83, 13.249.74.5, 13.249.74.25 |
| AAAA | 2600:9000:211f:f400:7:7859:3840:93a1, 2600:9000:211f:cc00:7:7859:3840:93a1, 2600:9000:211f:d200:7:7859:3840:93a1, 2600:9000:211f:ba00:7:7859:3840:93a1, 2600:9000:211f:fc00:7:7859:3840:93a1, 2600:9000:211f:2c00:7:7859:3840:93a1, 2600:9000:211f:de00:7:7859:3840:93a1, 2600:9000:211f:a000:7:7859:3840:93a1 |
| CNAME | d1zmu2nnrptrdt.cloudfront.net |
| NS | ns-1470.awsdns-55.org, ns-194.awsdns-24.com, ns-2001.awsdns-58.co.uk, ns-890.awsdns-47.net |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
BTLS Certificate Expiry & Recommendations306 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+Redirect ChainNo redirects — direct accessPASS
https://www.mongodb.com
19 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.mongodb.com | 200 | 19 ms | HTTP/1.1 | istio-envoy |
A+Crawlabilityrobots.txt present, sitemap with 15 URLsPASS
# See http://www.robotstxt.org/robotstxt.html for documentation on how to use the robots.txt file
User-agent: mauibot
Disallow: /community/forums/
User-agent: semrushbot
Disallow: /community/forums/
User-agent: ahrefsbot
Disallow: /community/forums/
User-agent: blexbot
Disallow: /community/forums/
User-agent: seo spider
Disallow: /community/forums/
User-agent: bingbot
Disallow: /community/forums/auth/
Disallow: /community/forums/assets/browser-update*.js
Disallow: /community/forums/email/
Disallow: /community/forums/session
Disallow: /community/forums/session/
Disallow: /community/forums/admin
Disallow: /community/forums/admin/
Disallow: /community/forums/user-api-key
Disallow: /community/forums/user-api-key/
Disallow: /community/forums/*?api_key*
Disallow: /community/forums/*?*api_key*
User-agent: *
Disallow: /misc/
Disallow: /profiles/
Disallow: /u/
Disallow: /community/forums/auth/
Disallow: /community/forums/email/
Disallow: /community/forums/session
Disallow: /community/forums/session/
Disallow: /community/forums/admin
Disallow: /community/forums/admin/
Disallow: /community/forums/user-api-key
Disallow: /community/forums/user-api-key/
Disallow: /community/forums/g/
Disallow: /community/forums/u/
Disallow: /community/forums/user_avatar/
# Files
Disallow: /admin/*
Disallow: /data/*
Disallow: /comment/reply/
Disallow: /filter/tips/
Disallow: /node/add/
Disallow: /search/
Disallow: /search
Disallow: /user/register/
Disallow: /user/password/
Disallow: /user/login/
Disallow: /user/logout/
Disallow: /lp/p/*
Disallow: /lp/s/*
Disallow: /lp/d/*
Disallow: /thank-you/*
Disallow: /link/*
Disallow: /community/forums/assets/browser-update*.js
Disallow: /docs/*.epub
Disallow: /docs/*.pdf
Disallow: /docs/atlas/app-services/
# No access for quicktabs in the URL
Disallow: /*?quicktabs_*
Disallow: /*&quicktabs_*
Disallow: /*?qt-view_*
Disallow: /*&qt-view_*
# No crawling field collections or taxonomy
Disallow: /field-collection/*
Disallow: /tags/*
Disallow: /taxonomy/term/*
# Paths (no clean URLs)
Disallow: /?q=admin/
Disallow: /?q=comment/reply/
Disallow: /?q=filter/tips/
Disallow: /?q=node/add/
Disallow: /?q=search/
Disallow: /?q=user/password/
Disallow: /?q=user/register/
Disallow: /?q=user/login/
Disallow: /?q=user/logout/
# Specific pages
Disallow: /commercialsupport/
Disallow: /partners/referral-federal
Disallow: /customer-evaluation-downloads-development-versions
Disallow: /community/forums/*?api_key*
Disallow: /community/forums/*?*api_key*
Disallow: /docs/meta/
Disallow: /docs/search/
Disallow: /docs/openapi/
# Prevent exposing future docs
Disallow: /docs-qa*
# Prevent exposing devhub UAT
Disallow: /devcenter-uat*
Disallow: /de-de/developer*
Disallow: /es/developer*
Disallow: /fr-fr/developer*
Disallow: /it-it/developer*
Disallow: /ja-jp/developer*
Disallow: /ko-kr/developer*
Allow: /pt-br/developer*
Disallow: /zh-cn/developer*
Disallow: /lp/internal/cheq-ppc-invalid-users*
Disallow: /llms.txt
Disallow: /.well-known/security.txt
Sitemap: https://www.mongodb.com/sitemap.xml
- https://www.mongodb.com/sitemap-pages.xm...
- https://www.mongodb.com/community/forums...
- https://www.mongodb.com/developer/sitema...
- https://www.mongodb.com/docs/sitemap.xml
- https://www.mongodb.com/docs/sitemap-ind...
- https://learn.mongodb.com/sitemap-index-...
- https://www.mongodb.com/zh-cn/sitemap-pa...
- https://www.mongodb.com/zh-tw/sitemap-pa...
- https://www.mongodb.com/ko-kr/sitemap-pa...
- https://www.mongodb.com/ja-jp/sitemap-pa...
- https://www.mongodb.com/fr-fr/sitemap-pa...
- https://www.mongodb.com/de-de/sitemap-pa...
- https://www.mongodb.com/it-it/sitemap-pa...
- https://www.mongodb.com/pt-br/sitemap-pa...
- https://www.mongodb.com/es/sitemap-pages...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligencemongodb.com — via Gandi SAS, 17 years, 11 months old, hosted on AWSPASS
2554 days
July 8, 2033
306 days
Issued by Amazon
17 years, 11 months
Registered July 8, 2008
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
3.33.132.188
Gandi SAS
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033