Skip to content
https://bloomsbury.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
2 redirect(s), 775 ms total
REVIEW
2 redirect(s), 775 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Redirect overhead: 775 ms total
Got: 775 ms

https://bloomsbury.com

51 ms · HTTP/1.1

301

https://www.bloomsbury.com/

44 ms · HTTP/1.1

301

https://www.bloomsbury.com/uk/

681 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bloomsbury.com30151 msHTTP/1.1
2https://www.bloomsbury.com/30144 msHTTP/1.1cloudflare
3https://www.bloomsbury.com/uk/200681 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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
TLS Certificate Expiry & Recommendations
39 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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 Records
1 A records, 6 ms lookup
PASS
1 A records, 6 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 157.96.37.33
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1145.awsdns-15.org, ns-1892.awsdns-44.co.uk, ns-315.awsdns-39.com, ns-985.awsdns-59.net
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: 6 ms
Got: 6 ms
A157.96.37.33
AAAA—
CNAME—
NSns-1145.awsdns-15.org, ns-1892.awsdns-44.co.uk, ns-315.awsdns-39.com, ns-985.awsdns-59.net
MX
10 d217041.b.ess.uk.barracudanetworks.com
10 d217041.a.ess.uk.barracudanetworks.com
TXT
0s5FjjRz/XAHYzx8kLhPC9C4LJpuZNpZ9DpPN6ZHlSdNExPPp3PmnuEUzZw0O4CC+qYKTvBREiHFuiIX...
adobe-idp-site-verification=8293d4a5-8d70-41a4-be2b-33e4d764d6df
atlassian-domain-verification=/q7d/4w08+VbbYLzz52MJSPknnpkpFhvqjoID55t6fE2Fwkn0k...
atlassian-domain-verification=LqC2odN8bV3PnmamaFiEWgaIQurmiYcGrrHwvtJUwiSefhfB6Z...
dropbox-domain-verification=cjx5jnvfh4t3
extensis-domain-verification=9148ea61-cfcd-49df-9eb4-980cb7d9c30c
google-gws-recovery-domain-verification=64672055
google-site-verification=JE-JI7eZHoQNQ_hdrcvx3JRxi2pJHlpmyDSCQ2ZL5pA
ild4jvnh50aghv9g8vg6fj31ub
smartsheet-site-validation=qhhn2w5FqNjTtUvtnENnLBRgV87COoKq
v700tabb972c0jfq8g76ars7fl.
SPF v=spf1 ip4:193.117.153.36/32 include:_spf.smtp.com include:sendgrid.net include:...
zapier-domain-verification-challenge=b026c78b-41bb-4c8a-b504-1655ab073d14
CAALookup not available with standard resolver
Resolved in 6 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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+
Crawlability
robots.txt present, sitemap with 11 URLs
PASS
robots.txt present, sitemap with 11 URLs
Info::
robots.txt is present
Got: 811 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 11 entries
Info::
Sitemap index with 11 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 811 B Sitemaps referenced 5 User-agents OAI-SearchBot, *, MegaIndex.ru/2.0, PetalBot, SemrushBot, SeznamBot, BLEXBot, GPTBot, Googlebot, MJ12bot, Seekport Crawler, YandexBot, AhrefsBot Blocking No — crawling allowed
User-agent: *

Disallow: /*?*

Disallow: /*/Account/

Disallow: /*/account/


#Block bots

User-agent: MegaIndex.ru/2.0

Disallow: /


User-agent: MJ12bot

Disallow: /


User-agent: PetalBot

Disallow: /


User-agent: Seekport Crawler

Disallow: /


User-agent: SemrushBot

Disallow: /


User-agent: SeznamBot

Disallow: /


User-agent: YandexBot

Disallow: /


User-agent: BLEXBot

Disallow: /


User-agent: AhrefsBot

Disallow: /


User-agent: GPTBot

Disallow: /


User-agent: Googlebot

Allow: .js

Allow: .css


User-agent: OAI-SearchBot

Allow: /


SiteMap: https://www.bloomsbury.com/uk/sitemap/

SiteMap: https://www.bloomsbury.com/us/sitemap/

SiteMap: https://www.bloomsbury.com/ca/sitemap/

SiteMap: https://www.bloomsbury.com/au/sitemap/

SiteMap: https://www.bloomsbury.com/in/sitemap/
sitemap.xml 200 OK
Type Sitemap Index URLs 11 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.bloomsbury.com/
200https://bloomsbury.com/

Preferred variant: non-www

HTTP → HTTPS

301http://bloomsbury.com/ → https://www.bloomsbury.com/

Consistent

A+
Domain Intelligence
bloomsbury.com — via Netregistry Wholesale Pty Ltd, 30 years, 6 months old, hosted on NODE4-AS, GB
PASS
bloomsbury.com — via Netregistry Wholesale Pty Ltd, 30 years, 6 months old, hosted on NODE4-AS, GB
Info::
Domain registered until Mar 16, 2028 (1 years, 11 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: Netregistry Wholesale Pty 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: NODE4-AS, GB
Got: AS31727
Domain expiry

606 days

March 16, 2028

SSL certificate

39 days

Issued by Let's Encrypt

Domain age

30 years, 6 months

Registered March 15, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

NODE4-AS, GB

ASN AS31727

157.96.37.33

Registrar

Netregistry Wholesale Pty Ltd

Unlocked 4 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 Netregistry Wholesale Pty Ltd
Created March 15, 1996 (30 years, 6 months ago)
Expires March 16, 2028 (1 years, 11 months)
Last Updated March 9, 2026
Name Servers ns-1145.awsdns-15.org, ns-1892.awsdns-44.co.uk, ns-315.awsdns-39.com, ns-985.awsdns-59.net
DNSSEC Not enabled
Hosting
IP Address 157.96.37.33
ASN AS31727 (NODE4-AS, GB)
Provider NODE4-AS, GB
Data source: rdap (0.3s)

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 49 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
6 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
9 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
25 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
49 ms
Total Time Total request time from DNS lookup through full response.
49 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 9 ms TLS Handshake 25 ms Server Processing 9 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