Service

Online email verifier

Check a single address before sending. Valid, invalid, risky, and catch-all results without delivering a message to the recipient.

Free trial credits
Results in seconds
No credit card required

Create account See pricing

What is an email verifier?

An email verifier checks whether an address exists and whether it is worth sending a campaign to. It is not a test message to the recipient inbox, but a technical analysis: syntax, DNS, MX, and SMTP response.

Self-serve: create an account, upload a list or connect the API without a sales call.

What do the statuses mean?

Every result includes a clear sending recommendation.

Valid: the address appears active and safe to send to.
Invalid: no MX, mailbox does not exist, or the domain is dead.
Risky: catch-all, disposable, or role-based address such as info@.
Unknown: the server did not respond clearly; re-verification is recommended.

When should you verify a single address?

Single-address verification saves time for support, sales, and product teams.

Support: will the ticket reach an existing inbox?
Sales: verify a lead before the first email.
QA: test a registration form before launch.

Polish email providers

We recognize popular domains and hosting providers in Poland, including home.pl, nazwa.pl, o2.pl, and business mailboxes on custom domains.

What exactly do we check?

Verification runs in several layers. No single layer is enough on its own — together they produce a result you can trust before sending.

RFC syntax and common typos (e.g. gmail.con instead of gmail.com).
DNS and MX records — whether the domain accepts mail at all.
SMTP handshake without delivering message content to the inbox.
Heuristics: disposable, role-based, catch-all, free vs corporate.

Verifier and deliverability

One invalid address caught before sending costs less than a hard bounce in a campaign. The verifier is the first line of defense for sender reputation, ESP costs, and support time spent fixing bad addresses manually.

Web dashboard and real-time API

The same verification engine powers the product hero form, the signed-in dashboard, and the API for signup forms and CRM workflows. In the dashboard you see check history and credit balance; in the API you integrate POST /api/v1/verify with a Bearer token. Latency is typically a few seconds, so users can fix typos before submitting a form.

Hero on site: quick test without an account (trial credits after registration).
Dashboard: manual checks for support and sales.
API: automatic validation when saving a lead or ticket.

How to read a verification result

The response includes status (valid, invalid, risky, unknown), an optional score, and a classification reason. Invalid blocks marketing sends. Risky requires a decision: catch-all in B2B is sometimes acceptable, disposable is almost always rejected. Unknown is a signal to retry, not to auto-delete from your database without context.

Common mistakes without verification

Teams often rely only on regex in forms or on double opt-in. That does not detect dead mailboxes after job changes, expired domains after a company shuts down, or typos in corporate domains. The verifier closes the gap between “valid format” and “an address that will accept mail.”

Regex does not check MX or SMTP.
Double opt-in does not help when the mailbox no longer exists.
Manual fixes in support do not scale at hundreds of leads per day.

Privacy for a single check

We inspect the address technically without sending marketing content to the recipient. As an EU-based operator we design the process for GDPR: data minimization, retention described in terms, and a DPA on request for B2B customers. A single verification does not build a public people directory.

Manual checks vs automated verification

Sending a test email by hand or pinging from a terminal does not scale and hurts sender reputation. The verifier performs SMTP handshake in a controlled way without content in the recipient inbox. On signup forms the API blocks invalid saves; in CRM a single “verify” button saves minutes per lead. At hundreds of addresses per day, the gap between a minute and a second per record adds up to hours of team time.

Exporting results to CRM and spreadsheets

You can copy a single result from the dashboard or download check history. With API integration you store status next to the CRM record — HubSpot, Pipedrive, or your own database — and filter leads before an outbound sequence. Sales sees immediately whether an address is valid instead of discovering a hard bounce after the first message.

Enter the address

In the hero form or in the dashboard after sign-in.
Wait for analysis

We check syntax, DNS, MX, and SMTP response.
Get the result

Status, score, and classification reason ready for your decision.

“We cleaned 40k leads before a cold email push. Bounce dropped from 9% to under 1% — domain reputation recovered.”
Marta, B2B SaaSVerified customer

“We upload a CSV from CRM every week. Export with statuses saves hours of manual checking.”
Tomasz, outbound agencyVerified customer

“Trial credits were enough to judge quality. Then we bought a pack for our B2B newsletter.”
Kamil, marketing automationVerified customer

Email verification API Signup verification Verification accuracy

Frequently asked questions

Is the verifier free?

After registration you receive free trial credits. Each single verification uses one credit.

Do you send an email to the recipient?

No. We inspect mail infrastructure without delivering content to the inbox.

How long does a check take?

Typically a few seconds. Timing depends on the recipient server response.

Can I use the verifier in a form on my website?

Yes — via the real-time verification API. In the dashboard you generate a Bearer key and call POST /api/v1/verify on registration.

What about catch-all addresses?

Catch-all means the server accepts any local-part. We mark them as risky — verify the lead through another channel or exclude them from bulk sends.