When you press Check, the page first runs four checks locally, without contacting any server. Non-printable and non-ASCII characters are removed and the address is lowercased first. Only if the format check passes does the address go to the server for the network checks described in the next section.
Format: the address must match a simplified pattern: 1 to 64 letters, digits or the characters . _ % + - before the @, then a domain of letters, digits, dots and hyphens that ends in an alphabetic top-level domain of at least two letters.
Disposable domain: the domain is compared with a built-in list of around forty well-known temporary-mail domains, including inboxburn.com itself.
Free provider: the domain is compared with a list of common consumer mailbox providers such as gmail.com, outlook.com, yahoo.com, proton.me and mail.ru.
Role-based address: the part before the @, ignoring any +tag, is compared with generic mailbox names such as info, support, admin, sales, noreply and postmaster.
Network checks on the InboxBurn server
If the format is valid, your browser sends the full address to the InboxBurn API. The server verifies the Cloudflare Turnstile challenge when it is enabled and allows ten requests per minute per client. It then performs the following steps:
Looks up the domain's MX records in DNS and sorts them by priority; up to five are shown.
Resolves the highest-priority mail server and refuses to connect if it points to a private or reserved IP address.
Opens an SMTP connection on port 25, waits for the 220 greeting, sends EHLO inboxburn.com and MAIL FROM:<[email protected]>, then RCPT TO with your address.
Reads the reply to RCPT TO and immediately sends QUIT. No DATA command is issued, so no message is ever delivered to the mailbox.
Gives up after about nine seconds if the server does not respond in time.
Reading the results
A 250 or 251 reply to RCPT TO is shown as mailbox exists, a 550 to 554 reply as mailbox does not exist, and anything else, including 4xx temporary replies, as uncertain. The verdict banner combines all checks in a fixed order: invalid format, then disposable domain, missing MX records, and a definite does-not-exist reply. A confirmed mailbox on a non-free, non-role address is shown as good; free-provider and role-based addresses are marked for caution; otherwise the banner reports that the format is valid.
Free and role-based addresses are perfectly legitimate. The caution label matters mainly for business sign-ups and mailing lists, where shared role mailboxes are read by several people and generate complaints more often. The server route does not store the address in a database; because it travels as a URL parameter, it can appear in standard web-server logs like any URL.
Why a valid-looking address can still bounce
Format and DNS checks only show that delivery is possible in principle, and the SMTP answer is a snapshot. Delivery can still fail later for several reasons:
Catch-all domains accept every recipient during the SMTP dialogue and bounce or discard unknown ones afterwards, so mailbox exists can be a false positive.
Many large providers deliberately answer the same way for existing and nonexistent recipients, or temporarily defer unknown senders (greylisting), to stop address harvesting. These cases show as uncertain.
A mailbox can exist but be full or disabled, or the receiving server can reject a real message because of its content, the sender's reputation or failed authentication.
Only the highest-priority MX server is tested. If it cannot be reached from InboxBurn, a backup server may still accept mail.
Mailboxes are created and deleted all the time; a result describes one moment.
Limitations of the format check
The pattern is deliberately stricter than the standards. RFC 5321 and RFC 5322 also allow quoted local parts and other special characters, and SMTPUTF8 permits non-ASCII addresses. Such addresses are rare in practice but are reported as invalid here, and internationalised domain names must be written in their ASCII (xn--) form.
If a domain publishes no MX records, the result says so. The SMTP standard allows falling back to the domain's own address record in that case, but this tool does not attempt that fallback. In practice nearly all domains that receive mail publish MX records, so a missing MX is a strong warning sign. The disposable and free-provider lists are short, hand-maintained lists, not comprehensive databases: an unfamiliar temporary-mail domain will pass the disposable check.
Using validation responsibly
On sign-up forms, check the format as the user types and confirm ownership with a verification email; only a clicked link or entered code proves that someone controls the address.
Do not reject an address just because the SMTP result is uncertain; you would block legitimate users of providers that hide mailbox existence.
Remove addresses that hard-bounce with a 5xx error from mailing lists promptly; repeatedly sending to invalid addresses harms your sender reputation.
Avoid bulk SMTP probing. Mail servers can treat it as directory harvesting and block the probing IP address.