E-mail Check Invalid or Disposable Domain API – Review & Guide

What this API does and who should use it

The E-mail Check Invalid or Disposable Domain API solves two distinct but related problems that surface repeatedly in web application development: catching email addresses that simply cannot receive mail, and blocking throwaway addresses created specifically to bypass registration walls or evade bans.

The first problem—invalid domains—is more subtle than it looks. A user can type a syntactically valid address like [email protected] that passes any regex check but will silently drop every email you send. The API detects this by querying live MX records in DNS, so it catches real-world deliverability failures rather than just formatting issues.

The second problem—disposable addresses—is handled through a maintained blacklist combined with heuristic analysis. Services like Mailinator are caught by the blacklist, while newer or obscure throwaway providers can be flagged by behavioral patterns the API applies at query time.

The target audience is broad: any team running a signup flow, gating content behind email verification, accepting user-generated content, or running an anti-abuse system will find the validation logic directly applicable. It is equally useful for batch-cleaning an existing email list.

Endpoint walkthrough

The API exposes a single endpoint:

GET /

You pass the email address as a query parameter, and the response includes structured data about the validity check. Based on the documented fields, a typical response includes:

• valid — the primary boolean outcome (true/false)
• reason — a human-readable explanation when the check fails, for example Blacklist for known disposable providers
• mx_host — the actual MX hostname resolved from DNS (e.g., mail.mailinator.com)
• mx_info — a descriptive string explaining which MX pointer was used and its DNS priority
• mx_ip — the resolved IP address of the mail server

The reason field is particularly useful for communicating failures to end users or logging them for analytics. You can distinguish between "domain has no MX record" (likely a typo) and "domain is on the disposable blacklist" (likely abuse), and tailor your application's response accordingly.

With a reported average latency of 442 ms and a 100% success rate across observed calls, the API is well-suited for synchronous use during form submission. That said, 442 ms is a noticeable pause in a user-facing flow—consider running the check asynchronously or after initial client-side validation to keep perceived performance tight.

Pricing breakdown

The API follows a freemium model with four tiers:

The free BASIC plan is genuinely useful for prototyping, internal tooling, or low-traffic applications. At 1,000 requests per month, it supports a small but real user base—if your signup rate is under roughly 33 per day, you can stay on the free tier indefinitely.

The jump to PRO at $50/month is significant in cost but delivers 200× the capacity. At that volume, the per-request cost works out to $0.00025, which is competitive for a check that combines DNS lookup and disposable-domain intelligence. ULTRA and MEGA follow a near-linear pricing curve, so there is little penalty for growing into higher tiers.

For reference, if your application processes 10,000 signups per month, PRO covers you comfortably. At 600,000 signups per month, MEGA is the right fit. There is no published overage policy in the available data, so confirming behavior at limit thresholds before going to production is advisable.

Practical use cases

Signup form validation is the most common application. Rather than discovering an undeliverable address after a welcome email bounces, you reject or warn at the point of entry. The MX-based check catches domain typos that look valid on the surface.

Disposable email blocking is the second major use case. Forums, SaaS trials, and freemium products are frequently abused by users who sign up with throwaway addresses to reset trial periods or avoid bans. The blacklist and heuristic layer address this directly.

Email list hygiene is a less obvious but valuable batch use case. If you have an existing subscriber list with unknown quality, running addresses through the API can identify undeliverable entries before a campaign send, protecting your sender reputation.

Fraud and abuse detection systems can use the reason field as one signal among many. A disposable domain is not definitive proof of fraud, but it is a meaningful risk indicator when combined with other signals.

Limitations and things to check before integrating

A few practical considerations worth validating before committing to integration:

• Single endpoint scope: The API confirms domain validity and disposable status; it does not verify that the specific mailbox exists (that would require SMTP probing, which most providers avoid to prevent abuse). Factor this into your validation strategy.
• Latency in synchronous flows: 442 ms average means some requests will take longer. Build in appropriate timeouts and a graceful fallback so a slow API response does not block your form submission entirely.
• Blacklist freshness: Disposable email services multiply rapidly. The effectiveness of the disposable check depends on how frequently the provider updates its blacklist and heuristics. The documentation mentions heuristic methods in addition to the blacklist, which helps cover newer domains, but this is worth monitoring in production.
• Rate limits within a plan: The documented limits are monthly totals. If you have bursty traffic patterns (e.g., a product launch), confirm whether there are per-second or per-minute rate limits beyond the monthly quota.
• Single endpoint architecture: With only one endpoint, there is no batch API documented. High-volume list cleaning would need to be parallelized on the client side.

With over 5,400 marketplace subscribers and a popularity score of 9.9 out of 10, the API has a large user base, which is a reasonable proxy for reliability and continued maintenance.

Getting started

The API is available through the marketplace and documented on the Check-Mail.org website. To integrate:

1. Subscribe to the BASIC plan to get API credentials at no cost.
2. Make a GET request to the root endpoint with your target email address as a query parameter.
3. Parse the valid boolean for the primary decision, and use reason, mx_host, and mx_ip for logging or user-facing messaging.
4. Test against known disposable domains (Mailinator is documented as an example) to confirm your integration handles the valid: false + reason: Blacklist path correctly.
5. Monitor your monthly request count and upgrade to PRO before you approach the 1,000-request ceiling if your traffic warrants it.

The combination of domain MX validation and disposable-email detection in a single lightweight call makes this API a pragmatic addition to any signup or account-creation flow.