rsh-recruitment.nl

Checked 22 October 2026, 15:42 UTC · via 8.8.8.8
!Passed with warnings
20 passed 3 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/rsh-recruitment.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/rsh-recruitment.nl returned HTTP 429
    #3

Delegation

warn

ns1.wp.one, ns2.wp.one

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.wp.one, ns2.wp.one
NS in the zone
ns1.wp.one, ns2.wp.one
NameserverAddressesNetwork (AS)Glue
ns1.wp.one91.200.176.1AS200325 BunnyCDN - BUNNYWAY, informacijske storitve d.o.o., SI-
ns2.wp.one109.104.147.1AS200325 BunnyCDN - BUNNYWAY, informacijske storitve d.o.o., SI-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.wp.one, ns2.wp.one.
    #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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS200325 (BunnyCDN - BUNNYWAY, informacijske storitve d.o.o., SI): 2 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 .one
    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

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.wp.one 91.200.176.1NOERROR, 14 ms, authoritativenoyes / yesrefused-
ns2.wp.one 109.104.147.1NOERROR, 3 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 2 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 2021738710 · primary ns1.wp.one

Found

Primary (MNAME)
ns1.wp.one
Contact (RNAME)
hostmaster.bunny.net
Serial
2021738710
Refresh / retry
7200 s / 900 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.wp.one (91.200.176.1)2021738710
ns2.wp.one (109.104.147.1)2021738710

Checks

  • ✓ Serial 2021738710 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 15m, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.wp.one is one of the listed nameservers.
  • ✓ Contact hostmaster@bunny.net #25
    The SOA RNAME hostmaster.bunny.net means hostmaster@bunny.net.
  • ✓ Timestamp serial #26
    The serial 2021738710 is a Unix timestamp (2034-01-24 18:05 UTC).

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

warn

7 records at the apex

Found

Read from
91.200.176.1:53
TypeValueTTL
SOAns1.wp.one. hostmaster.bunny.net. 2021738710 7200 900 1209600 86400900
NSns1.wp.one.172800
NSns2.wp.one.172800
A185.111.111.15435
AAAA2400:52e0:1e00:2::1332:135
MX0 cufaaxmjj.mx.service.one.300
TXT"v=spf1 a mx include:_spf.hostnet.nl include:smtp.wp-cloud.fi -all"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (35s), AAAA (35s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 2d; resolvers may use either.
    #32
  • ✓ 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