Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.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
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.
BTLS Certificate Expiry & Recommendations136 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+DNS Records4 A records, 107 ms lookupPASS
| A | 18.67.250.64, 18.67.250.28, 18.67.250.40, 18.67.250.73 |
| AAAA | — |
| CNAME | — |
| NS | ns-514.awsdns-00.net, ns-1026.awsdns-00.org, ns-230.awsdns-28.com, ns-1723.awsdns-23.co.uk |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | fastly-domain-delegation-lHDS6yvr4CVHHKnr-#526123-2022-08-23 onetrust-domain-verification=d381bc7429ba4303bc288952d3e2291b atlassian-domain-verification=kpW93Gl0HucESn1XIuigK0EfPnA8gPRAkNY/HH6ej3NcfKLftx... MS=ms51740217 d3vc9g5lfoexwz.cloudfront.net google-site-verification=B4YiM1AMRmRxZokjTlp9fEsXeFgZ1dCK5FtD2gpb8ak SPF v=spf1 include:_spf.google.com ~all onetrust-domain-verification=6a0f32b404ce44ab9f846a571b40db1e citrix-verification-code=d409e05c-b335-425e-a215-204389a91206 MS=ms74645168 facebook-domain-verification=6fj5bqy5ypyad2lqfo7l56cnica6ka google-site-verification=2vj8liJykIp_twB7iqGJXSvu1gdjhj2WRtXlbv50hdE google-site-verification=q4m_Qtyp6r5s8NwvpLjzlAuj-7Hox7pigEAoTiLkWHs fastly-domain-delegation-r4QqUNzN2Z5GPFvD-568289-2023-01-30 google-site-verification=KAUbQ2E7KXxBCMdp42KCmke3GHEejxhLW_WStVM6kfw SPF v=spf1 include:servers.mcsv.net ?all zrtl4rb41l611631srp8b1c1klpphl31 google-site-verification=vVzzWl6hH3GlrYq6c7gH03Fle_YzB_VPK8J65ApD4Rw r3l0yk16b9wf7xsx9qy94ktd9zmj0tvz docusign=f6ed7987-8396-476d-b76e-1251c0fa75ff fastly-domain-delegation-lnYFR7XAspYWCDr-#518056-2022-07-19 cursor-domain-verification-8x16vk=nSAF8Y95RSKRSB5oIBt9seThK ahrefs-site-verification_e608251d484c28256d6e39259fb2d78c0971f422502addc2f345756... mongodb-site-verification=DZabVN0N2nIFzrDovMKp6dmih13qM1il |
| 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.
ARedirect Chain1 redirect(s), 105 ms totalPASS
https://howstuffworks.com
9 ms · HTTP/1.1
https://www.howstuffworks.com/
96 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://howstuffworks.com | 301 | 9 ms | HTTP/1.1 | AmazonS3 |
| 2 | https://www.howstuffworks.com/ | 202 | 96 ms | HTTP/1.1 | CloudFront |
See the visual redirect chain in the HTTP Probe tab →
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencehowstuffworks.com — via eNom, LLC, 28 years, 2 months old, hosted on AWSPASS
1456 days
July 10, 2030
136 days
Issued by Amazon
28 years, 2 months
Registered July 11, 1998
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
18.67.250.28
eNom, LLC
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