Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations52 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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, 47 ms lookupPASS
| A | 172.67.134.67, 104.21.25.133 |
| AAAA | 2606:4700:3035::ac43:8643, 2606:4700:3030::6815:1985 |
| CNAME | — |
| NS | linda.ns.cloudflare.com, elliott.ns.cloudflare.com |
| MX | 5 bookstime-com.mail.protection.outlook.com |
| TXT | slack-domain-verification=8lguXbo8mIcR4KEbZSZvYdQdWDKFWrEQzwdDKQVR MS=ms58617240 ZOOM_verify_m85fqGwwtdhhJGqKsrGbaL google-site-verification=QLXnjvKgSd1PaCUAjITW_E3quNEkY56eCI4XBRi9K2I SPF v=spf1 include:spf.protection.outlook.com include:sender.zohoinvoice.com -all 7g084dd.bookings.cs.zohohost.com zoho-verification=zb10471058.zmverify.zoho.com anthropic-domain-verification-9eyehy=drhVJEe32YVw3niMzyqFUhBUm linkedin-site-verification=d5434ea2-2147-4725-98eb-0e4348c9acd5 k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDoB4V9w9YEZgDilXxCVe4ExhNuXZ4xCuE... ahrefs-site-verification_27d690d4f8f4fd1e6e5e54e94623f2644b5588b603cb748c2321c74... |
| 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), 254 ms totalPASS
https://bookstime.com
137 ms · HTTP/1.1
https://www.bookstime.com/
117 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://bookstime.com | 301 | 137 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.bookstime.com/ | 200 | 117 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 6 URLsPASS
User-agent: *
Disallow: /cgi-bin
Disallow: /wp-*
Disallow: /*?*
Disallow: /tag
Disallow: /lp
Disallow: /reviews/written-reviews
Disallow: /reviews/video-reviews
Allow: */uploads
Allow: /wp-*/*.css
Allow: /wp-*/*.js
Allow: /wp-*/*.jpg
Allow: /wp-*/*.mp4
Allow: /wp-*/*.woff
Allow: /wp-*/*.ttf
Allow: /wp-*/*.png
Allow: /wp-*/*.svg
Allow: /wp-*/*.webp
Sitemap: https://www.bookstime.com/sitemap_index.xml
A+Domain Intelligencebookstime.com — via NameCheap, Inc., 19 years, 6 months oldPASS
192 days
January 21, 2027
52 days
Issued by Google Trust Services
19 years, 6 months
Registered January 21, 2007
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:3035::ac43:8643
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