businessinsider.nl

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

Registration

info

.nl country-code · 101domain GRS Limited

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
101domain GRS Limited
Registered
18 March 2012
Last changed
18 August 2026
Status
active
Registry nameservers
bruce.ns.cloudflare.com, kim.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

bruce.ns.cloudflare.com, kim.ns.cloudflare.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
bruce.ns.cloudflare.com, kim.ns.cloudflare.com
NS in the zone
bruce.ns.cloudflare.com, kim.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
bruce.ns.cloudflare.com173.245.59.77 172.64.33.77 108.162.193.77 2803:f800:50::6ca2:c14d 2606:4700:58::adf5:3b4d 2a06:98c1:50::ac40:214dAS13335 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-
kim.ns.cloudflare.com172.64.32.126 173.245.58.126 108.162.192.126 2803:f800:50::6ca2:c07e 2a06:98c1:50::ac40:207e 2606:4700:50::adf5:3a7eAS13335 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: bruce.ns.cloudflare.com, kim.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
bruce.ns.cloudflare.com 173.245.59.77NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
bruce.ns.cloudflare.com 172.64.33.77NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
bruce.ns.cloudflare.com 108.162.193.77NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
bruce.ns.cloudflare.com 2803:f800:50::6ca2:c14dNOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
bruce.ns.cloudflare.com 2606:4700:58::adf5:3b4dNOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
bruce.ns.cloudflare.com 2a06:98c1:50::ac40:214dNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
kim.ns.cloudflare.com 172.64.32.126NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
kim.ns.cloudflare.com 173.245.58.126NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
kim.ns.cloudflare.com 108.162.192.126NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
kim.ns.cloudflare.com 2803:f800:50::6ca2:c07eNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
kim.ns.cloudflare.com 2a06:98c1:50::ac40:207eNOERROR, 20 ms, authoritativenoyes / yesrefused2026.10.2
kim.ns.cloudflare.com 2606:4700:50::adf5:3a7eNOERROR, 17 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: bruce.ns.cloudflare.com: "2026.10.2"; kim.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 2417520891 · primary bruce.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
bruce.ns.cloudflare.com (173.245.59.77)2417520891
bruce.ns.cloudflare.com (172.64.33.77)2417520891
bruce.ns.cloudflare.com (108.162.193.77)2417520891
bruce.ns.cloudflare.com (2803:f800:50::6ca2:c14d)2417520891
bruce.ns.cloudflare.com (2606:4700:58::adf5:3b4d)2417520891
bruce.ns.cloudflare.com (2a06:98c1:50::ac40:214d)2417520891
kim.ns.cloudflare.com (172.64.32.126)2417520891
kim.ns.cloudflare.com (173.245.58.126)2417520891
kim.ns.cloudflare.com (108.162.192.126)2417520891
kim.ns.cloudflare.com (2803:f800:50::6ca2:c07e)2417520891
kim.ns.cloudflare.com (2a06:98c1:50::ac40:207e)2417520891
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)2417520891

Checks

  • ✓ Serial 2417520891 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 bruce.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 2417520891 is a Unix timestamp (2046-08-10 13:34 UTC).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC
Signatures valid until
22 October 2026

DNSKEY in the zone

Key tagRoleAlgorithm
2371KSK (257)ECDSAP256SHA256 (13)
34505ZSK (256)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-20 20:00 UTC and expires at 2026-10-22 22:00 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

15 records at the apex

Found

Read from
173.245.59.77:53
TypeValueTTL
SOAbruce.ns.cloudflare.com. dns.cloudflare.com. 2417520891 10000 2400 604800 18001800
NSbruce.ns.cloudflare.com.86400
NSkim.ns.cloudflare.com.86400
A188.114.96.2300
A188.114.97.2300
AAAA2a06:98c1:3120::2300
AAAA2a06:98c1:3121::2300
MX0 businessinsider-nl.mail.protection.outlook.com.3600
TXT"MS=ms65567861"300
TXT"MS=ms65884387"300
TXT"google-site-verification=0Z7RE0-oqILx_dD-WCjsWH-TDGnLNDuslgN49cFZY0w"300
TXT"google-site-verification=cdTBopgsBNhJZyJbJNuIFWHaM3wID2WWrsrm4bs2PgA"300
TXT"google-site-verification=jFTBax8_afm4yerzHc7U9VY7irSlyrimekLjK2mRzKI"300
TXT"google-site-verification=qyTJu0BPI1UdsLt8OVSzbqyHm7IUgjp3tJ6fwOX3FjI"300
TXT"v=spf1 mx include:_spf.google.com include:emsd1.com include:amazonses.com include:spf.protection.outlook.com ~all"300

Checks

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