SurfaceMap › i › itsme.be

itsme.be

Checked 2026-10-22 06:40 UTC · first added 2026-10-21
!Passed with warnings Score 79 of 100

Domain & DNS

warn

22 passed 3 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns2-34.azure-dns.net: "Knot DNS 3.1.2.1770717641.d6b376aff"; ns4-34.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". 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
  • !
    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. The NS TTL at the parent is 1d and in the zone 2d; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for itsme.be ›

Mail

warn

25 passed 4 warn 0 failed

Areas

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

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IP addresses
    MX · The following MX hosts could not be resolved to IP addresses: ms66513025.msv1.invalid
    #10
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: ms66513025.msv1.invalid
    #11
  • !
    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 itsme.be ›