Provider deliverability · Hotmail / Outlook.com consumer inboxes

Why do emails go to junk in Hotmail and Outlook?

Samuel Chenard

By Samuel Chenard · CEO & Co-Founder, Palisade · Reviewed July 17, 2026

Emails go to junk in Hotmail and Outlook.com when Microsoft's SmartScreen filter distrusts the sender: missing or misaligned SPF, DKIM, or DMARC, a high junk-complaint rate, a new IP with no history, or a stale mailing list. Since May 2025, Microsoft's high-volume sender requirements make failing authentication a documented enforcement trigger: Junk placement first, then rejection. Fix authentication first; reputation follows.

The 30-second check

This page covers consumer inboxes: recipients at hotmail.com, live.com, and outlook.com addresses. (Mail junked inside a company's Microsoft 365 tenant is governed by that tenant's own policies; see the Microsoft 365 page instead.) Start by testing the domain you send from. The free Microsoft compliance checker verifies that your domain publishes the SPF, DKIM, and DMARC records Microsoft's requirements call for, so you can see at a glance which record is missing or broken.

Check your domain now

Enter your sending domain and the check runs instantly on the next page. Free, no signup.

Why Hotmail / Outlook.com consumer inboxes is blocking your email

Likely causeWhat's happening
Your domain fails SPF, DKIM, or DMARCSince May 5, 2025, Microsoft requires domains sending 5,000+ messages a day to its consumer addresses to pass SPF and DKIM and to publish a DMARC record of at least p=none that aligns with one of them. Microsoft's live postmaster page says non-compliant messages are sent to the Junk folder, with rejection to follow shortly; the announcement's April 29, 2025 update went further and said rejection (550 5.7.515) would apply from May 5, 2025. Either way, failing the requirements is the documented cause of Junk placement or worse (checked 2026-07-17). Below 5,000 a day, authentication still feeds SmartScreen's verdict on every message.
Recipients are clicking Junk on your mailMicrosoft's postmaster documentation states that one of the principal factors driving down a sender's reputation and deliverability is the junk email complaint rate. Every Hotmail recipient who junks your message votes against your next one. Microsoft publishes no numeric complaint threshold on its postmaster pages (checked 2026-07-17), so treat any visible complaint stream in JMRP as too high.
New IP or domain with no sending historySmartScreen scores on history, and a fresh IP has none. Microsoft's troubleshooting guidance says newly deployed IPs are more likely to experience deliverability issues, expects a new IP to be fully ramped within a couple of weeks or sooner depending on volume and list accuracy, and notes that an IP added to an authenticated SPF record can inherit some of the domain's reputation. Cold-starting at full volume reads as spam.
Stale list: dead Hotmail addresses and bouncesMicrosoft names list accuracy as a SmartScreen input alongside IP, domain, authentication, complaint rates, and content. Consumer Hotmail lists age badly; a list collected years ago is full of abandoned mailboxes, and the resulting bounce and complaint pattern marks you as a sender who doesn't manage their list. Microsoft's hygiene recommendations tell senders to remove invalid addresses regularly.
Your own DMARC policy is quarantining youIf your domain publishes p=quarantine and a legitimate sending service fails aligned SPF and DKIM, receivers are instructed to accept the mail but mark it. Microsoft's documentation describes quarantine handling as delivery to the Junk Email folder. In that case Junk placement is your own policy working as written against a source you never authenticated.
Missing unsubscribe link or misleading contentMicrosoft's sender requirements call for functional, clearly visible unsubscribe links, accurate subject lines, no deceptive headers, and recipient consent, and state that Outlook reserves the right to take negative action, including filtering, against senders with hygiene breaches. Mail with no opt-out route forces recipients to use the Junk button as their unsubscribe, which feeds the complaint-rate problem above.
Checklist card titled Six checks before you blame the Hotmail junk filter: SPF, DKIM, and DMARC pass and align with the From domain; junk-complaint rate under control via JMRP; sending IP and domain have history; the list is clean of dead addresses; your own p=quarantine DMARC policy is not junking unauthenticated services; unsubscribe link is visible and every recipient opted in

