incijfers.nl

Checked 22 October 2026, 13:52 UTC · via 8.8.8.8
iAll checks passed
25 passed 0 warnings 0 failed 10 info

Registration

info

.nl country-code · Metaregistrar B.V.

Found

TLD
.nl (country-code)
ICANN policies apply
no
Registrar
Metaregistrar B.V.
Registered
2 July 2007
Last changed
25 June 2025
Status
active
Registry nameservers
ns1.premium-dns.net, ns2.premium-dns.net
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

info

ns1.premium-dns.net, ns2.premium-dns.net

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.premium-dns.net, ns2.premium-dns.net
NS in the zone
ns1.premium-dns.net, ns2.premium-dns.net
NameserverAddressesNetwork (AS)Glue
ns1.premium-dns.net192.174.68.15 2001:67c:1bc::15AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ns2.premium-dns.net176.97.158.15 2001:67c:10b8::15AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.premium-dns.net, ns2.premium-dns.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 (AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 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

info

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.premium-dns.net 192.174.68.15NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns1.premium-dns.net 2001:67c:1bc::15NOERROR, 3 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ns2.premium-dns.net 176.97.158.15NOERROR, 14 ms, authoritativenoyes / yesrefusedreg-wie1
ns2.premium-dns.net 2001:67c:10b8::15NOERROR, 13 ms, authoritativenoyes / yesrefusedreg-wie1

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.premium-dns.net: "RcodeZero DNS"; ns2.premium-dns.net: "reg-wie1".
    #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 2026102202 · primary ns1.premium-dns.net

Found

Primary (MNAME)
ns1.premium-dns.net
Contact (RNAME)
hostmaster.incijfers.nl
Serial
2026102202
Refresh / retry
86400 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.premium-dns.net (192.174.68.15)2026102202
ns1.premium-dns.net (2001:67c:1bc::15)2026102202
ns2.premium-dns.net (176.97.158.15)2026102202
ns2.premium-dns.net (2001:67c:10b8::15)2026102202

Checks

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

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
47886ECDSAP256SHA256 (13)SHA256 88545E73C9ED9672…yes

DNSKEY in the zone

Key tagRoleAlgorithm
47886KSK (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 47886 (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

info

11 records at the apex

Found

Read from
192.174.68.15:53
TypeValueTTL
SOAns1.premium-dns.net. hostmaster.incijfers.nl. 2026102202 86400 3600 604800 360086400
NSns1.premium-dns.net.3600
NSns2.premium-dns.net.3600
A94.228.143.563600
AAAA2a00:d00:101:950::56:13600
MX5 incijfers-nl.mail.protection.outlook.com.3600
MX10 wm.abf.nl.3600
MX20 ml.abf.nl.3600
TXT"spf2.0/pra"3600
TXT"MS=ms95906778"3600
TXT"v=spf1 ip4:87.236.4.64/26 ip4:94.228.143.0/26 ip4:195.72.123.169 ip6:2a00:a000:1::/48 ip6:2a00:0d00:0101::/48 include:servers.mcsv.net include:spf.protection.outlook.com -all"3600

Checks

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