Mail domain report: flunch.fr

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.google.com include:amazonses.com ip4:62.160.65.242 ip4:212.31.129.106 ip4:34.252.31.96 ip4:35.181.25.130 ip4:5.135.233.59 ip4:52.51.186.35 ip4:185.225.64.14 ip4:185.225.64.16 ip4:185.225.64.55 ip4:213.41.42.93 ~all
DNS lookups: 2 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

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

fail

p=none (_dmarc.flunch.fr)

Found

Record: v=DMARC1; p=none;rua=mailto:rapports.dmarc@flunch.fr;
Found at: _dmarc.flunch.fr

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:rapports.dmarc@flunch.fr	Aggregate report addresses

Checks

✗

Policy: none (monitoring only)

DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:rapports.dmarc@flunch.fr
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

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

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

6 mail servers

Found

Priority	Host	Records	Reverse DNS
1	aspmx.l.google.com	A 142.251.127.27 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
5	alt1.aspmx.l.google.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1b	rd-in-f27.1e100.net ✓ rd-in-f27.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	aspmx2.googlemail.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1b	rd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
10	aspmx3.googlemail.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.1e100.net ✓

Checks

✓ 6 MX records #9

Found 6 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 6 MX records, which provides redundancy for email delivery.
!

More than 5 MX records

Found 6 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

#13
✓ 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 12 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 6 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	-
aspmx2.googlemail.com	none	-
aspmx3.googlemail.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