Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
CTLS Certificate Expiry & RecommendationsAction17 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Renew certificate — 17 days remaining
- 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, 7 ms lookupPASS
| A | 45.60.196.209, 45.60.206.209 |
| AAAA | — |
| CNAME | — |
| NS | ns22.digicertdns.com, ns21.digicertdns.com, ns20.digicertdns.com, ns25.digicertdns.net, ns24.digicertdns.net, pdns196.ultradns.com, pdns196.ultradns.biz, ns23.digicertdns.net, pdns196.ultradns.net, pdns196.ultradns.org |
| MX | 10 thawte-com.mail.protection.outlook.com |
| TXT | d9wjp35ljwyfxqr4xqsw40syr0248sbj _2iu6z2hqh86wfvz5vdacq81ohpdh46x SPF v=spf1 include:spf.protection.outlook.com ip4:216.168.254.20/31 a:houston.thawte... MS=ms81472366 _ge3fjt3qqh47qwpxlsf6kkvsytybohy fastly-domain-delegation-CVX4M7mS--20250313 |
| 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), 188 ms totalPASS
https://thawte.com
133 ms · HTTP/1.1
https://www.thawte.com/
55 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://thawte.com | 301 | 133 ms | HTTP/1.1 | |
| 2 | https://www.thawte.com/ | 200 | 55 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 37 URLsPASS
# Welcome to www.thawte.com
# robots.txt for https://www.thawte.com
User-agent: *
Disallow: /content/dam/digicert/pdfs/*
Disallow: /*.net
Sitemap: https://www.thawte.com/sitemap.xml
Sitemap: https://www.thawte.com/fr/sitemap.xml
Sitemap: https://www.thawte.com/de/sitemap.xml
A+Domain Intelligencethawte.com — via MarkMonitor Inc., 30 years, 7 months old, hosted on INCAPSULA - Incapsula Inc, USPASS
240 days
February 11, 2027
17 days
Issued by DigiCert, Inc.
30 years, 7 months
Registered February 10, 1996
Not enabled
Protects against DNS spoofing
INCAPSULA - Incapsula Inc, US
ASN AS19551
45.60.196.209
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Renew the TLS certificate or verify auto-renewal is working
- 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