Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityrobots.txt present, sitemap with 0 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
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Sitemap: https://www.worldscientific.com/sitemap-index-1.txt
User-agent: *
Disallow: /action
Disallow: /help
Disallow: /search
Disallow: /feedback
Disallow: /rss
Disallow: /page/account-confirmation-thanks
Disallow: /media
Disallow: /medical-research
Disallow: /servlet/linkout
Disallow: /na101/
Disallow: /na101v1/
Disallow: /na102/
Disallow: /doi/mlt/
Disallow: /topic
Disallow: /author/
Disallow: /doi/metrics/
Disallow: /authored-by/
Disallow: /history/
Allow: /action/showJournal
Allow: /action/showPublications
Allow: /action/showXml
Allow: /action/showTopic
Allow: /action/showBook
Allow: /action/showCoverImage
User-agent: facebookexternalhit
User-agent: LinkedInBot
User-agent: Twitterbot
Allow: /
User-agent: GPTBot
Disallow: /
Crawl-delay: 1
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations68 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
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 Records3 A records, 7 ms lookupPASS
| A | 104.26.3.222, 104.26.2.222, 172.67.69.44 |
| AAAA | 2606:4700:20::681a:3de, 2606:4700:20::ac43:452c, 2606:4700:20::681a:2de |
| CNAME | — |
| NS | amber.ns.cloudflare.com, andy.ns.cloudflare.com |
| MX | 20 mail.wspc.com.sg |
| TXT | UK-federation-domain-verification=acb4106707596389a2bb5cf6f4353934 brevo-code:7285b12f5b19761999a515c67b7a7853 facebook-domain-verification=bhub1p8ltumtssuqet9ego57dv0lnd google-site-verification=l4Ic3ABtKMpws4dbiYLxJiJH4-nCpG3ly4ovSGlUsrE r7s94nl3b8ts9kgwgp8pyngzrnlv3w80 SPF v=spf1 a:mail.wspc.com.sg a:mail7.wspc.com a:o25.em.wspc.com.sg a:intranet.wspc.... verify_9ea900efe1cf2c3e13b1eef5393f5b85 |
| 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.
ARedirect Chain1 redirect(s), 657 ms totalPASS
https://worldscientific.com
628 ms · HTTP/1.1
https://www.worldscientific.com/
29 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://worldscientific.com | 301 | 628 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.worldscientific.com/ | 403 | 29 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Domain Intelligenceworldscientific.com — via Cloudflare, Inc., 28 years, 9 months oldPASS
95 days
November 20, 2026
68 days
Issued by Google Trust Services
28 years, 9 months
Registered November 21, 1997
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:20::681a:3de
Cloudflare, Inc.
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