mpi.nl

Checked 21 October 2026, 21:23 UTC · via 8.8.8.8
✗Problems found
19 passed 4 warnings 2 failed 6 info

Registration

info

.nl country-code · SURF B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
SURF B.V.
Registered
3 March 1987
Last changed
5 January 2026
Status
active
Registry nameservers
ns1.mpi.nl, ns2.mpi.nl
RDAP server
https://rdap.sidn.nl/

Checks

  • i
    .nl is a country-code TLD (ccTLD)
    Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.
    #1
  • ✓ TLD delegated and signed #2
    .nl is delegated in the root zone and DNSSEC-signed.
  • i
    Expiry date not published
    The registry does not publish the expiry date in RDAP. Check it with your registrar.
    #3
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.mpi.nl, ns2.mpi.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.mpi.nl, ns2.mpi.nl
NS in the zone
ns1.mpi.nl, ns2.mpi.nl
NameserverAddressesNetwork (AS)Glue
ns1.mpi.nl192.87.79.168 2001:610:180:2:250:56ff:feba:1771AS1103 SURFNET-NL - SURF B.V., NL AS1103 SURFNET-NL - SURF B.V., NL192.87.79.168 2001:610:180:2:250:56ff:feba:1771
ns2.mpi.nl192.87.79.169 2001:610:180:2:250:56ff:feba:4ae9AS1103 SURFNET-NL - SURF B.V., NL AS1103 SURFNET-NL - SURF B.V., NL192.87.79.169 2001:610:180:2:250:56ff:feba:4ae9

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.mpi.nl, ns2.mpi.nl.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.mpi.nl, ns2.mpi.nl.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    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
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS1103 (SURFNET-NL - SURF B.V., NL): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .nl
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

2 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.mpi.nl 192.87.79.168NOERROR, 14 ms, authoritativenoyes / yesALLOWED (443 records)9.20.26
ns1.mpi.nl 2001:610:180:2:250:56ff:feba:1771no responsenono / no--
ns2.mpi.nl 192.87.79.169NOERROR, 14 ms, authoritativenoyes / yesALLOWED (443 records)9.20.26
ns2.mpi.nl 2001:610:180:2:250:56ff:feba:4ae9no responsenono / no--

Checks

  • ✗
    Nameservers not responding
    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
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    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
  • ✗
    Zone transfer allowed
    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
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026091702 · primary ns1.mpi.nl

Found

Primary (MNAME)
ns1.mpi.nl
Contact (RNAME)
hostmaster.mpi.nl
Serial
2026091702
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.mpi.nl (192.87.79.168)2026091702
ns2.mpi.nl (192.87.79.169)2026091702

Checks

  • ✓ Serial 2026091702 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.mpi.nl is one of the listed nameservers.
  • ✓ Contact hostmaster@mpi.nl #25
    The SOA RNAME hostmaster.mpi.nl means hostmaster@mpi.nl.
  • ✓ Date-based serial #26
    The serial 2026091702 follows the YYYYMMDDnn convention (2026-09-17).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

warn

22 records at the apex

Found

Read from
192.87.79.168:53
TypeValueTTL
SOAns1.mpi.nl. hostmaster.mpi.nl. 2026091702 10800 3600 604800 8640060
NSns1.mpi.nl.60
NSns2.mpi.nl.60
A192.87.79.5160
MX75 lux06.mpi.nl.60
MX10 b1232.mx.srv.dfn.de.60
MX10 c1232.mx.srv.dfn.de.60
MX65 lux05.mpi.nl.60
MX10 a1232.mx.srv.dfn.de.60
TXT"QuoVadis=6a551ac8-1537-4a2f-97f8-98603d38be23"3600
TXT"apple-domain-verification=KsBvNwQ0UsWhjlUb"3600
TXT"HARICA-jv59Rm8GU3Wo0yErkw6"3600
TXT"MS=C8943973DAD96F057331DE79AD737FE57746F3B9"3600
TXT"adobe-idp-site-verification=85ccdc5eedcea3d2bc75d2752fbbf51cb6e651683df1e839ffb7691b85749423"3600
TXT"v=spf1 include:spf.gwdg.de include:spf.de.umantis.com include:return-cname.emailsys.net ~all"3600
TXT"MS=ms12210383"3600
CAA0 issue "pki.dfn.de"60
CAA0 issue "letsencrypt.org"60
CAA0 issue "telesec.de"60
CAA0 issue "sectigo.com"60
CAA0 issue "harica.gr"60
CAA0 issuewild "harica.gr"60

Checks

  • !
    Very low TTLs
    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
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: pki.dfn.de, letsencrypt.org, telesec.de, sectigo.com, harica.gr.