Seatext library / BotRefund evidence
Which Disposable Email Domains Does BotRefund Block? The Real Answer
BotRefund does not publish a public list of disposable email domains it blocks. Instead, it uses disposable email patterns as one behavioral signal among many, combined with cross-checks, which means the exact blocked set...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
What BotRefund Actually Blocks
BotRefund does not maintain or publish a static list of disposable email domains. The question assumes such a list exists, but the company's own materials treat disposable email patterns as one behavioral signal inside a larger detection model, not as a standalone blocklist.
For example, in its guide to affiliate lead fraud, BotRefund lists “Disposable email patterns” as a red flag. It describes them as “a high concentration of signups from obscure domains or matching specific character lengths.” That is a pattern, not a domain list. Similarly, its Meta ads invalid traffic guide mentions “invalid email domains” as part of contactability checks, but again without naming specific domains.
So the honest answer: there is no public list to reference. The domains BotRefund considers disposable change over time and are folded into its scoring, not exposed to advertisers.
How BotRefund Catches Disposable Email Use
BotRefund’s approach is behavioral, not just domain-based. It installs a lightweight script that tracks sessions from click to conversion. The system looks at 106 independent checks, according to its own pages, including:
- Ghost click detection – catches click activity that lacks human intent.
- Honeypot traps – watches for bots responding to hidden elements.
- Robotic linear mouse movements – flags unnaturally straight pointer paths.
- Superhuman input speed – identifies sub-millisecond form fills.
- Absence of humanlike tremor – detects overly smooth motion.
Applied to forms, these signals reveal a session where an email field is populated instantly with a disposable domain, without mouse movement, scrolling, or field corrections. That pattern is what triggers a score, not the domain itself.
BotRefund also cross-checks each signal. A single anomaly is not a verdict. Privacy tools, corporate networks, or unusual devices can produce false positives, so the system weighs the complete picture before flagging a conversion.
Why There Is No Public Blocklist
Publishing a static list would be self-defeating. Disposable email providers spin up new domains constantly. A published list would become stale within days and would give fraudsters a direct map of what to avoid.
Instead, BotRefund treats disposable email as a moving target. The engine considers domain reputation, character patterns (like fixed-length random strings), and whether the domain appears in multiple submissions from the same session. That dynamic approach is more effective than a static blacklist.
Additionally, a public list would create a false sense of security. Advertisers might think “if the domain isn’t on the list, it’s safe.” BotRefund avoids that by never exposing the list.
Options for Handling Disposable Email Signups
If you’re trying to block disposable emails on your site, you have several options. Each has trade-offs:
Option 1: Rely on BotRefund’s behavioral detection
BotRefund doesn’t give you a list, but it gives you a verdict. It scores each conversion as approve, review, hold, or reject. You get evidence, not just a score. This handles new domains that static lists miss.
Option 2: Use a third-party disposable email verification API
Services like block-disposable-email.com maintain large lists (their own site claims over 190,000 unique domains). These are useful for real-time email validation. But they only catch known domains. A brand-new disposable domain will slip through until added.
Option 3: Build your own list
You can collect domains from failed follow-ups or high-bounce rates. This is slow and reactive. It also requires ongoing maintenance to stay accurate.
Option 4: Combine multiple signals
Use a verification API for instant checks, plus behavioral analysis for everything else. This is the most robust approach, but it adds complexity and cost.
Trade-Offs at a Glance
| Approach | Strengths | Weaknesses | Bottom Line |
|---|---|---|---|
| BotRefund behavioral detection | Catches new domains, avoids false positives with cross-checks | No public domain list; requires script installation | Best for fraud protection across a full user session |
| Third-party domain verification API | Fast, simple, known-domain coverage | Misses brand-new domains, can have false positives | Use as a first pass, not your only shield |
| Your own manual list | You control it, no external dependency | Reactive, time-consuming, stale quickly | Only useful as a supplement |
| Combined approach | High accuracy, covers both known and new domains | Higher cost, more integration work | Best for high-value signups |
Practical Steps to Reduce Disposable Email Signups
- Start with a free audit. BotRefund’s homepage offers a free bot audit that will show you how many suspicious sessions you’re getting. This gives you a baseline.
- Install BotRefund’s script. It’s described as taking about one minute. No credit card is required. The script collects behavioral data on every visitor.
- Review payout reports. Before each affiliate payout cycle, BotRefund generates a scored report. Look for a high concentration of “review” or “hold” tags tied to email-related anomalies.
- Layer an email verification API. For extra safety on high-value forms, add a real-time disposable domain check. But treat it as one input, not the whole answer.
- Set up alerting. If you see a spike in rejections from a particular domain pattern, investigate whether it’s a new fraud campaign or a misconfiguration.
Limitations and When This Advice Doesn’t Apply
BotRefund’s behavioral detection is not a guaranteed catch-all. Here’s what to keep in mind:
- Privacy tools can mislead. Users with strict browser privacy settings or VPNs may produce signals that look bot-like. BotRefund cross-checks, but false positives are possible.
- It’s not a substitute for email validation. If you need to verify that an email address is deliverable and belongs to a real person, you still need an email verification service.
- It doesn’t give you a domain list. If your goal is to see which domains are blocked, you won’t get that from BotRefund. You’ll get a score per conversion.
- It’s designed for fraud, not generic spam filtering. If you’re dealing with newsletter signups where disposable emails are a nuisance but not a financial threat, a simple verification API may be enough.
Frequently Asked Questions
Does BotRefund publish a list of disposable email domains?
No. The company does not make any blocklist public. Its documentation refers to disposable email patterns as a signal, not a static list.
How can I check if a specific domain is blocked by BotRefund?
You can’t directly, because there is no public lookup. You could run a test with a disposable email address and see how BotRefund scores the conversion, but that’s a manual, one-off check.
Is BotRefund’s detection better than a domain blocklist?
For fraud prevention, yes. A blocklist only catches known domains, while BotRefund catches the behavioral pattern. The two complement each other, but BotRefund’s approach is more adaptable.
What should I do if I see a lot of disposable email signups?
Run a free bot audit first. Then decide whether the traffic is from real people using temporary emails for privacy, or from bots. BotRefund’s scoring will help you distinguish.
Will BotRefund cause false positives for some legitimate users?
Its own documentation acknowledges that privacy tools and unusual devices can create anomalies. It cross-checks signals and uses a prediction AI to weigh the full pattern, but no system is perfect.
Can I combine BotRefund with a verification API?
Yes. That’s a strong combination. Use the API for instant domain checks and let BotRefund handle the behavioral layer.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.