Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain2 redirect(s), 382 ms totalREVIEW
https://sncf.com
90 ms · HTTP/1.1
https://www.sncf.com:443/
146 ms · HTTP/1.1
https://www.groupe-sncf.com:443/
147 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://sncf.com | 301 | 90 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.sncf.com:443/ | 301 | 146 ms | HTTP/1.1 | awselb/2.0 |
| 3 | https://www.groupe-sncf.com:443/ | 403 | 147 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
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 & Recommendations183 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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 Records2 A records, 53 ms lookupPASS
| A | 99.83.160.166, 75.2.83.188 |
| AAAA | — |
| CNAME | — |
| NS | ns-483.awsdns-60.com, ns-2003.awsdns-58.co.uk, ns-627.awsdns-14.net, ns-1446.awsdns-52.org |
| MX | 10 mxa-00363202.gslb.pphosted.com 10 mxb-00363202.gslb.pphosted.com |
| TXT | QuoVadis=847b49f2-c52e-46d5-ab05-347b47c14ee9 c1mr9w7pc74b38wy0xtcj86z0xfdc36w content.idcab=722dfc866e7b9d3ce54e655871ed2631 QuoVadis=25e612c2-e8b6-4411-9494-1fca9c386580 QuoVadis=4e155450-c1bf-492f-bcfe-44188b0aed11 _ksonqb9h22mv3vjei1lfwz2i4nh32qh facebook-domain-verification=127ugsc6ryh3k2fnfbey7pe4s3la7h SPF v=spf1 include:spf.sncf.fr include:_spf.prod.vsct.fr include:_spf.dev.vsct.fr -a... MS=ms87452117 _civzp9xthpuo7s3drc1nv7yn8739vvg QuoVadis=6f062c66-53ca-4d56-a4be-0e3f8dd65b26 content.pap=b8e72c8dd7f1d54b1752e202f1c22337 QuoVadis=510f6335-dd3e-4c84-8557-e8d0faeaf463 QuoVadis=b5ed5e02-4394-49d2-aff7-b722680eda1b 2639e13d-563a-41aa-997e-9f8b66ea6fb0 4yhwwgtr4t8qwf423z12dgrk5n65t6xt |
| 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 Intelligencesncf.com — via SafeBrands SAS, 29 years, 11 months old, hosted on AWSPASS
91 days
October 13, 2026
183 days
Issued by Amazon
29 years, 11 months
Registered October 14, 1996
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
75.2.83.188
SafeBrands SAS
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