mvonederland.nl

Checked 21 October 2026, 21:23 UTC · via 8.8.8.8
!Passed with warnings
26 passed 3 warnings 0 failed 6 info

Registration

info

.nl country-code · Registrar.eu

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
Registrar.eu
Registered
8 July 2004
Last changed
4 July 2025
Status
active
Registry nameservers
ns1.qweb.nl, ns2.qweb.nl, ns3.qweb.co
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

pass

ns1.qweb.nl, ns2.qweb.nl, ns3.qweb.co

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.qweb.nl, ns2.qweb.nl, ns3.qweb.co
NS in the zone
ns1.qweb.nl, ns2.qweb.nl, ns3.qweb.co
NameserverAddressesNetwork (AS)Glue
ns1.qweb.nl217.18.64.243 2a00:19c0:a064:243::1AS21221 InfoPact-AS - Infopact Netwerkdiensten B.V., NL AS21221 InfoPact-AS - Infopact Netwerkdiensten B.V., NL-
ns2.qweb.nl185.214.151.241 2a0b:9cc0:151:241::1AS21221 InfoPact-AS - Infopact Netwerkdiensten B.V., NL AS21221 InfoPact-AS - Infopact Netwerkdiensten B.V., NL-
ns3.qweb.co142.93.171.61 2a03:b0c0:3:f0:0:2:b08f:0AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US AS14061 DIGITALOCEAN-ASN - DigitalOcean, LLC, US-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.qweb.nl, ns2.qweb.nl, ns3.qweb.co.
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US): 2 addresses; AS21221 (InfoPact-AS - Infopact Netwerkdiensten B.V., NL): 4 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .co, .nl.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.qweb.nl 217.18.64.243NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)
ns1.qweb.nl 2a00:19c0:a064:243::1NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)
ns2.qweb.nl 185.214.151.241NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)
ns2.qweb.nl 2a0b:9cc0:151:241::1NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)
ns3.qweb.co 142.93.171.61NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)
ns3.qweb.co 2a03:b0c0:3:f0:0:2:b08f:0NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.qweb.nl: "PowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)"; ns2.qweb.nl: "PowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)"; ns3.qweb.co: "PowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)". 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

warn

serial 2026100801 · primary ns1.qweb.nl

Found

Primary (MNAME)
ns1.qweb.nl
Contact (RNAME)
hostmaster.qweb.nl
Serial
2026100801
Refresh / retry
3600 s / 3600 s
Expire
604800 s
Negative TTL
14400 s

Serial per nameserver

NameserverSerial
ns1.qweb.nl (217.18.64.243)2026100801
ns1.qweb.nl (2a00:19c0:a064:243::1)2026100801
ns2.qweb.nl (185.214.151.241)2026100801
ns2.qweb.nl (2a0b:9cc0:151:241::1)2026100801
ns3.qweb.co (142.93.171.61)2026100801
ns3.qweb.co (2a03:b0c0:3:f0:0:2:b08f:0)2026100801

Checks

  • ✓ Serial 2026100801 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 7d, negative TTL 4h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.qweb.nl is one of the listed nameservers.
  • ✓ Contact hostmaster@qweb.nl #25
    The SOA RNAME hostmaster.qweb.nl means hostmaster@qweb.nl.
  • ✓ Date-based serial #26
    The serial 2026100801 follows the YYYYMMDDnn convention (2026-10-08).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
29 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
55217ECDSAP256SHA256 (13)SHA256 21A814E659F0F4E3…yes

DNSKEY in the zone

Key tagRoleAlgorithm
55217KSK (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 55217 (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.
  • 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

warn

17 records at the apex

Found

Read from
217.18.64.243:53
TypeValueTTL
SOAns1.qweb.nl. hostmaster.qweb.nl. 2026100801 3600 3600 604800 144003600
NSns3.qweb.co.3600
NSns2.qweb.nl.3600
NSns1.qweb.nl.3600
A185.67.200.31100
AAAA2a03:9700:67:200:31::1100
MX0 mvonederland-nl.mail.protection.outlook.com.300
TXT"yvzvs5fk1h356qry992bx826yt26x6rt"3600
TXT"v=spf1 ip4:185.214.114.126 ip4:176.62.168.243 ip4:176.62.168.242 include:authsmtp.com include:spf.protection.outlook.com include:spf.avetica.net include:_spf.exactonline.nl include:26725107.spf05.hubspotemail.net ~all"3600
TXT"google-site-verification=2NnPqI7nxZWXlDDTNDVkTVNu5K5LMu1N8VHJx1Zs1yg"3600
TXT"asv=58c6f4e4e147e679d747173248a9bb35"600
TXT"KTPp2fYPvevqYxzkd0UdrNST09wFIAvoRpBPRKUIy+ZNfUrUQW0AaJNviVZF98Jggj39BNqaCx1jlyZCu2x69A=="3600
TXT"google-site-verification=xwfUlWQTfpexWzBkH_QLUJpDjVU-mDbZ3BBDbFTRot4"3600
TXT"5pwlnpyfgz3l00rrx364n7j3hwxqkcmf"10
TXT"as=1392204338"30
TXT"MS=ms24031885"3600
TXT"Sendinblue-code:58d254059ac06520d90a254ee3a46af2"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m40s), AAAA (1m40s). Low TTLs are useful just before a planned change.
    #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