Submit up to 1,000 email addresses and get each one sorted into one of three origins - disposable, free or corporate. The signal that separates a genuine business signup from a ten-minute address created to claim a trial.
The service checks the origin of an address rather than the mailbox behind it. Every address lands in one of these, and each means something different for what you do next.
A throwaway address from a temporary-mail service, designed to be abandoned within minutes. Almost always a deliberate choice to stay anonymous - the strongest signal in the set, and usually the one you act on.
A consumer mailbox from a public provider - the gmail.com and outlook.com kind. Entirely legitimate, and millions of real businesses run on one, so this is a soft signal rather than a red flag.
An address on an organisation's own domain. For B2B work this is the useful end of the scale: it ties a person to a company, which is what makes the rest of your enrichment possible.
This is the point most people miss, and it's the reason this service exists separately from verification.
Temporary-mail services work. Their mailboxes accept mail, so an address from one will pass a deliverability check quite happily - the Email Address Verifier would report it as receiving, and it would be right. Nothing is broken about a throwaway address; it just belongs to somebody who doesn't want to be found next week.
So the two services answer different questions. Verification asks whether a message will arrive. Classification asks what kind of address you're dealing with. A signup can pass the first and fail the second, and for fraud and trial abuse it's the second that catches it.
Run both when the stakes justify it: classify to decide whether you want the record at all, verify to check the mail will land before you send anything.
An email address is the entire input. Nothing else to configure.
No domain list to maintain, no blocklist to keep current - that's the part this replaces.
One row per address you submitted, carrying its classification.
The three possible values are the ones described above - disposable, free and corporate - and those are documented. What the reference does not publish is the response field names, so we're not going to print a column identifier and have you build a parser against a guess. The categories are dependable; the exact column naming is something to confirm from real output.
Which takes about a minute: run a handful of addresses on the free tier where you already know the expected answer - one from a temporary-mail service, one consumer mailbox, one on a company domain - and you'll have both the column names and a sanity check on the classification at the same time. Other services here do publish their schemas in full; the Company Insights and SimilarWeb pages list every field.
One category column plus three matching flags, so you can filter either by name or by boolean without reshaping the sheet.
disposable, free or corporate.type and the three flags say the same thing two ways. Filter on type when you want a readable sheet, or on the flags when you want arithmetic - summing disposable across a signup cohort gives you a count without a group-by. Nothing here tells you whether mail would arrive; that is the Verifier.
Where knowing the origin of an address changes a decision.
Free trials get farmed with throwaway addresses, and a serial abuser can create a new one every few seconds. Because temporary addresses pass ordinary validation, classification is what actually catches this - and it catches it before the account is provisioned rather than after the credits are spent.
For B2B, an address on a company domain is a materially stronger signal than a consumer mailbox, and a throwaway is barely a lead at all. Sorting inbound by origin puts sales attention on the enquiries most likely to convert, without anyone reading a list by hand.
Enrichment and verification both cost money per row, and spending either on throwaway addresses is waste. Classifying first is the cheapest filter in the pipeline: drop the disposables, then pay to enrich only the records worth enriching.
Both are about how you act on the result rather than the result itself.
Free is not a red flag. Enormous numbers of real, paying, entirely legitimate businesses run on a consumer mailbox - sole traders, small agencies, tradespeople, most of the long tail. Treating "free" as suspicious will quietly reject a lot of good customers. Use it as one weak input to a score, not as a gate.
Temporary-mail services appear faster than any list. New throwaway domains are created constantly, which is precisely why maintaining your own blocklist stops working - but it also means no classifier catches every one on the day it launches. Expect very good coverage rather than perfect coverage, and don't design a flow whose only defence is this single check.
No subscription, no minimum, no per-seat licence. Your first 500 rows are on us - after that, pay-as-you-go.
Every new account, one-time. No credit card required. All scrapers unlocked - enough to classify a real slice of your signups and see what proportion of them are throwaways.
Roughly $2 per 1,000 addresses. As the cheapest filter to run first, it usually pays for itself in the enrichment and verification you no longer waste on junk records.
Volume pricing, SLAs, dedicated workers and bespoke onboarding for teams screening large numbers of registrations. Tell us your numbers and we'll quote.
LIVESCRAPER10 at checkout.Classification is the cheapest step and belongs first. These are what you run on the records that survive it.
Checks whether the mailbox accepts mail, at the server. A disposable address passes this happily, which is exactly why the two checks answer different questions and work best together.
Once you know an address is on a company domain, this turns that domain into named contacts with titles. The natural next step on anything classified corporate.
One of the lightest services in the catalogue, and it's worth understanding why.
The question this answers is about the provider, not the person: is this domain a temporary-mail service, a public consumer provider, or an organisation's own? That's a fact about infrastructure. Nothing about the individual is looked up, no mailbox is read, and nothing new is collected - you already hold the addresses you submit.
An email address identifying a person is still personal data, so submitting one for checking is processing it, and the ordinary transparency and erasure duties apply to your records. But there's no lookup of a person here and no new personal data acquired, which makes this a much lighter question than contact discovery or anything touching identity.
One practical fairness point rather than a legal one: if you use this to reject signups, tell people. A user turned away with no explanation will assume your product is broken.
The questions we hear most. Anything else? Talk to us - humans, not bots, write the answers.
Paste up to 1,000 addresses and get each sorted into disposable, free or corporate - the cheapest filter to run before you enrich or verify anything. Your first 500 rows are free.
Not every email address is offered in good faith. Free trials get farmed with throwaway addresses created in seconds and abandoned just as fast, inbound lead forms fill with entries nobody intends to answer, and lists bought or inherited carry a proportion of records that were never real. The Disposable Email Checker sorts that out by origin: submit up to 1,000 addresses in a run and each comes back classified as disposable, free or corporate. Disposable means a temporary-mail service. Free means a public consumer provider of the gmail.com or outlook.com kind. Corporate means an address on an organisation's own domain - the useful end of the scale for B2B, because it ties a person to a company and makes everything downstream possible.
The single most important thing to understand is that a disposable address is usually a perfectly valid one. Temporary-mail services work: their mailboxes accept mail, so a throwaway address will pass a deliverability check without difficulty, and the Email Address Verifier would correctly report it as receiving. Nothing is broken about such an address - it simply belongs to somebody who does not intend to be reachable next week. That is why verification and classification are separate services rather than one. Verification asks whether a message will arrive; classification asks what kind of address you are dealing with. A signup can pass the first and fail the second, and for trial abuse and signup fraud it is the second check that catches it.
Three workflows account for most of the use. Trust and safety teams screen registrations before an account is provisioned, catching serial abusers at the point where it is still cheap to do so rather than after the credits have been spent. Sales and marketing teams rank inbound enquiries by origin, since a company-domain address is a materially stronger signal than a consumer mailbox and a throwaway is barely a lead at all. And marketing operations teams run classification first in a pipeline, because both enrichment and verification cost money per row and spending either on a disposable address is pure waste - this is the cheapest filter available and it belongs at the front.
Two cautions about acting on the result. Free is not a red flag: an enormous number of real, paying, legitimate businesses run on a consumer mailbox, particularly sole traders, small agencies and the long tail generally, so treating "free" as suspicious will quietly turn away good customers. Use it as one weak input to a score rather than as a gate. And no classifier is perfectly current, because new temporary-mail domains appear constantly - which is precisely why maintaining your own blocklist stops working, but also means you should expect very good coverage rather than complete coverage and avoid designing a flow whose only defence is a single check. On the legal side this is among the lightest services here: the question concerns the provider behind an address rather than the person using it, no mailbox is read and no new personal data is acquired. One fairness point that isn't a legal obligation but should be: if you reject signups on this basis, tell people why, because a user turned away without explanation will assume your product is broken. Start free: your first 500 rows cost nothing and need no credit card.