All data shown is public and sourced from DNS.
Last checked about 3 hours ago
legisocial.fr domain score
Your domain has strong email authentication. A few improvements can get you to a perfect score.
Top Recommendation
Add aggregate reporting (rua) to receive DMARC reports
DMARC improvement
legisocial.fr has a DMARC record but no reporting configured, limiting visibility into authentication results. SPF is correctly configured with a strict policy (-all), specifying which servers may send on its behalf. A few improvements would strengthen legisocial.fr's email authentication posture.
Curious how this compares? See the DMARC posture of the top 100 domains.
DMARC Check Results
35 / 50 points
Score Breakdown
Configuration issues detected
DMARC record is valid but no reporting email is configured.
Entry:
v=DMARC1; p=reject; sp=none; pct=100; adkim=r; aspf=r
Without a reporting address (rua), you won't receive aggregate reports from email providers. These reports show who is sending email as your domain and whether authentication passes or fails.
Read more: DMARC policy migration from p=none to p=reject.
Enable Reports Now
Great! You have a DMARC policy in place. Now start receiving reports in your own monitoring inbox to track email authentication results and identify potential issues.
- Automated DMARC report processing every 5 minutes
- Track all sending sources and authentication results
- Email alerts when your DNS records change
BIMI Check (default selector)
15 / 20 points
Score Breakdown
BIMI Record Found and Looks Good
Current BIMI Entry:
v=BIMI1;l=https://www.legisocial.fr/static/images/logos/favicon-abo.svg;a=
Logo URL
https://www.legisocial.fr/static/images/logos/favicon-abo.svg
image/svg+xml
Note: We do not parse SVG content for safety.
Mark Certificate
No certificate URL provided (a=). Optional when using self-asserted logos.
SPF Record Check Results
30 / 30 points
Score Breakdown
SPF record is valid.
legisocial.fr TXT SPF Entry:
v=spf1 ip4:89.30.106.0/24 ip4:185.32.96.0/22 ip4:185.32.97.64/26 mx include:amazonses.com include:spf.emailing.netlegis.fr -all
Syntax Check
OK
DNS Lookup Count
5 / 10 max
Root-level mechanisms requiring DNS queries: 3.
Void Lookups
1 / 2 max
Default Policy
-allFail: Reject emails from unauthorized servers (recommended for production)
All Authorized IP Addresses
Grouped by DNS record source (includes and sub-includes)
legisocial.fr (Root SPF Record)
This record also contains:
include:amazonses.com | Amazon SES
include:spf.emailing.netlegis.fr
DNS Lookup Details
mx:
legisocial.fr
MX records found: 1
MX Records:
include:
amazonses.com
| Amazon SES
SPF record found
legisocial.fr
TXT Record
v=spf1 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:76.223.176.0/20 ip4:54.240.64.0/18 ip4:76.223.128.0/19 ip4:216.221.160.0/19 ip4:206.55.144.0/20 ip4:24.110.64.0/18 -all
Processed recursively per RFC 7208
include:
spf.emailing.netlegis.fr
SPF record found
legisocial.fr
TXT Record
v=spf1 ip4:89.30.106.1/24 ip4:185.32.99.0/24 ip4:185.32.97.64/26 mx -all
Processed recursively per RFC 7208
mx:
spf.emailing.netlegis.fr
No MX records found
TLS Security
0 / 10 points
Score Breakdown
TLS-RPT (Reporting)
TLS-RPT Not Configured
Publish a TXT record at _smtp._tls.legisocial.fr with v=TLSRPTv1 and reporting URI (rua=).
MTA-STS (Policy)
MTA-STS Not Configured
Publish a TXT record at _mta-sts.legisocial.fr with v=STSv1 and policy ID (id=).
Protect inbound transport
You've checked your outbound authentication. But without MTA-STS and TLS-RPT, mail delivered to legisocial.fr isn't protected against transport downgrade attacks. Receiver Shield helps you deploy, monitor, and safely enforce transport security.
Know when your DNS records change
The check you just ran shows your current configuration. But DNS records change, sometimes without you knowing. A well-meaning IT change, a third-party provider update, or an unauthorized modification can break your email delivery overnight.
Configuration Drift
IT changes that accidentally break authentication
Provider Updates
Third-party services changing their SPF includes
Unauthorized Changes
Attackers modifying records to send as you
DMARCTrust monitors your DNS records continuously. When something changes, you get an email alert with exactly what changed and why it matters. No more surprises when customers complain their emails bounced.
Check Another Domain
Run a free email authentication check (DMARC, SPF, BIMI).
We will generate a shareable URL for your domain.
Try popular examples: google.com, amazon.com, booking.com
Explore other domains
Discover how other organizations configure their email authentication
Popular Domains
Frequently checked
Well-Configured
Reject policy + valid SPF
Same Policy
Also using reject
Showing domains checked by our users. All data is from public DNS records.
About This Checker
What we check
We analyze your domain's email authentication: DMARC policy and alignment, SPF record and includes, and BIMI logo and certificate status when present.
Why it matters
Healthy authentication improves delivery and blocks spoofing. Major inbox providers increasingly expect DMARC and aligned SPF/DKIM from senders.
Included features
- DMARC syntax, policy, and reporting validation
- SPF record evaluation and include analysis
- DKIM/SPF alignment interpretation
- BIMI record and VMC detection
- Clear setup and remediation guidance
Monitor your email authentication 24/7
This check shows a snapshot. With DMARCTrust, you get continuous monitoring of your DMARC reports and DNS records, with instant alerts when something changes.