SurfaceMap › i › irceline.be

irceline.be

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

Domain & DNS

fail

18 passed 2 warn 3 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns2.belnet.be (193.190.182.40): SERVFAIL, authoritative=false; ns2.belnet.be (2001:6a8:3c80:c000::40): SERVFAIL, authoritative=false.
    #15
  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: dnsext.irceline.be (193.190.137.132): 163 records. Restrict zone transfers to your secondary servers.
    #18
  • ✗
    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: ns2.belnet.be (193.190.182.40): ; ns2.belnet.be (2001:6a8:3c80:c000::40): .
    #19
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dnsext.irceline.be: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.14". 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 irceline.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 IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mail.irceline.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
  • !
    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 irceline.be ›