yorhel.nl

Checked 21 October 2026, 21:27 UTC · via 8.8.8.8
!Passed with warnings
23 passed 1 warning 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/yorhel.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/yorhel.nl returned HTTP 429
    #3

Delegation

info

ns1.blicky.net, ns2.blicky.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.blicky.net, ns2.blicky.net
NS in the zone
ns1.blicky.net, ns2.blicky.net
NameserverAddressesNetwork (AS)Glue
ns1.blicky.net51.158.170.79 2001:bc8:1640:1262:dc00:ff:fe1e:406fAS12876 AS12876 - Scaleway SAS, FR AS12876 AS12876 - Scaleway SAS, FR-
ns2.blicky.net107.189.13.208 2605:6400:30:fcbc::1AS53667 PONYNET - FranTech Solutions, US AS53667 PONYNET - FranTech Solutions, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.blicky.net, ns2.blicky.net.
    #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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS12876 (AS12876 - Scaleway SAS, FR): 2 addresses; AS53667 (PONYNET - FranTech Solutions, US): 2 addresses.
  • i
    All nameserver names under .net
    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

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.blicky.net 51.158.170.79NOERROR, 28 ms, authoritativenoyes / yesrefused-
ns1.blicky.net 2001:bc8:1640:1262:dc00:ff:fe1e:406fNOERROR, 27 ms, authoritativenoyes / yesrefused-
ns2.blicky.net 107.189.13.208NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns2.blicky.net 2605:6400:30:fcbc::1NOERROR, 33 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 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 151 · primary ns1.blicky.net

Found

Primary (MNAME)
ns1.blicky.net
Contact (RNAME)
hostmaster.blicky.net
Serial
151
Refresh / retry
43200 s / 300 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.blicky.net (51.158.170.79)151
ns1.blicky.net (2001:bc8:1640:1262:dc00:ff:fe1e:406f)151
ns2.blicky.net (107.189.13.208)151
ns2.blicky.net (2605:6400:30:fcbc::1)151

Checks

  • ✓ Serial 151 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 5m, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.blicky.net is one of the listed nameservers.
  • ✓ Contact hostmaster@blicky.net #25
    The SOA RNAME hostmaster.blicky.net means hostmaster@blicky.net.
  • ✓ Counter serial #26
    The serial 151 is a plain counter.

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

info

10 records at the apex

Found

Read from
51.158.170.79:53
TypeValueTTL
SOAns1.blicky.net. hostmaster.blicky.net. 151 43200 300 604800 36003600
NSns2.blicky.net.3600
NSns1.blicky.net.3600
A104.244.79.2303600
AAAA2605:6400:30:f3ec:b826:9d00:7112:47d23600
MX10 mx1.blicky.net.3600
MX10 mx2.blicky.net.3600
TXT"v=spf1 include:authsmtp.com include:soverin.net -all"3600
CAA0 issuewild ";"3600
CAA0 issue "letsencrypt.org"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 1h, MX 1h, NS 1h.
  • ✓ 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: none (issuance forbidden), letsencrypt.org.