Academy › Email Verification Certification › Lesson 2 of 5
How an address is checked without sending an email
A good verifier never sends a message to the person you are checking. Instead it runs a series of checks, each one stricter than the last.
- Syntax. Is it written like an email address at all? A missing @, spaces or a bad domain end the check here.
- Domain. Does the domain exist in DNS? Typos such as gmial.com are caught at this step.
- Mail servers (MX records). Does the domain say which servers receive its email? A domain without any cannot receive mail.
- The mailbox (SMTP). The verifier connects to the company's mail server and starts the same conversation a real email would: "I have a message for priya@company.com". The server answers whether it would accept it. The verifier then hangs up before any message is sent.
Extra checks that change the answer
- Disposable domains: temporary inboxes that disappear after a few minutes.
- Role addresses: shared inboxes such as info@ or sales@, which rarely reach a decision-maker.
- Catch-all detection: the verifier also asks about an address that cannot exist. If the server says yes to that too, it accepts everything, and a "yes" proves nothing.
When servers do not answer clearly
Some servers ask senders to come back later (greylisting), slow down strangers, or block unknown connections. A careful verifier retries politely and, if it still has no clear answer, says Unknown rather than guessing.
Key idea: the mailbox check is a conversation that stops just before the email is sent. Nothing ever reaches the person.