SurfaceMap › t › turbo.fr

turbo.fr

Checked 2026-10-22 05:32 UTC · first added 2026-10-21
✗Problems found Score 72 of 100

Domain & DNS

fail

20 passed 4 warn 1 failed

Areas

iRegistration ✗Delegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Nameserver names are CNAMEs
    Delegation · Nameserver names must not be aliases (RFC 2181 10.3): ns3.odiso.net -> ns1.odiso.net.
    #9
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns3.odiso.net. ns1.odiso.net, ns2.odiso.net, ns3.odiso.net report NS ns1.odiso.net ns2.odiso.net ns3.odiso.net.
    #7
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 89.248.211.0/24; all IPv6 addresses are in 2a0a:1580:2000::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.odiso.net: "PowerDNS Authoritative Server 4.8.5 (built Feb 7 2025 09:21:19 by root@localhost)"; ns2.odiso.net: "PowerDNS Authoritative Server 4.8.5 (built Feb 7 2025 09:21:19 by root@localhost)"; ns3.odiso.net: "PowerDNS Authoritative Server 4.8.5 (built Feb 7 2025 09:21:19 by root@localhost)". Hide or replace the version string.
    #17
  • !
    Not signed
    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.
    #27

Recent checks

✗

Full report

Domain & DNS report for turbo.fr ›

Mail

warn

27 passed 2 warn 0 failed

Areas

✓SPF ✓DMARC ✓DKIM !DNSSEC ✓MX !TLS iBIMI

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Not configured
    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.
    #32

Recent checks

!

Full report

Mail report for turbo.fr ›