Free Email Verifier: Check If an Email Address Is Valid

To check if an email address is real, verify it in three layers: syntax, DNS, and mailbox. Cleanlist AI runs all three. It parses the address against RFC 5322, queries the domain's authoritative nameservers for MX records to confirm a live mail server exists, then flags known disposable mailbox providers and role-based local parts like info@ or sales@. What a DNS-level check cannot do is prove that one specific mailbox exists on a live domain. That takes an SMTP handshake, where a verifier opens a connection to the mail server and asks whether it would accept mail for that exact address without ever sending one. Cleanlist AI runs the SMTP layer here for 2 free checks every 30 days, and at half a credit per email on a whole list.

An SMTP handshake is a test conversation with a mail server that checks whether an address would be accepted, without sending an email. The verifier connects to the domain's MX host, identifies itself with EHLO, declares a return path with MAIL FROM, names the target address with RCPT TO, and reads the reply code. A 250 means the server would accept mail for that mailbox. A 550 means the mailbox does not exist. Cleanlist AI runs this layer through a dedicated verification provider, at 2 free checks every 30 days on this page and half a credit per email on a list: SMTP probes are slow, several large mailbox providers rate-limit or block them outright, and running them at volume from a shared IP is a reliable way to get that IP blocklisted.

Email validation checks the format of an address, and email verification checks whether that address can actually receive mail. Validation is a parsing step: does the string have a legal local part, an @ sign, and a domain with a real top-level domain, per RFC 5322? Verification adds network checks: does the domain resolve, does it publish MX records, and will the mail server accept a message addressed to that specific mailbox? Most vendors, Cleanlist AI included, sell both under a single name, and "email checker" is the everyday umbrella term for the pair. The distinction matters in one practical case: a perfectly well-formed address at a dead domain passes validation and fails verification, and only the second result tells you whether it is safe to send.

A catch-all domain is a domain configured to accept mail addressed to any mailbox at that domain, including mailboxes that do not exist. That setting defeats SMTP verification, because the server answers "accepted" for every address, so no verifier can separate a real mailbox from a typo. Microsoft 365 tenants and small self-hosted mail servers are the common cases. The practical consequence is that an address on a catch-all domain can come back valid from any verifier and still bounce later, once the receiving server sorts the message internally and finds no recipient. Cleanlist AI reports catch-all as its own status rather than calling it valid, so you can decide per segment whether to send, hold, or go find a different contact at that company.

A disposable email address is a temporary mailbox from a throwaway provider such as Mailinator, Guerrilla Mail, YOPmail or Temp-Mail, created to receive one message and then abandoned. Disposable addresses pass syntax checks and pass MX checks, because the throwaway provider runs real mail servers, so the only thing that catches them is a maintained list of known disposable domains. Cleanlist AI checks every address against that list and marks a match as invalid. Disposable addresses matter in two places: on signup forms, where they let someone claim a free trial without a reachable identity, and inside purchased B2B lists, where their presence is a dependable signal the list was assembled from low-quality sources.

A spam trap is an email address kept alive by a mailbox provider or blocklist operator purely to catch senders mailing addresses they never earned. There are two kinds. A pristine trap was never a real person's address and was published where only a scraper would find it, so any message sent to it proves the sender harvested addresses. A recycled trap is a real mailbox that was abandoned, left to hard-bounce for months, then reactivated as a trap. No verifier can identify a spam trap with certainty, because a trap answers an SMTP handshake exactly like a live mailbox. What verification does is remove the dead and never-valid addresses that correlate with trap hits, which is why re-verifying a list before every send matters more than verifying it once.

A role-based email address belongs to a function rather than a person: info@, sales@, support@, admin@, billing@, hello@. Cleanlist AI flags these separately because they behave differently from personal mailboxes. They are usually shared by several people or routed straight into a ticketing system, they are filtered more aggressively, and a spam complaint from one counts against your sending domain exactly like a personal complaint. A role address is not invalid, and for some motions, support-led sales or procurement outreach, it is the correct target. For cold outbound aimed at a named individual, a role address is usually a sign that the contact record is a fallback rather than a real match, and worth replacing before you send.

An MX record is a DNS entry naming the mail servers responsible for a domain, each with a priority number, and an email verifier checks it because a domain with no MX record cannot receive email at all. Cleanlist AI queries the domain's authoritative nameservers directly and returns the record count and the primary mail exchange. A missing MX record is the most decisive signal available at the DNS layer: it means the address is undeliverable no matter how well formed it looks. A present MX record proves the domain accepts mail, not that the individual mailbox exists. To inspect a domain's full DNS picture, including SPF and DMARC alongside MX, use Cleanlist AI's free domain validator.

