thuisgekookt.nl

Checked 22 October 2026, 16:32 UTC · via 8.8.8.8
iAll checks passed
24 passed 0 warnings 0 failed 9 info

Registration

info

.nl country-code

Found

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

Delegation

info

ns1.vultr.com, ns2.vultr.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.vultr.com, ns2.vultr.com
NS in the zone
ns1.vultr.com, ns2.vultr.com
NameserverAddressesNetwork (AS)Glue
ns1.vultr.com173.199.96.96 2001:19f0:ccc::1 2001:19f0:ccd::1AS20473 AS-VULTR - The Constant Company, LLC, US AS20473 AS-VULTR - The Constant Company, LLC, US AS20473 AS-VULTR - The Constant Company, LLC, US-
ns2.vultr.com173.199.96.97 2001:19f0:ccd::2 2001:19f0:ccc::2AS20473 AS-VULTR - The Constant Company, LLC, US AS20473 AS-VULTR - The Constant Company, LLC, US AS20473 AS-VULTR - The Constant Company, LLC, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.vultr.com, ns2.vultr.com.
    #6
  • ✓ 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.
  • i
    One address family in one network
    all IPv4 addresses are in 173.199.96.0/24, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS20473 (AS-VULTR - The Constant Company, LLC, US): 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
  • i
    All nameserver names under .com
    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

info

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.vultr.com 173.199.96.96NOERROR, 4 ms, authoritativenoyes / yesrefusedChoopaDNS
ns1.vultr.com 2001:19f0:ccc::1NOERROR, 4 ms, authoritativenoyes / yesrefusedChoopaDNS
ns1.vultr.com 2001:19f0:ccd::1NOERROR, 4 ms, authoritativenoyes / yesrefusedChoopaDNS
ns2.vultr.com 173.199.96.97NOERROR, 4 ms, authoritativenoyes / yesrefusedChoopaDNS
ns2.vultr.com 2001:19f0:ccd::2NOERROR, 4 ms, authoritativenoyes / yesrefusedChoopaDNS
ns2.vultr.com 2001:19f0:ccc::2NOERROR, 4 ms, authoritativenoyes / yesrefusedChoopaDNS

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.vultr.com: "ChoopaDNS"; ns2.vultr.com: "ChoopaDNS".
    #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 0 · primary ns1.vultr.com

Found

Primary (MNAME)
ns1.vultr.com
Contact (RNAME)
dnsadm.choopa.com
Serial
0
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.vultr.com (173.199.96.96)0
ns1.vultr.com (2001:19f0:ccc::1)0
ns1.vultr.com (2001:19f0:ccd::1)0
ns2.vultr.com (173.199.96.97)0
ns2.vultr.com (2001:19f0:ccd::2)0
ns2.vultr.com (2001:19f0:ccc::2)0

Checks

  • ✓ Serial 0 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.vultr.com is one of the listed nameservers.
  • ✓ Contact dnsadm@choopa.com #25
    The SOA RNAME dnsadm.choopa.com means dnsadm@choopa.com.
  • ✓ Counter serial #26
    The serial 0 is a plain counter.

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
31997ECDSAP256SHA256 (13)SHA256 BBF628E5A16BAE6D…yes

DNSKEY in the zone

Key tagRoleAlgorithm
31997KSK (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 31997 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ 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

19 records at the apex

Found

Read from
173.199.96.96:53
TypeValueTTL
SOAns1.vultr.com. dnsadm.choopa.com. 0 10800 3600 604800 3600300
NSns1.vultr.com.300
NSns2.vultr.com.300
A209.250.250.12300
MX10 thuisgekookt.nl.3600
MX10 alt4.aspmx.l.google.com.3600
MX5 alt2.aspmx.l.google.com.3600
MX5 alt1.aspmx.l.google.com.3600
MX10 alt3.aspmx.l.google.com.3600
MX1 aspmx.l.google.com.3600
TXT"google-site-verification=Q7qRK21gdNUkRYt_n3G9n-D_VQvMyo67rhvGxtWYGds"3600
TXT"00D68000003lIjH=1TBP500000000uT"3600
TXT"v=spf1 a mx include:_spf.mlsend.com include:_spf.google.com ~all"3600
TXT"google-site-verification=QjHI5-i9wuLMNUXcunnIAJfI-6d9LUPyHrdAeTyt6xM"3600
TXT"anthropic-domain-verification-t9r8sj=55eDczb0NSzhPkBvq9i0uMT4g"3600
TXT"brevo-code:0ef3272eb714a2e17f927b013a5c1784"3600
TXT"MS=ms92992090"3600
TXT"MS=477A6D43333AFE7AA84C1EE7EE93588F9454806E"3600
CAA0 issue "letsencrypt.org"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 1h, NS 5m. The NS TTL at the parent is 1h and in the zone 5m; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org.