How to fix it, step by step

  1. Run the Microsoft compliance check on your sending domain

    Use the free checker above (or at /tools/microsoft-compliance-checker). It checks that your domain publishes the SPF, DKIM, and DMARC records Microsoft's requirements call for, so you know which record is missing or broken instead of guessing at content tweaks. To confirm messages actually pass with alignment, check real message headers in step 6.

  2. Authenticate every service that sends as your domain

    Add each sending platform to your SPF record, enable DKIM signing with your own domain rather than the provider's default, and publish a DMARC record. Microsoft requires the passing mechanism to align with your From domain; verify each piece with the free checkers at /tools/spf, /tools/dkim, and /tools/dmarc.

  3. Enroll in SNDS and JMRP

    Smart Network Data Services shows Microsoft's own verdict on your sending IPs, and the Junk Email Reporting Program sends you a report when Outlook.com users junk your messages. Together they turn 'Hotmail hates me' into a per-IP, per-campaign diagnosis using Microsoft's data instead of folklore.

  4. Remove the complaint drivers Microsoft names

    Make the unsubscribe link obvious and functional, keep subject lines accurate, send only to recipients who opted in, and confirm your From or Reply-To address is valid and can receive replies. These come straight from Microsoft's published hygiene recommendations, and they are what moves the complaint rate.

  5. Prune the list and warm up new IPs

    Drop addresses that bounce or never engage, then ramp volume gradually on any new IP. Microsoft expects a new IP to reach full ramp within a couple of weeks depending on volume and list accuracy, and an authenticated SPF record lets it inherit some of your domain's existing reputation.

  6. Re-test against a real Hotmail mailbox

    Send a test to an outlook.com or hotmail.com address, open the message headers, and confirm spf=pass, dkim=pass, and dmarc=pass. Then keep DMARC aggregate reports flowing so the next unauthenticated sender on your domain surfaces in a report instead of the Junk folder.

Related free tools: SPF checker · DKIM checker · DMARC checker · Domain reputation · Email security score

If you send in volume: Hotmail / Outlook.com consumer inboxes's published rules

Microsoft's high-volume sender requirements apply to its consumer service: hotmail.com, live.com, and outlook.com addresses. Domains sending more than 5,000 messages a day must pass SPF, pass DKIM, and publish DMARC at a minimum of p=none that aligns with SPF or DKIM (Microsoft says preferably both). Enforcement began May 5, 2025: Microsoft's postmaster page describes routing non-compliant mail to the Junk folder with rejection to follow, and the announcement's April 29, 2025 update said rejection (the 550 5.7.515 authentication-level bounce) would apply from that date. Microsoft also lists hygiene expectations by name: a valid From or Reply-To address that can receive replies, functional unsubscribe links, list and bounce management, and transparent mailing practices (announcement checked 2026-07-17). Below 5,000 a day the same checks still steer SmartScreen, so treat them as the baseline at any volume.

Check your standing with Hotmail / Outlook.com consumer inboxes

Bounce codes you may be seeing

Blocks in this cluster surface as specific SMTP codes. Match yours below; the linked guides cover each code's verbatim provider messages and full fix.

The real root cause: unenforced authentication

Junk placement at Hotmail is the early-warning stage of one loop. Unauthenticated or misaligned mail scores badly with SmartScreen, Junk placement invites complaints from the recipients who do find it, complaints drag reputation down further, and the endpoint is outright rejection under Microsoft's requirements. Microsoft's own framing on the SNDS site is that reputation is always the responsibility of the sender, and the part of reputation you control completely is authentication: correct SPF and DKIM for every sending service, DMARC alignment on the From domain, and a policy enforced at p=reject so spoofed mail stops burning the domain's name while you fix the rest. Monitoring shows you which senders are failing; enforcement is what makes the Junk folder stop being your default destination.

