pb1sam.nl

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

Delegation

warn

ns1.pb1sam.nl, ns2.pb1sam.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.pb1sam.nl, ns2.pb1sam.nl
NS in the zone
ns1.pb1sam.nl, ns2.pb1sam.nl
NameserverAddressesNetwork (AS)Glue
ns1.pb1sam.nl212.114.109.209 2001:7b8:60c:1:4:48:4c:1AS12859 NL-BIT - BIT BV, NL AS12859 NL-BIT - BIT BV, NL212.114.109.209
ns2.pb1sam.nl212.114.109.209 2001:7b8:60c:1:4:48:4c:1AS12859 NL-BIT - BIT BV, NL AS12859 NL-BIT - BIT BV, NL2001:7b8:60c:1:4:48:4c:1

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.pb1sam.nl, ns2.pb1sam.nl.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns1.pb1sam.nl (glue 212.114.109.209, zone 212.114.109.209, 2001:7b8:60c:1:4:48:4c:1); ns2.pb1sam.nl (glue 2001:7b8:60c:1:4:48:4c:1, zone 212.114.109.209, 2001:7b8:60c:1:4:48:4c:1). Update the glue at your registrar.
    #8
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 212.114.109.0/24; all IPv6 addresses are in 2001:7b8:60c::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS12859 (NL-BIT - BIT BV, NL): 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 .nl
    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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.pb1sam.nl 212.114.109.209NOERROR, 14 ms, authoritativenoyes / yesrefused9.20.26-1~deb13u1-Debian
ns1.pb1sam.nl 2001:7b8:60c:1:4:48:4c:1NOERROR, 14 ms, authoritativenoyes / yesrefused9.20.26-1~deb13u1-Debian
ns2.pb1sam.nl 212.114.109.209NOERROR, 12 ms, authoritativenoyes / yesrefused9.20.26-1~deb13u1-Debian
ns2.pb1sam.nl 2001:7b8:60c:1:4:48:4c:1NOERROR, 12 ms, authoritativenoyes / yesrefused9.20.26-1~deb13u1-Debian

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.pb1sam.nl: "9.20.26-1~deb13u1-Debian"; ns2.pb1sam.nl: "9.20.26-1~deb13u1-Debian". Hide or replace the version string.
    #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

warn

serial 2025121801 · primary ns1.pb1sam.nl

Found

Primary (MNAME)
ns1.pb1sam.nl
Contact (RNAME)
admin.pb1sam.nl
Serial
2025121801
Refresh / retry
7200 s / 7200 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.pb1sam.nl (212.114.109.209)2025121801
ns1.pb1sam.nl (2001:7b8:60c:1:4:48:4c:1)2025121801
ns2.pb1sam.nl (212.114.109.209)2025121801
ns2.pb1sam.nl (2001:7b8:60c:1:4:48:4c:1)2025121801

Checks

  • ✓ Serial 2025121801 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 2h should be shorter than refresh 2h. Current values: refresh 2h, retry 2h, expire 7d, negative TTL 5m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.pb1sam.nl is one of the listed nameservers.
  • ✓ Contact admin@pb1sam.nl #25
    The SOA RNAME admin.pb1sam.nl means admin@pb1sam.nl.
  • ✓ Date-based serial #26
    The serial 2025121801 follows the YYYYMMDDnn convention (2025-12-18).

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

7 records at the apex

Found

Read from
212.114.109.209:53
TypeValueTTL
SOAns1.pb1sam.nl. admin.pb1sam.nl. 2025121801 7200 7200 604800 300300
NSns1.pb1sam.nl.300
NSns2.pb1sam.nl.300
A212.114.109.209300
AAAA2001:7b8:60c:1:4:48:4c:1300
MX10 mail.pb1sam.nl.pb1sam.nl.300
TXT"v=spf1 a mx ~all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 5m, MX 5m, 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
  • 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