SurfaceMap › i › iminds.be

iminds.be

Checked 2026-10-22 06:40 UTC · first added 2026-10-21
✗Problems found Score 62 of 100

Domain & DNS

fail

19 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns1.ilabt.imec.be (2001:6a8:1d80:23::182): read udp [2a01:4f8:1c1c:eebf::1]:35463->[2001:6a8:1d80:23::182]:53: i/o timeout; hal.ilabt.imec.be (2001:6a8:1d80:23::1): read udp [2a01:4f8:1c1c:eebf::1]:55647->[2001:6a8:1d80:23::1]:53: i/o timeout.
    #14
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 193.191.148.0/24; all IPv6 addresses are in 2001:6a8:1d80::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns1.ilabt.imec.be: "9.20.30-1~deb13u1-Debian"; hal.ilabt.imec.be: "9.10.3-P4-Debian". Hide or replace the version string.
    #17
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

✗

Full report

Domain & DNS report for iminds.be ›

Mail

fail

23 passed 3 warn 1 failed

Areas

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

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.iminds.be does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    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 iminds.be ›