Enforce it — don't just monitor it

Palisade's AI agent takes domains all the way to enforcement: hosted SPF, DKIM, DMARC, and MTA-STS records, DMARC reports monitored continuously, and policies advanced to p=reject automatically. Your first domain is free, and the full product is open for 15 days, no card.

Start free trialBook a demo

Free 15-day trial · No credit card · Your own domain free forever (NFR)

Fixing this across every client domain

When one client's newsletter lands in Junk at Hotmail, the ticket says 'email is broken' and the diagnosis spans SPF, DKIM, DMARC, SNDS, JMRP, and list hygiene, per domain, for every client on your books. Palisade collapses that into one workflow: it hosts and manages the SPF, DKIM, DMARC, and MTA-STS records for every client domain, surfaces failing or unauthenticated senders from DMARC reports before Microsoft's filter reacts, and walks each domain to p=reject automatically. Tickets land in ConnectWise, HaloPSA, or Autotask through native PSA integrations, pricing is per domain ($9, dropping to $7 at 100+ and $5 at 1,000+), and your own MSP domain runs free as an NFR domain to prove it on.

Frequently asked questions

Persistent junking means a standing signal, not a one-off: usually an authentication record that fails or misaligns on every send, a complaint rate SmartScreen keeps counting, or a list full of dead Hotmail addresses. Run the compliance check first; content tweaks won't outweigh a failing SPF, DKIM, or DMARC record.

Passing isn't aligning. Microsoft's DMARC requirement wants the passing domain to match your From domain, and a signature for your ESP's domain doesn't count. If alignment is genuinely clean, the remaining drivers are reputation: complaint rate, new-IP history, and list accuracy, all visible through SNDS and JMRP.

Hotmail's spam folder and Outlook.com's Junk folder are the same thing behind the same filter. Fix authentication to Microsoft's published bar (SPF, DKIM, aligned DMARC), enroll in SNDS and JMRP, add a visible unsubscribe link, and prune non-engaging addresses. The step-by-step fix above covers each in order.

No. Microsoft's postmaster pages name the junk email complaint rate as one of the principal factors dragging down reputation and deliverability, but publish no numeric ceiling (checked 2026-07-17). Practically, enroll in JMRP, watch which sends generate junk reports, and cut those segments before the rate compounds.

No. hotmail.com, live.com, and outlook.com addresses all ride the same Outlook.com consumer infrastructure, and Microsoft's high-volume sender requirements name all three. Individual recipients still have their own Safe Senders lists and junk settings, but a sender-side fix (authentication, reputation, list hygiene) applies to the whole family at once.

Different machines. Consumer Hotmail and Outlook.com placement comes from Microsoft's SmartScreen filter and sender requirements, which you fix from the sending side. A work mailbox sits in a Microsoft 365 tenant where that organization's anti-spam and anti-phishing policies decide, including how sender DMARC policies are honored. See the Microsoft 365 page for that path.

Each provider scores you on its own data. Microsoft's SmartScreen weighs its own complaint reports, its own view of your IP history, and its own list-accuracy signals, none of which Gmail shares. Passing at Gmail proves your DNS basics; it says nothing about your standing in SNDS or your JMRP complaint stream.

Yes, if the IP is new. Microsoft says newly deployed IPs are more likely to hit deliverability issues and expects full ramp within a couple of weeks or sooner, depending on volume and list accuracy. Adding the IP to an already-authenticated SPF record lets it inherit some of your domain's reputation.

Related guides

Why is Outlook blocking my emails?How to stop emails going to spam in OutlookWhy is Microsoft 365 blocking outbound emails?Why does Outlook move emails to junk after they arrive?550 5.7.509421 4.7.0550 5.7.1p=quarantineadkim / aspfinclude:
Email deliverability, fixed: the full guide