SurfaceMap › z › zorgneticuro.be

zorgneticuro.be

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

Domain & DNS

warn

21 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.edpnet.net, ns2.edpnet.net. ns1.edpnet.be, ns1.edpnet.net, ns2.edpnet.be, ns2.edpnet.net report NS ns1.edpnet.be ns2.edpnet.be.
    #7
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.edpnet.be (glue 212.71.0.2, zone 212.71.0.2, 2a02:578:8000:2:212:71:0:2); ns2.edpnet.be (glue 212.71.8.11, zone 212.71.8.11, 2a02:578:1001:3:212:71:8:11). Update the glue at your registrar.
    #8
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.edpnet.be: "ZX Spectrum (Pentagon) 128K nameserver v0.923.7"; ns1.edpnet.net: "ZX Spectrum (Pentagon) 128K nameserver v0.923.7"; ns2.edpnet.be: "ZX Spectrum (Pentagon) 128K nameserver v0.923.7"; ns2.edpnet.net: "ZX Spectrum (Pentagon) 128K nameserver v0.923.7". 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 zorgneticuro.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
  • !
    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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (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 zorgneticuro.be ›