SurfaceMap › v › visitoost.nl

visitoost.nl

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

Domain & DNS

error

25 passed 2 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns.eatserver.nl: "PowerDNS Authoritative Server 4.7.4 (built Apr 17 2023 07:39:17 by root@89eec22969dd)"; ns2.eatserver.nl: "PowerDNS Authoritative Server 4.7.4 (built Apr 17 2023 07:39:17 by root@89eec22969dd)". Hide or replace the version string.
    #17
  • !
    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 visitoost.nl ›

Mail

fail

22 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
  • !
    5 of 10 DNS lookups, with problems
    SPF · SPF record needs 5 DNS lookups (limit is 10). Problems found: include:mail.tripolis.com has no SPF record.
    #2
  • !
    Ends with ?all (neutral)
    SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #3
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (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 visitoost.nl ›