SurfaceMap › s › schouwburgconcertzaaltilburg.nl

schouwburgconcertzaaltilburg.nl

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

Domain & DNS

error

23 passed 3 warn 1 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC !Records

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 152h0m0s). 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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 15m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for schouwburgconcertzaaltilburg.nl ›

Mail

warn

26 passed 6 warn 0 failed

Areas

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

Problems

  • !
    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
  • !
    Signatures expire in 152h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-29T00:00:00Z (in 152h0m0s). Check that re-signing works.
    #21
  • !
    Unreadable DKIM key
    DKIM · These keys could not be parsed, so signatures made with them will fail: pm (public key is not valid base64).
    #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
  • !
    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 schouwburgconcertzaaltilburg.nl ›