Mail domain report: allianz.fr

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:194.127.3.0/26 ip4:87.106.1.21 ip4:208.86.168.7 ip4:135.84.68.123 ip4:193.240.14.113 ip4:87.253.235.76 ip4:87.253.235.96 ip4:204.93.80.116/31 ip4:194.98.34.224/31 ip4:168.245.49.60 ip4:168.245.33.125 ip4:167.89.89.170 ip4:34.102.136.180 ip4:185.42.28.57 ip4:194.206.174.243 ip4:194.127.27.125 ip4:77.32.148.42 include:spf.allianz.com include:spf.postal.sensiwave.com include:spf.prosodie.net include:_spf.salesforce.com include:spf.mailjet.com include:_spf-dc33.sapsf.eu include:mx.arkea.com ~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.allianz.fr)

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.allianz.fr
External report address: mailto:Rua-allianz@allianz.com (authorized)
External report address: mailto:Ruf-allianz@allianz.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
rua	mailto:Rua-allianz@allianz.com	Aggregate report addresses
ruf	mailto:Ruf-allianz@allianz.com	Failure report addresses
fo	1	Failure reporting options
ri	3600	Report 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

warn

No keys found under the checked selectors

Found

Selectors: None found
_domainkey: NOERROR

Checks

!

No key under common selectors

The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

#7

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

Priority	Host	Records	Reverse DNS
10	mx1.hc1435-93.eu.iphmx.com	A 23.90.123.237 A 23.90.122.253	esa.hc1435-93.eu.iphmx.com ✓ esa.hc1435-93.eu.iphmx.com ✓
10	mx2.hc1435-93.eu.iphmx.com	A 23.90.122.253 A 23.90.123.237	esa.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 host	TLSA	DNSSEC
mx1.hc1435-93.eu.iphmx.com	none	-
mx2.hc1435-93.eu.iphmx.com	none	-

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

pass

https://vmc.digicert.com/82fb00f1-bb64-4012-87d9-1e85a1456348.svg

Found

Record: v=BIMI1;l=https://vmc.digicert.com/82fb00f1-bb64-4012-87d9-1e85a1456348.svg;a=https://vmc.digicert.com/5c182d62-9c6c-41e1-88e5-feb2ef26a418.pem;
Found at: default._bimi.allianz.fr
Logo: https://vmc.digicert.com/82fb00f1-bb64-4012-87d9-1e85a1456348.svg
Certificate: https://vmc.digicert.com/5c182d62-9c6c-41e1-88e5-feb2ef26a418.pem

Checks

✓ Logo and certificate published #38

BIMI logo: https://vmc.digicert.com/82fb00f1-bb64-4012-87d9-1e85a1456348.svg; certificate: https://vmc.digicert.com/5c182d62-9c6c-41e1-88e5-feb2ef26a418.pem
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.