Strategy

Email Header Analysis for Solo Ads: A Buyer's Checklist

By Phil | SoloAdsGuide.comNovember 16, 202615 min read
Solo ads strategy illustration for Email Header Analysis for Solo Ads: A Buyer's Checklist

Full disclosure: Philip Coble, the owner of SoloAdsGuide.com, owns PulseTraffic, PhilSoloAds and PulseTrack. That is exactly why this guide teaches you to verify claims instead of trusting them. Hold my services to the same standard as any other provider.

An email header shows where a message really came from and which servers handled it, so you can check a solo ad vendor's sending setup before you spend money. Read five fields (From, Return-Path, Received, Message-ID and Authentication-Results) and you can tell whether a sample email was sent the way the vendor says it was. A clean header does not prove the list is good, though, so pair it with click tracking and lead checks.

This guide is for buyers, not email engineers. You will learn how to pull up the full header, what each important line means in plain terms, which mismatches should make you pause, and how to document what you find.

TL;DR

  • A header is the hidden routing record of an email. In a solo ad it shows the sending domain, the servers in the path and whether SPF, DKIM and DMARC passed.
  • Check five fields: From, Return-Path, Received, Message-ID and Authentication-Results. Compare them with each other and with what the vendor told you.
  • Read Received lines from the bottom up. Trust the lines your own mail provider added, not older lines that anyone could have written.
  • A pass on all three authentication checks is one good sign, not a verdict. A failure is a strong warning.
  • Back up header findings with click tracking and lead-quality checks before you scale an order.

Table of Contents

What an email header is and why solo ad buyers should care

A solo ad is a single email, sent by a vendor to their list, with one call to action. You pay for the send, and the quality of that send depends on the vendor's list and on how the email is delivered. The header is the one part of the message that records how it was delivered.

According to Klaviyo's help center, a header includes the from and reply-to addresses, the subject, the recipient and the network path the message took. That network path is what makes it useful to you. If a vendor says they send from their own authenticated domain on a clean mail server, the header either supports that or it doesn't.

Headers also matter for legal reasons. Under CAN-SPAM, the US law for commercial email, the From, To, Reply-To and routing information must be accurate and identify the person or business that started the message, as one engineering guide to the law explains. If your offer goes out in an email with falsified routing data, your name is attached to the problem. Our guide on avoiding CAN-SPAM fines when vetting email scrapers covers that side in more depth.

How to get the full header

You can only analyze what you can see. In a solo ad setting, that usually means a sample broadcast the vendor sends to an address you control, or a message that arrives at an inbox you have on the vendor's list. Whichever you use, you need the complete original message, not a screenshot.

In Gmail, open the message, click More next to Reply, and choose Show original. Google's instructions say the full header then appears in a new window. Klaviyo's help page also walks through the same task for AOL, Outlook and Hotmail on the web, Yahoo and Apple Mail.

Keep the original, not a copy. emailauth.io points out that screenshots, forwarded copies and pasted fragments can drop duplicate fields, change line folding or add new transport events. Download the original message file, store it untouched, and do your notes on a separate copy.

Woman preserving an original email message file

If you are new to how email sending works in general, email marketing basics will help the terms below make more sense.

The five fields that matter

A typical message carries 20 to 40 header fields, but according to Nylas, only a handful matter for tracing delivery and catching spoofing. Here they are in the order we read them.

FieldWhat it tells youWho controls it
FromThe name and address the reader seesThe sender. Anyone can set it.
Return-PathWhere bounces go; also what SPF checksSender-controlled, but a mismatch with From is itself a red flag
ReceivedEach server that handled the message, with time stampsMixed: your provider's line is reliable, older lines may be forged
Message-IDA unique ID for the messageThe sender
Authentication-ResultsSPF, DKIM and DMARC outcomesYour receiving mail server

The table follows InventiveHQ's header reference, which notes that Authentication-Results is added by the receiving server, so on mail you received the sender can't forge it. SendKit's documentation makes the same point from the other side: the From header can be spoofed by anyone, which is why the authentication checks exist.

The idea behind all of this is provenance: who could have written each line. emailauth.io frames it this way. Some fields are the sender's own claims. Others record what a receiver actually observed. Give more weight to the second kind.

Read Received lines from the bottom up

Every server that handles a message adds a Received line at the top. That means the oldest hop is at the bottom and the newest is at the top. ActiveCampaign's help guide says these lines are usually the most reliable part of a header and are best read bottom to top: the bottom shows where the mail originated, and the top shows your own mail server.

For each Received line, note three things:

  1. The sending host and the receiving host. Do the server names look consistent with the vendor's claimed setup?
  2. The IP address. Does it belong to a mail platform or hosting provider you would expect, in a country you would expect?
  3. The time stamp. Nylas says a normal hop completes in under a second, and a gap of several minutes points to greylisting (a temporary rejection to test the sender) or a backed-up queue.

