To verify an email address, you have to ask the server that would receive the mail. A format check cannot do that. The BillionVerify Email Verifier takes one address and runs a live SMTP handshake against the receiving server. This page covers what that handshake proves and where its limits are.
Key facts:
- The BillionVerify Email Verifier tests syntax, then MX, then the mailbox over SMTP, and finally adds risk flags.
- It does not send an email body or place a message in the inbox.
- Per RFC 5321, a 5xx reply is a permanent refusal and a 4xx reply is temporary, which is why some answers stay unknown.
- The limit is 20 free full checks per IP every 24 hours, no sign-up, one address at a time.
- It runs the same check as the Email Checker, and this page is written around the SMTP proof.
How to verify an email address, layer by layer
Structure
The address is normalized and split at the @ sign. Missing domains, broken separators and illegal characters fail here, before any network call.
MX records
Next the domain is checked for a published mail route. An MX record names the server that takes mail for the domain. If none exists, the tool cannot continue to the mailbox. An MX record proves the domain is ready for mail. It says nothing about one person’s inbox.
The SMTP handshake
This is the layer that separates a verifier from a validator. The tool opens a conversation with the receiving server and names the recipient. It reads the reply and stops before the message is sent. The server answers one of three ways: it accepts the recipient, it refuses for good, or it defers. The result page shows these as a pass, a fail or an inconclusive mark on the SMTP mailbox chip.
Risk flags
Disposable, role and catch-all signals arrive on the same result. They explain why an accepted address may still deserve a second look.
How to use it on a bounced list
Take the recipients that bounced, and verify a few before you resend. Paste one address and press Verify email. When a bounce reads as “user unknown”, the verifier should agree. When it does not, the bounce may have been soft.
If you want the checker’s flag-first reading of the same result, use BillionVerify’s online checker.
How to read the answer
Valid
The mailbox accepted the probe at that moment. It is safe to treat as deliverable for most uses, but it is a snapshot.
Invalid
The mailbox does not exist or permanently refuses mail. Do not send to it again.
Catch-all
The domain accepts every local part. SMTP then says “accepted” even for names that do not exist, so the probe cannot prove this person is real. Keep catch-all addresses in their own segment.
Unknown and Risky
Unknown means the server deferred or answered vaguely. Greylisting and provider policy cause this. Risky means the address exists with elevated risk. Treat both as “review”, and never as safe.
What the verifier cannot prove
A valid answer does not guarantee inbox placement. It also does not guarantee that the owner reads the mail. It only shows that the server accepted the recipient. Before each resend, verify one address in real time for every failure you plan to keep. For the rest, use the authentication and reputation checks elsewhere on this site, starting with the MX lookup for the domain.