sncf-connect.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: blue.foundationdns.com: "2026.10.0"; blue.foundationdns.net: "2026.10.0"; blue.foundationdns.org: "2026.10.0". Hide or replace the version string.

SOA · The nameservers serve different versions of the zone: 1 on ns-1020.awsdns-63.net (205.251.195.252), ns-1020.awsdns-63.net (2600:9000:5303:fc00::1), ns-1251.awsdns-28.org (205.251.196.227), ns-1251.awsdns-28.org (2600:9000:5304:e300::1), ns-1574.awsdns-04.co.uk (205.251.198.38), ns-1574.awsdns-04.co.uk (2600:9000:5306:2600::1), ns-366.awsdns-45.com (205.251.193.110), ns-366.awsdns-45.com (2600:9000:5301:6e00::1); 2416939118 on blue.foundationdns.com (162.159.60.1), blue.foundationdns.com (172.64.40.1), blue.foundationdns.com (108.162.198.1), blue.foundationdns.com (2606:4700:57::6ca2:c601), blue.foundationdns.com (2a06:98c1:56::ac40:2801), blue.foundationdns.com (2803:f800:52::a29f:3c01), blue.foundationdns.net (108.162.198.31), blue.foundationdns.net (162.159.60.31), blue.foundationdns.net (172.64.40.31), blue.foundationdns.net (2a06:98c1:56::ac40:281f), blue.foundationdns.net (2803:f800:52::a29f:3c1f), blue.foundationdns.net (2606:4700:57::6ca2:c61f), blue.foundationdns.org (108.162.198.61), blue.foundationdns.org (162.159.60.61), blue.foundationdns.org (172.64.40.61), blue.foundationdns.org (2a06:98c1:56::ac40:283d), blue.foundationdns.org (2803:f800:52::a29f:3c3d), blue.foundationdns.org (2606:4700:57::6ca2:c63d). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

MX · The following MX hosts could not be resolved to IPv6 addresses: inbound-smtp.eu-west-3.amazonaws.com

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.