SurfaceMap › v › vvebeheer-denhaag.nl

vvebeheer-denhaag.nl

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

Domain & DNS

error

22 passed 2 warn 1 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    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: ns3.flexwebhosting.com (185.231.200.133): dial tcp 185.231.200.133:53: connect: no route to host.
    #19
  • !
    Signatures expire soon
    DNSSEC · The earliest signature expires at 2026-10-29 00:00 UTC (in 151h0m0s). Check that automatic re-signing works.
    #30
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 1 iteration and a 1-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 vvebeheer-denhaag.nl ›

Mail

fail

18 passed 5 warn 1 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: srv1.flexfilter.nl, srv2.flexfilter.nl
    #11
  • !
    Signatures expire in 151h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-29T00:00:00Z (in 151h0m0s). 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
  • !
    Not configured
    TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35

Recent checks

✗

Full report

Mail report for vvebeheer-denhaag.nl ›