outlook.com
72/100
Mail provider: Microsoft 365
| Check | Details | |
|---|---|---|
| MX | ✔ | outlook-com.olc.protection.outlook.com |
| SPF | ⚠ | v=spf1 include:spf2.outlook.com -all (1 lookups); does not include Microsoft 365 (include:spf.protection.outlook.com) |
| DKIM | ✔ | Selectors found: selector1 (2048-bit+), selector2 (2048-bit+) |
| DMARC | ⚠ | v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1; p=none only monitors - spoofed mail is still delivered |
| MTA-STS | ✔ | mode: enforce |
| TLS-RPT | ✔ | v=TLSRPTv1;rua=https://tlsrpt.azurewebsites.net/report |
| BIMI | ℹ | Not set (optional; shows your logo in Gmail/Yahoo; needs DMARC quarantine/reject) |
How to fix it
- SPF — Update the TXT record at outlook.com (keeps your existing senders)
v=spf1 include:spf2.outlook.com include:spf.protection.outlook.com -all
- DMARC — Update TXT at _dmarc.outlook.com
v=DMARC1; p=quarantine; rua=mailto:dmarc@outlook.com; adkim=r; aspf=r; pct=100
DNS changes can take up to 24–48 hours. Re-run the check afterwards.
Want it fixed for you? I set up SPF, DKIM and DMARC without breaking your other senders,
with a before/after report.
Get it fixed on Fiverr
Get it fixed on Fiverr
Prefer to do it yourself? Get the step-by-step Fix Kit ($15) – 19-page guide, checklist, 20+ providers.