How EmailCheckPro verifies an email address

Complete one check

This section covers realtime checks: the SaaS dashboard and the synchronous REST endpoints share one check service and one response meaning. Very large lists have an asynchronous bulk option, covered at the end of this page.

1. 1

   Submit an email address

   Submit one complete email address, as described in the API documentation.

2. 2

   Use service_type=email

   The tg product checks whether the email address was registered with its mailbox provider at check time.

3. 3

   Read the result

   Read registered in the same response. Run a new check when you need an updated status.

Which email address format to submit

EmailCheckPro accepts one email address per check: the local part, an @ sign, and the domain — for example name@example.com. Any domain works, consumer mailboxes and company mailboxes alike. The domain only decides which route runs behind the scenes; you never pick one, and the response tells you which provider the address resolved to. Addresses are trimmed and lower-cased before the check, so casing and stray spaces never change the result.

• Submit the complete address. A bare local part or a bare domain cannot be checked.
• Display names and angle brackets are not accepted — send the address itself, not "Name <name@example.com>".
• Email addresses in the wrong format are rejected before any charge; a rejected format is not a "not registered" result.

What does registered mean?

registered is the answer of an email check. It only appears in a successful response, and it is a boolean: true means the address is registered with its mailbox provider at the moment of the request, false means it is not. Anything else — a timeout, an undetermined result, an invalid address — comes back as an error code instead, and EmailCheckPro refunds that check automatically. So a missing registered field never means "not registered"; it means the check did not produce a result. The value reflects the moment you asked: accounts are created and deleted all the time, so refresh the check before you act on an old result rather than caching it for weeks.

• registered=true means registered.
• registered=false means not registered.
• Handle other outcomes according to the API response code; do not infer registered yourself.

Use the result within its scope

A check reflects the status at request time. It is not identity verification or permission to contact someone.

• It does not confirm who owns the email address, whether they are online at this moment, or any message content; the activity products return last-seen time and active days, not live presence.
• A registered result does not establish consent to contact the email address.
• Run a new check when the business decision needs a current status.

Very large lists: the asynchronous option

The dashboard multi check and the API multi endpoint cover most lists. Only when a list far exceeds those limits does it make sense to submit the whole file as one asynchronous bulk task.

• Upload a .txt or .csv with one email address per line, from the bulk check page or through the API.
• The full-address check takes any domain in one file; the avatar check covers Gmail, Yandex and Mail.ru and accepts all three mixed in one file, while addresses outside those three are rejected before any charge.
• Balance is reserved for the valid lines on submit, you are charged only for email addresses that return a result, and the difference is refunded.
• The task runs in the background; download the result file when it finishes. A failed task is refunded in full.