hmrv.de

Checked 21 October 2026, 22:50 UTC · via 8.8.8.8
✗Problems found
24 passed 3 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx:hansemerkur.de -all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 1 of 10 DNS lookups #2
    SPF record needs 1 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.hmrv.de)

Found

Record
v=DMARC1; p=none; sp=none; rua=mailto:hm_dmarc@hansemerkur.de,mailto:dmarc_agg@vali.email; ruf=mailto:postmaster@hansemerkur.de; fo=0; adkim=r; aspf=r; pct=100; rf=afrf; ri=86400;
Found at
_dmarc.hmrv.de
External report address
mailto:hm_dmarc@hansemerkur.de (not authorized)
External report address
mailto:dmarc_agg@vali.email (authorized)
External report address
mailto:postmaster@hansemerkur.de (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:hm_dmarc@hansemerkur.de,mailto:dmarc_agg@vali.emailAggregate report addresses
rufmailto:postmaster@hansemerkur.deFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo0Failure reporting options
rfafrfFailure report format
ri86400Report interval (seconds)

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:hm_dmarc@hansemerkur.de, mailto:dmarc_agg@vali.email
  • !
    Report address not authorized
    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

DKIM

pass

Selectors: dkim

Found

Selectors
dkim
_domainkey
NOERROR
SelectorKeyFlags
dkimRSA 2048 bits

Checks

  • ✓ Keys found: dkim #7
    DKIM keys found for this domain with selectors: dkim
  • ✓ Strong keys #23
    DKIM keys are strong enough: dkim: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
2371, 34505
Signatures valid until
3 December 2026, 14:05 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-12-03 #21
    DNSKEY signatures are valid until 2026-12-03T14:05:24Z.

MX

warn

3 mail servers

Found

PriorityHostRecordsReverse DNS
10vamail01.hansemerkur.deA 185.190.195.41vamail01.hansemerkur.de ✓
10vamail02.hansemerkur.deA 185.190.195.42vamail02.hansemerkur.de ✓
20vamail03.hansemerkur.deA 185.190.193.43vamail03.hansemerkur.de ✓

Checks

  • ✓ 3 MX records #9
    Found 3 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: vamail01.hansemerkur.de, vamail02.hansemerkur.de, vamail03.hansemerkur.de
    #11
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 3 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 3 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
vamail01.hansemerkur.denone-
vamail02.hansemerkur.denone-
vamail03.hansemerkur.denone-

Checks

  • !
    Not configured
    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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38