Mail domain report: departement18.fr

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:213.182.41.202 ip4:213.218.152.30 ip4:46.20.161.243 ip4:185.116.131.140 ip4:128.204.211.170 ip4:46.20.161.242 ip4:37.58.197.121 ip4:213.218.152.18 ip4:149.202.173.247 ip4:149.202.164.112 ip4:93.188.174.202 ip4:87.252.16.35 ip4:5.135.23.164 ip4:213.182.55.135 include:spf.protection.outlook.com include:amazonses.com include:spf-00a40801.pphosted.com include:spf.jobaffinity.fr include:spf.mailjet.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.departement18.fr)

Found

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

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:rapports-dmarc@secours.departement18.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@secours.departement18.fr
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: default, selector1

Found

Selectors: default, selector1
_domainkey: NOERROR

Selector	Key	Flags
default	RSA 2048 bits
selector1	RSA 1024 bits

Checks

✓ Keys found: default, selector1 #7

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

1024-bit DKIM key

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

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (2)
DS at parent: Yes
Algorithms: RSASHA256 (8)
Key tags: 63571, 54415
Signatures valid until: 14 November 2026, 06:46 UTC

Checks

✓ Signed, DS published at parent #8

DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
✓ Signatures valid until 2026-11-14 #21

DNSKEY signatures are valid until 2026-11-14T06:46:42Z.

MX

warn

2 mail servers

Found

Priority	Host	Records	Reverse DNS
1	mxa-00a40801.gslb.pphosted.com	A 66.159.244.180	mx07-00a40801.pphosted.com ✓
1	mxb-00a40801.gslb.pphosted.com	A 66.159.243.35	mx08-00a40801.pphosted.com ✓

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: mxa-00a40801.gslb.pphosted.com, mxb-00a40801.gslb.pphosted.com

#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 confirmed #30

All 2 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mxa-00a40801.gslb.pphosted.com	none	-
mxb-00a40801.gslb.pphosted.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