Mail domain report: ffplum.fr

SPF

pass

SPF record published

Found

Record: v=spf1 a mx ip4:178.33.242.115 ip4:51.38.210.102 ip4:164.132.235.17 ip4:87.98.154.146 ip4:145.239.37.162 ip4:172.246.35.166 include:spf.sendinblue.com -all
DNS lookups: 3 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 3 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.ffplum.fr)

Found

Record: v=DMARC1; p=reject; sp=reject; rua=mailto:ipm34yl@ar.glockapps.com,mailto:postmaster@ffplum.fr; ruf=mailto:ipm34yl@fr.glockapps.com; fo=1; aspf=s; pct=100;
Found at: _dmarc.ffplum.fr
External report address: mailto:ipm34yl@ar.glockapps.com (authorized)
External report address: mailto:ipm34yl@fr.glockapps.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	reject	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:ipm34yl@ar.glockapps.com,mailto:postmaster@ffplum.fr	Aggregate report addresses
ruf	mailto:ipm34yl@fr.glockapps.com	Failure report addresses
aspf	s	SPF alignment (r = relaxed, s = strict)
fo	1	Failure reporting options

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:ipm34yl@ar.glockapps.com, mailto:postmaster@ffplum.fr
✓ 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

Selectors: mail

Found

Selectors: mail
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 1024 bits

Checks

✓ Keys found: mail #7

DKIM keys found for this domain with selectors: mail
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits). Rotate to a 2048-bit key.

#23
✓ No problematic flags #24

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

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (2)
DS at parent: Yes
Algorithms: RSASHA256 (8)
Key tags: 19102, 34639
Signatures valid until: 20 November 2026, 04:26 UTC

Checks

✓ Signed, DS published at parent #8

DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
✓ Signatures valid until 2026-11-20 #21

DNSKEY signatures are valid until 2026-11-20T04:26:09Z.

MX

warn

4 mail servers

Found

Priority	Host	Records	Reverse DNS
1	mx1.mail.ovh.net	A 188.165.36.237	mx1.mail.ovh.net ✓
5	mx2.mail.ovh.net	A 87.98.160.167	mx2.mail.ovh.net ✓
100	mx3.mail.ovh.net	A 91.121.53.175	mx3.mail.ovh.net ✓
150	smtp.elasticemail.com	A 51.254.13.185	api.elasticemail.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: mx1.mail.ovh.net, mx2.mail.ovh.net, mx3.mail.ovh.net, smtp.elasticemail.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 host	TLSA	DNSSEC
mx1.mail.ovh.net	none	-
mx2.mail.ovh.net	none	-
mx3.mail.ovh.net	none	-
smtp.elasticemail.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

warn

https://ffplum.fr/images/logo-ffplum.svg

Found

Record: v=BIMI1; l=https://ffplum.fr/images/logo-ffplum.svg;
Found at: default._bimi.ffplum.fr
Logo: https://ffplum.fr/images/logo-ffplum.svg

Checks

!

No certificate (a=)

The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.

#38
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.