To verify a whole list, upload it as a CSV to a bulk verifier instead of checking addresses one at a time. In Cleanlist AI you import the CSV, map the email column, and Cleanlist AI runs syntax, DNS and MX checks plus an SMTP mailbox handshake and catch-all detection on every row, then returns a status per address that you can export back to CSV. Verification costs half a credit per email either way. Every new Cleanlist AI workspace starts with 14 days of Pro, free: 250 credits, 3 seats, agents, Sequences and Clu in Slack. After the trial, Starter is $49 per seat a month with 750 credits per seat, Pro is $89 per seat with 1,500, and Enterprise is custom. Annual billing takes 25% off. The $0 Free plan is 50 credits a month, enough to verify 100 addresses. Pushing the verified statuses straight into HubSpot or Salesforce is a Pro-and-above feature.

Bulk email verification is free in small volumes and paid at scale, at every vendor including Cleanlist AI. Every new Cleanlist AI workspace starts with 14 days of Pro, free: 250 credits, 3 seats, agents, Sequences and Clu in Slack, so a first bulk run of up to 500 addresses costs nothing. After the trial, the $0 Free plan is 50 credits a month and validation costs half a credit, so it covers 100 addresses a month. Free tiers read from published pricing pages on August 2, 2026: Bouncer gives 100 credits on signup, Verifalia gives 25 verifications a day that expire nightly, and Snov.io gives a 50-credit trial that renews every 30 days. No vendor verifies a 50,000-row list for free.

Keep hard bounces under 2%, and treat the thresholds the mailbox providers publish as the real limit. Google's sender guidelines require every sender to authenticate with SPF or DKIM and to keep the spam rate reported in Postmaster Tools below 0.3%, with a recommended target below 0.10%; senders of 5,000 or more messages a day to Gmail must additionally publish a DMARC policy and support one-click unsubscribe. Yahoo requires one-click unsubscribe under RFC 8058 and urges every sending domain to publish a DMARC policy, and states it will not specify a volume threshold for what counts as a bulk sender. Bounce rate and spam rate are different metrics, but they move together, and a high bounce rate is the fastest route to having a sending domain throttled.

An email can bounce after passing verification for four reasons. First, the mailbox was deactivated between the verification date and the send: Cognism reports that 22.5% of B2B data goes bad each year, so a list verified months ago has already drifted. Second, the address sits on a catch-all domain, so the mail server accepted it during the SMTP handshake and rejected it internally afterwards. Third, it was a soft bounce (full mailbox, greylisting, a temporary outage) rather than a hard bounce, and it will clear on retry. Fourth, the rejection was about you rather than the address: a broken SPF, DKIM or DMARC setup on your sending domain, or a damaged domain reputation, produces rejections that look like bounces but would happen to every recipient.

No. Email verification tells you an address exists and can receive mail, and says nothing about whether your message will be accepted. Delivery is decided on the sender side: your domain's SPF, DKIM and DMARC records, your sending IP and domain reputation, your complaint rate, how fast you ramped volume, and content filtering. Google's sender guidelines make this explicit, requiring authentication and a Postmaster Tools spam rate below 0.3% regardless of whether the recipient address is valid. Verification removes exactly one failure mode, the invalid recipient, and it happens to be the failure mode that damages sender reputation fastest. Verification cannot compensate for an unauthenticated sending domain, a cold IP pushing 10,000 messages on day one, or copy that trips content filters.

Accuracy depends on how deep the checks go, and no verifier is 100% accurate. A DNS-level check catches every malformed address, every dead or misspelled domain and every known disposable provider, and cannot rule on whether one specific mailbox exists on a live domain. An SMTP-level check adds the mailbox verdict and is conclusive except on catch-all domains, where the server accepts everything by design. Cleanlist AI's product spec for emails returned from enrichment is 98% verified, cross-checked across a waterfall of 25+ providers and a dedicated verification pass. Treat any advertised near-perfect deliverability rate as a marketing number, because SMTP gives no verifier a way to prove it.

Verify a cold list immediately before every send, and re-verify your CRM at least quarterly. The reason is decay rather than error: people change jobs, companies get acquired, domains lapse, and Cognism reports that 22.5% of B2B data goes bad each year, close to 2% a month. A list verified in January and sent in June has drifted by about a tenth. The rule Cleanlist AI recommends is to re-verify any segment not mailed in 60 days, verify every imported list before its first touch, and run a full CRM pass each quarter. Verification costs half a credit per address in Cleanlist AI, so a quarterly pass over 5,000 records costs 2,500 credits, which fits in one month of a two-seat Pro workspace at 1,500 credits per seat.