SurfaceMap › v › voo.be

voo.be

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

Domain & DNS

fail

21 passed 2 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: brutele01.brutele.be (185.3.160.71): read tcp 46.225.38.91:39764->185.3.160.71:53: i/o timeout; brutele01.brutele.be (2a02:2788:fff5:2::71): read tcp [2a01:4f8:1c1c:eebf::1]:59612->[2a02:2788:fff5:2::71]:53: i/o timeout; brutele02.brutele.be (185.3.160.72): read tcp 46.225.38.91:59748->185.3.160.72:53: i/o timeout; brutele02.brutele.be (2a02:2788:fff5:2::72): read tcp [2a01:4f8:1c1c:eebf::1]:42478->[2a02:2788:fff5:2::72]:53: i/o timeout.
    #19
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 185.3.160.0/24; all IPv6 addresses are in 2a02:2788:fff5::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    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 voo.be ›

Mail

warn

22 passed 6 warn 0 failed

Areas

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

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    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: mrouterin.brutele.be
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    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 voo.be ›