SurfaceMap › g › genopole.fr

genopole.fr

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

Domain & DNS

fail

23 passed 3 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: seine.genopole.fr (193.51.128.129): REFUSED, authoritative=false; seine.genopole.fr (2001:660:3020:20:0:50:5689:1015): REFUSED, authoritative=false.
    #15
  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: seine.genopole.fr (193.51.128.129): ; seine.genopole.fr (2001:660:3020:20:0:50:5689:1015): .
    #19
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: seine.genopole.fr (glue 193.51.128.129, zone 193.51.128.129, 2001:660:3020:20:0:50:5689:1015); volga.genopole.fr (glue 193.51.128.163, zone 193.51.128.163, 2001:660:3020:667:0:50:5689:28c7). Update the glue at your registrar.
    #8
  • !
    Unusual SOA timers
    SOA · expire 12h is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 6h, retry 30m, expire 12h, negative TTL 1h.
    #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

Recent checks

✗

Full report

Domain & DNS report for genopole.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
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Key in test mode
    DKIM · These keys have t=y, so receivers treat DKIM failures as a test: mail. Remove t=y once DKIM works.
    #24
  • !
    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 genopole.fr ›