Email Validation — Verify Any Address in Real Time

The threshold Gmail and Outlook publicly enforce is 2%. Once your bounce rate hits that mark, they start throttling delivery from your domain — fewer emails land in the inbox, more go to spam, and some don’t arrive at all. At 5%, you’re looking at active reputation damage that doesn’t reset overnight.

The frustrating part is that this damage follows your domain for months, not days. The fix isn’t to send less — it’s to clean the list first.

Not quite — but it removes the biggest reasons they don’t. Validation eliminates hard bounces (addresses that don’t exist), catches disposable emails that would never engage, and flags risky addresses so you can decide whether to include them.

What it can’t do is fix a sender reputation that’s already damaged, or override a spam filter triggered by your content. Think of it as clearing the road — you still have to drive well.

A catch-all domain accepts every email sent to it, regardless of whether the specific mailbox exists. So if you send to john.smith@company.com and that inbox doesn’t exist, the server still accepts it — the message appears delivered, but it’s going nowhere.

Most basic validators mark these as “valid” because technically the server didn’t reject it. ValidPeak flags them separately as Risky, so you know you’re dealing with a catch-all before you send 10,000 emails into the void.

It runs 25+ checks in sequence. First, syntax validation against RFC 5321/5322 standards. Then DNS resolution and MX record lookup. Then a live SMTP connection to the mail server to check whether the specific mailbox exists — without sending any actual email. On top of that: disposable address detection, role-based filtering (info@, support@), spam trap identification, catch-all flagging, and a composite risk score from 0 to 100.

The whole process runs in under 200ms per address.

Valid — passed every check. Safe to send.

Invalid— will bounce, guaranteed. The domain doesn’t exist, the mailbox was rejected, or the syntax is broken. Remove every single one before sending.

Risky— something’s off, usually a catch-all domain or a low deliverability score. You can send, but expect a higher bounce rate. For cold outreach or high-stakes campaigns, it’s worth excluding them.

Unknown— the mail server didn’t respond in time, often due to greylisting. Not a confirmed bounce, but not a confirmed deliverable either.

For 10,000 emails: typically 5–15 minutes. For 50,000: around 15–30 minutes. For 100,000: 30–60 minutes. The variation comes from how quickly the mail servers respond — some use rate-limiting or greylisting that slows things down.

ValidPeak processes addresses in parallel to keep total time down. You’ll get a notification when results are ready, so you don’t have to sit watching a progress bar.

Double opt-in helps a lot, but it doesn’t cover everything. It confirms someone clicked a link — it doesn’t catch catch-all domains that silently accept all mail, disposable addresses used just to pass the confirmation step, or addresses that were valid at signup but have since been abandoned or deleted.

Lists also degrade over time — roughly 22% of contacts per year go stale as people change jobs, abandon inboxes, or switch domains. Validation catches what opt-in misses.

It’s processed to generate results, then deleted. Bulk uploads are removed once you’ve downloaded your cleaned file. Individual API validations are discarded immediately after processing. Logs are kept for up to 90 days for debugging, then purged permanently.

ValidPeak is SOC 2 Type II certified and GDPR compliant — your contact data is never sold, shared, or used for anything beyond the validation you requested. For DPA requests, contact legal@validpeak.com.

Yes — that’s one of the most common use cases. You add a single API call to your form that fires when someone submits their email. The response comes back in under 200ms— fast enough that the user doesn’t notice the delay before seeing a confirmation.

If the address is fake, disposable, or doesn’t exist, you block it before it enters your database. The API handles up to 10,000 requests per minute and has official SDKs for Python, Node.js, PHP, Ruby, Go, Java, and .NET. Full docs at validpeak.com/docs.

No — never. Whether you buy them as a one-off pack or receive them as part of a monthly plan, they stay in your account until you use them.

Most validation services expire credits after 12 months or reset monthly allocations regardless of usage. ValidPeak doesn’t. If your campaigns are seasonal or you want to buy a larger pack at a lower per-credit rate and use it over the next 18 months — not a single credit is lost.