You scheduled a campaign to 12,000 contacts. HubSpot sent it. Then the bounce notifications started, and by the time you checked, your bounce rate had crossed the line where HubSpot steps in to protect its own sending reputation, throttling your emails and suppressing contacts. The list you spent weeks building is now working against you.
Here's the part that stings: most of those bad addresses didn't sneak in. They came through the front door. A form submission with a typo. An Apollo import full of guessed addresses. A Clay run that enriched 3,000 companies overnight. A migration that carried across years of dead mailboxes from your old CRM. Every one of them walked straight into HubSpot, and nothing checked whether the address was real before it landed in a list you'd eventually email.
Email validation is the check that should have happened at the door. This guide covers what it actually verifies, why your HubSpot fills with invalid addresses in the first place, what those addresses cost you, and how to validate them, on entry and in bulk, without exporting a thing.
What email validation actually checks
"Email validation" and "email verification" get used interchangeably, and for most purposes they mean the same thing: confirming that an address can actually receive mail before you send to it. A proper check runs several layers, from cheap-and-obvious to genuinely useful:
- Syntax. Is it a validly formed address at all? (
jane@@acmefails here.) HubSpot already does this much on forms. - Domain and MX records. Does the domain exist, and is it configured to receive email? A form-filler who types
gmial.comclears syntax but fails here. - Mailbox. Does the specific inbox exist on that domain? This is the layer that separates real validation from format-checking, and it's the one HubSpot doesn't do natively.
- Risk flags. Is the address a catch-all, a role-based address like
info@orsales@, a disposable or spam-trap address? These are technically deliverable but risky to email, and knowing which is which is the difference between a clean list and a suppressed one.
The distinction that matters: HubSpot validates format. It doesn't verify whether the mailbox behind the address actually exists. That gap is where bad data gets in, and it's why a contact can look perfectly valid in your CRM right up until the moment it hard bounces.
Why your HubSpot fills up with bad emails
If invalid addresses only arrived once, you'd clean them once and move on. But for most HubSpot portals, bad emails aren't a one-off mess. They're a continuous supply, fed by the same stack that runs your go-to-market. This is the difference between a portal that needs a scrub and a portal that needs ongoing validation.
The usual sources:
- Forms. People mistype their own address, use a throwaway to get a gated PDF, or submit
test@test.com. As one customer running over a million HubSpot contacts put it, the problem starts with form submissions "where people may use different variations of their name or multiple email addresses." - Enrichment tools. Apollo, Clay, and Clearbit are the fastest-growing source of questionable emails in HubSpot. Enrichment often guesses addresses from name-plus-domain patterns, and a guessed address is unverified by definition. Every enrichment pass adds more.
- Imports and migrations. Moving from Salesforce or another CRM brings across every dead address the old system accumulated. A list bought or inherited two years ago is now decaying at roughly 20% to 30% a year as people change jobs.
- Team growth without governance. More people creating records, fewer rules about how, and no one checking whether the addresses are real.
Because these sources never stop, the invalid-email rate never stays fixed. Clean the list today and the next Apollo run, the next campaign's form fills, and the next month of natural decay start rebuilding it. That's why validation belongs in your CRM as infrastructure, not as a quarterly chore.
What invalid emails are actually costing you
Everyone knows bad addresses are "not ideal." Fewer people have counted what they cost, and the number is usually worse than expected, because it lands in four places at once.
Your sender reputation. Mailbox providers judge you on how many of your sends bounce or hit dead addresses. A high bounce rate tells Gmail and Outlook you don't manage your list, and they respond by routing more of your mail to spam, including the mail to your good contacts. One bad campaign quietly taxes every campaign after it.
Your campaigns. Once your bounce rate crosses HubSpot's threshold, HubSpot steps in to protect shared sending infrastructure, suppressing contacts and, in the worst cases, restricting your ability to send. The list you built to run campaigns becomes the reason you can't.
Your HubSpot bill. Invalid addresses are still Marketing Contacts, and you pay for Marketing Contacts whether or not they can receive a single email. An address that hard bounced last quarter is a line item you're renewing this quarter for nothing. (If that's your acute pain, the mechanics of cutting it are covered in reducing your HubSpot Marketing Contacts; validation is the upstream half of the same fix.)
Your team's trust. This is the one that compounds. When reps see bounced emails, wrong contacts, and dead addresses in the CRM, they stop trusting the CRM, and a sales team that doesn't trust the data goes back to their own spreadsheets. Rebuilding that trust is slow, and every invalid address chips at it.
The two jobs validation has to do
Any approach that only does one of these leaves the problem half-solved.
Job one: the bulk cleanup. You have a backlog: thousands, sometimes tens of thousands, of unverified addresses already sitting in HubSpot. These need checking in bulk so you can suppress, correct, or remove the dead ones before your next big send. This is the job most email-checking tools are built for, and it's the easy half.
Job two: the ongoing prevention. This is the half that actually keeps your list clean. Validating an address the moment it enters HubSpot, on form submission, on import, or after an enrichment pass, stops the bad ones before they ever join a list. Real-time validation on entry is what turns a list you constantly re-clean into one that stays clean on its own.
A one-time scrub feels like progress and then decays. The portals that stay healthy are the ones running both jobs: clear the backlog once, then validate on entry so the backlog never rebuilds. "Set it and forget it," as Koalify customers describe the equivalent on the deduplication side. The same principle applies here.
How to validate emails in HubSpot
There are three realistic ways to do this, and they're honestly not equal.
HubSpot on its own. HubSpot checks email format on forms and automatically handles bounces after they happen, marking hard-bounced contacts and stopping future sends to them. That's genuinely useful, but it's reactive: HubSpot learns an address is dead by sending to it and watching it bounce, which is exactly the event that damages your reputation. There's no native mailbox-level check that verifies an address before you email it, and no native way to bulk-verify a list you already hold.
A standalone verification tool. NeverBounce, Kickbox, ZeroBounce and similar tools do proper mailbox-level checking. The catch is the workflow: you export a list out of HubSpot, run it through their platform, and import the results back. It's a manual round-trip you have to remember to repeat, on a separate tool your team has to learn and log into. For a one-time cleanup that's fine. For ongoing prevention it breaks down fast, because nobody re-runs a manual export every time a form is filled. And for EU or UK teams there's a second catch: most of these tools process data on US infrastructure, which is a genuine blocker for anyone with GDPR data-residency requirements.
Validation inside HubSpot. The third option is to validate without leaving HubSpot at all: addresses checked on entry through your existing workflows, one-click checks from the contact record, and bulk verification of the list you already hold, with every result written straight onto the contact as a native HubSpot property you can filter, report, and build lists on. No export, no second tool, no round-trip. This is the approach Koalify takes, and it's the same philosophy behind its deduplication tool: fix the problem where it lives, using the properties and workflows you already know.
Doing it without leaving HubSpot
Koalify's email validation runs where your data already is, through three pieces that map to the two jobs above.
The Workflow Action handles both bulk and prevention. Run it across your entire list in one pass to clear the backlog, then leave it enrolled so every new contact is validated automatically as it's created or updated. That's the on-entry check that stops bad addresses before they reach a list.
The Email Validation Card sits in the sidebar of every contact record. Before you enrol someone in a sequence, or whenever an address looks off, one click returns a status and the reason behind it, with no export and no waiting.
Native HubSpot properties are where every result lands. Because the validation status lives on the contact like any other property, you build views and reports on database health, trigger alerts when an invalid address appears, and, the one that protects your sends, filter on the status to build a suppression list so invalid addresses never enter a send in the first place.
The outcomes are the point, not the mechanism. RevOps and marketing teams have run an entire marketable database through it in minutes and cut sends down to a 0.4% bounce rate across 4,000+ emails, comfortably inside the range mailbox providers reward rather than penalise. Your campaigns land, your sender reputation holds, and you stop paying to store addresses that will never open anything.
Two honest trade-offs worth stating plainly. First, no validation tool is perfect. A catch-all domain that accepts everything can't be verified with certainty by anyone, so validation reduces risk rather than eliminating it. Koalify returns context-rich statuses (the reason an address was flagged) precisely so you can make the judgement call on the grey-area ones. Being clear about that is more useful than a "100% accurate" claim you'd catch us on later. Second, for regulated EU and UK buyers, where your data is processed matters as much as how well. Koalify runs inside HubSpot with GDPR support, SOC 2 Type II and ISO 27001 certification, and is a HubSpot Certified App, a deliberate difference from tools that process your contacts on US infrastructure.
Validation and deduplication are the same problem
Worth naming, because it's why Koalify ships email validation and deduplication as two apps from one team rather than treating them as unrelated. Invalid emails and duplicate records are two symptoms of one condition: a CRM your team can't fully trust. They come from the same sources (forms, imports, enrichment tools, team growth), they inflate the same Marketing Contacts bill, and they break the same reports. Cleaning duplicates while ignoring dead addresses, or the reverse, leaves the job half done. A genuinely clean HubSpot needs both.
Frequently asked questions
Does HubSpot validate email addresses automatically? HubSpot validates the format of an address on forms, so it'll reject something that isn't shaped like an email, and it automatically marks and suppresses contacts after they hard bounce. What it doesn't do is verify that the mailbox actually exists before you send. That means HubSpot typically discovers a dead address by emailing it and watching it bounce, which is the exact event that hurts your sender reputation. Mailbox-level validation closes that gap by checking the address before the first send.
What's the difference between email validation and email verification in HubSpot? For practical purposes they're the same thing, and most people use the terms interchangeably. If you want a distinction: "verification" usually refers narrowly to confirming a mailbox exists, while "validation" tends to cover the fuller set of checks, including syntax, domain, mailbox, and risk flags like catch-all, role-based, and disposable addresses. When you're comparing tools, look at which layers each one actually runs rather than which word it uses.
Can I validate emails in real time and in bulk in HubSpot? Yes, and doing both is the point. Bulk validation clears the backlog already in your portal before a big send. Real-time validation on entry, through a workflow that runs as contacts are created and updated, stops new bad addresses before they ever join a list. A one-time bulk scrub on its own decays as forms, imports, and enrichment keep feeding new addresses in.
Will validating emails lower my HubSpot Marketing Contacts bill? It can. Invalid addresses still count as Marketing Contacts, so you're paying to store and renew addresses that can't receive a single email. Identifying them lets you set them as non-marketing or remove them, so you stop paying for contacts that will never convert. Validation is the upstream half of the same cost story as reducing Marketing Contacts directly.
Is email validation safe for GDPR and EU data-residency requirements? It depends entirely on where the tool processes your contacts. Many popular verification tools run your data through US infrastructure, which is a blocker for teams with EU or UK data-residency obligations. Validating inside HubSpot with a GDPR-supported provider that's SOC 2 Type II and ISO 27001 certified keeps your contacts within the residency boundary your compliance team cares about, without shipping your database to a third-party platform.
Your list is only as good as the addresses in it, and right now something is adding bad ones faster than you can catch them. See how many invalid addresses are already sitting in your HubSpot, and stop the next batch at the door.