SurfaceMap › p › poitiers.fr

poitiers.fr

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

Domain & DNS

fail

19 passed 5 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    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: pdns1.idline.fr (109.239.119.203): dial tcp 109.239.119.203:53: i/o timeout; pdns2.idline.fr (109.239.119.209): dial tcp 109.239.119.209:53: i/o timeout.
    #19
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: pdns1.idline.fr (glue 109.239.119.203, 109.239.119.209, zone 109.239.119.203); pdns2.idline.fr (glue 109.239.119.203, 109.239.119.209, zone 109.239.119.209). Update the glue at your registrar.
    #8
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 109.239.119.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: pdns1.idline.fr: "PowerDNS Authoritative Server 4.9.3 (built Dec 16 2024 08:52:59 by root@localhost)"; pdns2.idline.fr: "PowerDNS Authoritative Server 4.9.3 (built Dec 16 2024 08:52:59 by root@localhost)". 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 poitiers.fr ›

Mail

fail

20 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
  • !
    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
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (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 poitiers.fr ›