Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain2 redirect(s), 468 ms totalREVIEW
https://mozilla.com
197 ms · HTTP/1.1
https://www.mozilla.org/firefox
22 ms · HTTP/1.1
https://www.firefox.com/
249 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://mozilla.com | 301 | 197 ms | HTTP/1.1 | nginx |
| 2 | https://www.mozilla.org/firefox | 301 | 22 ms | HTTP/1.1 | granian |
| 3 | https://www.firefox.com/ | 200 | 249 ms | HTTP/1.1 | granian |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
user-agent: *
disallow: /*/newsletter/existing/
disallow: /*/etc/
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations83 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
BCDN & DeliveryGoogle Cloud CDNREVIEW
A+DNS Records1 A records, 78 ms lookupPASS
| A | 35.190.14.201 |
| AAAA | — |
| CNAME | — |
| NS | ns1-240.akam.net, ns7-66.akam.net, ns5-65.akam.net, ns4-64.akam.net |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx3.googlemail.com |
| TXT | stripe-verification=12da43cd3189cf99e5c3ecdfdae9c97c7d4230aed93a22ae62892f0cee02... asv=922480dc61f55632a133db2c25597e3d MS=ms53448578 docker-verification=2f2414f7-df6b-4bf5-80e4-b7212e54af13 notion-domain-verification=iFlGX1ER56vtEhhqy0jkEDrJTKztyPXD2BPU4BNYTTG apple-domain-verification=AW6Ub2u78cjUEoTz aocGrHyfAWIi8sU8mTrID9Pj1A xp5tz620d79rq5wg8tss9cqj6ync5ffb status-page-domain-verification=66thnl6f725t knowbe4-site-verification=06f6ae33f35b924850c58ba985731eb7 atlassian-domain-verification=8xkMty0tOT0eog0PN17DvoBgD4NC/3/j/Tkx6tRZN5Zl15VBEF... SPF v=spf1 include:mozilla.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._sp... _1060zlgc0yohte6a6xuiyfrybkulurt openai-domain-verification=dv-K4BRwXIccR9ZPEk5YkygkYoA google-site-verification=IpSwLqTy1MSoslsauQbp2ohg2A92W2Qq2SAw5QQC5jA docusign=b3fe0d4f-0830-4d21-8ac4-3247fd53199c remote-domain-verification=cf65a23c-16ed-4181-8ee9-2bc2741130d5 status-page-domain-verification=v1vmjp2v89c0 h1-domain-verification=npd53FESN2jo7DQNQvMum8E9zdXKmNNjLZKNUHFVDKEoBYwD intacct-esk=4FED1A6DBF25C0CAE053D606A8C0F840 anthropic-domain-verification-bhww58=QIicfKVPKNxTK78KvVLOTg9HY |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
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.
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligencemozilla.com — via MarkMonitor Inc., 31 years, 11 months old, hosted on Google CloudPASS
460 days
October 17, 2027
83 days
Issued by Google Trust Services
31 years, 11 months
Registered October 18, 1994
Not enabled
Protects against DNS spoofing
Google Cloud
ASN AS396982
35.190.14.201
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice