SurfaceMap › m › mpi.nl

mpi.nl

Checked 2026-10-21 21:23 UTC · first added 2026-10-21
✗Problems found Score 33 of 100

Domain & DNS

fail

19 passed 4 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC !Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1.mpi.nl (2001:610:180:2:250:56ff:feba:1771): read udp [2a01:4f8:1c1c:eebf::1]:56955->[2001:610:180:2:250:56ff:feba:1771]:53: i/o timeout; ns2.mpi.nl (2001:610:180:2:250:56ff:feba:4ae9): read udp [2a01:4f8:1c1c:eebf::1]:58508->[2001:610:180:2:250:56ff:feba:4ae9]:53: i/o timeout.
    #14
  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns1.mpi.nl (192.87.79.168): 443 records; ns2.mpi.nl (192.87.79.169): 443 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 192.87.79.0/24; all IPv6 addresses are in 2001:610:180::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.mpi.nl: "9.20.26"; ns2.mpi.nl: "9.20.26". 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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 1m; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for mpi.nl ›

Mail

fail

16 passed 5 warn 2 failed

Areas

✓SPF ✗DMARC ✗DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No DKIM keys published
    DKIM · _domainkey.mpi.nl does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    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: a1232.mx.srv.dfn.de, b1232.mx.srv.dfn.de, c1232.mx.srv.dfn.de, lux05.mpi.nl, lux06.mpi.nl
    #11
  • !
    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
  • !
    Not configured
    TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35
  • !
    Not all MX hosts use DANE
    TLS · These MX hosts publish no TLSA records, so mail to them is not protected by DANE: lux05.mpi.nl, lux06.mpi.nl.
    #36

Recent checks

✗

Full report

Mail report for mpi.nl ›