vip.nl

Checked 21 October 2026, 21:26 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 warnings 0 failed 5 info

Registration

info

.nl country-code

Found

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

Delegation

info

be.ns.vip.nl, dns.resolver.domains, nl.ns.vip.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
be.ns.vip.nl, dns.resolver.domains, nl.ns.vip.nl
NS in the zone
be.ns.vip.nl, dns.resolver.domains, nl.ns.vip.nl
NameserverAddressesNetwork (AS)Glue
be.ns.vip.nl185.94.228.197 2a05:1500:501:1:1c00:a4ff:fe00:135AS48635 CLDIN-NL - Your Hosting B.V., NL AS48635 CLDIN-NL - Your Hosting B.V., NL185.94.228.197 2a05:1500:501:1:1c00:a4ff:fe00:135
dns.resolver.domains185.109.216.162 2a05:1500:600:0:1c00:1ff:fe00:9eAS48635 CLDIN-NL - Your Hosting B.V., NL AS48635 CLDIN-NL - Your Hosting B.V., NL-
nl.ns.vip.nl92.63.173.176 2a05:1500:702:3:1c00:5fff:fe00:14b9AS48635 CLDIN-NL - Your Hosting B.V., NL AS48635 CLDIN-NL - Your Hosting B.V., NL92.63.173.176 2a05:1500:702:3:1c00:5fff:fe00:14b9

Checks

  • ✓ 3 nameservers #6
    Delegated to be.ns.vip.nl, dns.resolver.domains, nl.ns.vip.nl.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: be.ns.vip.nl, nl.ns.vip.nl.
  • ✓ 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 3 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS48635 (CLDIN-NL - Your Hosting B.V., NL): 6 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .domains, .nl.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
be.ns.vip.nl 185.94.228.197NOERROR, 9 ms, authoritativenoyes / yesrefused-
be.ns.vip.nl 2a05:1500:501:1:1c00:a4ff:fe00:135NOERROR, 10 ms, authoritativenoyes / yesrefused-
dns.resolver.domains 185.109.216.162NOERROR, 10 ms, authoritativenoyes / yesrefused-
dns.resolver.domains 2a05:1500:600:0:1c00:1ff:fe00:9eNOERROR, 10 ms, authoritativenoyes / yesrefused-
nl.ns.vip.nl 92.63.173.176NOERROR, 10 ms, authoritativenoyes / yesrefused-
nl.ns.vip.nl 2a05:1500:702:3:1c00:5fff:fe00:14b9NOERROR, 14 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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 2026081701 · primary dns.resolver.domains

Found

Primary (MNAME)
dns.resolver.domains
Contact (RNAME)
hostmaster.vip.nl
Serial
2026081701
Refresh / retry
86400 s / 10800 s
Expire
3600000 s
Negative TTL
172800 s

Serial per nameserver

NameserverSerial
be.ns.vip.nl (185.94.228.197)2026081701
be.ns.vip.nl (2a05:1500:501:1:1c00:a4ff:fe00:135)2026081701
dns.resolver.domains (185.109.216.162)2026081701
dns.resolver.domains (2a05:1500:600:0:1c00:1ff:fe00:9e)2026081701
nl.ns.vip.nl (92.63.173.176)2026081701
nl.ns.vip.nl (2a05:1500:702:3:1c00:5fff:fe00:14b9)2026081701

Checks

  • ✓ Serial 2026081701 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 3h, expire 1000h, negative TTL 2d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns.resolver.domains is one of the listed nameservers.
  • ✓ Contact hostmaster@vip.nl #25
    The SOA RNAME hostmaster.vip.nl means hostmaster@vip.nl.
  • ✓ Date-based serial #26
    The serial 2026081701 follows the YYYYMMDDnn convention (2026-08-17).

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

12 records at the apex

Found

Read from
185.94.228.197:53
TypeValueTTL
SOAdns.resolver.domains. hostmaster.vip.nl. 2026081701 86400 10800 3600000 17280086400
NSdns.resolver.domains.86400
NSnl.ns.vip.nl.86400
NSbe.ns.vip.nl.86400
A185.87.184.113600
MX5 mx01.provider.nl.3600
MX10 mx02.provider.nl.3600
TXT"v=spf1 include:se.spf.provider.nl include:net.spf.provider.nl include:sendgrid.net include:spf.protection.outlook.com include:servers.mcsv.net include:ab.sendgrid.net ~all"3600
TXT"MS=ms11061342"3600
TXT"blitz=mu-4bc1411c-9f121b46-5a504196-e84e1bd6"3600
TXT"google-site-verification=bOiFbuWbH71evzlCqJ1rRdrqKzIFJh_7CJ-SNxz60os"3600
TXT"MS=ms71078870"3600

Checks

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