auerswald.de

Checked 21 October 2026, 21:31 UTC · via 8.8.8.8
✗Problems found
21 passed 5 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.hornetsecurity.com include:set1.spf-cust.portunity.de include:spf.protection.outlook.com include:_spf.auerswald.de a:smtp.ispworks.net -all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 5 of 10 DNS lookups #2
    SPF record needs 5 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.auerswald.de)

Found

Record
v=DMARC1; p=none; sp=none; pct=100; ruf=mailto:hostmaster@auerswald.de; rua=mailto:hostmaster@auerswald.de; adkim=s; aspf=r
Found at
_dmarc.auerswald.de
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:hostmaster@auerswald.deAggregate report addresses
rufmailto:hostmaster@auerswald.deFailure report addresses
adkimsDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)

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:hostmaster@auerswald.de
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: default, selector1, selector2

Found

Selectors
default, selector1, selector2
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bitstest mode (t=y)
selector1RSA 1024 bits
selector2RSA 1024 bits

Checks

  • ✓ Keys found: default, selector1, selector2 #7
    DKIM keys found for this domain with selectors: default, selector1, selector2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), selector1 (1024 bits), selector2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Key in test mode
    These keys have t=y, so receivers treat DKIM failures as a test: default. Remove t=y once DKIM works.
    #24

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

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

warn

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

Found

DANE (TLSA records)

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

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