Mail domain report: actual-immo.fr

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.mx.cloudflare.net include:spf.infomaniak.ch include:_spf.google.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

fail

p=none (_dmarc.actual-immo.fr)

Found

Record: v=DMARC1; p=none; rua=mailto:cyril@actual-immo.fr; adkim=r; aspf=r
Found at: _dmarc.actual-immo.fr

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:cyril@actual-immo.fr	Aggregate report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)

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:cyril@actual-immo.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

pass

3 mail servers

Found

Priority	Host	Records	Reverse DNS
24	route3.mx.cloudflare.net	A 162.159.205.25 A 162.159.205.24 A 162.159.205.23 AAAA 2606:4700:f5::12 AAAA 2606:4700:f5::13 AAAA 2606:4700:f5::11	route3.mx.cloudflare.net ✓ route3.mx.cloudflare.net ✓ route3.mx.cloudflare.net ✓ route3.mx.cloudflare.net ✓ route3.mx.cloudflare.net ✓ route3.mx.cloudflare.net ✓
49	route2.mx.cloudflare.net	A 162.159.205.18 A 162.159.205.17 A 162.159.205.19 AAAA 2606:4700:f5::f AAAA 2606:4700:f5::10 AAAA 2606:4700:f5::e	route2.mx.cloudflare.net ✓ route2.mx.cloudflare.net ✓ route2.mx.cloudflare.net ✓ route2.mx.cloudflare.net ✓ route2.mx.cloudflare.net ✓ route2.mx.cloudflare.net ✓
99	route1.mx.cloudflare.net	A 162.159.205.13 A 162.159.205.12 A 162.159.205.11 AAAA 2606:4700:f5::c AAAA 2606:4700:f5::d AAAA 2606:4700:f5::b	route1.mx.cloudflare.net ✓ route1.mx.cloudflare.net ✓ route1.mx.cloudflare.net ✓ route1.mx.cloudflare.net ✓ route1.mx.cloudflare.net ✓ route1.mx.cloudflare.net ✓

Checks

✓ 3 MX records #9

Found 3 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 3 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
route3.mx.cloudflare.net	2 1 1 59e738e674221702… 3 1 1 0f0c6c164a36f97e… 3 1 1 9be5b7d47f9eff93…	Yes
route2.mx.cloudflare.net	2 1 1 59e738e674221702… 3 1 1 0f0c6c164a36f97e… 3 1 1 9be5b7d47f9eff93…	Yes
route1.mx.cloudflare.net	3 1 1 9be5b7d47f9eff93… 3 1 1 0f0c6c164a36f97e… 2 1 1 59e738e674221702…	Yes

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
!

Not configured

MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".

#35
✓ DANE on all MX hosts #36

All 3 MX hosts publish DNSSEC-validated TLSA records.

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