Skip to content
https://cell.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
302 Found
Checks
9
6 PASS 2 REVIEW 1 FIX
F
Redirect Chain
Action
5 redirect(s), 1429 ms total
FIX
5 redirect(s), 1429 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://cell.com
Warning::
Redirect overhead: 1429 ms total
Got: 1429 ms
Info::
Cross-domain redirect detected

https://cell.com

141 ms · HTTP/1.1

302

https://id.elsevier.com/as/authorization...

158 ms · HTTP/1.1

302

https://www.cell.com/callback?red_uri=%2...

434 ms · HTTP/1.1

302

https://www.cell.com/

120 ms · HTTP/1.1

302

https://id.elsevier.com/as/authorization...

159 ms · HTTP/1.1

302

https://www.cell.com/callback?red_uri=%2...

417 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cell.com302141 msHTTP/1.1cloudflare
2https://id.elsevier.com/as/authorization...302158 msHTTP/1.1cloudflare
3https://www.cell.com/callback?red_uri=%2...302434 msHTTP/1.1cloudflare
4https://www.cell.com/302120 msHTTP/1.1cloudflare
5https://id.elsevier.com/as/authorization...302159 msHTTP/1.1cloudflare
6https://www.cell.com/callback?red_uri=%2...302417 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

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 41 ms lookup
PASS
2 A records, 41 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.66.0.112, 162.159.140.114
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns1.reedelsevier.com, ns3.reedelsevier.com, ns2.reedelsevier.com
Info::
1 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: 41 ms
Got: 41 ms
A172.66.0.112, 162.159.140.114
AAAA
CNAME
NSns1.reedelsevier.com, ns3.reedelsevier.com, ns2.reedelsevier.com
MX
10 cell-com.mail.protection.outlook.com
TXT
onetrust-domain-verification=703cad9baa55456ab0ed05c40cd00445
atlassian-domain-verification=2ckcJUmjEfh8TAauQPrWb9eLXpM1UyNHPk+6SmzC3X0tqBzJKZ...
miro-verification=edd5a54fc20add96505c5c718975977b28f370a9
ZOOM_verify_W4AuTEx9ROGD4kK_ePkcBA
SPF v=spf1 include:spf.protection.outlook.com include:519224.spf06.hubspotemail.net ...
pendo-domain-verification=f1e205fa-06f4-4a13-a73a-3e0f82e7f104
NNaG7DvrFpIe+hqV6axdB2BDDbaBT5OUuQ8dl5fRyvYVFnuNb39lU9OREInFizJw5B3FZ91RQjKgRLOa...
MS=ms13784580
adobe-idp-site-verification=fd4fae74b683e6e22ef9b491871ae9f0faf7856b8a8588d267e2...
onetrust-domain-verification=509af418dcce43c5a6330cd2128ee529
CAALookup not available with standard resolver
Resolved in 41 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
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1485 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references 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

robots.txt 200 OK
Size 1485 B Sitemaps referenced 2 User-agents PerplexityBot, AI2Bot, Bytespider, cohere-training-data-crawler, cohere-ai, Diffbot, meta-externalagent, *, LinkedInBot, GPTBot, CCBot, ClaudeBot, iAskBot/1.0, MistralAI-User, TimpiBot, Twitterbot, ChatGPT-User, Google-Extended, omgili, Amazonbot, anthropic-ai, YouBot Blocking No — crawling allowed
Sitemap: https://www.cell.com/sitemap-index-1.txt
Sitemap: https://www.cell.com/custom_pages.gz

User-agent: *
Disallow: /action
Disallow: /help
Disallow: /search
Disallow: /feedback
Disallow: /rss
Disallow: /action/clickThrough
Disallow: /action/showLogin
Disallow: /page/account-confirmation-thanks
Disallow: /media
Disallow: /medical-research
Disallow: /servlet/linkout
Disallow: /na101/
Disallow: /na101v1/
Disallow: /na102/
Disallow: /doi/mlt/
Disallow: /cms/attachment/92c526c4-ef1f-4065-b12b-ca4ae0f3e84f/gr1*
Disallow: /personalize/addFavoritePublication
Disallow: /pb/widgets/*
Allow: /action/showJournal
Allow: /action/showXml
Allow: /series
Allow: /isbn
Allow: /doi/book
Allow: /.well-known/*

User-agent: Twitterbot
Allow: /

User-agent: LinkedInBot
Allow: /

User-agent: GPTBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: AI2Bot
Disallow: /

User-agent: Amazonbot
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: cohere-training-data-crawler
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: iAskBot/1.0
Disallow: /

User-agent: meta-externalagent
Disallow: /

User-agent: MistralAI-User
Disallow: /

User-agent: omgili
Disallow: /

User-agent: TimpiBot
Disallow: /

User-agent: YouBot
Disallow: /

Crawl-delay: 1

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

302https://www.cell.com/
200https://cell.com/

Preferred variant: non-www

HTTP → HTTPS

301http://cell.com/ https://cell.com/

Consistent

A+
Domain Intelligence
cell.com — via SafeNames Ltd., 32 years, 1 months old, hosted on Cloudflare
PASS
cell.com — via SafeNames Ltd., 32 years, 1 months old, hosted on Cloudflare
Info::
Domain registered until Aug 21, 2031 (5 years, 4 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

1863 days

August 21, 2031

SSL certificate

80 days

Issued by Google Trust Services

Domain age

32 years, 1 months

Registered August 22, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

162.159.140.114

Registrar

SafeNames Ltd.

Unlocked 3 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 August 22, 1994 (32 years, 1 months ago)
Expires August 21, 2031 (5 years, 4 months)
Last Updated October 14, 2025
Name Servers ns1.reedelsevier.com, ns2.reedelsevier.com, ns3.reedelsevier.com
DNSSEC Not enabled
Hosting
IP Address 162.159.140.114
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.1s)

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

Connection waterfall

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

Send Feedback