vgz.nl

Checked 21 October 2026, 21:26 UTC · via 8.8.8.8
iAll checks passed
27 passed 0 warnings 0 failed 6 info

Registration

info

.nl country-code

Found

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

Delegation

info

ns0.leaseweb.com, ns1.leaseweb.com

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns0.leaseweb.com, ns1.leaseweb.com
NS in the zone
ns0.leaseweb.com, ns1.leaseweb.com
NameserverAddressesNetwork (AS)Glue
ns0.leaseweb.com23.19.196.53 2607:f5b5::53AS7203 LEASEWEB-USA-SFO - Leaseweb USA, Inc., US AS28753 LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH, DE-
ns1.leaseweb.com23.19.197.53 2607:f5b5:1::53AS7203 LEASEWEB-USA-SFO - Leaseweb USA, Inc., US AS28753 LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns0.leaseweb.com, ns1.leaseweb.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 2 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS28753 (LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH, DE): 2 addresses; AS7203 (LEASEWEB-USA-SFO - Leaseweb USA, Inc., US): 2 addresses.
  • 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

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns0.leaseweb.com 23.19.196.53NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns0.leaseweb.com 2607:f5b5::53NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.leaseweb.com 23.19.197.53NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns1.leaseweb.com 2607:f5b5:1::53NOERROR, 4 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

pass

serial 2026101401 · primary ns0.leaseweb.com

Found

Primary (MNAME)
ns0.leaseweb.com
Contact (RNAME)
postmaster.leaseweb.com
Serial
2026101401
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns0.leaseweb.com (23.19.196.53)2026101401
ns0.leaseweb.com (2607:f5b5::53)2026101401
ns1.leaseweb.com (23.19.197.53)2026101401
ns1.leaseweb.com (2607:f5b5:1::53)2026101401

Checks

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

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
29 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
44695ECDSAP256SHA256 (13)SHA256 DAEF6DD0B9CDB963…yes

DNSKEY in the zone

Key tagRoleAlgorithm
44695KSK (257)ECDSAP256SHA256 (13)

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 44695 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-10-29 #30
    The earliest DNSKEY/SOA signature expires at 2026-10-29 00:00 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

24 records at the apex

Found

Read from
23.19.196.53:53
TypeValueTTL
SOAns0.leaseweb.com. postmaster.leaseweb.com. 2026101401 10800 3600 1209600 36003600
NSns1.leaseweb.com.3600
NSns0.leaseweb.com.3600
A20.15.2.76300
MX10 vgz-nl.mail.protection.outlook.com.300
TXT"_kmvq70a1vzo0nzoq1i0ilwjkwzmssc4"300
TXT"amazonses:e6adrZL6HGEzCF2UqRBlLjaky/5PCoDzPY0JaWF49i0="300
TXT"_4ul6rotwbi32aaub3dlxxgne3sqwzwe"300
TXT"_bx9zkboxedoqchoxlghvdbwf6wyuj2j"300
TXT"apple-domain-verification=WFX119Qphpy5iXpz"300
TXT"_ix3h7vbe1vzwi0onw3pop91osu2j928"300
TXT"ms-domain-verification=ceac381e-3294-4868-afc5-a0d259932843"300
TXT"pardot596711=b8b929fdd000c7261bd4e25fb456f8a7003218316aef4c37eb4084217821fa5f"300
TXT"_ic8tn18kuseipm3slrf51ziobm26ike"300
TXT"_ima5qs98pwzlczi5on6pa6nh3ajiuoz"300
TXT"v=NTA7516-1;startdate=2026-02;enddate=2034-02;provider=secumailer"300
TXT"pardot596711=34b3aa2509fbc3922f7c1f50185b2bc179a72459c8f9566d8e2326082d5e42b8"300
TXT"_x3tk15gssnzd561u6ydp3atrc6zxjw3"300
TXT"_qtz58aco4pytixbfsj180wkn3l8sat5"300
TXT"b3FDbnV5HzG1VC9icg+8q4RmpS6XNk2NfNtWNI9xMr1wa45OamH7GgkbGYiPmjUZqhx7t5W9yABy3ohJ1+Rm7A=="300
TXT"582f4483-98c2-4853-8d30-02aa28b97838-17072018"300
TXT"v=spf1 include:spf.protection.outlook.com include:spf1.vgz.nl ip4:85.222.158.224/28 ip4:81.93.51.192/26 ip4:77.74.54.216 ip4:147.181.10.36 ip4:194.150.14.85 include:spf.flowmailer.net include:carerix.net include:secumail.email ip4:20.229.30.51 ip4:20.71.2" "7.2 ip4:192.174.81.0 ip4:192.174.81.1 -all"300
TXT"google-site-verification=lSWTonkTKqjV33Suz6tHwNIZZNncpI1JSjqD__Cgkv0"300
TXT"_d9y9g0aj3k1roahquyvkvw9s06jhknc"300

Checks

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