Inbox Placement Test and Email Deliverability Checker for Gmail and Outlook

An inbox placement test checks where your emails actually land and why. It combines message receipt checks with authentication, content, and sender-quality diagnostics so teams can distinguish "accepted by the server" from "visible in the inbox."

Use this workflow when you need to check email deliverability before a campaign, product launch, sender migration, or template change. MailSlurp helps teams turn deliverability checks into repeatable evidence instead of one-off screenshots or vague spam scores.

Quick answer

A complete inbox placement test should verify:

• inbox vs spam placement outcomes for key message types
• Gmail, Outlook, Yahoo, and enterprise mailbox behavior when those providers matter to your audience
• SPF, DKIM, and DMARC pass status
• stable sender identity and routing headers
• consistent outcomes across release/campaign variants

If you searched for mail tester, mail-tester, or test email for spam, start with the Email spam checker or Spam score checker for quick triage, then use inbox placement testing to prove the real outcome.

MailSlurp placement evidence workflow

Use inbox placement after the message has passed the earlier diagnostic layers:

1. Send the exact product, lifecycle, or campaign email through the real send path.
2. Confirm SPF, DKIM, DMARC, MX, and DNS state with MailSlurp tools.
3. Inspect Email header analyzer results for sender identity, return path, and routing changes.
4. Compare Email spam checker and Spam score checker signals against the mailbox result.
5. Save the inbox, spam, missing, or delayed outcome as release evidence before campaign launch, sender migration, or product release.

That sequence helps teams explain why a message landed where it did instead of treating placement as a mystery.

Delivery vs deliverability vs inbox placement

Teams often use these phrases together, but they answer different questions.

Term	What it measures	Why it can mislead
Delivery	Whether the receiving server accepted the message	Accepted mail can still land in spam or a low-visibility tab
Deliverability	Whether the message reached a useful destination with enough trust	It needs evidence from authentication, content, sender health, and placement
Inbox placement	Where the message appeared after delivery	It is the most visible customer outcome, but it still needs diagnostics when it fails

A useful email deliverability checker should not stop at "sent" or "delivered." It should show the mailbox outcome and the technical evidence behind it.

Placement test workflow

1. Define critical message flows (signup, reset, billing, alerts).
2. Send test messages to controlled inbox cohorts.
3. Capture placement and timing outcomes.
4. Validate sender auth and header consistency.
5. Investigate poor outcomes and re-test before rollout.

For campaigns, run the workflow on the final subject line, HTML, text fallback, link domains, and tracking setup. For product email, run it on the exact application path that sends the message, such as signup verification, password reset, OTP, invoice, or account alert.

How to check email deliverability step by step

1. Choose the message path

Start with the message that creates the most customer or revenue risk:

• signup verification
• password reset or magic link
• OTP and MFA messages
• billing receipts and invoices
• security alerts
• lifecycle or campaign sends

Do not test a generic placeholder if the real message has different headers, sender identity, images, links, or tracking.

2. Confirm sender identity

Before judging content, validate the sender:

• SPF record exists and authorizes the sending service
• DKIM selector is active and signing the message
• DMARC exists and aligns with the visible From domain
• Return-Path and header From are consistent with the intended route
• DNS changes have propagated before the test result is trusted

Use SPF checker, DKIM checker, DMARC checker, and DNS propagation checker as the first diagnostic layer.

3. Send to representative inboxes

A seed list should match the real recipient mix. Include Gmail, Outlook, Yahoo, and the enterprise mailbox providers that matter to your audience. Separate the results by provider so one healthy provider does not hide a failing one.

For each received message, record:

• placement bucket
• delivery latency
• raw headers
• authentication results
• link and image rendering
• unexpected rewriting or forwarding behavior

4. Inspect spam and reputation signals

If placement is weak, check the surrounding signals:

• Email spam checker
• Spam score checker
• Email blacklist checker
• Email header analyzer

Fix authentication and routing issues before rewriting copy. Many deliverability drops come from DNS, alignment, blacklist, or header problems rather than wording alone.

5. Retest after every meaningful fix

Do not ship after a single passing check if the first run required changes. Retest the corrected version and keep the evidence attached to the launch, campaign, or sender record.

Inbox placement test vs mail tester vs spam score

These checks overlap, but they should not be treated as substitutes:

Search intent	Best first step	What it cannot prove alone
mail tester or mail-tester alternative	Mail-Tester alternative workflow	Whether your production workflow can repeat the check safely
spam score checker	Spam score checker	Whether Gmail, Outlook, or Yahoo placed the message in the inbox
email spam checker	Email spam checker	Whether every critical user flow received the exact expected message
inbox placement test	This workflow	Why a specific auth or header layer failed without deeper diagnostics

