What this checker does
The tool makes two checks and nothing more. First it tests the address with PHP's FILTER_VALIDATE_EMAIL filter, which applies the address syntax of RFC 5321 and RFC 5322: one @ sign, a local part of permitted characters without leading, trailing or doubled dots, and a domain made of valid labels (see the PHP filter constants). Second, if the format passes, it asks our server's DNS resolver for the domain's MX records, the records that name the servers accepting mail for that domain.
The three result cards map onto those checks. "Format" is the syntax test. "Domain" turns green whenever a domain part could be read from a well-formed address; it is not a lookup, so it says nothing about whether the domain exists. "MX Records" is the DNS check. A domain that publishes a Null MX record, the "0 ." entry defined in RFC 7505 to declare that it accepts no mail, counts as having no mail servers.
Two results from our tests on 11 October 2026 show the range. info@edeskcloud.com passed both checks, with mx1.hostinger.com and mx2.hostinger.com as its mail servers. someone@gmial.com, a common misspelling of gmail.com, passed the format check and failed the MX check, because that domain publishes no mail servers. A mistyped domain that does run mail would pass both checks, so the tool catches some typos and not others.
What it cannot tell you
Whether the mailbox exists. Confirming that would mean connecting to the mail server and asking it to accept the recipient, which many providers refuse to answer, or answer "yes" to for every address (a catch-all). This tool never contacts the mail server. A green result means "this address is well formed and its domain can receive mail", not "this person exists" or "a message will be delivered".
Whether mail could still arrive without MX records. RFC 5321 says that when a domain has no MX records a sender should treat its A or AAAA record as an implicit mail server, and some small domains still receive mail that way. The tool reports MX records only, so read a failed MX check on a domain with a working website as "probably not set up for mail", not as proof.
Disposable, role-based or risky addresses. It keeps no list of temporary-mail domains and does not flag info@, admin@ or sales@ addresses. It also does not check SPF, DKIM or DMARC, which concern the sender's domain rather than the recipient's; you can read those TXT records with the DNS checker, and the hosting checker lists a domain's MX hosts with their priorities.
Keeping a sending list in good shape
Format and MX checks catch typos and dead domains before you send, which keeps hard bounces down, and bounce and complaint rates are what mailbox providers judge you on. Google's Email sender guidelines ask bulk senders to keep the spam rate reported in Postmaster Tools below 0.10% and never to reach 0.30%, to authenticate with SPF, DKIM and DMARC, and to offer one-click unsubscribe. A clean list helps with the first of those; the others are configuration on your own domain. Checking addresses at signup, sending a confirmation message before the first real email, and removing anything that hard-bounces straight away will do more for deliverability than cleaning a list after the fact.