Email authentication check

cinemi.fr

This check reviews the domain's email authentication setup to help protect against spoofing and phishing.

All data is public, sourced from DNS Last checked about 17 hours ago
Strong setup

cinemi.fr has email authentication in place, with important improvements still available.

cinemi.fr publishes strong public DNS records for email authentication and transport security.

91 out of 110
2 of 4 checks passed
Last checked about 17 hours ago
Compare with other domains

DMARC

Passed

Domain-based Message Authentication

50 / 50

Strict reject policy enforced

DMARC record is valid and configured correctly.

_dmarc.cinemi.fr TXT
v=DMARC1;p=reject;sp=none;pct=100;rua=mailto:[email protected];ruf=mailto:[email protected];ri=86400;aspf=s;adkim=s;fo=1;

Score breakdown

  • DMARC record published +10
  • Syntax valid +5
  • Reject policy (maximum protection) +20
  • Aggregate reporting (rua) configured and verified +10
  • Failure reporting (ruf) configured +5

Configuration

Policy (p)
reject
DKIM alignment (adkim)
Strict (s)
SPF alignment (aspf)
Strict (s)
Subdomain policy (sp)
none
Failure reporting (fo)
1

Reporting (RUA / RUF)

Aggregate reports Passed
External domain verification successful
Failure reports Passed
External domain verification successful
RFC 9989 note on p=reject
RFC 9989 cautions against p=reject for domains whose users post to mailing lists, and §7.4 requires receivers to treat p=reject as p=quarantine unless their own analysis justifies rejecting. For transactional or marketing-only domains, p=reject stays appropriate; mailbox domains should consider p=quarantine with sp=reject on non-sending subdomains.
Record uses tags removed by RFC 9989
RFC 9989 (May 2026) removed the pct tag. Use t=y for staged rollouts instead. RFC 9989 (May 2026) removed the ri tag. Receivers send aggregate reports daily regardless.

SPF

Optional

Sender Policy Framework

26 / 30

SPF record is valid

SPF record is valid and complies with RFC 7208.

cinemi.fr TXT
v=spf1 include:mx.ovh.com ~all

Score breakdown

  • SPF record published +10
  • Syntax valid +5
  • Soft fail policy (~all) +6
  • No configuration warnings +5

Configuration

Default policy
~all (soft fail)
DNS lookups
3 / 10 max
Void lookups
0 / 2 max
Syntax check
OK

DNS lookup detail

Each mechanism that may trigger a DNS query at delivery time.

1 include: mx.ovh.com Valid

SPF record found

v=spf1 ptr:mail-out.ovh.net ptr:mail.ovh.net ip4:8.33.137.105/32 ip4:192.99.77.81/32 ?all

Processed recursively per RFC 7208

2 ptr: mail-out.ovh.net Not implemented

PTR mechanism found but not fully implemented (discouraged)

3 ptr: mail.ovh.net Not implemented

PTR mechanism found but not fully implemented (discouraged)

Authorized IP addresses

include:mx.ovh.com

8.33.137.105/32 192.99.77.81/32

BIMI

Failed

Brand Indicators for Message Identification

5 / 20

BIMI record has configuration errors

Logo URL not reachable or not served as SVG

default._bimi.cinemi.fr TXT
v=BIMI1;l=https://www.cinemi.fr/images/Cinemi-logo-2024-noir-02_tiny_ps.svg;

Score breakdown

  • BIMI record published +5
  • BIMI record valid 0 / 5
  • Logo URL accessible and valid SVG 0 / 5
  • No VMC certificate configured (optional) 0 / 5

Configuration

Logo (l)
text/html; charset=iso-8859-1
Mark certificate (a)
Not configured
Selector
default
Note
SVG content is not parsed, for safety

TLS

Passed

Transport security · MTA-STS & TLS-RPT

10 / 10

Inbound transport protection configured

cinemi.fr publishes both TLS-RPT reporting and MTA-STS policy records.

Score breakdown

  • TLS-RPT record configured +5
  • MTA-STS policy configured +5

Configuration

TLS-RPT
Configured
MTA-STS
Configured
TLS-RPT reporting URIs
mailto:[email protected]
MTA-STS policy ID
none

Transport checks

TLS-RPT (reporting) Configured
v=TLSRPTv1; rua=mailto:[email protected]

TLS-RPT record is valid and configured correctly.

MTA-STS (policy) Configured
v=STSv1; id=none

MTA-STS record is valid and configured correctly.

cinemi.fr enforces a strict DMARC reject policy, instructing receivers to block unauthenticated emails. SPF is published with a soft fail policy (~all), flagging unauthorized senders without blocking them. Overall, cinemi.fr has solid email authentication with room for minor improvements.

Keep cinemi.fr protected automatically

This check is a snapshot. DNS records drift when providers change, teams edit records, or unauthorized changes slip in. DMARCTrust watches the same authentication layer continuously and tells you when something moves.

DMARC report processing

Aggregate and failure DMARC reports are received, parsed, and turned into sender visibility without manual XML handling.

DNS change alerts

DNS checks run every 5 minutes for monitored domains, with email alerts when DMARC, SPF, BIMI, TLS-RPT, or MTA-STS records change.

Receiver Shield for inbound

Deploy, host, and safely enforce MTA-STS and TLS-RPT when this checker finds an inbound transport gap.

Start monitoring cinemi.fr View plans First checked about 2 months ago

Check another domain

Run a free email authentication check: DMARC, SPF, BIMI, TLS-RPT, and MTA-STS.

Try a popular example: google.com, amazon.com, booking.com
Explore

How other domains configure email authentication

Showing domains checked by our users. All data is from public DNS records.

Popular domains

Frequently checked

Well configured

Reject policy + valid SPF

Same policy

Also using reject

What we check

DMARC policy and alignment, SPF record and includes, BIMI logo and certificate, and inbound transport security with MTA-STS and TLS-RPT.

Why it matters

Healthy authentication improves delivery and blocks spoofing. Major inbox providers increasingly expect DMARC and aligned SPF or DKIM from senders.

What you get

Syntax, policy, reporting validation, include analysis, alignment interpretation, and clear setup guidance for every result.