Mail domain report: domadoo.fr

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.google.com include:spf.brevo.com include:sendgrid.net -all
DNS lookups: 4 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 4 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.domadoo.fr)

Found

Record: v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com; pct=100; fo=1
Found at: _dmarc.domadoo.fr
External report address: mailto:rua@dmarc.brevo.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:rua@dmarc.brevo.com	Aggregate report addresses
fo	1	Failure reporting options

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:rua@dmarc.brevo.com
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, s2

Found

Selectors: mail, s2
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 1024 bits
s2	RSA 1024 bits

Checks

✓ Keys found: mail, s2 #7

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

1024-bit DKIM key

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

Signed, but no DS at parent

Found

DNSKEY records: Yes (2)
DS at parent: No
Algorithms: ECDSAP256SHA256 (13)
Key tags: 2371, 34505
Signatures valid until: 18 December 2026, 12:45 UTC

Checks

!

Signed, but no DS at parent

The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.

#8
✓ Signatures valid until 2026-12-18 #21

DNSKEY signatures are valid until 2026-12-18T12:45:09Z.

MX

pass

4 mail servers

Found

Priority	Host	Records	Reverse DNS
10	aspmx.l.google.com	A 142.251.127.27 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
20	alt1.aspmx.l.google.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1a	rd-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
30	alt2.aspmx.l.google.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
40	aspmx2.googlemail.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1b	rd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓

Checks

✓ 4 MX records #9

Found 4 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.
✓ Redundant MX hosts #12

Found 4 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 4 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

fail

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

Found

MTA-STS record: v=STSv1; id=20260605
Policy URL: https://mta-sts.domadoo.fr/.well-known/mta-sts.txt
Mode: enforce
Allowed MX: aspmx.l.google.com, *.aspmx.l.google.com
Max age: 86400 seconds

DANE (TLSA records)

MX host	TLSA	DNSSEC
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
aspmx2.googlemail.com	none	-

Checks

✓ Record published #32

MTA-STS record found with id 20260605.
✓ Policy enforced #33

The MTA-STS policy is enforced and cached for 24h0m0s.
✗

MX hosts missing from policy

These MX hosts are not listed in the MTA-STS policy (mx: aspmx.l.google.com, *.aspmx.l.google.com): aspmx2.googlemail.com. Senders that enforce MTA-STS will refuse to deliver to them.

#34
!

Not configured

MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".

#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