SurfaceMap › v › valdoise.fr

valdoise.fr

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

Domain & DNS

fail

22 passed 1 warn 2 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns01.eolas.fr (178.237.104.1): SERVFAIL, authoritative=false; ns01.eolas.fr (2a00:4280:100:d00:33ab:7bbd:9949:389): SERVFAIL, authoritative=false; ns02.eolas.fr (178.237.108.1): SERVFAIL, authoritative=false; ns02.eolas.fr (2a00:4280:100:e00:833b:4c9:5cf8:8ea0): SERVFAIL, authoritative=false; ns03.eolas-dns.eu (51.83.201.211): SERVFAIL, authoritative=false; ns03.eolas-dns.eu (2001:41d0:a800:801:f592:7c6d:e501:b473): SERVFAIL, 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: ns01.eolas.fr (178.237.104.1): ; ns01.eolas.fr (2a00:4280:100:d00:33ab:7bbd:9949:389): ; ns02.eolas.fr (178.237.108.1): ; ns02.eolas.fr (2a00:4280:100:e00:833b:4c9:5cf8:8ea0): ; ns03.eolas-dns.eu (51.83.201.211): ; ns03.eolas-dns.eu (2001:41d0:a800:801:f592:7c6d:e501:b473): .
    #19
  • !
    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 valdoise.fr ›

Mail

fail

22 passed 4 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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    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: selector1 (1024 bits), s2 (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 valdoise.fr ›