The practical release gate uses all four signals: score, spam-risk review, header evidence, and actual inbox placement.

Pass and pause thresholds

Define thresholds before the send. The exact numbers depend on your risk tolerance, but teams should agree on what blocks a launch.

Signal	Passing pattern	Pause pattern
Authentication	SPF, DKIM, and DMARC pass and align	Any missing or inconsistent sender-auth result
Placement	Key providers place test mail in visible inbox locations	Spam, junk, missing, or delayed placement on a provider that matters
Headers	Return path, Message-ID, From, and routing are consistent	Unexpected relays, duplicate headers, or identity mismatch
Reputation	No new blacklist or domain-health alerts	New listing, complaint spike, or suspicious sender drift
Workflow	Correct content, links, codes, and timing	Broken links, expired OTPs, wrong template, or missing personalization

MailSlurp helps turn these thresholds into repeatable checks for engineering, QA, and lifecycle teams.

What to investigate when placement drops

Authentication drift

Use:

• SPF checker
• DKIM checker
• DMARC checker

DNS and identity issues

Use:

• DNS lookup
• DNS propagation checker
• Reverse DNS lookup

Content and reputation issues

Use:

• Email spam checker
• Spam score checker
• Email blacklist checker
• Email header analyzer

Seed-list and provider coverage

A useful seed list is representative, not just large. Include the mailbox providers that matter for your recipients, then separate results by provider so one poor outcome is not hidden by a blended average.

For product email, start with signup, password reset, OTP, billing, and support workflows. For marketing email, test the final rendered campaign with production links and tracking parameters, then compare placement before and after risky copy or sender changes.

When to run an inbox placement test

Run placement checks when:

• launching a new sender domain or subdomain
• moving to a new email provider
• changing SPF, DKIM, DMARC, MX, or tracking domains
• releasing a new transactional template
• preparing a large campaign or lifecycle send
• warming up a sender before volume increases
• investigating user reports about missing emails

For warmup-specific workflows, read Email warmup explained and Best email warmup tools.

How MailSlurp fits

MailSlurp gives teams the inbox, message, and sender-health evidence needed to make deliverability decisions:

• create controlled inboxes for repeatable tests
• inspect received messages, headers, links, and content
• pair inbox placement with spam and blacklist checks
• monitor sender domain posture over time
• use APIs and webhooks to connect results to release gates

That makes MailSlurp the strongest path when email deliverability checks need to be repeatable, testable, and useful to the people who own the send path.

Release-gate checklist

• auth checks must pass
• no critical template defects
• expected receipt count and latency thresholds met
• remediation tickets created for any failed checks
• re-test completed before production send

For full rollout readiness, follow Email deliverability test.

Troubleshooting failed placement

Gmail is healthy but Outlook is poor

Compare headers and authentication results by provider. Outlook and Microsoft 365 can react differently to forwarding, reputation, content, and link patterns. Check blacklist status, routing history, and whether the message stream is sharing risk with a campaign sender.

Messages are accepted but land in spam

Start with authentication, headers, and blacklist exposure. Then inspect template content, link domains, image loading, and sender display names.

Placement changes after a template update

Retest the previous template against the new one. Look for changed link domains, tracking setup, HTML structure, subject line, display name, and sender identity.

Results look good once but fail later

Turn the check into monitoring. Use Domain monitor and deliverability monitoring so teams see drift after DNS edits, provider changes, warmup ramps, or high-volume sends.

FAQ

What is an inbox placement test?

An inbox placement test sends a real message to controlled inboxes and records where it lands, such as primary inbox, spam, junk, promotions, updates, or missing. It should also capture the sender and header evidence needed to explain the result.

How do I check email deliverability?

Check authentication first, then send the actual message to representative inboxes, inspect placement by provider, review spam and blacklist risk, and retest after fixes. MailSlurp helps teams run that workflow repeatedly.

Is a spam score enough?

No. A spam score can help triage content and sender risk, but it does not prove where Gmail, Outlook, Yahoo, or enterprise inboxes placed the message.

Should product teams run inbox placement tests?

Yes. Product teams should test signup, password reset, OTP, billing, and alert messages because those flows fail quietly when mail lands in spam or arrives late.

How often should teams test inbox placement?

Test before major launches, template changes, sender migrations, DNS edits, warmup ramps, and high-volume campaigns. For important send paths, add recurring monitoring so drift is caught before customers report missing mail.