Go to Marketing, then Email, click the name of the email, open the Preview and test dropdown at the top right, choose Send test email, pick recipients from the Send test to dropdown, and click Send.
Now the part that changes what the result means. HubSpot's documentation states that the test email will have a from address of noreply@hubspot.com and a from name of Marketing Email Preview Send. The message you are about to inspect was not sent by you. It was sent by HubSpot, from HubSpot's infrastructure, signed with HubSpot's keys, from a domain with a sending history that has nothing in common with yours.
Everything downstream of that follows. A HubSpot test send cannot tell you anything about your authentication, your domain reputation or your placement, because none of those three were involved.
| Question | Does a HubSpot test send answer it |
|---|---|
| Does the layout hold up | Yes |
| Do my personalization tokens resolve for a real contact | Yes, using Preview as contact |
| Does the plain text version read properly | Yes, via the Advanced section |
| Does my SPF, DKIM and DMARC setup pass | No. The message authenticates as hubspot.com |
| Is my sending domain in good standing | No. The sending domain is HubSpot's |
| Will my campaign land in the inbox | No, for both reasons above |
Send a test email in HubSpot
The control sits on the email itself rather than in a separate testing area, and the same path covers every option.
- Go to Marketing, then Email.
- Click the name of the email you want to test.
- Click the Preview and test dropdown in the top right.
- Choose Send test email.
- Select recipients from the Send test to dropdown.
- Optionally, click the Preview as contact dropdown and select a contact, so tokens resolve with that contact's real property values.
- Optionally, expand Advanced and tick Send plain text version.
- Click Send.
This needs Marketing Hub Starter, Professional or Enterprise, plus edit permissions on marketing email. HubSpot's documentation for the flow was last updated on 17 July 2026.
The From address is the whole story
It is worth being concrete about what noreply@hubspot.com costs you, because the consequences are not obvious from the interface.
SPF, DKIM and DMARC are HubSpot's, not yours. Open the headers of a HubSpot test send and every authentication result you read belongs to hubspot.com. If your own DKIM key is missing, misaligned or signing with the wrong domain, a test send will look perfect. Across messages tested with Unspam this year, 90% pass DKIM, and the ones that fail almost never discover it from a platform's own test send.
Your sending domain never appears. The connected domain you set up, warmed and are trying to protect is bypassed entirely.
Your IP pool is not used. Whatever shared or dedicated address your campaigns leave from, the test does not travel it.
The reputation being tested belongs to HubSpot. noreply@hubspot.com sends an enormous volume of mail and is well known to every mailbox provider. Your domain is not. Reading placement from a test send is reading someone else's reputation.
Preview as contact is the one test feature worth using every time
Most personalization bugs are invisible until a token fails in front of the whole list, and HubSpot has a control that catches them. In the Send test email panel, the Preview as contact dropdown renders the email using a real contact's property values.
Pick a contact with sparse data rather than your best-populated record. A missing first name that falls back to "there" is fine; a missing company name that falls back to an empty string and leaves a sentence reading "welcome to , where" is the sort of thing this feature exists to catch.
Client previews are Professional and above, and metered
Rendering previews sit under Preview and test, then Preview in an email client. They require Marketing Hub Professional or Enterprise, so Starter accounts have no client preview at all and no spam test of any kind.
The allowance is 500 tests per rolling 30-day period on Professional and 1,500 on Enterprise, and each client you select counts as one test. One email checked across twelve clients spends twelve. That is generous compared with most platforms in this category, and it still measures only rendering.
HubSpot's email health tool is engagement, and it is blind at Gmail
The Health tab under Marketing, then Email, produces a score from 1 to 10 across 30 days of engagement, comparing open, click, hard bounce and unsubscribe rates against benchmarks, alongside spam report counts and a 12-month trend.
HubSpot documents its own limitation here, and the sentence is unusually direct for a vendor: spam report data is not available for Gmail, and the recommendation is to use Google Postmaster Tools instead. Since Gmail is the largest mailbox provider most senders reach, the health score is missing complaint data from the place it matters most.
There is a deeper issue with engagement as a proxy for placement, and it applies to every score of this kind. Opens, clicks and unsubscribes can only be recorded for mail that arrived somewhere a person could act on it. Messages filed into spam produce almost none of any of them, so they quietly leave the calculation. Of the campaigns run through Unspam so far this year, 65% of emails reach the primary inbox, and the Unspam deliverability benchmark tracks where the rest go.
When you need a real Send now instead
Once the layout is right and the tokens resolve, everything still open requires a message that left through your connected domain: your DKIM signature, your SPF alignment, your tracking links and your actual reputation at each provider.
That means a real Send now to a small list of seed contacts rather than a test send. The HubSpot deliverability guide covers the setup, including the graymail suppression setting that will silently skip your seeds unless you untick it. For placement, an inbox placement test delivers the campaign to seed mailboxes at Gmail, Outlook, Yahoo and five other providers and reports where each copy was filed.
When the email is ready to go, run it through the free Unspam spam test as a real send, and read the authentication panel: if the DKIM signing domain is yours rather than HubSpot's, you are finally testing your own mail.
