Only SPF is configured. Your domain needs SPF, DKIM, and DMARC working together to prevent spoofing.
| Protocol | Status | Score |
|---|---|---|
| DMARC | Monitor Only | 19 / 35 |
| SPF | Soft Fail (~all) | 21 / 25 |
| DKIM | Not Detected | 0 / 20 |
| MTA-STS | Not Configured | 0 / 10 |
| TLS-RPT | Not Configured | 0 / 5 |
| BIMI | Not Found | 0 / 5 |
Assessment of fbcdn.net against major email security compliance frameworks.
| Framework | Reference | Requirements | Status |
|---|---|---|---|
| PCI DSS 4.0 | Req 5.4.1 | DMARC + SPF + DKIM | Partial |
| Google / Yahoo Bulk Sender | 2024 Requirements | DMARC + SPF + DKIM | Partial |
| NIST SP 800-177 | Rev. 1 | SPF + DKIM + DMARC | Partial |
| CISA BOD 18-01 | Binding Operational Directive | DMARC (p=reject) | Non-Compliant |
| Cyber Essentials | UK NCSC | DMARC + SPF | Partial |
DMARC policy is set to none (monitor only). Unauthorized emails are still delivered.
| Policy | none |
| Aggregate Reporting | mailto:a@dmarc.facebookmail.com |
| Subdomain Policy | none |
| DKIM Alignment | relaxed |
| SPF Alignment | relaxed |
SPF record found with 2 DNS lookups and ~all.
| All Mechanism | ~all (soft fail) |
| DNS Lookups | 2/10 |
| Record Length | 13 bytes |
No DKIM record found for common selectors on fbcdn.net. DKIM may use a custom selector that could not be auto-detected.
Transport-layer email security protocols that protect messages in transit between mail servers.
No MTA-STS record found for fbcdn.net. Inbound SMTP connections are vulnerable to TLS downgrade attacks.
No TLS-RPT record found for fbcdn.net. TLS delivery failures are invisible.
No BIMI record found for fbcdn.net. Brand logo will not appear in supporting email clients.
Prioritized findings and recommended fixes. These can be implemented by your internal IT team, or you can use Authex to monitor, manage, and automate these changes with our AI-powered platform starting at $9/domain per month.
| # | Protocol | Finding | Severity | Fix |
|---|---|---|---|---|
| 1 | DKIM | Not Detected | High | Ensure your email provider has published DKIM keys. If using a custom selector, DKIM may still be active. |
| 2 | MTA-STS | Not Configured | High | Publish an MTA-STS TXT record and host a policy file at https://mta-sts.yourdomain/.well-known/mta-sts.txt. |
| 3 | TLS-RPT | Not Configured | High | Publish a TLS-RPT record to receive reports when sending servers fail to establish encrypted connections. |
| 4 | BIMI | Not Found | High | Publish a BIMI record with your brand SVG logo. Requires DMARC at p=quarantine or p=reject with pct=100. |
| 5 | DMARC | Monitor Only | Medium | Progress to p=quarantine and then p=reject once you have identified all legitimate senders via RUA reports. |
| 6 | SPF | Soft Fail (~all) | Low | Consider tightening to -all for stricter enforcement alongside your DMARC policy. |
Authex continuously monitors your email authentication, detects misconfigurations, and helps you fix them. Our AI agent handles SPF flattening, DKIM rotation, and DMARC enforcement automatically. DIY plans start at $9/domain. Managed plans include a dedicated security engineer. Visit authex.online to get started with a free scan.
| Protocol | Max Points | Weight |
|---|---|---|
| DMARC | 35 | 35% |
| SPF | 25 | 25% |
| DKIM | 20 | 20% |
| MTA-STS | 10 | 10% |
| TLS-RPT | 5 | 5% |
| BIMI | 5 | 5% |
| Grade | Score Range |
|---|---|
| A+ | 95 - 100 |
| A | 85 - 94 |
| B | 70 - 84 |
| C | 50 - 69 |
| D | 30 - 49 |
| F | 0 - 29 |