Mail domain report: ensosp.fr

SPF

pass

SPF record published

Found

Record: v=spf1 include:mx.ovh.com mx ip4:37.58.177.64/28 ip4:37.58.177.240/29 ip4:85.115.32.0/19 ip4:85.115.32.0/19 ip4:86.111.216.0/23 ip4:116.50.56.0/21 ip4:208.87.232.0/21 ip4:86.111.220.0/22 ip4:103.1.196.0/22 ip4:177.39.96.0/22 ip4:196.216.238.0/23 ip4:80.74.77.110/32 include:cluster-z.mailcontrol.com include:spf.mailjet.com include:spf.protection.outlook.com -all
DNS lookups: 8 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 8 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.ensosp.fr)

Found

Record: v=DMARC1; p=none; aspf=r;
Found at: _dmarc.ensosp.fr

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
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.
!

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

DKIM

warn

Selectors: selector1, selector2

Found

Selectors: selector1, selector2
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 1024 bits
selector2	RSA 1024 bits

Checks

✓ Keys found: selector1, selector2 #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), selector2 (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

3 mail servers

Found

Priority	Host	Records	Reverse DNS
1	cust66029-1.in.mailcontrol.com	A 85.115.52.190	cluster-a.mailcontrol.com ✓
2	cust66029-2.in.mailcontrol.com	A 85.115.60.190	cluster-d.mailcontrol.com ✓
5	ensosp-fr.mail.protection.outlook.com	A 52.101.68.27 A 52.101.73.123 A 52.101.103.162 A 52.101.68.15 AAAA 2a01:111:f403:ca09::a AAAA 2a01:111:f403:ca04::10 AAAA 2a01:111:f403:ca09::28 AAAA 2a01:111:f403:ca09::20	mail-db7pr03cu00503.inbound.protection.outlook.com ✓ mail-am6pr02cu00203.inbound.protection.outlook.com ✓ mail-miypr03cu00202.inbound.protection.outlook.com ✓ mail-db6pr03cu00107.inbound.protection.outlook.com ✓ mail-am7pr02cu00202.inbound.protection.outlook.com ✓ mail-dbapr03cu00100.inbound.protection.outlook.com ✓ mail-am6pr02cu00300.inbound.protection.outlook.com ✓ mail-as8pr05cu00400.inbound.protection.outlook.com ✓

Checks

✓ 3 MX records #9

Found 3 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: cust66029-1.in.mailcontrol.com, cust66029-2.in.mailcontrol.com

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
cust66029-1.in.mailcontrol.com	none	-
cust66029-2.in.mailcontrol.com	none	-
ensosp-fr.mail.protection.outlook.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