Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BTLS Certificate Expiry & Recommendations34 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 Records3 A records, 6 ms lookupPASS
| A | 104.26.1.204, 172.67.71.236, 104.26.0.204 |
| AAAA | 2606:4700:20::681a:cc, 2606:4700:20::ac43:47ec, 2606:4700:20::681a:1cc |
| CNAME | — |
| NS | henry.ns.cloudflare.com, kristin.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | ca3-cdf5f862483847feb4f5135b47fd2928 google-site-verification=UO6yURBZsU4LoK8EOC16aUUSAVUWeFECRVMsNTqsBTk google-site-verification=X7yuHwqV8i-A-2Ax1WvwYWUcMzRp-Vy7HXBTdjOUmMU google-site-verification=nWvV-casKHxl1hqp1OOxLP1URReKT2AiYoec-H8AeZc google-site-verification=yOZqvk4x8W8tWJhUBMYVfo3G2DdBudDx4o3-6-sAYbo SPF v=spf1 include:_spf.google.com include:_spf.mlsend.com include:spf.happyfox.com ... |
| 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://pydata.org
694 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://pydata.org | 200 | 694 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 7 URLsPASS
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Crawl-delay: 10
Sitemap: https://pydata.org/wp-sitemap.xml
- https://pydata.org/wp-sitemap-posts-page...
- https://pydata.org/wp-sitemap-posts-proj...
- https://pydata.org/wp-sitemap-posts-mec-...
- https://pydata.org/wp-sitemap-taxonomies...
- https://pydata.org/wp-sitemap-taxonomies...
- https://pydata.org/wp-sitemap-taxonomies...
- https://pydata.org/wp-sitemap-users-1.xm...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencepydata.org — via NameCheap, Inc., 14 years, 6 months oldPASS
917 days
December 16, 2028
34 days
Issued by Google Trust Services
14 years, 6 months
Registered December 16, 2011
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:20::ac43:47ec
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