mijngelderland.nl

Checked 22 October 2026, 14:31 UTC · via 8.8.8.8
iAll checks passed
27 passed 0 warnings 0 failed 6 info

Registration

info

.nl country-code

Found

TLD
.nl (country-code)
ICANN policies apply
no
Lookup error: https://rdap.sidn.nl/domain/mijngelderland.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/mijngelderland.nl returned HTTP 429
    #3

Delegation

info

ns1.computel-standby.nl, ns2.computel-standby.net, ns3.computel-standby.eu

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.computel-standby.nl, ns2.computel-standby.net, ns3.computel-standby.eu
NS in the zone
ns1.computel-standby.nl, ns2.computel-standby.net, ns3.computel-standby.eu
NameserverAddressesNetwork (AS)Glue
ns1.computel-standby.nl78.41.78.126 2001:4038:8000:78:120::126AS31383 NEDERLANDNET-AS - Computel Standby BV, NL AS31383 NEDERLANDNET-AS - Computel Standby BV, NL78.41.78.126 2001:4038:8000:78:120::126
ns2.computel-standby.net83.137.17.10 2001:4038:0:17::10AS31383 NEDERLANDNET-AS - Computel Standby BV, NL AS31383 NEDERLANDNET-AS - Computel Standby BV, NL-
ns3.computel-standby.eu83.137.20.153 2001:4038:0:21::153AS31383 NEDERLANDNET-AS - Computel Standby BV, NL AS31383 NEDERLANDNET-AS - Computel Standby BV, NL-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.computel-standby.nl, ns2.computel-standby.net, ns3.computel-standby.eu.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ 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 3 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS31383 (NEDERLANDNET-AS - Computel Standby BV, NL): 6 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 3 TLDs #12
    Nameserver names use the TLDs .eu, .net, .nl.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.computel-standby.nl 78.41.78.126NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns1.computel-standby.nl 2001:4038:8000:78:120::126NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns2.computel-standby.net 83.137.17.10NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns2.computel-standby.net 2001:4038:0:17::10NOERROR, 13 ms, authoritativenoyes / yesrefused-
ns3.computel-standby.eu 83.137.20.153NOERROR, 12 ms, authoritativenoyes / yesrefused-
ns3.computel-standby.eu 2001:4038:0:21::153NOERROR, 15 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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

info

serial 2021110911 · primary ns0.computel-standby.nl

Found

Primary (MNAME)
ns0.computel-standby.nl
Contact (RNAME)
hostmaster.computel.nl
Serial
2021110911
Refresh / retry
14400 s / 3600 s
Expire
604800 s
Negative TTL
14400 s

Serial per nameserver

NameserverSerial
ns1.computel-standby.nl (78.41.78.126)2021110911
ns1.computel-standby.nl (2001:4038:8000:78:120::126)2021110911
ns2.computel-standby.net (83.137.17.10)2021110911
ns2.computel-standby.net (2001:4038:0:17::10)2021110911
ns3.computel-standby.eu (83.137.20.153)2021110911
ns3.computel-standby.eu (2001:4038:0:21::153)2021110911

Checks

  • ✓ Serial 2021110911 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 1h, expire 7d, negative TTL 4h.
  • i
    Hidden master
    The primary nameserver ns0.computel-standby.nl is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@computel.nl #25
    The SOA RNAME hostmaster.computel.nl means hostmaster@computel.nl.
  • ✓ Date-based serial #26
    The serial 2021110911 follows the YYYYMMDDnn convention (2021-11-09).

DNSSEC

info

Signed, DS published at parent

Found

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

DS at the parent

Key tagAlgorithmDigestMatches a key
29329RSASHA256 (8)SHA256 A5B771EDCD275C9D…yes

DNSKEY in the zone

Key tagRoleAlgorithm
29329KSK (257)RSASHA256 (8)
42745ZSK (256)RSASHA256 (8)

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 29329 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 00:00 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
78.41.78.126:53
TypeValueTTL
SOAns0.computel-standby.nl. hostmaster.computel.nl. 2021110911 14400 3600 604800 1440014400
NSns3.computel-standby.eu.14400
NSns1.computel-standby.nl.14400
NSns2.computel-standby.net.14400
A178.22.58.14814400
AAAA2a0b:3100:20::673600
MX0 mijngelderland-nl.mail.protection.outlook.com.3600
TXT"MS=ms19396602"3600
TXT"v=spf1 include:spf.mandrillapp.com include:spf.protection.outlook.com -all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 4h, AAAA 1h, MX 1h, NS 4h. The NS TTL at the parent is 1h and in the zone 4h; 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