Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction3 redirect(s), 455 ms totalFIX
https://ssrn.com
220 ms · HTTP/1.1
https://www.ssrn.com/
136 ms · HTTP/1.1
https://www.ssrn.com/index.cfm/en/
29 ms · HTTP/1.1
https://www.ssrn.com:443/ssrn/
70 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://ssrn.com | 301 | 220 ms | HTTP/1.1 | AmazonS3 |
| 2 | https://www.ssrn.com/ | 302 | 136 ms | HTTP/1.1 | cloudflare |
| 3 | https://www.ssrn.com/index.cfm/en/ | 302 | 29 ms | HTTP/1.1 | cloudflare |
| 4 | https://www.ssrn.com:443/ssrn/ | 200 | 70 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
BCrawlabilityrobots.txt present, no sitemapREVIEW
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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: *
Crawl-Delay: 5
Disallow: /admin/
Disallow: /tasks/
Disallow: /config/
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations326 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
A+DNS Records4 A records, 34 ms lookupPASS
| A | 99.84.9.85, 99.84.9.102, 99.84.9.127, 99.84.9.118 |
| AAAA | — |
| CNAME | — |
| NS | ns-1867.awsdns-41.co.uk, ns-882.awsdns-46.net, ns-489.awsdns-61.com, ns-1049.awsdns-03.org |
| MX | 10 ssrn-com.mail.protection.outlook.com |
| TXT | atlassian-domain-verification=2ckcJUmjEfh8TAauQPrWb9eLXpM1UyNHPk+6SmzC3X0tqBzJKZ... onetrust-domain-verification=b723e6161d8a486d943dcbe590623d20 smartsheet-site-validation=UgmlEIYa0v1b7YNk8Fzd7HoLd8QYTXKS onetrust-domain-verification=acf02e01907848c79ce2b5003bbdec47 pendo-domain-verification=055d7ffc-8cc0-43c9-97ac-d4ee5c925648 40ea9a76-302a-4c8e-9d61-f82fdc151549 google-site-verification=Dh-t4sb6GyIWxT2euRXP0GsuKfj2vmJnfIk6RpyHrx0 MS=ms53079298 SPF v=spf1 mx mx:ssrn.com include:spf.protection.outlook.com include:spf.clearslide.... adobe-idp-site-verification=fd4fae74b683e6e22ef9b491871ae9f0faf7856b8a8588d267e2... google-site-verification=Ttz4nMpj8cnDDgDnRlx4rdQAzp8hpK8hhtTmj38TzFU adobe-sign-verification=aaa14179513de8c14b3d3e09640d5a26| google-site-verification=559E5yUgcdxIlCP732UjARKiFeuYRpgznGoFOTwTH38 |
| 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.
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencessrn.com — via SafeNames Ltd., 30 years, 7 months old, hosted on AWSPASS
216 days
February 16, 2027
326 days
Issued by Amazon
30 years, 7 months
Registered February 15, 1996
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
99.84.9.102
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