sandberg.nl

Checked 22 October 2026, 15:50 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 warnings 0 failed 9 info

Registration

info

.nl country-code

Found

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

Delegation

info

ns1.webtic.net, ns2.webtic.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.webtic.net, ns2.webtic.net
NS in the zone
ns1.webtic.net, ns2.webtic.net
NameserverAddressesNetwork (AS)Glue
ns1.webtic.net91.99.131.59 2a01:4f8:1c1a:3aef::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns2.webtic.net78.47.50.200 2a01:4f8:1c1a:bf99::1AS24940 HETZNER-AS - Hetzner Online GmbH, DE AS24940 HETZNER-AS - Hetzner Online GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.webtic.net, ns2.webtic.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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a01:4f8:1c1a::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.webtic.net 91.99.131.59NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns1.webtic.net 2a01:4f8:1c1a:3aef::1NOERROR, 6 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns2.webtic.net 78.47.50.200NOERROR, 3 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.17 (built Aug 5 2026 13:25:56 by root@localhost)
ns2.webtic.net 2a01:4f8:1c1a:bf99::1NOERROR, 2 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.17 (built Aug 5 2026 13:25:56 by root@localhost)

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.webtic.net: "PowerDNS Authoritative Server 4.8.3"; ns2.webtic.net: "PowerDNS Authoritative Server 4.9.17 (built Aug 5 2026 13:25:56 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

pass

serial 2025091101 · primary ns1.webtic.net

Found

Primary (MNAME)
ns1.webtic.net
Contact (RNAME)
hostmaster.sandberg.nl
Serial
2025091101
Refresh / retry
3600 s / 1800 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.webtic.net (91.99.131.59)2025091101
ns1.webtic.net (2a01:4f8:1c1a:3aef::1)2025091101
ns2.webtic.net (78.47.50.200)2025091101
ns2.webtic.net (2a01:4f8:1c1a:bf99::1)2025091101

Checks

  • ✓ Serial 2025091101 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 30m, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.webtic.net is one of the listed nameservers.
  • ✓ Contact hostmaster@sandberg.nl #25
    The SOA RNAME hostmaster.sandberg.nl means hostmaster@sandberg.nl.
  • ✓ Date-based serial #26
    The serial 2025091101 follows the YYYYMMDDnn convention (2025-09-11).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
5 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
37241ECDSAP256SHA256 (13)SHA256 4F04CAE4DC5AAA18…yes

DNSKEY in the zone

Key tagRoleAlgorithm
37241KSK (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 37241 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-05 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-05 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

9 records at the apex

Found

Read from
91.99.131.59:53
TypeValueTTL
SOAns1.webtic.net. hostmaster.sandberg.nl. 2025091101 3600 1800 604800 36003600
NSns2.webtic.net.60
NSns1.webtic.net.60
A176.9.223.403600
MX0 sandberg-nl.mail.protection.outlook.com.3600
TXT"google-site-verification=6Jt0ygH4YbWrte55GT1HhWc2BQ1GLDZlxL2dCqfr9t4"60
TXT"MS=ms96843302"60
TXT"brevo-code:c1f3ab19988e658487274a0d309af7f2"60
TXT"v=spf1 mx a:spf.protection.outlook.com a:sandberg.nl include:spf.protection.outlook.com -all"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: 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