ebnerstolz.de

Checked 21 October 2026, 22:17 UTC · via 8.8.8.8
!Passed with warnings
31 passed 1 warning 0 failed 3 info

SPF

info

SPF record published

Found

Record
v=spf1 redirect=ebnerstolz.de.spf.hornetdmarc.com
DNS lookups
6 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 6 of 10 DNS lookups #2
    SPF record needs 6 DNS lookups (limit is 10).
  • i
    Delegated via redirect
    SPF record has no 'all' mechanism but redirects to ebnerstolz.de.spf.hornetdmarc.com, whose policy applies.
    #3
  • ✓ 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

pass

p=reject (_dmarc.ebnerstolz.de)

Found

Record
v=DMARC1; p=reject; pct=100; fo=1:0; rua=mailto:a.feurlxmu@reports.hornetdmarc.com; ruf=mailto:rsmebnerstolz1@eu.cp-dmarc.com
Found at
_dmarc.ebnerstolz.de
External report address
mailto:a.feurlxmu@reports.hornetdmarc.com (authorized)
External report address
mailto:rsmebnerstolz1@eu.cp-dmarc.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
pct100Percentage of mail the policy applies to
ruamailto:a.feurlxmu@reports.hornetdmarc.comAggregate report addresses
rufmailto:rsmebnerstolz1@eu.cp-dmarc.comFailure report addresses
fo1:0Failure reporting options

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:a.feurlxmu@reports.hornetdmarc.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

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
18565, 64651
Signatures valid until
1 December 2026, 04:00 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-01 #21
    DNSKEY signatures are valid until 2026-12-01T04:00:27Z.

MX

warn

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mx01.hornetsecurity.comA 94.100.132.8mx01.hornetsecurity.com ✓
20mx02.hornetsecurity.comA 94.100.136.8mx02.hornetsecurity.com ✓
30mx03.hornetsecurity.comA 94.100.134.8mx03.hornetsecurity.com ✓
40mx04.hornetsecurity.comA 94.100.136.7mx04.hornetsecurity.com ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: mx01.hornetsecurity.com, mx02.hornetsecurity.com, mx03.hornetsecurity.com, mx04.hornetsecurity.com
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 4 MX addresss have a PTR record that resolves back to them.

TLS

info

MTA-STS enforce · TLS-RPT · DANE on 0 of 4 MX hosts

Found

MTA-STS record
v=STSv1; id=1744027686
Policy URL
https://mta-sts.ebnerstolz.de/.well-known/mta-sts.txt
Mode
enforce
Allowed MX
mx03.hornetsecurity.com, mx02.hornetsecurity.com, mx01.hornetsecurity.com, mx04.hornetsecurity.com
Max age
604800 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:reports@reports.hornetdmarc.com

DANE (TLSA records)

MX hostTLSADNSSEC
mx01.hornetsecurity.comnone-
mx02.hornetsecurity.comnone-
mx03.hornetsecurity.comnone-
mx04.hornetsecurity.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 1744027686.
  • ✓ Policy enforced #33
    The MTA-STS policy is enforced and cached for 168h0m0s.
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:reports@reports.hornetdmarc.com
  • 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