Why us

Email verification accuracy

Syntax, DNS, MX, SMTP, catch-all, and disposable detection. Deep analysis without sending a message to the recipient.

Multi-step process
Transparent statuses
No false 100% promises

Honest about the industry

SMTP is not 100% deterministic. Servers can return non-standard responses. That is why we show status, score, and classification reason instead of a single magic yes/no.

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

Verification process

Each address goes through a sequence of checks tailored to the domain type.

Deduplication on list upload
RFC syntax check
Domain and MX record verification
SMTP test without delivering content
Catch-all, disposable, and role-based detection
Retry on greylisting

Greylisting and unknown

Some mail servers deliberately delay the first SMTP response. The status may then be unknown — not automatically invalid. Bulk jobs retry; at signup plan for retry or brief wait in the UI.

Transparency over “100% accuracy”

We promise clear statuses, classification reasons, and honest copy — not marketing “100% accuracy” that SMTP cannot guarantee. You decide what to send, remove, or flag for manual review.

Layers: syntax, DNS, SMTP

RFC syntax rejects obvious errors before any network call. DNS and MX confirm the domain is configured to receive mail. The SMTP handshake checks whether the server accepts the specific local-part — without delivering message content. Heuristics at the end classify disposable, role-based, and catch-all. No single layer replaces the others.

False signals and retries

Greylisting, rate limits on the recipient server, and temporary timeouts can produce unknown status. Bulk jobs retry automatically. For a single check in a form, show “try again in a moment” instead of treating unknown as invalid. That reduces rejecting valid leads.

Status policy: B2B vs cold email

In relational B2B, catch-all on a corporate domain is often kept with a risky tag. In cold email and performance marketing, risky and disposable are usually excluded entirely because the cost of one hard bounce outweighs a single contact. Invalid is always out — regardless of channel.

Customer newsletter: invalid out, risky case-by-case.
Cold outreach: invalid and risky out, valid only.
Product signup: block invalid, block disposable, risky optional.

Audit trail in bulk export

Every row in the CSV export includes status and classification reason. Compliance and marketing teams see why an address was marked invalid or risky — without guessing from the label alone. That makes pre-campaign audits easier and helps when an ESP asks about list quality.

What affects SMTP response time?

Corporate servers, shared hosting, and large mail domains respond with different latency. Greylisting deliberately delays the first response. Connection limits on the verifier IP and recipient firewalls can also lengthen unknown results. Bulk uses queuing and retry; for a single check a few seconds is normal, not a failure.

Bulk vs single verification

A single address gets the full layer sequence in real time. Bulk processes a list in batches with deduplication and automatic unknown retry. Layer accuracy is the same; throughput and retry policy differ. So hero form result and CSV export for the same address should be consistent, except for temporary unknown under greylisting.

Mail provider specifics

Gmail, Outlook, Polish hosts, and on-premise servers return different SMTP codes. Catch-all on a small company domain is not the same as catch-all at a global provider. Our heuristics account for domain type, but the final risky vs valid call on borderline cases always belongs to your sending policy — that is why we show classification reason, not just a colored label.

Email address format

The first filter in every verification. We validate syntax against internet mail standards before running more expensive DNS and SMTP tests.

Why we check this

Invalid syntax is the fastest signal that a record should not be sent to. Typos, missing @ signs, and illegal characters are often rejected before delivery is even attempted.

What you gain

You save credits on deeper tests and immediately see records to fix manually in CSV or CRM. Less noise in your export from the very start of list cleaning.

We detect

invalid format
invalid domain
disallowed characters
RFC compliance errors
addresses that cannot be mailed

Example

jane.doe@gmail.com
jane@@gmail.com
jane.gmail.com

Email verifier GDPR and security Pricing

Frequently asked questions

How is risky different from invalid?

Invalid is an address you should not send to. Risky is a gray zone that requires a business decision.

Does verification guarantee delivery?

No. We confirm SMTP-level deliverability potential, not opens or inbox placement.

What does unknown status mean?

The mail server did not give a clear answer (greylisting, timeout). In bulk we retry automatically.