outlook.com
Live email deliverability and anti-spoofing audit. Every value below was read from public DNS at the moment this page was generated.
85/100 — Solid configuration with a few gaps worth closing. Accepts mail · Spoofable: anyone can forge this sender · Hosted by Microsoft 365
Findings
-
mx redundancy
Only one mail exchanger is published, so there is no failover.
outlook-com.olc.protection.outlook.com
Fix: Add a secondary MX at a higher priority number.
-
dmarc
DMARC is in monitoring mode (p=none), so spoofed mail is still delivered.
v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1
Fix: Move to p=quarantine and then p=reject once your reports show only legitimate senders failing.
-
mx
Mail is handled by Microsoft 365.
5 outlook-com.olc.protection.outlook.com
-
spf
SPF is published and enforcing.
v=spf1 include:spf2.outlook.com -all
-
dkim
DKIM keys found for 2 selectors.
selector1._domainkey, selector2._domainkey
-
mta sts
MTA-STS is published, so senders will refuse to downgrade to plaintext SMTP.
v=STSv1; id=20190225000000Z;
-
tls rpt
TLS reporting is enabled.
v=TLSRPTv1;rua=https://tlsrpt.azurewebsites.net/report
-
dnssec
DNSSEC is validating, so these records cannot be silently tampered with in transit.
AD flag set
Records
| MX | 5 outlook-com.olc.protection.outlook.com |
|---|---|
| SPF | v=spf1 include:spf2.outlook.com -all |
| DMARC | v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1 |
| DKIM selectors | selector1, selector2 |
| MTA-STS | published |
| TLS-RPT | published |
| BIMI | not published |
| DNSSEC | validating |
Same data, as JSON, in one request. No SMTP probing, no stored recipient data, 250 free calls a month.
curl "https://mailgrade.dev/v1/domain?domain=outlook.com"
Also available: /v1/verify?email=… for individual addresses, and
/v1/verify/batch for lists.