SurfaceMap › h › hmrv.de

hmrv.de

Checked 2026-10-21 22:50 UTC · first added 2026-10-21
✗Problems found Score 78 of 100

Domain & DNS

warn

26 passed 1 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA iDNSSEC ✓Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: lars.ns.cloudflare.com: "2026.10.2"; tani.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #17

Recent checks

!

Full report

Domain & DNS report for hmrv.de ›

Mail

fail

24 passed 3 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: vamail01.hansemerkur.de, vamail02.hansemerkur.de, vamail03.hansemerkur.de
    #11
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:hm_dmarc@hansemerkur.de (needs hmrv.de._report._dmarc.hansemerkur.de); mailto:postmaster@hansemerkur.de (needs hmrv.de._report._dmarc.hansemerkur.de). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 hmrv.de ›