SurfaceMap › a › angouleme.fr

angouleme.fr

Checked 2026-10-22 01:34 UTC · first added 2026-10-21
✗Problems found Score 56 of 100

Domain & DNS

fail

23 passed 4 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA iDNSSEC 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

Recent checks

✗

Full report

Domain & DNS report for angouleme.fr ›

Mail

fail

21 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
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: postix.angouleme.fr, idmx03.idline.fr, idmx04.idline.fr
    #11
  • !
    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:dmarc@idline.fr (needs angouleme.fr._report._dmarc.idline.fr). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 angouleme.fr ›