A: Thanks for reaching out and raising this question - it’s an important one.

Mailcheck is designed primarily as an email validation tool, not an access restriction system. This means that while we can accurately detect disposable, temporary, or low-quality email addresses via our API and bulk checks, it's up to each platform to implement logic based on the validation results - for example, blocking temporary emails during registration.

If you tested our sign-up using a disposable address, you’re right: the system allowed it. That’s intentional - our public-facing portal doesn’t block any emails because we want users to test freely, including with temporary emails.
However, when integrated into your own product via our API, you have full control to:
- Block disposable or low-quality emails in real-time
- Prevent signups from suspicious sources
- Improve deliverability and database hygiene
In short: our detection engine works - but how it’s enforced is up to the implementation.
Let me know if you’d like a quick demo or help integrating Mailcheck to enforce stricter logic on your side.