SurfaceMap › c › creuse.fr

creuse.fr

Checked 2026-10-22 02:28 UTC · first added 2026-10-21
✗Problems found Score 78 of 100

Domain & DNS

ok

28 passed 0 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers ✓SOA ✓DNSSEC iRecords

Recent checks

✓

Full report

Domain & DNS report for creuse.fr ›

Mail

fail

23 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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: vade-mx-fr01.hornetsecurity.com, vade-mx-fr02.hornetsecurity.com, vade-mx-eu-fallback01.hornetsecurity.com, vade-mx-eu-fallback02.hornetsecurity.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (1024 bits), selector2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:rua+rce2af27d94d88293ecdf587d@dmarc.com (needs creuse.fr._report._dmarc.dmarc.com); mailto:dmarc-creuse@cg23.com (needs creuse.fr._report._dmarc.cg23.com). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 creuse.fr ›