Mail domain report: monoprix.fr

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:94.199.92.0/23 ip4:103.196.252.0/23 ip4:185.93.140.0/22 ip4:185.215.216.0/22 ip4:207.126.136.0/22 ip4:199.204.12.0/22 include:_spf.salesforce.com ip6:2a02:7b01:1000:42::1:0/114 ip6:2a02:7b01:2000:42::1:0/114 ip6:2a02:7b02:2000:42::1:0/114 ip6:2a02:7b02:0:42::1:0/114 ip6:2a02:7b03:0:42::1:0/114 ip4:5.39.8.116 ip4:5.39.8.122 ip4:5.39.8.123 ip4:20.74.37.146 ip4:20.74.97.162 ip4:20.74.99.62 ip4:37.26.186.156 ip4:37.26.186.158 ip4:46.137.124.132 ip4:54.229.107.2 ip4:34.240.252.50 ip4:34.252.193.151 ip4:54.171.91.37 ip4:52.30.26.187 ip4:86.104.181.16 ip4:194.2.122.190 ip4:195.25.67.22 ip4:104.46.62.125 ip4:167.89.67.207 ip4:209.85.220.41 ip4:209.85.220.69 ip4:5.39.31.8 ip4:5.39.31.9 ip4:95.131.139.228 ip4:94.125.168.227 ip4:94.125.168.228 ip4:83.145.109.0/24 ip4:31.172.161.0/24 ip4:78.153.243.64/26 ip4:91.212.152.0/24 ip4:195.167.226.128/26 ip4:195.167.228.208/28 ip4:185.51.216.86 ip4:51.77.185.250 ip4:178.33.104.94 ip6:2a01:0240:ab0b:fffe:0078:0153:0243:0000/112 ip4:94.199.90.95 ip4:94.199.88.74 ip4:94.199.90.91 ip4:94.199.90.92 ip4:94.199.90.85 ip4:94.199.90.90 ip4:94.199.88.75 ip4:94.199.90.94 ip4:94.199.88.76 ip4:94.199.88.78 ip4:94.199.88.101 ip4:62.245.148.41 ip4:54.216.148.164 ip4:52.210.242.66 ip4:34.243.30.142 ip4:3.250.248.228 ip4:91.188.69.49 ip4:213.182.36.41 ip4:213.139.100.32/27 ip4:213.139.122.32/27 ip4:213.139.117.32/27 ip4:213.139.101.32/27 ip4:195.46.216.96/28 ip4:178.22.157.0/29 ip4:213.139.122.176/29 ip4:80.253.212.0/24 ip4:212.37.192.0/19 ip4:213.41.78.164 ip4:213.41.78.165 ip4:213.41.78.180 ip4:213.41.78.182 ip4:213.41.78.174 ip4:213.41.78.175 ip4:94.125.168.150 ip4:94.125.168.151 ip4:159.183.179.228 exists:%{i}.spf.hc1583-69.eu.iphmx.com include:spf.protection.outlook.com include:amazonses.com include:spf.cloud.vadesecure.com include:spf.mailjet.com -all
DNS lookups: 7 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 7 of 10 DNS lookups #2

SPF record needs 7 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

warn

p=quarantine (_dmarc.monoprix.fr)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:e6xigpnvei@rua.powerdmarc.com,mailto:ardmarc@fp-lp.fr; ruf=mailto:e6xigpnvei@ruf.powerdmarc.com,mailto:frdmarc@fp-lp.fr; fo=0:1:d:s; pct=100;
Found at: _dmarc.monoprix.fr
External report address: mailto:e6xigpnvei@rua.powerdmarc.com (authorized)
External report address: mailto:ardmarc@fp-lp.fr (authorized)
External report address: mailto:e6xigpnvei@ruf.powerdmarc.com (authorized)
External report address: mailto:frdmarc@fp-lp.fr (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:e6xigpnvei@rua.powerdmarc.com,mailto:ardmarc@fp-lp.fr	Aggregate report addresses
ruf	mailto:e6xigpnvei@ruf.powerdmarc.com,mailto:frdmarc@fp-lp.fr	Failure report addresses
fo	0:1:d:s	Failure reporting options

Checks

!

Policy: quarantine

DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
✓ 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:e6xigpnvei@rua.powerdmarc.com, mailto:ardmarc@fp-lp.fr
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

pass

Selectors: selector1, selector2, s1, s2

Found

Selectors: selector1, selector2, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 2048 bits
selector2	RSA 2048 bits
s1	RSA 2048 bits
s2	RSA 2048 bits

Checks

✓ Keys found: selector1, selector2, s1, s2 #7

DKIM keys found for this domain with selectors: selector1, selector2, s1, s2
✓ Strong keys #23

DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits; 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

Priority	Host	Records	Reverse DNS
10	mx1.hc1583-69.eu.iphmx.com	A 23.90.117.237 A 23.90.118.55	esa.hc1583-69.eu.iphmx.com ✓ esa.hc1583-69.eu.iphmx.com ✓
10	mx2.hc1583-69.eu.iphmx.com	A 23.90.118.55 A 23.90.117.237	esa.hc1583-69.eu.iphmx.com ✓ esa.hc1583-69.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.hc1583-69.eu.iphmx.com, mx2.hc1583-69.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.hc1583-69.eu.iphmx.com	none	-
mx2.hc1583-69.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

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