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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations68 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
BCDN & DeliveryCloudflare (BYPASS)REVIEW
A+DNS Records2 A records, 42 ms lookupPASS
| A | 104.17.185.26, 104.17.184.26 |
| AAAA | — |
| CNAME | — |
| NS | daisy.ns.cloudflare.com, logan.ns.cloudflare.com |
| MX | 10 us-smtp-inbound-1.mimecast.com 10 us-smtp-inbound-2.mimecast.com |
| TXT | SPF v=spf1 ip4:52.31.198.36 ip4:52.31.209.56 ip4:34.240.88.199 ip4:52.16.87.118 ip4... MS=ms15913158 google-site-verification=SKuCqyE_CKZn9yTZE4If5Mq46enB9i8ryOVJDTSnD3Q uaSsDEvb6MOLggzUww76ETh8Et+RxFIjrr2Lw+7qKq1GeirNHkmXctUci27MIR+ZFOucwMAMBapGd59H... google-site-verification=zCOvhtD49-whwOTL8jZgrKL7cWXuXDk6SVmeBNh3VCg |
| 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), 667 ms totalPASS
https://routledge.com
193 ms · HTTP/1.1
https://www.routledge.com/
473 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://routledge.com | 301 | 193 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.routledge.com/ | 200 | 473 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 19 URLsPASS
User-agent: *
#Disallow select URLs
Disallow: /account
Disallow: /wishlist
Disallow: /cart
Disallow: /c/
Disallow: /cw/
Disallow: /cdn-cgi/
Disallow: /sitemap_*.xml
#Allow these Bots to crawl Sitemap
User-agent: AdsBot
User-agent: Adsbot-Google
User-agent: AdsBot-Google-Mobile
User-agent: AdsBot-Google-Mobile-Apps
User-agent: AdIdxBot
User-agent: Applebot
User-agent: APIs-Google
User-agent: baiduspider
User-agent: Bingbot
User-agent: BingPreview
User-agent: Caliperbot
User-agent: CCBot
User-agent: ContentKing
User-agent: Deepcrawl
User-agent: DuckDuckBot
User-agent: facebot
User-agent: facebookexternalhit/1.0
User-agent: facebookexternalhit/1.1
User-agent: Googlebot
User-agent: Googlebot-Image
User-agent: Googlebot-News
User-agent: Googlebot-Video
User-agent: LinkedInBot
User-agent: MicrosoftPreview
User-agent: Mediapartners-Google
User-agent: Neevabot
User-agent: PetalBot
User-agent: SemrushBot
User-agent: Slurp
User-agent: Siteimprove
User-agent: SemanticScholarBot
User-agent: Storebot-Google
User-agent: Twitterbot
User-agent: YandexBot
Allow: /sitemap_*.xml
Disallow: /account
Disallow: /wishlist
Disallow: /cart
Disallow: /c/
Disallow: /cw/
Disallow: /cdn-cgi/
#Disallow everything for AhrefsBot
User-agent: AhrefsBot
Disallow: /
#Sitemaps-https
Sitemap: https://www.routledge.com/sitemap_index.xml
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_produc...
- https://www.routledge.com/sitemap_series...
- https://www.routledge.com/sitemap_landin...
- https://www.routledge.com/sitemap_cmspag...
- https://www.routledge.com/sitemap_hierar...
A+Domain Intelligenceroutledge.com — via SafeNames Ltd., 32 years, 7 months old, hosted on CloudflarePASS
223 days
February 26, 2027
68 days
Issued by Google Trust Services
32 years, 7 months
Registered February 25, 1994
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
104.17.185.26
SafeNames Ltd.
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