SurfaceMap › s › sfr.fr

sfr.fr

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

Domain & DNS

fail

18 passed 4 warn 2 failed

Areas

!Registration !Delegation ✗Nameservers iSOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1pub.sfr.fr (92.90.26.129): read udp 46.225.38.91:35788->92.90.26.129:53: i/o timeout.
    #14
  • ✗
    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: ns2pub.sfr.fr (92.90.26.145): read tcp 46.225.38.91:50556->92.90.26.145:53: read: connection reset by peer.
    #19
  • !
    Expires in 27 days
    Registration · The registration expires on 2026-11-18. Make sure it is renewed.
    #3
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 92.90.26.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    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 sfr.fr ›

Mail

warn

24 passed 5 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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: smtp-in.sfr.fr
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mx (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 sfr.fr ›