SurfaceMap › n › ntgent.be

ntgent.be

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

Domain & DNS

warn

20 passed 3 warn 0 failed

Areas

iRegistration !Delegation iNameservers ✓SOA !DNSSEC !Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns.be.hostbasket.com, ns.fr.hostbasket.com, ns.nl.hostbasket.com; only in the zone: ns1.cloud.telenet.be, ns2.cloud.telenet.be, ns3.cloud.telenet.be. ns.be.hostbasket.com, ns.fr.hostbasket.com, ns.nl.hostbasket.com, ns1.cloud.telenet.be, ns2.cloud.telenet.be, ns3.cloud.telenet.be report NS ns1.cloud.telenet.be ns2.cloud.telenet.be ns3.cloud.telenet.be.
    #7
  • !
    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 (1m30s), MX (1m30s), NS (1m30s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1m30s; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for ntgent.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: s2 (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 ntgent.be ›