Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.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: /*/etc/
No sitemap found
Adding a sitemap helps search engines discover your pages.
CURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
BTLS Certificate Expiry & Recommendations55 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, 4 ms lookupPASS
| A | 35.190.14.201 |
| AAAA | 2600:1901:0:c197:: |
| CNAME | — |
| NS | ns4-64.akam.net, ns7-66.akam.net, ns1-240.akam.net, ns5-65.akam.net |
| MX | 10 smtp1.mdc1.mozilla.com |
| TXT | google-site-verification=v8PIY1kSh7pPuimUXQ9-_A3i9_lzUakke3IM84Kydm0 google-site-verification=XhMUzMo_1XF_gE3oDEbbZXe7YFRse5S1i56GRYAsZ6c google-site-verification=5wrBmyx3ifvHZaMlf2aRWtmrQyucSbae9tRVGLny6b8 google-site-verification=8VDxHwx5SDmTQP1NRDm_sEERLZPvmDiTOLpEQMh9sxI google-site-verification=NZ6YuiV9PaFX7rWqXJZxDpunitn7M8mtlnoaN2Z8Dcs 3mjnbdj3h9wpslgz0gfly0pbr94wd12y SPF v=spf1 mx a include:amazonses.com include:mail.zendesk.com include:%{i}._ip.%{h}... google-site-verification=_WNoj_JxZRdbVS22FKJpI1gK5oZZMNbXGF57WcqO0MA google-site-verification=8m_NyuMhNncHiV0a_gN7FTA_Pk0N0QE4-AKfN5XBwpY kr1887r7cjn94rzlgp1bpnj8v94wd3mg facebook-domain-verification=wcer1w80xkwrzqftwc3shhkel9ys8m _vrrc3v9222jxd6yhvt728lc4om6z0ff |
| 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.
ARedirect Chain1 redirect(s), 183 ms totalPASS
https://firefox.com
162 ms · HTTP/1.1
https://www.firefox.com/
21 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://firefox.com | 302 | 162 ms | HTTP/1.1 | nginx |
| 2 | https://www.firefox.com/ | 200 | 21 ms | HTTP/1.1 | granian |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
A+IPv6 ReadinessIPv6 reachable (2 ms)PASS
A+Domain Intelligencefirefox.com — via MarkMonitor Inc., 27 years, 11 months oldPASS
83 days
October 5, 2026
55 days
Issued by Let's Encrypt
27 years, 11 months
Registered October 6, 1998
Not enabled
Protects against DNS spoofing
Unknown
2600:1901:0:c197::
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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