SurfaceMap › s › sofcot.fr

sofcot.fr

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

Domain & DNS

fail

20 passed 3 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: sdns01.zzbind.com (2a02:28c0:0:ebe1::6f): read udp [2a01:4f8:1c1c:eebf::1]:58709->[2a02:28c0:0:ebe1::6f]:53: i/o timeout; sdns02.zzbind.com (2a02:28c0:0:ebe1::de): read udp [2a01:4f8:1c1c:eebf::1]:58897->[2a02:28c0:0:ebe1::de]:53: i/o timeout.
    #14
  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: sdns02.zzbind.com (46.19.24.222): 39 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 46.19.24.0/24; all IPv6 addresses are in 2a02:28c0::/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: sdns01.zzbind.com: "9.16.50-Debian"; sdns02.zzbind.com: "9.16.50-Debian". 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 sofcot.fr ›

Mail

fail

15 passed 8 warn 1 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    5 of 10 DNS lookups, with problems
    SPF · SPF record needs 5 DNS lookups (limit is 10). Problems found: include:outlook.office365.com does not exist or has no records.
    #2
  • !
    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 IP addresses
    MX · The following MX hosts could not be resolved to IP addresses: ms35182786.msv1.invalid
    #10
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: ms35182786.msv1.invalid
    #11
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1 void lookup
    SPF · 1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • !
    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 sofcot.fr ›