SurfaceMap › v › vlaco.be

vlaco.be

Checked 2026-10-22 07:21 UTC · first added 2026-10-21
✗Problems found Score 66 of 100

Domain & DNS

warn

24 passed 2 warn 0 failed

Areas

iRegistration ✓Delegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns1.level27.eu: "9.18.18-0ubuntu0.22.04.1-Ubuntu"; dns2.level27.eu: "9.18.39-0ubuntu0.24.04.5-Ubuntu"; dns3.level27.net: "9.18.39-0ubuntu0.24.04.3-Ubuntu". 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 vlaco.be ›

Mail

fail

20 passed 6 warn 1 failed

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
  • !
    3 of 10 DNS lookups, with problems
    SPF · SPF record needs 3 DNS lookups (limit is 10). Problems found: include:3sign-vlaco-web1.level27.eu does not exist or has no records.
    #2
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: d304240.a.ess.de.barracudanetworks.com, d304240.b.ess.de.barracudanetworks.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    1 void lookup
    SPF · 1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • !
    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 vlaco.be ›