Mail domain report: toutfaire.fr

SPF

pass

SPF record published

Found

Record: v=spf1 include:spf.protection.outlook.com include:mail.zendesk.com include:mailgun.org include:spf.mailjet.com include:_spf.google.com -all
DNS lookups: 9 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 9 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=reject (_dmarc.toutfaire.fr)

Found

Record: v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; ruf=mailto:dmarc@toutfaire.fr; fo=1
Found at: _dmarc.toutfaire.fr

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	reject	Subdomain policy
ruf	mailto:dmarc@toutfaire.fr	Failure report addresses
adkim	s	DKIM alignment (r = relaxed, s = strict)
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.
!

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: reject #20

Subdomains are covered by policy 'reject'.
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: selector1, selector2, google, mx

Found

Selectors: selector1, selector2, google, mx
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 2048 bits
selector2	RSA 2048 bits
google	RSA 2048 bits
mx	RSA 1024 bits

Checks

✓ Keys found: selector1, selector2, google, mx #7

DKIM keys found for this domain with selectors: selector1, selector2, google, mx
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mx (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

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-eu.emailsecurity.app	A 132.164.188.153	mx2-eu.emailsecurity.app (does not resolve back)
20	mx2-eu.emailsecurity.app	A 4.245.183.72	mx1-eu.emailsecurity.app (does not resolve back)

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-eu.emailsecurity.app, mx2-eu.emailsecurity.app

#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 does not match

The PTR name of these addresses does not resolve back to the same address: 132.164.188.153 -> mx2-eu.emailsecurity.app, 4.245.183.72 -> mx1-eu.emailsecurity.app.

#30

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx1-eu.emailsecurity.app	none	-
mx2-eu.emailsecurity.app	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