SurfaceMap › p › peterprint.nl

peterprint.nl

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

Domain & DNS

error

20 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: melany.ns.cloudflare.com: "2026.10.2"; vin.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #17
  • !
    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 peterprint.nl ›

Mail

fail

15 passed 7 warn 2 failed

Areas

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

Problems

  • ✗
    12 DNS lookups, over the limit of 10
    SPF · SPF record needs 12 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✗
    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
  • !
    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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IP addresses
    MX · The following MX hosts could not be resolved to IP addresses: ms61419302.msv1.invalid
    #10
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: ms61419302.msv1.invalid
    #11
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 172.67.72.137 (mail.peterprint.nl), 104.26.7.127 (mail.peterprint.nl), 104.26.6.127 (mail.peterprint.nl), 2606:4700:20::681a:77f (mail.peterprint.nl), 2606:4700:20::681a:67f (mail.peterprint.nl), 2606:4700:20::ac43:4889 (mail.peterprint.nl). Ask your hosting provider to set one.
    #30
  • !
    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 peterprint.nl ›