SurfaceMap › l › lepartidegauche.fr

lepartidegauche.fr

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

Domain & DNS

fail

25 passed 2 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: dns1.lepartidegauche.fr (2001:41d0:12a:9c00::1): read udp [2a01:4f8:1c1c:eebf::1]:56921->[2001:41d0:12a:9c00::1]:53: i/o timeout; dns2.lepartidegauche.fr (2001:41d0:a:7c18::1): read udp [2a01:4f8:1c1c:eebf::1]:48082->[2001:41d0:a:7c18::1]:53: i/o timeout.
    #14
  • !
    Signatures expire soon
    DNSSEC · The earliest signature expires at 2026-10-25 03:10 UTC (in 71h0m0s). Check that automatic re-signing works.
    #30
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 5 iterations and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Recent checks

✗

Full report

Domain & DNS report for lepartidegauche.fr ›

Mail

fail

24 passed 5 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
  • !
    Signatures expire in 71h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-25T03:10:27Z (in 71h0m0s). Check that re-signing works.
    #21
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), k1 (1024 bits), s1 (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 2001:41d0:12a:9c00::16 (mx0.lepartidegauche.fr). Ask your hosting provider to set one.
    #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
  • !
    Not configured
    TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35

Recent checks

✗

Full report

Mail report for lepartidegauche.fr ›