Mail domain report: sante-ra.fr

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:194.56.95.4 ip4:194.167.143.180/32 ip4:195.254.161.233 ip4:195.254.161.235 ip4:195.254.161.195 a:smtp-pub.sante-ra.fr a:smtp0.sante-ra.fr a:smtp1.sante-ra.fr a:smtp2.sante-ra.fr a:smtp3.sante-ra.fr a:smtp.sante-ra.fr include:spf.protection.outlook.com ~all
DNS lookups: 7 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 7 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.sante-ra.fr)

Found

Record: v=DMARC1; p=none; rua=mailto:exploitPLH@espacecancer.sante-ra.fr
Found at: _dmarc.sante-ra.fr

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:exploitPLH@espacecancer.sante-ra.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:exploitPLH@espacecancer.sante-ra.fr
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

fail

Selectors: dkim, mail

Found

Selectors: dkim, mail
_domainkey: NOERROR

Selector	Key	Flags
dkim	RSA 768 bits	test mode (t=y)
mail	RSA 2048 bits	h=sha256

Checks

✓ Keys found: dkim, mail #7

DKIM keys found for this domain with selectors: dkim, mail
✗

Weak DKIM key

RSA keys shorter than 1024 bits can be cracked and are ignored by receivers (RFC 8301): dkim (768 bits). Rotate to a 2048-bit key.

#23
!

Key in test mode

These keys have t=y, so receivers treat DKIM failures as a test: dkim. Remove t=y once DKIM works.

#24

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

1 mail server

Found

Priority	Host	Records	Reverse DNS
0	santera-fr01c.mail.protection.outlook.com	A 52.101.103.137 A 52.101.68.21 A 52.101.73.123 A 52.101.103.162 AAAA 2a01:111:f403:ca3c::6 AAAA 2a01:111:f403:ca48::10 AAAA 2a01:111:f403:ca09::26 AAAA 2a01:111:f403:ca48::c	mail-miypr02cu00101.inbound.protection.outlook.com ✓ mail-db4pr02cu00205.inbound.protection.outlook.com ✓ mail-am6pr02cu00203.inbound.protection.outlook.com ✓ mail-miypr03cu00202.inbound.protection.outlook.com ✓ mail-zrxpr04cu00106.inbound.protection.outlook.com ✓ mail-miypr05cu00100.inbound.protection.outlook.com ✓ mail-am8pr83cu00106.inbound.protection.outlook.com ✓ mail-miypr03cu00104.inbound.protection.outlook.com ✓

Checks

✓ 1 MX record #9

Found 1 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.
!

Single MX host, no backup

Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
✓ At most 5 MX records #13

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
santera-fr01c.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