There is one important limit. Received lines are added as mail moves, so emailauth.io advises trusting the portion your own provider added, working from the newest hop toward older ones, and stopping where you reach material you can't verify. An older claimed hop can be fabricated even when the last trusted hop genuinely received the message. Treat unverifiable hops as claims, not facts.

MakeUseOf adds a useful detail: attackers can forge older Received lines, but the line added by the receiving provider cannot be forged, so a mismatch between that line and the rest of the chain should raise suspicion.

SPF, DKIM and DMARC in plain terms

These three results sit in the Authentication-Results field. You don't need to configure them to read them.

  • SPF checks whether the sending server is allowed to send for the domain in the Return-Path. It looks at the envelope sender, not the From address you see.
  • DKIM is a digital signature added by the sender. A valid signature, checked against the domain owner's public key, suggests the message came from that domain and wasn't changed on the way. Ars Technica's forensic guide says an invalid signature means the message either didn't come from that domain or was altered.
  • DMARC is a set of instructions telling receiving servers what to do with mail that fails SPF or DKIM: pass it, quarantine it or reject it. Ars Technica notes it adds no checks of its own.

The key word for DMARC is alignment. A passing SPF or DKIM result has to match the domain in the visible From address. MailSlurp explains that strict alignment needs the same domain, while relaxed alignment accepts the same organizational domain. It also warns you to use the result your own receiving provider added, not any field that happens to contain the word pass, because a sender can supply text like that.

Alignment is where solo ads often go wrong. MailSlurp notes that an email platform can authenticate its own domain successfully while a campaign using your From address fails alignment. For a solo ad, the equivalent question is whether the sending domain, the signing domain and the From domain all tell the same story. Our walkthrough on verifying DKIM and SPF with a test email shows the hands-on version of this check.

Red flags in a solo ad header

No single mismatch convicts a vendor. Several together are a pattern. These are the signs worth writing down:

  • From and Return-Path on different domains. MailTester lists this as a core spoofing indicator. Some legitimate platforms send this way, so ask why before you judge.
  • Reply-To that differs from From. Phishing guides treat it as a warning sign. In a solo ad, replies going to an unrelated domain means leads or replies may not go where you expect.
  • SPF, DKIM or DMARC failures. In one phishing walkthrough, three failures in a single block meant the domain owner had explicitly told the internet not to trust unsigned messages.
  • Unexpected infrastructure. Adaptive Security lists a sender suddenly using an unfamiliar cloud tenant or residential network, and a Message-ID structure that differs from earlier messages by the same sender.
  • Odd timing. A message that appears to arrive before an earlier relay time stamp, or to cross several regions within seconds, points to tampering or a faulty chain.
  • Lookalike domains. Substituted characters, added words or altered endings in the sending domain.
  • No encryption between servers or inconsistent server names across the Received chain.

The MITRE ATT&CK detection guidance takes the same approach: correlate failed checks with mismatched return-paths and abnormal sender domains, rather than leaning on any one signal.

A worked example

Say a vendor tells you they send from their own domain, mailer.example-vendor.com, with proper authentication. They send a sample to a Gmail address you control. You open Show original and see this, simplified:

Here is how to read it:

  1. From and Return-Path are on different domains. That already fails the claim that the vendor sends from their own domain.
  2. The Reply-To is a third, unrelated domain. Replies would go somewhere you didn't expect.
  3. SPF softfail, no DKIM signature and a DMARC fail mean the message did not authenticate against the From domain. Gmail added that result, so it is the line to trust.
  4. The bottom Received hop is an IP you can't tie to the vendor's setup.

This pattern matches the worked spoofing example in CaptainDNS's write-up: a mismatched Return-Path, an unknown IP in the chain and a triple authentication failure. For a buyer, the sensible reading is that this vendor's sending doesn't match what they described, and you should not place an order until they can explain it.

Now flip it. If From, Return-Path and the DKIM signing domain all sit on the same domain, SPF and DKIM pass, DMARC passes and the Received chain moves quickly through servers that fit the vendor's description, you have a consistent technical setup. That is a good start, and only a start.

What header analysis cannot tell you

Headers prove where an email came from. They do not prove the list behind it is real, opted in or interested in your offer.

MakeUseOf notes that even a full SPF, DKIM and DMARC pass only shows technical control of a domain, which anyone can register. emailauth.io says a pass is a bounded domain-authentication result, not proof the message is harmless. Adaptive Security adds that a failed check strengthens the case against a sender but doesn't prove it. So weigh identity mismatches and infrastructure changes together.

