SurfaceMap › l › lefred.be

lefred.be

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

Domain & DNS

fail

16 passed 5 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Open recursion
    Nameservers · These nameservers resolve names for anyone, which makes them usable for DNS amplification attacks and cache poisoning: ns1.lefred.be (162.19.248.192), ns2.lefred.be (188.165.239.85). Disable recursion on authoritative servers.
    #16
  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns1.lefred.be (162.19.248.192): 48 records; ns2.lefred.be (188.165.239.85): 48 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns2.lefred.be. ns1.lefred.be, ns2.lefred.be report NS ns1.lefred.be.
    #7
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.lefred.be: "9.16.23-RH"; ns2.lefred.be: "9.16.23-RH". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · retry 2h should be shorter than refresh 2h; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 2h, retry 2h, expire 1d, negative TTL 1d.
    #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

Recent checks

✗

Full report

Domain & DNS report for lefred.be ›

Mail

fail

20 passed 5 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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mail.lefred.be, mail2.lefred.be
    #11
  • !
    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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 lefred.be ›