vbag.nl

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

Delegation

info

dns12.ovh.net, ns12.ovh.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
dns12.ovh.net, ns12.ovh.net
NS in the zone
dns12.ovh.net, ns12.ovh.net
NameserverAddressesNetwork (AS)Glue
dns12.ovh.net5.135.86.81 2001:41d0:d00:f100::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns12.ovh.net5.39.102.21 2001:41d0:b00:eb00::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns12.ovh.net, ns12.ovh.net.
    #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 2 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH SAS, FR): 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 .net
    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

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns12.ovh.net 5.135.86.81NOERROR, 18 ms, authoritativenoyes / yesrefused-
dns12.ovh.net 2001:41d0:d00:f100::2NOERROR, 18 ms, authoritativenoyes / yesrefused-
ns12.ovh.net 5.39.102.21NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns12.ovh.net 2001:41d0:b00:eb00::2NOERROR, 15 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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 2090807724 · primary dns12.ovh.net

Found

Primary (MNAME)
dns12.ovh.net
Contact (RNAME)
tech.ovh.net
Serial
2090807724
Refresh / retry
86400 s / 3600 s
Expire
3600000 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
dns12.ovh.net (5.135.86.81)2090807724
dns12.ovh.net (2001:41d0:d00:f100::2)2090807724
ns12.ovh.net (5.39.102.21)2090807724
ns12.ovh.net (2001:41d0:b00:eb00::2)2090807724

Checks

  • ✓ Serial 2090807724 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 1h, expire 1000h, negative TTL 1m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns12.ovh.net is one of the listed nameservers.
  • ✓ Contact tech@ovh.net #25
    The SOA RNAME tech.ovh.net means tech@ovh.net.
  • ✓ Timestamp serial #26
    The serial 2090807724 is a Unix timestamp (2036-04-03 03:55 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
30 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
6214RSASHA256 (8)SHA256 C893BF651E995D43…yes

DNSKEY in the zone

Key tagRoleAlgorithm
6214KSK (257)RSASHA256 (8)
50901ZSK (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 6214 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-10-30 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-30 21:35 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

warn

10 records at the apex

Found

Read from
5.135.86.81:53
TypeValueTTL
SOAdns12.ovh.net. tech.ovh.net. 2090807724 86400 3600 3600000 6060
NSns12.ovh.net.60
NSdns12.ovh.net.60
A162.159.135.4260
AAAA2606:4700:7::a29f:872a60
MX0 vbag-nl.mail.protection.outlook.com.60
TXT"1|www.vbag.nl"60
TXT"v=spf1 a mx a:hallo.themedutch.ovh ip4:217.182.245.120 ip4:185.103.18.45 ip6:2001:41d0:303:f50a:: include:mailgun.org include:spf.protection.outlook.com include:_spf.exactonline.nl ~all"60
TXT"google-site-verification=kE2R4Fp1ILru0N0gliWbxXNHYlYp5F1bqq2_ft6Wo3Q"60
TXT"MS=ms96947212"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m), MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 1m; resolvers may use either.
    #32
  • ✓ 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