SurfaceMap › l › lefigaro.fr

lefigaro.fr

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

Domain & DNS

warn

22 passed 4 warn 0 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-194.akam.net: "41824.5"; a16-64.akam.net: "48878.26"; a16-64.akam.net: "48878.32"; a2-67.akam.net: "48878.33"; a2-67.akam.net: "48878.30"; a3-64.akam.net: "41824.7"; a5-67.akam.net: "41824.6"; a5-67.akam.net: "41824.10"; a8-65.akam.net: "48878.27"; a8-65.akam.net: "48878.33". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 4d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 8h, retry 2h, expire 14d, negative TTL 4d.
    #23
  • !
    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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (20s), AAAA (20s). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for lefigaro.fr ›

Mail

fail

22 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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: rsmtp1.le-figaro.com, rsmtp2.le-figaro.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 lefigaro.fr ›