SurfaceMap › w › wervik.be

wervik.be

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

Domain & DNS

warn

24 passed 3 warn 0 failed

Areas

iRegistration !Delegation iNameservers ✓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: 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
  • !
    Signatures expire soon
    DNSSEC · The earliest signature expires at 2026-10-27 12:41 UTC (in 125h0m0s). Check that automatic re-signing works.
    #30
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 10 iterations and a 16-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Recent checks

!

Full report

Domain & DNS report for wervik.be ›

Mail

fail

25 passed 4 warn 1 failed

Areas

✗SPF !DMARC ✓DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    11 DNS lookups, over the limit of 10
    SPF · SPF record needs 11 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Signatures expire in 125h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-27T12:41:41Z (in 125h0m0s). Check that re-signing works.
    #21
  • !
    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 wervik.be ›