Mail domain report: communaute-paysbasque.fr

SPF

fail

SPF record published

Found

Record: v=spf1 include:_mail.incafu.com include:spf.protection.outlook.com include:spf4.sbr-master.net include:spf.ags-cloud.fr ip4:46.105.105.190/32 ip4:193.51.153.137/32 ip4:46.105.156.0/27 ip4:176.31.192.128/25 ip4:82.206.252.215/32 ip4:51.254.117.126/32 ip4:51.138.90.21/32 ip4:185.65.80.95 ip4:37.59.14.114/32 ip4:145.239.15.29 ip4:37.59.149.181/32 ip4:37.59.149.182/32 ip4:51.159.92.149/32 ip4:176.31.192.231 ip4:193.142.131.0/26 ip4:81.88.52.26 ip4:213.32.80.116 ip4:193.142.131.52 ip4:23.26.226.0/24 ip4:83.206.252.128/32 ip4:77.77.159.58/26 ip4:145.239.119.10 ip4:77.77.159.57 ~all
DNS lookups: 11 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✗

11 DNS lookups, over the limit of 10

SPF record needs 11 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.

#2
✓ 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=quarantine (_dmarc.communaute-paysbasque.fr)

Found

Record: v=DMARC1; p=quarantine; sp=none; rua=mailto:dmarc@mailinblue.com!10m; ruf=mailto:dmarc@mailinblue.com!10m;
Found at: _dmarc.communaute-paysbasque.fr
External report address: mailto:dmarc@mailinblue.com!10m (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	none	Subdomain policy
rua	mailto:dmarc@mailinblue.com!10m	Aggregate report addresses
ruf	mailto:dmarc@mailinblue.com!10m	Failure report addresses

Checks

!

Policy: quarantine

DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
✓ 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.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:dmarc@mailinblue.com!10m
!

Subdomains unprotected (sp=none)

DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

#20
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, k1, selector1

Found

Selectors: mail, k1, selector1
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 1024 bits
k1	RSA 1024 bits
selector1	RSA 1024 bits

Checks

✓ Keys found: mail, k1, selector1 #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), k1 (1024 bits), 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: 59975, 63864
Signatures valid until: 20 November 2026, 12:33 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-20 #21

DNSKEY signatures are valid until 2026-11-20T12:33:00Z.

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
0	communautepaysbasque-fr02e.mail.protection.outlook.com	A 52.101.91.153 A 52.101.181.153 A 52.101.185.24 A 52.101.103.36 AAAA 2a01:111:f403:ca38::8 AAAA 2a01:111:f403:c967::8 AAAA 2a01:111:f403:ca48::12 AAAA 2a01:111:f403:ca3c::8	mail-matpr04cu00101.inbound.protection.outlook.com ✓ mail-wa4pr04cu00101.inbound.protection.outlook.com ✓ mail-zrxpr07cu00100.inbound.protection.outlook.com ✓ mail-miypr05cu00104.inbound.protection.outlook.com ✓ mail-wa4pr04cu00100.inbound.protection.outlook.com ✓ mail-cpjpr04cu00100.inbound.protection.outlook.com ✓ mail-miypr05cu00202.inbound.protection.outlook.com ✓ mail-zrxpr05cu00100.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
communautepaysbasque-fr02e.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