SurfaceMap › v › vpro.nl

vpro.nl

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

Domain & DNS

error

26 passed 3 warn 0 failed 1 errors

lookups failed for rdap; results are incomplete

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC ✓Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.openprovider.nl: "2026.10.8". Hide or replace the version string.
    #17
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2025275949 on ns1.openprovider.nl (162.159.26.10), ns1.openprovider.nl (2400:cb00:2049:1::a29f:1a0a); 2025275956 on ns.vpro.nl (145.58.168.42), ns.vpro.nl (2a02:458:931:300::11). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 10 iterations and a 2-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 vpro.nl ›

Mail

fail

23 passed 4 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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: de-smtp-inbound-1.mimecast.com, de-smtp-inbound-2.mimecast.com
    #11
  • !
    Signatures expire in 69h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-24T18:12:49Z (in 69h0m0s). Check that re-signing works.
    #21
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: 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 vpro.nl ›