SurfaceMap › m › melenchon.fr

melenchon.fr

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

Domain & DNS

warn

24 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: jessica.ns.cloudflare.com: "2026.10.2"; roan.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #17
  • !
    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 melenchon.fr ›

Mail

fail

18 passed 5 warn 2 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
  • ✗
    No DKIM keys published
    DKIM · _domainkey.melenchon.fr does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Ends with ?all (neutral)
    SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #3
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    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:site@lafranceinsoumise.fr (needs melenchon.fr._report._dmarc.lafranceinsoumise.fr). Ask the report provider to publish the record, or check the address.
    #29
  • !
    Reverse DNS does not match
    MX · The PTR name of these addresses does not resolve back to the same address: 2001:4b98:dc4:8::216 -> spool7.mail.gandi.net, 2001:4b98:dc4:8::215 -> spool6.mail.gandi.net, 2001:4b98:dc4:8::217 -> spool8.mail.gandi.net.
    #30
  • !
    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 melenchon.fr ›