milieudefensie.nl

Checked 21 October 2026, 21:23 UTC · via 8.8.8.8
!Passed with warnings
25 passed 1 warning 0 failed 7 info

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/milieudefensie.nl returned HTTP 429

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
    Could not be checked
    The RDAP lookup failed, so this could not be checked: https://rdap.sidn.nl/domain/milieudefensie.nl returned HTTP 429
    #3

Delegation

info

ns1.milieudefensie.nl, ns2.milieudefensie.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.milieudefensie.nl, ns2.milieudefensie.nl
NS in the zone
ns1.milieudefensie.nl, ns2.milieudefensie.nl
NameserverAddressesNetwork (AS)Glue
ns1.milieudefensie.nl37.97.129.170 2a01:7c8:aabc:35c:5054:ff:fee7:24bAS20857 TRANSIP-AS - Signet B.V., NL AS20857 TRANSIP-AS - Signet B.V., NL37.97.129.170 2a01:7c8:aabc:35c:5054:ff:fee7:24b
ns2.milieudefensie.nl195.114.30.216AS206176 greenedge - GreenEdge B.V., NL195.114.30.216

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.milieudefensie.nl, ns2.milieudefensie.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.milieudefensie.nl, ns2.milieudefensie.nl.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 1 IPv6 /48.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS206176 (greenedge - GreenEdge B.V., NL): 1 address; AS20857 (TRANSIP-AS - Signet B.V., NL): 2 addresses.
  • 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns2.milieudefensie.nl.
    #13

Nameservers

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.milieudefensie.nl 37.97.129.170NOERROR, 11 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.6-Ubuntu
ns1.milieudefensie.nl 2a01:7c8:aabc:35c:5054:ff:fee7:24bNOERROR, 11 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.6-Ubuntu
ns2.milieudefensie.nl 195.114.30.216NOERROR, 10 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.6-Ubuntu

Checks

  • ✓ All respond #14
    All 3 nameserver addresses answered.
  • ✓ 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.milieudefensie.nl: "9.18.39-0ubuntu0.22.04.6-Ubuntu"; ns2.milieudefensie.nl: "9.18.39-0ubuntu0.22.04.6-Ubuntu". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ 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 2026101811 · primary ns1.milieudefensie.nl

Found

Primary (MNAME)
ns1.milieudefensie.nl
Contact (RNAME)
hostmaster.milieudefensie.nl
Serial
2026101811
Refresh / retry
3600 s / 800 s
Expire
2419200 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.milieudefensie.nl (37.97.129.170)2026101811
ns1.milieudefensie.nl (2a01:7c8:aabc:35c:5054:ff:fee7:24b)2026101811
ns2.milieudefensie.nl (195.114.30.216)2026101811

Checks

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

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
18 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
31537ECDSAP256SHA256 (13)SHA256 2370C8EEDC56360D…yes

DNSKEY in the zone

Key tagRoleAlgorithm
27079ZSK (256)ECDSAP256SHA256 (13)
31537KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 31537 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-18 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-18 06:22 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

9 records at the apex

Found

Read from
37.97.129.170:53
TypeValueTTL
SOAns1.milieudefensie.nl. hostmaster.milieudefensie.nl. 2026101811 3600 800 2419200 60086400
NSns2.milieudefensie.nl.86400
NSns1.milieudefensie.nl.86400
A84.22.115.17286400
MX10 mail.milieudefensie.nl.86400
TXT"MS=ms84051851"86400
TXT"google-site-verification=iHxd6e_RWIIRRbD93uw7oF1JWdH_r2RLIA1viWFlTmk"86400
TXT"mistral-domain-verification=dc68092e7c6c7d8d417e9acb44ebfa1e06633699"86400
TXT"v=spf1 include:spf_f1.milieudefensie.nl include:spf_f2.milieudefensie.nl include:spf_f3.milieudefensie.nl" " include:spf_f4.milieudefensie.nl include:spf_f5.milieudefensie.nl include:spf_f6.milieudefensie.nl" " include:spf_f7.milieudefensie.nl include:spf_f8.milieudefensie.nl include:spf_f9.milieudefensie.nl" " include:spf_f10.milieudefensie.nl -all"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, MX 1d, NS 1d. The NS TTL at the parent is 1h and in the zone 1d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35