Home · Deliverability

How to check if your emails land in spam (step-by-step)

Suspecting mail is going to spam is common. Guessing without a workflow wastes time. This is a practical sequence: authenticate → clean the list and content → seed-test → fix one variable → re-test. It soft-sells proper placement testing only where it belongs — after the basics.

No fear-mongering, no “never land in spam” promises, and no invented success rates.

1. Confirm it is really a spam problem

Before tools:

If mail never arrives anywhere, think infrastructure or blocklisting first, not subject-line tweaks.

2. Authentication first (non-negotiable)

Mailbox providers weight domain trust heavily. Before paying for placement tests:

  1. SPF — sending hosts authorised for the domain.
  2. DKIM — messages signed; signatures validating.
  3. DMARC — policy published; start monitoring (p=none) if you are new, then tighten with care.
  4. Alignment — From domain matches what SPF/DKIM authenticate (as your ESP docs describe).

Check the domain itself with the email authentication checker, or start from the record you are fixing: SPF, DMARC, DKIM. A pass there does not promise the inbox.

Skip this step and every spam test will mostly tell you “you look untrustworthy.”

3. List and sending hygiene

A clean test to a poisoned list still looks like spam behaviour downstream.

4. Content and technical sanity (cheap checks)

Use free or built-in checks for:

These catch silly mistakes. They do not prove multi-provider inbox placement.

5. Seed / inbox placement test

When auth and hygiene are in decent shape, run a seed-list placement test: send the real creative to a panel of addresses across providers and see inbox vs promotions vs spam vs missing.

That is the job class GlockApps and similar tools sit in. Use them when:

How to run a sensible test:

  1. Use the same From, subject, and body you will send live.
  2. Send from the production domain / stream you care about.
  3. Note time, ESP, and any A/B variant.
  4. Read inbox / promotions / spam / missing — not just a single “score.”
  5. Change one variable, then re-test.
Ad Commission if you use this link.

Broader tool categories: email deliverability testing tools.

6. Fix, then re-test

Common levers (pick one at a time):

Document what you changed. Without a re-test, you are still guessing.

Next step: process first, then test

Use a repeatable pre-flight order (auth → hygiene → content → test → monitor), then a placement tool only when you are ready to test.

Ad Commission if you use this link.

Related: GlockApps review · GlockApps pricing.

Fix deliverability over time

Authentication is only the first step. Warmy is a paid email warm-up and inbox-placement tool. It gradually sends and receives mail from a connected mailbox to help build sender reputation, and it also offers placement tests. It does not replace SPF, DKIM or DMARC, and it does not guarantee inbox placement.

Warmy’s pricing page lists a 7-day free trial with no credit card required. Its FAQ says the trial is limited to one mailbox and about 15–50 emails a day, which is not long enough to finish warming a new domain. Plans are volume-based. Confirm current plans and trial terms on Warmy’s site before you sign up.

Checked on warmy.io/pricing and warmy.io/faq, 18 November 2026 (GMT). This is a separate deliverability tool. It is not a substitute for authentication, list hygiene, a pre-send placement test, or HighLevel.