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
BTLS Certificate Expiry & Recommendations61 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 Records2 A records, 39 ms lookupPASS
| A | 141.193.213.20, 141.193.213.21 |
| AAAA | — |
| CNAME | — |
| NS | dawn.ns.cloudflare.com, syeef.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com |
| TXT | google-site-verification=itXtD9lkkx85DgNDyiipjB52N_FBSQghFdlnhzqHJK0 google-site-verification=HTDiMjHRQpX_eF537nQ6oXHs43WeGofH__iGR2zKYLE SPF v=spf1 include:_spf.google.com include:46095657.spf06.hubspotemail.net include:_... facebook-domain-verification=103lehoy3d3wnc0pmkrkpp3vthp2id google-site-verification=uOGTRG0t7XJ9Hk_fSOyU8yqreNeLVQ-_sTpZrQvCo4M wpe-verification=towardsdatasci google-site-verification=Ynxc45BkYggoDGQRrWbmRlnW-hIMPIMXCGuPUNfDBPI |
| 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 ChainNo redirects — direct accessPASS
https://towardsdatascience.com
168 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://towardsdatascience.com | 200 | 168 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 28 URLsPASS
Crawl-delay: 10
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:
Sitemap: https://towardsdatascience.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: FacebookBot
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: Cohere-ai
Disallow: /
User-agent: Seekr
Disallow: /
User-agent: Amazonbot
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: BLEXBot
Disallow: /
User-agent: ImagesiftBot
Disallow: /
User-agent: OAI-SearchBot
Disallow: /
User-agent: Applebot
Disallow: /
User-agent: YandexBot
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: GPTbot
Disallow: /
User-agent: meta-externalagent
Disallow: /
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/post-site...
- https://towardsdatascience.com/page-site...
- https://towardsdatascience.com/category-...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencetowardsdatascience.com — via GoDaddy.com, LLC, 9 years, 7 months old, hosted on CloudflarePASS
2288 days
October 22, 2032
61 days
Issued by Google Trust Services
9 years, 7 months
Registered October 22, 2016
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS209242
141.193.213.20
GoDaddy.com, 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