Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.
Learn more ▾ ▴
A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.
Source: robotstxt.org
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations82 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
BCDN & DeliveryCloudflareREVIEW
A+DNS Records3 A records, 65 ms lookupPASS
| A | 104.26.3.210, 172.67.73.4, 104.26.2.210 |
| AAAA | 2606:4700:20::ac43:4904, 2606:4700:20::681a:3d2, 2606:4700:20::681a:2d2 |
| CNAME | — |
| NS | sam.ns.cloudflare.com, tia.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com |
| TXT | canva-site-verification=NvK-kXR51RfbU-gI1UdS9w pinterest-site-verification=e55e025b0d2539af591f6fefd583d629 google-site-verification=RAzplC0Feitd-Cixj4F926vpRo_Mio2Dis8jdNYGrRY SPF v=spf1 include:_spf.google.com include:amazonses.com -all atlassian-sending-domain-verification=d2fc7aed-ee36-4f93-b68c-61903722b3f1 google-site-verification=1hz3mc2yY74qpX5anrDuBZSBPivcvj7Ss-LYTByfjO4 MS=ms59652260 facebook-domain-verification=ct6vu5teblmhqvm49kk2x41buf3bp4 _mur8jmfp2ena05od14yb5mys89rq1ln uber-domain-verification=67bcba49-168b-4916-b422-9041069d639a 6274674FB0 _v8f6cfpzhrssev71cqedtj5rfz7m9kk apple-domain-verification=88kAJl6MYvJPpfXc d3c28fbwo1q37r.cloudfront.net MS=ms59239349 google-site-verification=f1H0Tvx3li7DAsCTcrU2GYCeW9XTCjztPaRTiYP3REg 065011A1B1 google-site-verification=eH0BBY4UQu-oTIayELUMVNzecHxm0QpfJv0FoHI6X24 openai-domain-verification=dv-854kXSADWO0ujab7huL1PlUB anthropic-domain-verification-kg11q5=KyNne4qrnrSwpDKPjqldiZVwO |
| CAA | Lookup not available with standard resolver |
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.
A+Redirect Chain0 redirect(s), 58 ms totalPASS
https://money.com
58 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://money.com | 403 | 58 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Domain Intelligencemoney.com — via NameCheap, Inc., 31 years, 5 months oldPASS
1730 days
April 11, 2031
82 days
Issued by Let's Encrypt
31 years, 5 months
Registered April 10, 1995
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:20::681a:3d2
NameCheap, 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