kampeerwereld.nl

Checked 22 October 2026, 14:01 UTC · via 8.8.8.8
!Passed with warnings
19 passed 3 warnings 0 failed 7 info

Registration

info

.nl country-code

Found

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

Delegation

info

ns1.yoursrs.com, ns2.yoursrs.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.yoursrs.com, ns2.yoursrs.com
NS in the zone
ns1.yoursrs.com, ns2.yoursrs.com
NameserverAddressesNetwork (AS)Glue
ns1.yoursrs.com104.47.151.178 2603:1020:200::682f:a758AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns2.yoursrs.com20.79.93.42 2603:1020:c01:4::8AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.yoursrs.com, ns2.yoursrs.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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 4 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

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.yoursrs.com 104.47.151.178NOERROR, 14 ms, authoritativenoyes / yesrefused-
ns1.yoursrs.com 2603:1020:200::682f:a758NOERROR, 14 ms, authoritativenoyes / yesrefused-
ns2.yoursrs.com 20.79.93.42NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2.yoursrs.com 2603:1020:c01:4::8NOERROR, 5 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

warn

serial 2026031900 · primary ns1.yoursrs.com

Found

Primary (MNAME)
ns1.yoursrs.com
Contact (RNAME)
hostmaster.kampeerwereld.nl
Serial
2026031900
Refresh / retry
300 s / 300 s
Expire
86400 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.yoursrs.com (104.47.151.178)2026031900
ns1.yoursrs.com (2603:1020:200::682f:a758)2026031900
ns2.yoursrs.com (20.79.93.42)2026031900
ns2.yoursrs.com (2603:1020:c01:4::8)2026031900

Checks

  • ✓ Serial 2026031900 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 5m is outside 20m–1d; retry 5m should be shorter than refresh 5m; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 5m, retry 5m, expire 1d, negative TTL 5m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.yoursrs.com is one of the listed nameservers.
  • ✓ Contact hostmaster@kampeerwereld.nl #25
    The SOA RNAME hostmaster.kampeerwereld.nl means hostmaster@kampeerwereld.nl.
  • ✓ Date-based serial #26
    The serial 2026031900 follows the YYYYMMDDnn convention (2026-03-19).

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

9 records at the apex

Found

Read from
104.47.151.178:53
TypeValueTTL
SOAns1.yoursrs.com. hostmaster.kampeerwereld.nl. 2026031900 300 300 86400 300300
NSns2.yoursrs.com.300
NSns1.yoursrs.com.300
A87.238.163.114100
AAAA2001:9a8:68:0:87:233:194:2203600
MX1 kampeerwereld-nl.mail.protection.outlook.com.3600
TXT"google-site-verification=YF_0i1SaJr7-rQtyg6rDIDA1XcKg5cbcNgB6UPXzHM8"3600
TXT"v=spf1 ip4:141.138.223.3 ip4:94.126.67.36 ip4:87.233.194.218 ip4:87.233.194.220 include:spf.protection.outlook.com include:_spf.spotler.email include:servers.mcsv.net include:mail.zendesk.com mx -all"300
TXT"google-site-verification=tNJg3qk9mERKQFd1XlwagfA9sJ9eqGdW6-4XMr7IkOQ"3600

Checks

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