SurfaceMap › s › sb-roscoff.fr

sb-roscoff.fr

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

Domain & DNS

fail

18 passed 2 warn 5 failed

Areas

iRegistration ✗Delegation ✗Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • ✗
    Nameserver names don't resolve
    Delegation · These nameservers have no A or AAAA record, so they can't be reached (lame delegation): sbr.sb-roscoff.fr.
    #9
  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1.sb-roscoff.fr (192.168.1.130): read udp 46.225.38.91:57565->192.168.1.130:53: i/o timeout.
    #14
  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns4.cnrs.fr (195.220.197.11): REFUSED, authoritative=false; ns4.cnrs.fr (2001:660:500a:2210::11): REFUSED, authoritative=false.
    #15
  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns4.cnrs.fr (195.220.197.11): ; ns4.cnrs.fr (2001:660:500a:2210::11): .
    #19
  • ✗
    Private nameserver addresses
    Nameservers · These nameserver addresses can't be reached from the internet: ns1.sb-roscoff.fr (192.168.1.130).
    #21
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns4.cnrs.fr, resone.univ-rennes1.fr, sbr.sb-roscoff.fr; only in the zone: ns1.sb-roscoff.fr, resone.univ-rennes1.fr.sb-roscoff.fr. resone.univ-rennes1.fr, resone.univ-rennes1.fr.sb-roscoff.fr report NS ns1.sb-roscoff.fr resone.univ-rennes1.fr.sb-roscoff.fr.
    #7
  • !
    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 sb-roscoff.fr ›

Mail

warn

22 passed 5 warn 0 failed

Areas

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

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mx1.relay.renater.fr, mx2.relay.renater.fr
    #11
  • !
    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 sb-roscoff.fr ›