Skip to content
https://biomedcentral.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
72
GRADE
C
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
F
Redirect Chain
Action
5 redirect(s), 912 ms total
FIX
5 redirect(s), 912 ms total
Warning::
5 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://idp.springer.com/authorize?response_type=cookie&client_id=springerlink&redirect_uri=https%3A%2F%2Flink.springer.com%2Fbrands%2Fbmc
Info::
Redirect overhead: 912 ms total
Got: 912 ms
Info::
Cross-domain redirect detected

https://biomedcentral.com

94 ms · HTTP/1.1

301

https://www.biomedcentral.com/

133 ms · HTTP/1.1

301

https://link.springer.com/brands/bmc

99 ms · HTTP/1.1

303

https://idp.springer.com/authorize?respo...

87 ms · HTTP/1.1

302

https://idp.springer.com/transit?redirec...

36 ms · HTTP/1.1

302

https://link.springer.com/brands/bmc?err...

463 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://biomedcentral.com30194 msHTTP/1.1ee-www-redirect
2https://www.biomedcentral.com/301133 msHTTP/1.1Oscar Platform 0.2169.0
3https://link.springer.com/brands/bmc30399 msHTTP/1.1Oscar Platform 0.1651.0
4https://idp.springer.com/authorize?respo...30287 msHTTP/1.1
5https://idp.springer.com/transit?redirec...30236 msHTTP/1.1
6https://link.springer.com/brands/bmc?err...200463 msHTTP/1.1Oscar Platform 0.1651.0

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

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

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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

301http://biomedcentral.com/ http://www.biomedcentral.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

35
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
1 A records, 89 ms lookup
PASS
1 A records, 89 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 151.101.120.95
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: pdns3.ultradns.org, pdns1.ultradns.net, pdns5.ultradns.info, pdns2.ultradns.net, pdns4.ultradns.org, pdns6.ultradns.co.uk
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: 89 ms
Got: 89 ms
A151.101.120.95
AAAA
CNAME
NSpdns3.ultradns.org, pdns1.ultradns.net, pdns5.ultradns.info, pdns2.ultradns.net, pdns4.ultradns.org, pdns6.ultradns.co.uk
MX
10 mxa-002c5801.gslb.pphosted.com
10 mxb-002c5801.gslb.pphosted.com
TXT
cisco-ci-domain-verification=291ae6187ea18e0234c2e1c9f08f6baddd910afbb66b5c62fbb...
adobe-idp-site-verification=e7d316e26179ad0d4b3f90cf2a0754eec7efe5ffd4e42fd68fb1...
facebook-domain-verification=xre922w5m9nvmw5waqvlmnq41x7dcz
extensis-domain-verification=247a2c5e-b2c3-477e-a1a1-69522ce10b98
MS=ms78691022
1password-site-verification=SSE6LJR5OZCBPHTQVLNARPIPGI
docusign=c61dc97d-90e4-4de9-af63-e70f97e1f783
figma-domain-verification=a02807ceec187285dae088008460ab5e258fd494d08ac0c2c56f37...
amazonses:wq0TMrNu/vcOjc2BZI7xzuBznIUVO0yeSNu+kZ0/eV4=
docker-verification=4885e084-3f59-48db-93af-4a98f58a61eb
SPF v=spf1 a:mailer.biomedcentral.com ip4:167.89.16.99 ip4:195.140.184.0/22 ip4:195....
deepl-domain-verification=b8faec8a0acd4830a6c745d36a104c04
Hello GlobalSign CEOS1602043687
anthropic-domain-verification-xrx7w7=tReUnYJJ3wTsWsyQdP8GakqR6
google-site-verification=R7ISj7nuUNrrKZ5idAlSAyEzMWU6jdmcRZT2KBGF8LY
zapier-domain-verification-challenge=a25e9ca6-d313-4cec-94a5-aa8dde7c39cf
_globalsign-domain-verification=OYfE_CcZQWFlEEOrR5yVCfCtmiQrm0bBdyUAJyg3qE
logmein-verification-code=ab8ef76a-a2b4-415a-a019-7917caa85838
globalsign-domain-verification=Myyx9Ky7tszX0BbqISSvJjgoGcwXoeDJCF_AYv4UI4
canva-site-verification=0eQ4w0o1XIdbPUk-R__uFQ
google-site-verification=PMA0l5p3valJp2QZdgL9GFICUNmnMyz7xn8uUIqaod8
CAALookup not available with standard resolver
Resolved in 89 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+
Domain Intelligence
biomedcentral.com — via EuroDNS S.A., 27 years, 1 months old, hosted on Fastly
PASS
biomedcentral.com — via EuroDNS S.A., 27 years, 1 months old, hosted on Fastly
Info::
Domain registered until Aug 6, 2026 (3 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: EuroDNS S.A.
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: Fastly
Got: AS54113
Domain expiry

22 days

August 6, 2026

SSL certificate

35 days

Issued by Let's Encrypt

Domain age

27 years, 1 months

Registered August 6, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.120.95

Registrar

EuroDNS S.A.

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar EuroDNS S.A.
Created August 6, 1999 (27 years, 1 months ago)
Expires August 6, 2026 (3 months)
Last Updated July 31, 2025
Name Servers pdns1.ultradns.net, pdns2.ultradns.net, pdns3.ultradns.org, pdns4.ultradns.org, pdns5.ultradns.info, pdns6.ultradns.co.uk
DNSSEC Not enabled
Hosting
IP Address 151.101.120.95
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 38 ms TCP Connect 29 ms TLS Handshake 36 ms Server Processing 30 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT)
PASS
Fastly (HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-par-lfpb1150085-PAR
Info::
CDN cache status: HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT Evidence x-served-by: cache-par-lfpb1150085-PAR
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback