rembrandthuis.nl

Checked 21 October 2026, 21:24 UTC · via 8.8.8.8
!Passed with warnings
25 passed 2 warnings 0 failed 8 info

Registration

info

.nl country-code · Next Buzz B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
Next Buzz B.V.
Registered
17 December 1996
Last changed
24 April 2024
Status
active
Registry nameservers
ns1.nextbuzz.nl, ns2.nextbuzz.nl, ns3.nextbuzz.nl
RDAP server
https://rdap.sidn.nl/

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
    Expiry date not published
    The registry does not publish the expiry date in RDAP. Check it with your registrar.
    #3
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.nextbuzz.nl, ns2.nextbuzz.nl, ns3.nextbuzz.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.nextbuzz.nl, ns2.nextbuzz.nl, ns3.nextbuzz.nl
NS in the zone
ns1.nextbuzz.nl, ns2.nextbuzz.nl, ns3.nextbuzz.nl
NameserverAddressesNetwork (AS)Glue
ns1.nextbuzz.nl178.62.223.145AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US178.62.223.145 2a03:b0c0:2:d0::bad:3001
ns2.nextbuzz.nl64.227.74.163 2a03:b0c0:2:f0::202:7001AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US64.227.74.163 2a03:b0c0:2:f0::202:7001
ns3.nextbuzz.nl104.131.36.21 2604:a880:800:14::3:c000AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US104.131.36.21 2604:a880:800:14::3:c000

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.nextbuzz.nl, ns2.nextbuzz.nl, ns3.nextbuzz.nl.
  • ✓ 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.nextbuzz.nl (glue 178.62.223.145, 2a03:b0c0:2:d0::bad:3001, zone 178.62.223.145). Update the glue at your registrar.
    #8
  • ✓ 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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US): 5 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.nextbuzz.nl.
    #13

Nameservers

warn

5 of 5 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.nextbuzz.nl 178.62.223.145NOERROR, 15 ms, authoritativenoyes / yesrefusednone
ns2.nextbuzz.nl 64.227.74.163NOERROR, 11 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.7-Ubuntu
ns2.nextbuzz.nl 2a03:b0c0:2:f0::202:7001NOERROR, 14 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.7-Ubuntu
ns3.nextbuzz.nl 104.131.36.21NOERROR, 94 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.7-Ubuntu
ns3.nextbuzz.nl 2604:a880:800:14::3:c000NOERROR, 86 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.7-Ubuntu

Checks

  • ✓ All respond #14
    All 5 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: ns2.nextbuzz.nl: "9.18.39-0ubuntu0.22.04.7-Ubuntu"; ns3.nextbuzz.nl: "9.18.39-0ubuntu0.22.04.7-Ubuntu". 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

pass

serial 2026101410 · primary ns1.nextbuzz.nl

Found

Primary (MNAME)
ns1.nextbuzz.nl
Contact (RNAME)
m\.bosch.museumrembrandthuis.nl
Serial
2026101410
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns1.nextbuzz.nl (178.62.223.145)2026101410
ns2.nextbuzz.nl (64.227.74.163)2026101410
ns2.nextbuzz.nl (2a03:b0c0:2:f0::202:7001)2026101410
ns3.nextbuzz.nl (104.131.36.21)2026101410
ns3.nextbuzz.nl (2604:a880:800:14::3:c000)2026101410

Checks

  • ✓ Serial 2026101410 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 14d, negative TTL 3h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.nextbuzz.nl is one of the listed nameservers.
  • ✓ Contact m.bosch@museumrembrandthuis.nl #25
    The SOA RNAME m\.bosch.museumrembrandthuis.nl means m.bosch@museumrembrandthuis.nl.
  • ✓ Date-based serial #26
    The serial 2026101410 follows the YYYYMMDDnn convention (2026-10-14).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
29 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
27080RSASHA256 (8)SHA256 4E6452D6AE20DC34…yes
4826RSASHA256 (8)SHA256 C60A0178B6BE705D…yes

DNSKEY in the zone

Key tagRoleAlgorithm
4826KSK (257)RSASHA256 (8)
27080KSK (257)RSASHA256 (8)
65476ZSK (256)RSASHA256 (8)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 27080 (SHA256), key tag 4826 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-10-29 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-29 09:26 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

9 records at the apex

Found

Read from
178.62.223.145:53
TypeValueTTL
SOAns1.nextbuzz.nl. m\.bosch.museumrembrandthuis.nl. 2026101410 10800 3600 1209600 1080086400
NSns3.nextbuzz.nl.86400
NSns1.nextbuzz.nl.86400
NSns2.nextbuzz.nl.86400
A188.166.59.10186400
AAAA2a03:b0c0:2:d0::4e7:100186400
MX10 rembrandthuis-nl.mail.protection.outlook.com.86400
TXT"v=spf1 ip4:93.186.182.15 include:_spf.hellodialog.com include:spf.jewellabs.net include:spf.protection.outlook.com include:klantenbinder.nl include:relay.mailchannels.net include:_spf.exactonline.nl include:spf.mailcamp.nl -all"86400
TXT"MS=ms60028289"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, AAAA 1d, MX 1d, NS 1d. The NS TTL at the parent is 1h and in the zone 1d; resolvers may use either.
  • ✓ 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