plugandpay.nl

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

Registration

info

.nl country-code · team.blue nl B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
team.blue nl B.V.
Registered
28 March 2018
Last changed
15 February 2022
Status
active
Registry nameservers
holly.ns.cloudflare.com, jeff.ns.cloudflare.com
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

info

holly.ns.cloudflare.com, jeff.ns.cloudflare.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
holly.ns.cloudflare.com, jeff.ns.cloudflare.com
NS in the zone
holly.ns.cloudflare.com, jeff.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
holly.ns.cloudflare.com162.159.38.133 172.64.34.133 108.162.194.133 2803:f800:50::6ca2:c285 2606:4700:50::a29f:2685 2a06:98c1:50::ac40:2285AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
jeff.ns.cloudflare.com172.64.33.124 108.162.193.124 173.245.59.124 2a06:98c1:50::ac40:217c 2803:f800:50::6ca2:c17c 2606:4700:58::adf5:3b7cAS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: holly.ns.cloudflare.com, jeff.ns.cloudflare.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 6 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 12 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

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
holly.ns.cloudflare.com 162.159.38.133NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
holly.ns.cloudflare.com 172.64.34.133NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
holly.ns.cloudflare.com 108.162.194.133NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
holly.ns.cloudflare.com 2803:f800:50::6ca2:c285NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
holly.ns.cloudflare.com 2606:4700:50::a29f:2685NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
holly.ns.cloudflare.com 2a06:98c1:50::ac40:2285NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
jeff.ns.cloudflare.com 172.64.33.124NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
jeff.ns.cloudflare.com 108.162.193.124NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
jeff.ns.cloudflare.com 173.245.59.124NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
jeff.ns.cloudflare.com 2a06:98c1:50::ac40:217cNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jeff.ns.cloudflare.com 2803:f800:50::6ca2:c17cNOERROR, 21 ms, authoritativenoyes / yesrefused2026.10.2
jeff.ns.cloudflare.com 2606:4700:58::adf5:3b7cNOERROR, 21 ms, authoritativenoyes / yesrefused2026.10.2

Checks

  • ✓ All respond #14
    All 12 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: holly.ns.cloudflare.com: "2026.10.2"; jeff.ns.cloudflare.com: "2026.10.2". 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 2414209263 · primary holly.ns.cloudflare.com

Found

Primary (MNAME)
holly.ns.cloudflare.com
Contact (RNAME)
dns.cloudflare.com
Serial
2414209263
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
holly.ns.cloudflare.com (162.159.38.133)2414209263
holly.ns.cloudflare.com (172.64.34.133)2414209263
holly.ns.cloudflare.com (108.162.194.133)2414209263
holly.ns.cloudflare.com (2803:f800:50::6ca2:c285)2414209263
holly.ns.cloudflare.com (2606:4700:50::a29f:2685)2414209263
holly.ns.cloudflare.com (2a06:98c1:50::ac40:2285)2414209263
jeff.ns.cloudflare.com (172.64.33.124)2414209263
jeff.ns.cloudflare.com (108.162.193.124)2414209263
jeff.ns.cloudflare.com (173.245.59.124)2414209263
jeff.ns.cloudflare.com (2a06:98c1:50::ac40:217c)2414209263
jeff.ns.cloudflare.com (2803:f800:50::6ca2:c17c)2414209263
jeff.ns.cloudflare.com (2606:4700:58::adf5:3b7c)2414209263

Checks

  • ✓ Serial 2414209263 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver holly.ns.cloudflare.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2414209263 is a Unix timestamp (2046-07-03 05:41 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

info

16 records at the apex

Found

Read from
162.159.38.133:53
TypeValueTTL
SOAholly.ns.cloudflare.com. dns.cloudflare.com. 2414209263 10000 2400 604800 18001800
NSholly.ns.cloudflare.com.86400
NSjeff.ns.cloudflare.com.86400
A104.18.22.136300
A104.18.23.136300
AAAA2606:4700::6812:1688300
AAAA2606:4700::6812:1788300
MX1 aspmx.l.google.com.300
MX10 aspmx2.googlemail.com.300
MX10 aspmx3.googlemail.com.300
MX5 alt1.aspmx.l.google.com.300
MX5 alt2.aspmx.l.google.com.300
TXT"atlassian-domain-verification=cPIQb6rdNj8POAe7RyndKynw0PpzC534flZaJJ3Rg1dE3ejubUKkSfzxakRGcdMv"300
TXT"google-site-verification=_Ttip-RFrk_Y5Txfir_QAkz7gVfFYfW-lquvkhkfBbk"300
TXT"google-site-verification=g62PSP7lRc3CfO4RYAeSL5uQqZ4UlK8LkKke-JRsC5Q"300
TXT"v=spf1 include:_spf.google.com include:emsd1.com include:_spf.payt.nl ~all"300

Checks

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