Skip to content
https://routledge.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.routledge.com/
200https://routledge.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://routledge.com/ https://routledge.com/

Consistent

B
TLS Certificate Expiry & Recommendations
68 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

68
days left
0d 30d 60d 90d+

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
B
CDN & Delivery
Cloudflare (BYPASS)
REVIEW
Cloudflare (BYPASS)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f0730101d4b9e45-CDG
Info::
CDN cache status: BYPASS
CDN Detected: Cloudflare
Provider Cloudflare Cache Status BYPASS Evidence cf-ray: 9f0730101d4b9e45-CDG
A+
DNS Records
2 A records, 42 ms lookup
PASS
2 A records, 42 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.17.185.26, 104.17.184.26
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: daisy.ns.cloudflare.com, logan.ns.cloudflare.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 42 ms
Got: 42 ms
A104.17.185.26, 104.17.184.26
AAAA
CNAME
NSdaisy.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
CAALookup not available with standard resolver
Resolved in 42 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 667 ms total
PASS
1 redirect(s), 667 ms total
Info::
Single redirect
Got: https://routledge.com → https://www.routledge.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 667 ms total
Got: 667 ms

https://routledge.com

193 ms · HTTP/1.1

301

https://www.routledge.com/

473 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://routledge.com301193 msHTTP/1.1cloudflare
2https://www.routledge.com/200473 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 19 URLs
PASS
robots.txt present, sitemap with 19 URLs
Info::
robots.txt is present
Got: 1321 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 19 entries
Info::
Sitemap index with 19 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1321 B Sitemaps referenced 1 User-agents DuckDuckBot, Googlebot-Image, Googlebot-Video, Adsbot-Google, Applebot, Caliperbot, LinkedInBot, *, AdsBot, APIs-Google, baiduspider, PetalBot, AhrefsBot, MicrosoftPreview, Neevabot, Slurp, YandexBot, AdIdxBot, Deepcrawl, Googlebot, AdsBot-Google-Mobile, BingPreview, facebookexternalhit/1.1, CCBot, Googlebot-News, SemrushBot, Siteimprove, Storebot-Google, Twitterbot, AdsBot-Google-Mobile-Apps, facebot, facebookexternalhit/1.0, Mediapartners-Google, SemanticScholarBot, Bingbot, ContentKing Blocking No — crawling allowed
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
A+
Domain Intelligence
routledge.com — via SafeNames Ltd., 32 years, 7 months old, hosted on Cloudflare
PASS
routledge.com — via SafeNames Ltd., 32 years, 7 months old, hosted on Cloudflare
Info::
Domain registered until Feb 26, 2027 (10 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: SafeNames Ltd.
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

223 days

February 26, 2027

SSL certificate

68 days

Issued by Google Trust Services

Domain age

32 years, 7 months

Registered February 25, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.17.185.26

Registrar

SafeNames Ltd.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar SafeNames Ltd.
Created February 25, 1994 (32 years, 7 months ago)
Expires February 26, 2027 (10 months)
Last Updated February 27, 2026
Name Servers daisy.ns.cloudflare.com, logan.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 104.17.185.26
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

A+
HTTP Probe Timing
Total 225 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
40 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
225 ms
Total Time Total request time from DNS lookup through full response.
225 ms

Connection waterfall

DNS Lookup 40 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 146 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback