Test email landed in spam

Why a test email lands in spam

You sent yourself a test before the real campaign, and it turned up in the spam folder instead of the inbox. Now you want to know whether the campaign will do the same. A test email landing in spam means a mailbox provider filtered that one message as junk. It is an early warning about the sender, the domain or the content, caught before the whole list sees it.

The quick answer is to check which address the test actually came from. A first test often goes out from the Nitrosend brand subdomain sender, a Nitrosend address rather than your domain. That lets it send before any DNS records exist. A message that does not come from your domain is more likely to be filtered. If the test did come from your domain, check that SPF and DKIM pass, then check the content's spam score, then check the domain against blocklists. Hold the campaign until a test lands in the inbox, because a full send that ends up in junk folders does more harm than a late one.

The email deliverability testing guide covers how the different kinds of test fit together.

What sends a test email to spam?

Check these causes in order. The first one is the quickest to rule out.

1. The test was not sent from your domain. A first test to a single address does not need DNS verification, because it can go through the Nitrosend brand subdomain sender. That makes it possible to see an email arrive in minutes, but the message is not sending from your domain, and mailbox providers have no history tying that address to your brand. Check it first, because it is the quickest to rule out.
2. The sending domain is not authenticated. Once the test does come from your domain, missing or broken SPF and DKIM records leave a provider no way to confirm the message is really yours. Open the test in the inbox that received it and look at the authentication results in the headers.
3. The domain is new and has no sending history. A domain that verified yesterday has no reputation yet. Authentication passes, but filters stay cautious until the domain has sent steadily for a while.
4. The content trips spam filters. A high spam score, wrapped or shortened links that resolve somewhere unexpected, and a message that is mostly images with little text all count against it. These show up when authentication passes and tests still land in spam.
5. The domain or sending IP is on a blocklist. This is the most serious cause. The sign is spam placement at every provider, even for a short plain text message.

How to fix each cause

Not sent from your domain

Ask an agent to run nitro_get_status, which reports the current sender identity and whether the account is ready to send. If the test went out from the Nitrosend brand subdomain sender, add your own sending domain with nitro_manage_domains, publish the records it returns, and run the verify step. Then send the test again with nitro_send_test_message so it comes from the domain the campaign will use. A spam result from the Nitrosend brand subdomain sender says little about how your own domain will do, so judge placement only on tests from your domain.

Domain not authenticated

Run the diagnose step in nitro_manage_domains to see which records are missing or failing. SPF and DKIM both need to pass on the sending domain. The guide to email authentication protocols explains what each record does, and the domain deliverability checklist covers everything to confirm on the domain. If verification will not complete, the page on a domain stuck verifying lists the usual record mistakes.

New domain, no history

Authenticate the domain with SPF and DKIM, then ramp the first sends rather than starting with the whole list. The full walkthrough for a fresh domain lives on the page about new domain emails going to spam, and the guide to warming up an email domain sets out the pace. For the longer term, a separate sending domain or subdomain for marketing mail, warmed before its first campaign, keeps the main domain's reputation protected if the marketing side ever runs into trouble.

Content trips filters

Run nitro_review_delivery on the template or campaign. It is a read only review that covers validation, spam analysis and a preflight, and it never sends or approves anything. A clean result reads like this: domain verified, sender configured, audience valid, content compliant and spam score low. If the spam score is high, cut the image weight, make sure every link resolves where it says it does, and add plain text that reads like a message from a person. Then send another test. For an outside view, a spam test email service or mail tester scores the same message independently.

Domain or IP on a blocklist

Look the domain and sending IP up with a Spamhaus blacklist check. A listing has to be cleared with the list's owner before any test will land reliably, so stop sending from that domain until it is resolved.

Before the real send

If tests are landing in spam, do not send the campaign. A send that mostly ends up in junk folders reaches almost nobody, and the poor engagement that follows makes the next send harder.

The reverse also holds: a test that reaches the inbox is not a launch approval. A test send can go through even when a live launch would be blocked, for example by a missing physical address in the footer. The pre-send check worth running every time covers five things:

• Resolve wrapped links.
• Score the content for spam.
• Weigh images against text.
• Check how the message renders in dark mode.
• Send a test to a seed address.

Some sending tools build a version of this in, and where a tool does not, it is worth doing by hand. In Nitrosend that is nitro_review_delivery for the review and preflight, followed by nitro_send_test_message for the test itself.

One test inbox is also only one sample. Send tests to addresses at more than one mailbox provider, since Gmail, Outlook and Yahoo filter differently. The guide to sending a test email covers seed testing, and the roundup of free email testing tools lists what each one checks.

What to do next

1. Confirm the test came from your own domain, not the Nitrosend brand subdomain sender.
2. Check SPF and DKIM pass on that domain, and fix any record that does not.
3. Run a spam analysis and preflight on the message, and act on what it flags.
4. Send fresh tests to inboxes at two or three providers.
5. Send the campaign only once those tests land in the inbox.

An agent connected to Nitrosend can run the first three steps from Claude, Cursor or any other MCP client. To script the same checks in a deploy pipeline, start with the Nitrosend CLI or the guide to Python email automation. If the problem looks like it sits below the message, the SMTP test and telnet SMTP test guides check the connection itself.

Common questions

Go deeper

Sources

• Email marketing bible, pre-send preflight: resolve wrapped links, spam score, image to text weight, dark mode, and a seed address test before every send.