SurfaceMap › u › uza.be

uza.be

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

Domain & DNS

fail

15 passed 6 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC !Records

Problems

  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns.uza.be (193.190.131.96): 325 records; ns2.uza.be (193.190.131.109): 325 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns.uza.be (glue 193.190.131.96, 2001:6a8:460:1149:ffff:ffff:ffff:1a01, zone 193.190.131.96); ns2.uza.be (glue 193.190.131.109, 2001:6a8:460:1149:ffff:ffff:ffff:1a02, zone 193.190.131.109). Update the glue at your registrar.
    #8
  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 193.190.131.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Unusual SOA timers
    SOA · retry 1h should be shorter than refresh 1h; expire 12h is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 1h, expire 12h, negative TTL 12h.
    #23
  • !
    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), MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1m; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for uza.be ›

Mail

fail

23 passed 3 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
  • !
    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 uza.be ›