SurfaceMap › i › iclicks.nl

iclicks.nl

Checked 2026-10-22 13:51 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

error

23 passed 3 warn 1 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration !Delegation ✗Nameservers ✓SOA iDNSSEC !Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · 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
  • !
    Glue differs from the zone
    Delegation · 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
  • !
    Software version disclosed
    Nameservers · 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
  • !
    Very low TTLs
    Records · 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

Recent checks

!

Full report

Domain & DNS report for iclicks.nl ›

Mail

error

24 passed 3 warn 1 failed 1 errors

lookups failed for tls-rpt; results are incomplete

Areas

✓SPF ✗DMARC !DKIM ✓DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

!

Full report

Mail report for iclicks.nl ›