Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FRedirect ChainAction4 redirect(s), 1076 ms totalFIX
https://scopus.com
34 ms · HTTP/1.1
https://scopus.com/pages/home
120 ms · HTTP/1.1
https://www.scopus.com/pages/home
184 ms · HTTP/1.1
https://id.elsevier.com/as/authorization...
200 ms · HTTP/1.1
https://www.scopus.com/pages/callback/ur...
539 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://scopus.com | 307 | 34 ms | HTTP/1.1 | cloudflare |
| 2 | https://scopus.com/pages/home | 303 | 120 ms | HTTP/1.1 | cloudflare |
| 3 | https://www.scopus.com/pages/home | 307 | 184 ms | HTTP/1.1 | cloudflare |
| 4 | https://id.elsevier.com/as/authorization... | 302 | 200 ms | HTTP/1.1 | cloudflare |
| 5 | https://www.scopus.com/pages/callback/ur... | 307 | 539 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
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
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.
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations33 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
BCDN & DeliveryCloudflareREVIEW
A+DNS Records2 A records, 46 ms lookupPASS
| A | 203.22.241.5, 203.22.241.4 |
| AAAA | — |
| CNAME | — |
| NS | ns-206.awsdns-25.com, ns-1175.awsdns-18.org, ns-731.awsdns-27.net, ns-2035.awsdns-62.co.uk |
| MX | 10 scopus-com.mail.protection.outlook.com |
| TXT | L/UxhbgVDOBxucQ5zNS9tc9l5PKU3K/Z9IDSYZg7smiUFtM3O7xUZPE9Mt+w8T+n3DrU1ikRYsne8rq7... _acme-challenge.components.scopus.com TXT vCGXWAlC04HR9DGlCEf0nj8nSRb58L0NYTNQb5... amazonses:pcI09CFAg6HnK1TcO/T+SaqgTp1pooaFG+6cJ+r0pZ0= SPF v=spf1 ip4:63.32.228.194 ip4:99.80.120.176 ip4:23.106.239.17 include:rnmk.com in... 3710d7a1-2caf-4372-91d4-3aad2abb51eb _globalsign-domain-verification=jPzOaV8oCE0rGIIJRrEvWVqv2JfT_NmebX8H4DRpid MS=ms34950440 _globalsign-domain-verification=r6QOLISmLUkMTZdcNGAb56lfuelddXTqpT9Z7h72pp qJySvCLPamDf84CVmEwqQ1v2v3mThpak697rbmiS//zXJ8dq+s5I1uYaY+IS5HCYu+hC4cANEEDEXb0w... 6d80a56c-8656-44a3-b70a-22c0853c8b46 |
| 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.
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligencescopus.com — via SafeNames Ltd., 34 years, 5 months old, hosted on CloudflarePASS
1733 days
May 16, 2031
33 days
Issued by Google Trust Services
34 years, 5 months
Registered May 15, 1992
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS209242
203.22.241.5
SafeNames Ltd.
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