SurfaceMap › l › lameridionale.fr

lameridionale.fr

Checked 2026-10-22 03:43 UTC · first added 2026-10-21
✗Problems found Score 72 of 100

Domain & DNS

warn

27 passed 2 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers !SOA ✓DNSSEC !Records

Problems

  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 1h, expire 1000h, negative TTL 1m.
    #23
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: MX (0s), NS (0s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 0s; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for lameridionale.fr ›

Mail

fail

26 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
  • !
    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: mail (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Policy in testing mode
    TLS · With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.
    #33
  • !
    MX hosts missing from policy
    TLS · These MX hosts are not listed in the MTA-STS policy (mx: mx02.cloud.vadesecure.com, mx03.cloud.vadesecure.com, mx04.cloud.vadesecure.com, mx01.cloud.vadesecure.com): cmacgmgroup.mail.protection.outlook.com. This will break delivery once the policy is enforced.
    #34

Recent checks

✗

Full report

Mail report for lameridionale.fr ›