ilovespeelgoed.nl

Checked 22 October 2026, 13:52 UTC · via 8.8.8.8
!Passed with warnings
25 passed 2 warnings 0 failed 5 info

Registration

info

.nl country-code

Found

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

Delegation

warn

ns1.hypernode.com, ns2.hypernode.com, ns3.hypernode.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.hypernode.com, ns2.hypernode.com, ns3.hypernode.com
NS in the zone
ns1.hypernode.com, ns2.hypernode.com, ns3.hypernode.com
NameserverAddressesNetwork (AS)Glue
ns1.hypernode.com80.84.227.137AS31586 AS-TBNLTN - Signet B.V., NL-
ns2.hypernode.com18.196.180.73AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns3.hypernode.com34.251.57.20AS16509 AMAZON-02 - Amazon.com, Inc., US-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.hypernode.com, ns2.hypernode.com, ns3.hypernode.com.
  • ✓ 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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS16509 (AMAZON-02 - Amazon.com, Inc., US): 2 addresses; AS31586 (AS-TBNLTN - Signet B.V., NL): 1 address.
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.hypernode.com 80.84.227.137NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.hypernode.com 18.196.180.73NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3.hypernode.com 34.251.57.20NOERROR, 23 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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

pass

serial 2026072701 · primary ns1.hypernode.com

Found

Primary (MNAME)
ns1.hypernode.com
Contact (RNAME)
hostmaster.hypernode.com
Serial
2026072701
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.hypernode.com (80.84.227.137)2026072701
ns2.hypernode.com (18.196.180.73)2026072701
ns3.hypernode.com (34.251.57.20)2026072701

Checks

  • ✓ Serial 2026072701 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.hypernode.com is one of the listed nameservers.
  • ✓ Contact hostmaster@hypernode.com #25
    The SOA RNAME hostmaster.hypernode.com means hostmaster@hypernode.com.
  • ✓ Date-based serial #26
    The serial 2026072701 follows the YYYYMMDDnn convention (2026-07-27).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
5 November 2026

DNSKEY in the zone

Key tagRoleAlgorithm
13870KSK (257)RSASHA256 (8)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ 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.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

17 records at the apex

Found

Read from
80.84.227.137:53
TypeValueTTL
SOAns1.hypernode.com. hostmaster.hypernode.com. 2026072701 10800 3600 604800 3600600
NSns1.hypernode.com.23025
NSns2.hypernode.com.23025
NSns3.hypernode.com.23025
A23.227.38.65600
MX1 ASPMX.L.GOOGLE.COM.3600
MX10 ALT3.ASPMX.L.GOOGLE.COM.3600
MX5 ALT1.ASPMX.L.GOOGLE.COM.3600
MX10 ALT4.ASPMX.L.GOOGLE.COM.3600
MX5 ALT2.ASPMX.L.GOOGLE.COM.3600
TXT"klaviyo-site-verification=Spaq7K"600
TXT"google-site-verification=kNQ_HzrOzN-MTeycTjZ-SfCWu_RcD4g1hzcbA1JBKZU"600
TXT"google-site-verification=w3MJEu-olFcXiPFs_NCreUjCF3rsbNRNOEiakVBtCWI"600
TXT"google-site-verification=zU61EcYW1xsiG0XDzixU_FT9aULmEiqw7fswqc203bA"600
TXT"v=spf1 include:spf.monta.nl include:_spf.google.com include:spf.ils3.hypernode.io include:trustpilotservice.com include:spf.mandrillapp.com include:spf.transsmart.com include:mail.zendesk.com -all"600
TXT"MS=ms23186843"600
TXT"google-site-verification=9uG--fmL-XjS5Fec_IdCP7QN3wM09t4VsaBxeNaljzQ"600

Checks

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