SurfaceMap › m › merysuroise.fr

merysuroise.fr

Checked 2026-10-22 04:20 UTC · first added 2026-10-21
✗Problems found Score 68 of 100

Domain & DNS

fail

24 passed 1 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns2.safebrands.eu (194.50.187.18): read udp 46.225.38.91:60346->194.50.187.18:53: i/o timeout; ns2.safebrands.eu (2a04:2b00:14dd::18): read udp [2a01:4f8:1c1c:eebf::1]:34129->[2a04:2b00:14dd::18]:53: i/o timeout; ns5.safebrands.tech (194.50.187.21): read udp 46.225.38.91:50999->194.50.187.21:53: i/o timeout; ns5.safebrands.tech (2a04:2b00:14dd::21): read udp [2a01:4f8:1c1c:eebf::1]:36518->[2a04:2b00:14dd::21]:53: i/o timeout.
    #14
  • !
    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 merysuroise.fr ›

Mail

fail

23 passed 3 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
  • !
    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 merysuroise.fr ›