SurfaceMap › f › fondationcustodia.fr

fondationcustodia.fr

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

Domain & DNS

fail

20 passed 4 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: ns1.asimonetworks.com (2a0d:9c80:13::201): read udp [2a01:4f8:1c1c:eebf::1]:58596->[2a0d:9c80:13::201]:53: i/o timeout.
    #14
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.asimonetworks.com: "PowerDNS Authoritative Server 4.0.0-alpha2"; ns2.asimonetworks.nl: "PowerDNS Authoritative Server 4.0.0-alpha2". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · retry 169h should be shorter than refresh 2h; expire 5m is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 5m must be longer than refresh + retry. Current values: refresh 2h, retry 169h, expire 5m, negative TTL 1h.
    #23
  • !
    Invalid contact address
    SOA · The SOA RNAME "2022032400" is not a valid mailbox (expected e.g. hostmaster.example.com).
    #25
  • !
    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 fondationcustodia.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
  • !
    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 fondationcustodia.fr ›