For solo ads, that means the header answers a narrow question: is this send technically what the vendor says it is? The questions it can't answer need other tools:

A documented routine you can repeat

Write down the same things every time, so you can compare vendors fairly.

  1. Get the sample. Have the vendor send a sample of their own broadcast to an inbox you control. Don't use a forwarded copy.
  2. Save the original. Download the full message file and store it unaltered. Work on a copy.
  3. Record the identities. List the From, Return-Path, Reply-To and DKIM signing domain side by side.
  4. Record the results. Copy the SPF, DKIM and DMARC outcomes from the Authentication-Results line your own provider added.
  5. Walk the Received chain. Start from the top trusted hop and move down. Note IPs, countries, server names and time gaps.
  6. Mark each mismatch as a question. A mismatch isn't a verdict. Put it to the vendor in writing and see whether the answer is specific.
  7. Start small. If the header looks consistent, choose a small first order, track every click and judge the leads before any larger order.

That last step matters most. A technically clean sender can still deliver weak traffic, so order size and tracking are your real protection. When you are ready to place a first order, our page on buying solo ads traffic lays out the process, and you can also go to the order page we recommend.

If your own sending domain is part of the picture, for example when your autoresponder emails the leads you get, see our autoresponder setup guide, and our network compliance checks for what to confirm before you pay.

Where this fits in vendor vetting

Header analysis is one layer of a larger process. At SoloAdsGuide we teach a 21-question vendor vetting framework that covers deliverability, list sourcing, compliance and tracking. The header check answers the deliverability questions with evidence you can see for yourself, instead of a promise.

If you want the full set of questions, start with our guide to solo ad deliverability and the 21-question vetting framework. And if the difference between a solo ad and your own list sends is still fuzzy, read how a solo ad differs from email marketing.

Start with the framework, then verify with tracking

SoloAdsGuide is an educational resource, written by Philip Coble, a solo ads vendor with 11 years in the industry. We teach buyers to verify claims instead of trusting them: the 21-question vendor vetting framework, guides on click tracking and traffic verification, and honest breakdowns of red flags. Begin at SoloAdsGuide.com, apply the framework, and track your clicks before you spend.

Soloadsguide

If you plan to send to your leads from a fresh domain, our guide on how to warm up your email domain with Instantly covers that next step.

Our perspective

We have been on the selling side of this industry for 11 years, and the pattern is consistent: buyers who verify before they spend avoid most of the damage. Headers are the cheapest verification available. A sample email and a few minutes of reading tells you more about a vendor's setup than a sales page ever will.

We also want to be straight about the limits. A clean header does not make a vendor good. It makes the sending setup consistent with what the vendor said. That is why we teach headers as one step inside a vetting framework, next to click tracking, lead checks and careful order sizing.

Our advice is simple. Pull the original header, compare the identities, read the receiving provider's own authentication result, and write down every mismatch as a question. Then place a small order, track every click and let your own data decide whether to go further. Nobody can promise you results, and anyone who does is giving you a reason to look closer.

Philip Coble

FAQ

Can I analyze the header of a solo ad email I did not receive?

You need the full original message, which you can get from a sample the vendor sends to an inbox you control. Screenshots and forwarded copies can omit or change fields, so they are poor evidence. Save the original file and work from a copy.

If SPF, DKIM and DMARC all pass, is the vendor safe to buy from?

A pass means the sender controls the domain and set up authentication, which is one good sign. It does not show that the list is opted in or that the clicks are real people. Treat it as a first check, then track clicks and review the leads on a small first order.

Which header field is the most trustworthy?

Authentication-Results added by your own receiving mail server is the one to trust first, because the sender can't write it for mail you received. The Received line your provider added is also reliable. From, Message-ID and older Received lines are claims made by the sender or earlier servers.

Does a different Return-Path always mean something is wrong?

No. Some legitimate sending platforms use their own bounce domain. It becomes a concern when it appears together with failed authentication, a mismatched Reply-To or infrastructure that doesn't fit the vendor's description. Ask the vendor to explain it, and judge the answer.

Sources

Want Verified Traffic Without the Guesswork?

PulseTraffic screens every seller, filters bot clicks in real time, and shows you verified buyer traffic labels before you spend a dollar.

Phil, founder of SoloAdsGuide.com and solo ads expert since 2014
About the Author

Phil

Phil is the founder of PulseTraffic.app, PulseTrack.me, and PhilSoloAds. He's been selling solo ad traffic to affiliate marketers since 2014 and writes about what actually works, without the hype.

Ready to Buy Verified Solo Ad Traffic?

Stop guessing. Start buying traffic from vetted sources with built-in click fraud protection.

Visit PulseTraffic.app