SurfaceMap › r › red-by-sfr.fr

red-by-sfr.fr

Checked 2026-10-22 04:58 UTC · first added 2026-10-21

✗Problems found Score 55 of 100

Domain & DNS

fail

7 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !DNSSEC

Problems

✗

No nameserver responds

Nameservers · None of the nameserver addresses answered: ns1pub.sfr.fr (92.90.26.129): read udp 46.225.38.91:52015->92.90.26.129:53: i/o timeout; ns2pub.sfr.fr (92.90.26.145): read udp 46.225.38.91:36695->92.90.26.145:53: i/o timeout.

#14
!

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 red-by-sfr.fr ›

Mail

fail

12 passed 2 warn 2 failed

Areas

✓SPF ✗DMARC ✗DKIM !DNSSEC !MX 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
✗

No DKIM keys published

DKIM · _domainkey.red-by-sfr.fr does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.

#7
!

Not enabled

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

#8
!

No MX records

MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").

#9

Recent checks

✗

Full report

Mail report for red-by-sfr.fr ›