Microsoft Compliance
Check Outlook.com / Microsoft sender requirements.
Enter a value above to run Microsoft Compliance
e.g. example.com
Quick answer
This tool checks whether your domain meets Microsoft's sender requirements for delivery to Outlook.com, Hotmail, and Microsoft 365 inboxes, verifying SPF, DKIM, DMARC, and reverse DNS. Passing results mean your mail is aligned with Microsoft's rules; failures point to the specific record blocking your delivery.
Microsoft Compliance checks whether your sending domain meets the requirements Outlook.com, Hotmail, and Microsoft 365 apply to inbound mail. Microsoft has its own filtering pipeline and its own bar for accepting messages, separate from Gmail's. This tool inspects the DNS records and sender signals that Microsoft weighs most heavily: SPF, DKIM signing, a DMARC policy, valid reverse DNS on your sending IP, and whether that IP appears on Microsoft's blocklists. It surfaces the gaps that most often cause mail to land in Junk or get rejected outright.
How it works
The tool queries public DNS for your domain's SPF, DKIM, and DMARC records and validates their syntax against what Microsoft's filters expect. It also checks the sending IP for a matching PTR (reverse DNS) record and looks for signs of Microsoft-specific blocking. Microsoft weighs sender reputation, authentication alignment, and rDNS more strictly than many providers, so each check maps to a concrete reason a message might be filtered.
How to read the results
A pass on SPF, DKIM, and DMARC means your mail is authenticated the way Microsoft prefers, with DMARC alignment reducing spoofing suspicion. Warnings usually point to a missing PTR record, an SPF record that is too permissive or exceeds ten lookups, or no DMARC policy at all. Treat a listing on Microsoft's blocklist as urgent: it blocks delivery to every Outlook and Microsoft 365 mailbox until resolved.
Common problems & fixes
Missing reverse DNS is the most frequent cause of Junk placement; ask your host or cloud provider to set a PTR that resolves back to your mail hostname. If you are blocklisted, use Microsoft's Sender Support and SNDS programs to request delisting after fixing the root cause. For bulk senders, enroll in the Junk Mail Reporting Program (JMRP) so complaints reach you, and keep DKIM signing active on every stream.
Frequently asked questions
- Why does my mail reach Gmail fine but land in Outlook Junk?
- Microsoft runs an independent filter and reputation system. Common differences include stricter reverse DNS enforcement, its own IP blocklists, and heavier weight on DMARC alignment. Mail that Gmail accepts can still be junked by Outlook if your PTR record is missing, your IP has low reputation, or your SPF and DKIM do not both align with the From domain.
- How do I request delisting from Microsoft's blocklist?
- First fix whatever caused the listing: secure any compromised accounts, stop the spam source, and confirm SPF, DKIM, DMARC, and PTR are correct. Then submit a delisting request through Microsoft's Sender Support form. Enrolling your IP ranges in SNDS gives you visibility into spam-trap hits and complaint rates that Microsoft uses when evaluating your reputation.
- Does this tool guarantee delivery to Outlook.com?
- No tool can guarantee inbox placement. This check confirms your technical prerequisites are correct, which removes the most common reasons Microsoft filters or rejects mail. Actual placement still depends on ongoing sending reputation, recipient engagement, complaint rates, and content. Passing every check makes delivery far more likely but does not override a poor sending history.