Question 1

How to update the disposable email domain list in MailChecker?

Accepted Answer

Edit the central list.txt file in the GitHub repository and submit a pull request; running 'npm run build' regenerates all language libraries from this list. Regular updates are community-dependent, so you may need to monitor for new releases.

Question 2

MailChecker vs validator.js for email validation?

Accepted Answer

MailChecker adds disposable domain detection on top of basic format validation, while validator.js focuses solely on syntax and standards. Use MailChecker if blocking temporary emails is critical; otherwise, validator.js is lighter for format-only checks.

Question 3

Can MailChecker verify if an email address actually exists?

Accepted Answer

No, MailChecker only validates format and checks against its disposable domain database; it does not perform real-time deliverability checks like sending confirmation emails or querying MX records.

Question 4

How to add custom domains to the blacklist for my project?

Accepted Answer

You can fork the repository, append domains to list.txt, and rebuild the libraries locally. For production, consider maintaining a separate list or contributing to the main project to benefit the community.

Question 5

Is MailChecker suitable for high-traffic websites or APIs?

Accepted Answer

Yes, but the in-memory domain set may add memory overhead. Validation calls are fast O(1) lookups, so performance impact is minimal after initial load, but test in your environment for scalability.

Question 6

How to integrate MailChecker with a Django project?

Accepted Answer

Use the django-indisposable package mentioned in the README, which provides a Django validator wrapper. Alternatively, import the Python library directly and call MailChecker.is_valid() in your views or forms.

mailchecker

What is mailchecker?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions