SurfaceMap › d › degeschillencommissie.nl

degeschillencommissie.nl

Checked 2026-10-21 21:00 UTC · first added 2026-10-21
!Check could not complete

Domain & DNS

error

21 passed 4 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

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 in the zone: ns4.qweb.be. ns1.qweb.net, ns2.qweb.nu, ns3.qweb.co, ns4.qweb.be report NS ns1.qweb.net ns2.qweb.nu ns3.qweb.co ns4.qweb.be.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.qweb.net: "PowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)"; ns2.qweb.nu: "PowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)"; ns3.qweb.co: "PowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)"; ns4.qweb.be: "PowerDNS Authoritative Server 5.1.5 (built Oct 7 2026 06:13:16 by root@localhost)". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 7d, negative TTL 1h.
    #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 degeschillencommissie.nl ›

Mail

warn

23 passed 6 warn 0 failed

Areas

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

Problems

  • !
    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
  • !
    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
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), selector2 (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 degeschillencommissie.nl ›