allianzdirect.de

Checked 21 October 2026, 21:28 UTC · via 8.8.8.8
!Passed with warnings
26 passed 3 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:194.127.3.0/26 ip4:194.127.24.225 ip4:194.127.26.225 ip4:83.171.132.152 ip4:83.171.132.153 ip4:87.230.97.144/28 ip4:62.113.218.4/30 ip4:83.133.158.241 ip4:178.77.89.84 ip4:131.124.92.11 ip4:208.73.5.8 ip4:195.216.235.154 ip4:52.178.9.176 include:_spf.allianz.de include:spf.allianz.com include:_spf.psm.knowbe4.com include:_spf-dc33.sapsf.eu ~all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

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

pass

p=reject (_dmarc.allianzdirect.de)

Found

Record
v=DMARC1; p=reject; fo=1; ri=3600; rua=mailto:Rua-allianz@allianz.com; ruf=mailto:Ruf-allianz@allianz.com
Found at
_dmarc.allianzdirect.de
External report address
mailto:Rua-allianz@allianz.com (authorized)
External report address
mailto:Ruf-allianz@allianz.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:Rua-allianz@allianz.comAggregate report addresses
rufmailto:Ruf-allianz@allianz.comFailure report addresses
fo1Failure reporting options
ri3600Report interval (seconds)

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:Rua-allianz@allianz.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: s1, s2

Found

Selectors
s1, s2
_domainkey
NOERROR
SelectorKeyFlags
s1RSA 2048 bits
s2RSA 2048 bits

Checks

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

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

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.hc1435-93.eu.iphmx.comA 23.90.122.253 A 23.90.123.237esa.hc1435-93.eu.iphmx.com ✓ esa.hc1435-93.eu.iphmx.com ✓
10mx2.hc1435-93.eu.iphmx.comA 23.90.122.253 A 23.90.123.237esa.hc1435-93.eu.iphmx.com ✓ esa.hc1435-93.eu.iphmx.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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: mx1.hc1435-93.eu.iphmx.com, mx2.hc1435-93.eu.iphmx.com
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 2 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.hc1435-93.eu.iphmx.comnone-
mx2.hc1435-93.eu.iphmx.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