Skip to content
https://biorxiv.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
6 PASS 3 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 3636 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 3636 B Sitemaps referenced 0 User-agents phxbot, Qwantbot, Scanbot, Semrush, YoudaoBot, openai, Bolt, SeekportBot, ChatGPT-User, Gigabot, SuperBot, Amazonbot, AhrefsBot, ClaudeBot, Majestic12, facebookexternalhit/1.1, SMTBot, ScreenerBot, SuperHTTP, CCBot, wget, HybridBot, PerplexityBot, BLEXBot, Bytespider, JikeSpider, AwarioBot, python-requests/2.32.3, curl, *, Exabot, Baiduspider, YandexBot, Petalbot, Applebot, DataForSeoBot, DotBot, MJ12bot, BunnySlippers, SemrushBot, SiteLockSpider, GPTBot, SEMrush Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: BLEXBot
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: Exabot
Disallow: /
User-agent: Scanbot
Disallow: /
User-agent: Semrush
Disallow: /
User-agent: SemrushBot
Disallow: /
User-agent: YoudaoBot
Disallow: /
User-agent: Baiduspider
Disallow: /
User-agent: YandexBot
Disallow: /
User-agent: openai
Disallow: /
User-agent: Petalbot
Disallow: /
User-agent: Bolt
Disallow: /
User-agent: BunnySlippers
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: Gigabot
Disallow: /
User-agent: HybridBot
Disallow: /
User-agent: JikeSpider
Disallow: /
User-agent: SMTBot
Disallow: /
User-agent: ScreenerBot
Disallow: /
User-agent: SiteLockSpider
Disallow: /
User-agent: SuperBot
Disallow: /
User-agent: SuperHTTP
Disallow: /
User-agent: Amazonbot
Disallow: /
User-agent: AhrefsBot
Disallow: /
User-agent: Applebot
Disallow: /
User-agent: SEMrush
Disallow: /
User-agent: DataForSeoBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: DotBot
Disallow: /
User-agent: phxbot
Disallow: /
User-agent: AwarioBot
Disallow: /
User-agent: SeekportBot
Disallow: /
User-agent: MJ12bot
Disallow: /
User-agent: Majestic12
Disallow: /
User-agent: facebookexternalhit/1.1
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: Qwantbot
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: python-requests/2.32.3
Disallow: /
User-agent: wget
Disallow: /
User-agent: curl
Disallow: /

User-agent: *
Crawl-delay: 7
# CSS, JS, Images
Allow: /misc/*.css$
Allow: /misc/*.css?
Allow: /misc/*.js$
Allow: /misc/*.js?
Allow: /misc/*.gif
Allow: /misc/*.jpg
Allow: /misc/*.jpeg
Allow: /misc/*.png
Allow: /modules/*.css$
Allow: /modules/*.css?
Allow: /modules/*.js$
Allow: /modules/*.js?
Allow: /modules/*.gif
Allow: /modules/*.jpg
Allow: /modules/*.jpeg
Allow: /modules/*.png
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /themes/*.css$
Allow: /themes/*.css?
Allow: /themes/*.js$
Allow: /themes/*.js?
Allow: /themes/*.gif
Allow: /themes/*.jpg
Allow: /themes/*.jpeg
Allow: /themes/*.png
# Directories
Disallow: /includes/
Disallow: /misc/
Disallow: /modules/
Disallow: /profiles/
Disallow: /scripts/
Disallow: /themes/
# Files
Disallow: /CHANGELOG.txt
Disallow: /cron.php
Disallow: /INSTALL.mysql.txt
Disallow: /INSTALL.pgsql.txt
Disallow: /INSTALL.sqlite.txt
Disallow: /install.php
Disallow: /INSTALL.txt
Disallow: /LICENSE.txt
Disallow: /MAINTAINERS.txt
Disallow: /update.php
Disallow: /UPGRADE.txt
Disallow: /xmlrpc.php
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips/
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register/
Disallow: /user/password/
Disallow: /user/login/
Disallow: /user/logout/
# Paths (no clean URLs)
Disallow: /?q=admin/
Disallow: /?q=comment/reply/
Disallow: /?q=filter/tips/
Disallow: /?q=node/add/
Disallow: /?q=search/
Disallow: /?q=user/password/
Disallow: /?q=user/register/
Disallow: /?q=user/login/
Disallow: /?q=user/logout/
Disallow: /user
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.biorxiv.org/
200https://biorxiv.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://biorxiv.org/ https://www.biorxiv.org/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

44
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
A+
DNS Records
2 A records, 49 ms lookup
PASS
2 A records, 49 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.50.144, 172.67.207.1
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3034::6815:3290, 2606:4700:3030::ac43:cf01
Info::
2 nameserver(s) configured
Got: vin.ns.cloudflare.com, jen.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: 49 ms
Got: 49 ms
A104.21.50.144, 172.67.207.1
AAAA2606:4700:3034::6815:3290, 2606:4700:3030::ac43:cf01
CNAME
NSvin.ns.cloudflare.com, jen.ns.cloudflare.com
MX
10 usb-smtp-inbound-1.mimecast.com
10 usb-smtp-inbound-2.mimecast.com
TXT
SPF v=spf1 include:usb._netblocks.mimecast.com include:helpscoutemail.com a:it-ppmgw...
MS=ms36527074
CAALookup not available with standard resolver
Resolved in 49 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), 729 ms total
PASS
1 redirect(s), 729 ms total
Info::
Single redirect
Got: https://biorxiv.org → https://www.biorxiv.org/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://biorxiv.org
Info::
Redirect overhead: 729 ms total
Got: 729 ms

https://biorxiv.org

226 ms · HTTP/1.1

302

https://www.biorxiv.org/

502 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://biorxiv.org302226 msHTTP/1.1cloudflare
2https://www.biorxiv.org/200502 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

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

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3034::6815:3290, 2606:4700:3030::ac43:cf01
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3034::6815:3290, 2606:4700:3030::ac43:cf01 Connection Reachable (17 ms)
A+
Domain Intelligence
biorxiv.org — via CSC Corporate Domains, Inc., 13 years, 2 months old
PASS
biorxiv.org — via CSC Corporate Domains, Inc., 13 years, 2 months old
Info::
Domain registered until Apr 8, 2027 (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: CSC Corporate Domains, Inc.
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.
Domain expiry

266 days

April 8, 2027

SSL certificate

44 days

Issued by Google Trust Services

Domain age

13 years, 2 months

Registered April 8, 2013

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3034::6815:3290

Registrar

CSC Corporate Domains, Inc.

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 CSC Corporate Domains, Inc.
Created April 8, 2013 (13 years, 2 months ago)
Expires April 8, 2027 (11 months)
Last Updated April 9, 2026
Name Servers jen.ns.cloudflare.com, vin.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3034::6815:3290
Data source: rdap (0.7s)

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 272 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
49 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.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
273 ms
Total Time Total request time from DNS lookup through full response.
273 ms

Connection waterfall

DNS Lookup 49 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 184 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9eff2d0c082d2b02-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9eff2d0c082d2b02-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback