Check an email address for free
Enter an address: it is submitted to the validation API and the result details each check run, with its verdict. No account, no bank card, no message sent to the recipient. Each verdict is explained in plain words.
What verifying an address means
Verifying an address means establishing whether it can receive a message, without sending it one. The checks read the syntax, the public declarations of the domain and reference lists, then query the receiving server about the mailbox. Each produces a named verdict, not an opaque overall mark.
The gap between "this address looks correct" and "this server accepts this mailbox" is the whole craft. The first checks rely only on what is publicly declared: they are immediate and free. The last one opens a dialogue with the server hosting the mailbox: it is the most thorough verification, and the only one that consumes a credit.
Of the 20 checks run on each call, 19 are free and the last one, SMTP verification, is charged according to a single rule: A credit is charged if and only if SMTP verification was requested and the final status is not "unknown".
How to read the result
The result carries one status out of four, a definition, and the business decision that goes with it. These four statuses are those of the API: the public page and the programmatic call return exactly the same vocabulary, for the same address, at the same moment.
| Status | What it means | What to do with it |
|---|---|---|
| Valid | The address exists and the receiving server agrees to accept it. When SMTP verification is requested, this status is only returned if the server confirmed the mailbox. | Accept the address. |
| Invalid | The address cannot receive mail: malformed syntax, a domain with no MX record, a mailbox refused by the server, or an address present in the block list of the organisation. | Reject the address, it will produce a hard bounce. |
| Risk detected | The address is technically acceptable but carries a risk signal: disposable domain, malicious domain, typosquatted domain, no-reply address, or an overall score below the degradation threshold. | Accept under conditions, or discard according to the configured business policy. |
| Unknown | The receiving server gives no definitive answer, for instance on a catch-all domain or during a greylisting delay. The reason is named in the response. | Decide according to context. No credit is charged. |
Tricky cases, clearly flagged
A domain that accepts every address, a server that delays: these tricky cases are recognised and flagged with a dedicated status, unknown, rather than settled at random. This status is never charged.
In batch processing, the addresses of a server that delays are verified again automatically during a second pass, which most often obtains a firm answer. You only pay for the answers that inform you.
What happens during the test
No message is sent to the address analysed: the probe opens a dialogue with the receiving server and stops before sending. The analysis runs on the YesWeCheck validation infrastructure. The result displayed is that of the production API, not a simulation written for the page.
No message sent
SMTP verification opens a session with the receiving server, announces the sender and the recipient, then stops before writing the message. No mail arrives in the mailbox being analysed, and the person whose address is verified receives nothing.
Data hosted in France
Data hosted in France, by OVHcloud.
What is kept
The public demo feeds no validation history: that history is only written for the authenticated traffic of an account. What outlives a test concerns the domain, not the address, and benefits everyone: a domain recognised as answering for everything is not queried again for nothing.
Beyond a single address
Beyond a single address, YesWeCheck processes entire lists in batch processing, and protects your sign-up forms with the API or the widget. Same checks, same status vocabulary, whatever the way in.
An entire list
Batch processing imports a file and returns the same verdict line by line. A preliminary audit measures the quality of the file without charging any credit.
A sign-up form
The widget checks the address as it is typed, and the API does the same from a program, with the same status vocabulary.
Frequently asked questions
- Can an email address be verified without sending a message?
- SMTP verification opens a session with the receiving server, announces the sender and the recipient, then stops before writing the message. No mail arrives in the mailbox being analysed, and the person whose address is verified receives nothing.
- Do I need to create an account to test an address?
- No. The tool on this page submits the address to the production API and displays the full response, with no account, no bank card and no installation. An account becomes useful to process a list, connect a form or call the API from a program.
- What does the unknown status mean?
- It flags a receiving server that did not allow a conclusion about the mailbox, for instance a domain that accepts every address or a server that delays. Rather than a verdict at random, YesWeCheck says so clearly, and this status is never charged.
- Is the address tested kept?
- The public demo feeds no validation history: that history is only written for the authenticated traffic of an account. What outlives a test concerns the domain, not the address, and benefits everyone: a domain recognised as answering for everything is not queried again for nothing.
Content updated on 7 September 2026.