Mail domain report: acpm.fr

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:83.143.18.0/24 ip4:185.51.219.41/32 include:_spf.google.com include:spf.mailjet.com include:spf.activemailer.pro include:helpscoutemail.com include:spf.mandrillapp.com ~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

warn

p=quarantine (_dmarc.acpm.fr)

Found

Record: v=DMARC1; p=quarantine; pct=100;
Found at: _dmarc.acpm.fr

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
pct	100	Percentage of mail the policy applies to

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.
!

No aggregate reports (rua)

DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.

DKIM

pass

Selectors: google

Found

Selectors: google
_domainkey: NOERROR

Selector	Key	Flags
google	RSA 2048 bits

Checks

✓ Keys found: google #7

DKIM keys found for this domain with selectors: google
✓ Strong keys #23

DKIM keys are strong enough: google: RSA 2048 bits.
✓ No problematic flags #24

No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Signed, but no DS at parent

Found

DNSKEY records: Yes (2)
DS at parent: No
Algorithms: ECDSAP256SHA256 (13)
Key tags: 34505, 2371
Signatures valid until: 6 December 2026, 12:57 UTC

Checks

!

Signed, but no DS at parent

The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.

#8
✓ Signatures valid until 2026-12-06 #21

DNSKEY signatures are valid until 2026-12-06T12:57:04Z.

MX

pass

5 mail servers

Found

Priority	Host	Records	Reverse DNS
1	aspmx.l.google.com	A 142.251.127.26 AAAA 2a00:1450:4001:c21::1a	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
5	alt1.aspmx.l.google.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1a	rd-in-f27.1e100.net ✓ rd-in-f26.1e100.net ✓
5	alt2.aspmx.l.google.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1a	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
10	alt3.aspmx.l.google.com	A 192.179.20.27 AAAA 2404:6800:4000:1027::1b	ncboms-in-f27.1e100.net ✓ ncboms-in-f27.1e100.net ✓
10	alt4.aspmx.l.google.com	A 192.178.158.27 AAAA 2404:6800:4013:813::1a	lcdels-in-f27.1e100.net ✓ lcdels-in-f26.1e100.net ✓

Checks

✓ 5 MX records #9

Found 5 MX records for this domain.
✓ All hosts resolve #10

All MX records resolve to valid IP addresses.
✓ All hosts have IPv6 #11

All MX records resolve to IPv6 addresses.
✓ Redundant MX hosts #12

Found 5 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 5 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 10 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
alt3.aspmx.l.google.com	none	-
alt4.aspmx.l.google.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.eu/faea30c1-b6a2-420e-9593-6953a709a786.svg

Found

Record: v=BIMI1; l=https://vmc.digicert.eu/faea30c1-b6a2-420e-9593-6953a709a786.svg; a=https://vmc.digicert.eu/faea30c1-b6a2-420e-9593-6953a709a786.pem
Found at: default._bimi.acpm.fr
Logo: https://vmc.digicert.eu/faea30c1-b6a2-420e-9593-6953a709a786.svg
Certificate: https://vmc.digicert.eu/faea30c1-b6a2-420e-9593-6953a709a786.pem

Checks

✓ Logo and certificate published #38

BIMI logo: https://vmc.digicert.eu/faea30c1-b6a2-420e-9593-6953a709a786.svg; certificate: https://vmc.digicert.eu/faea30c1-b6a2-420e-9593-6953a709a786.pem
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.