Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain2 redirect(s), 593 ms totalREVIEW
https://cochranelibrary.com
209 ms · HTTP/1.1
https://www.cochranelibrary.com/
244 ms · HTTP/1.1
https://www.cochranelibrary.com/?cookies...
140 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://cochranelibrary.com | 301 | 209 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.cochranelibrary.com/ | 302 | 244 ms | HTTP/1.1 | cloudflare |
| 3 | https://www.cochranelibrary.com/?cookies... | 412 | 140 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
BCrawlabilityrobots.txt present, sitemap with 2105 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
Sitemap: https://www.cochranelibrary.com/sitemap.xml
User-agent: ByteDanceSpider
Disallow: /
User-agent: Claude
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: spider-feedback@bytedance.com
Disallow:/
User-agent: Bytespider
Disallow:/
User-agent:PetalBot
Disallow:/
User-agent: Amazonbot
Disallow:/
User-agent: Applebot
Disallow:/
User-agent: 008
Disallow: /
User-agent: Bingbot
Disallow:
Crawl-delay: 1
User-agent: Slurp
Disallow:
Crawl-delay: 1
User-agent: Googlebot
Disallow: /html/js/editor/fckeditor/*
User-agent: Googlebot
Disallow: /html/js/editor/*
User-agent: Googlebot
Disallow: /es/web/
User-agent: Googlebot
Disallow: /web/
BTLS Certificate Expiry & Recommendations47 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
- 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, 41 ms lookupPASS
| A | 104.18.37.68, 172.64.150.188 |
| AAAA | 2606:4700:4405::6812:2544, 2a06:98c1:3103::ac40:96bc |
| CNAME | — |
| NS | yolanda.ns.cloudflare.com, carl.ns.cloudflare.com |
| MX | — |
| TXT | _68s1n23xq7ssh2b74ybe2tuac09bind |
| 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.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencecochranelibrary.com — via GoDaddy Corporate Domains, LLC, 27 years, 6 months oldPASS
216 days
February 18, 2027
47 days
Issued by Google Trust Services
27 years, 6 months
Registered February 18, 1999
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:4405::6812:2544
GoDaddy Corporate Domains, LLC
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