iclicks.nl

Checked 22 October 2026, 13:51 UTC · via 8.8.8.8
✗Problems found
23 passed 3 warnings 1 failed 6 info

Registration

info

.nl country-code

Found

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

Delegation

warn

ns1.iclicks.nl, ns2.iclicks.nl, ns3.iclicks.nl

Found

Parent zone
nl
Delegation from
ns1.dns.nl (194.0.28.53)
NS at the parent
ns1.iclicks.nl, ns2.iclicks.nl, ns3.iclicks.nl
NS in the zone
ns1.iclicks.nl, ns2.iclicks.nl, ns3.iclicks.nl
NameserverAddressesNetwork (AS)Glue
ns1.iclicks.nl213.159.25.25 2a11:800::500AS208537 m3networks - M3 Groep BV, NL AS208537 m3networks - M3 Groep BV, NL213.159.25.25
ns2.iclicks.nl83.96.168.8 2001:828:400:1100:29::5353AS31586 AS-TBNLTN - Signet B.V., NL AS31586 AS-TBNLTN - Signet B.V., NL83.96.168.8
ns3.iclicks.nl149.210.134.176 2a01:7c8:aab2:2ed:5054:ff:fee7:a590AS20857 TRANSIP-AS - Signet B.V., NL AS20857 TRANSIP-AS - Signet B.V., NL149.210.134.176

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.iclicks.nl, ns2.iclicks.nl, ns3.iclicks.nl.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns1.iclicks.nl (glue 213.159.25.25, zone 213.159.25.25, 2a11:800::500); ns2.iclicks.nl (glue 83.96.168.8, zone 83.96.168.8, 2001:828:400:1100:29::5353); ns3.iclicks.nl (glue 149.210.134.176, zone 149.210.134.176, 2a01:7c8:aab2:2ed:5054:ff:fee7:a590). Update the glue at your registrar.
    #8
  • ✓ 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.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS208537 (m3networks - M3 Groep BV, NL): 2 addresses; AS20857 (TRANSIP-AS - Signet B.V., NL): 2 addresses; AS31586 (AS-TBNLTN - Signet B.V., NL): 2 addresses.
  • i
    All nameserver names under .nl
    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

fail

5 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.iclicks.nl 213.159.25.25NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.17
ns1.iclicks.nl 2a11:800::500no responsenono / no--
ns2.iclicks.nl 83.96.168.8NOERROR, 15 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.18 (built Oct 7 2026 06:11:27 by root@localhost)
ns2.iclicks.nl 2001:828:400:1100:29::5353NOERROR, 15 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.18 (built Oct 7 2026 06:11:27 by root@localhost)
ns3.iclicks.nl 149.210.134.176NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.18 (built Oct 7 2026 06:11:27 by root@localhost)
ns3.iclicks.nl 2a01:7c8:aab2:2ed:5054:ff:fee7:a590NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.9.18 (built Oct 7 2026 06:11:27 by root@localhost)

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns1.iclicks.nl (2a11:800::500): read udp [2a01:4f8:1c1c:eebf::1]:45936->[2a11:800::500]:53: i/o timeout.
    #14
  • ✓ 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.iclicks.nl: "PowerDNS Authoritative Server 4.9.17"; ns2.iclicks.nl: "PowerDNS Authoritative Server 4.9.18 (built Oct 7 2026 06:11:27 by root@localhost)"; ns3.iclicks.nl: "PowerDNS Authoritative Server 4.9.18 (built Oct 7 2026 06:11:27 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 2026102000 · primary ns1.iclicks.nl

Found

Primary (MNAME)
ns1.iclicks.nl
Contact (RNAME)
support.iclicks.nl
Serial
2026102000
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.iclicks.nl (213.159.25.25)2026102000
ns2.iclicks.nl (83.96.168.8)2026102000
ns2.iclicks.nl (2001:828:400:1100:29::5353)2026102000
ns3.iclicks.nl (149.210.134.176)2026102000
ns3.iclicks.nl (2a01:7c8:aab2:2ed:5054:ff:fee7:a590)2026102000

Checks

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

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
21117ECDSAP256SHA256 (13)SHA256 5B9D4F94953294AA…yes

DNSKEY in the zone

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

14 records at the apex

Found

Read from
213.159.25.25:53
TypeValueTTL
SOAns1.iclicks.nl. support.iclicks.nl. 2026102000 28800 7200 604800 8640086400
NSns3.iclicks.nl.3600
NSns1.iclicks.nl.3600
NSns2.iclicks.nl.3600
A213.159.24.24460
AAAA2a11:800::414600
MX0 iclicks-nl.mail.protection.outlook.com.3600
TXT"asv=d78d543f923c0f94376920cbee09acd9"600
TXT"ms=ms76337557"600
TXT"facebook-domain-verification=434h6v1er965fc3z8dshkyysw3pgb8"600
TXT"google-site-verification=XKfuc6iVJJ_8V1MeVaoJ5YjfTKPlQ70rjyNs41Syqzc"600
TXT"google-site-verification=I7trSimt1kLRSBvneAwZ7s9AkFrOxeL_67myqb8jlwA"600
TXT"ms=ms55322403"600
TXT"v=spf1 ip4:213.159.24.244 ip4:213.159.24.0/23 ip4:82.134.250.113 ip4:46.21.235.139 ip4:185.226.111.128/25 include:servers.mcsv.net include:_spf.google.com include:spf.protection.outlook.com include:_spf.gripp.com include:spf.flowmailer.net -all"600

Checks

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