Spam bots and freeloaders love disposable email addresses: they register accounts, place fake orders, and post comments with throwaway inboxes \u2014 addresses that are dead an hour later.<\/p>\n\n
Wonderful Disposable Email Blocker<\/strong> checks the submitted email address against a list of thousands of known disposable email domains and lets you block four areas of your site independently:<\/p>\n\n You decide what happens<\/strong> when a submission is blocked:<\/p>\n\n Your own lists:<\/strong><\/p>\n\n Built-in safety rails:<\/strong><\/p>\n\n Domain data:<\/strong> the plugin ships with a bundled copy of the community-maintained disposable-email-domains<\/a> list (thousands of domains, CC0 \/ public domain) and works completely offline out of the box. Optionally, one click downloads the newest list from GitHub onto your server, after which it refreshes itself once a week.<\/p>\n\n For developers: the This plugin can download the current disposable domain list from raw.githubusercontent.com (the disposable-email-domains community project on GitHub). The download only happens when you actively opt in by clicking the \"Update domain list now\" button on the settings page; afterwards a weekly scheduled refresh re-downloads the list from the same URL. The request contains no personal data whatsoever \u2014 it is a plain file download. Visitor email addresses are always checked locally on your server and never leave your site. This service is provided by GitHub: terms of service<\/a>, privacy statement<\/a>.<\/p>\n\n Without the opt-in the plugin makes no external requests at all and uses only the bundled list.<\/p>\n\n\n Nothing yet \u2014 all four areas start switched off. Blocking starts only for the areas you explicitly enable, so activating the plugin can never break a running shop.<\/p><\/dd>\n No. All checks run locally against a list file on your server. The only external request is the optional domain list download, which you trigger yourself and which contains no personal data.<\/p><\/dd>\n Put their email address (or their whole domain) on the allowlist. The allowlist always wins over every blocklist.<\/p><\/dd>\n From the community-maintained disposable-email-domains project (CC0 \/ public domain). A copy is bundled with the plugin, so it works completely offline; the update button fetches the newest version from GitHub.<\/p><\/dd>\n A checkout ends with a real order and a payment. Faking success would mean taking the customer's money without recording an order \u2014 so blocked checkouts always get an honest error message instead.<\/p><\/dd>\n Yes, as long as the form creates its customers through \n
\n
\n
\n
wonderful_disposable_email_blocker_pre_is_blocked<\/code> and wonderful_disposable_email_blocker_is_blocked<\/code> filters short-circuit or veto any decision, and every block fires the wonderful_disposable_email_blocker_blocked<\/code> action for logging.<\/p>\n\nExternal services<\/h3>\n\n
\n
wonderful-disposable-email-blocker<\/code> folder to the \/wp-content\/plugins\/<\/code> directory.<\/li>\n\n
What happens right after activation?<\/h3><\/dt>\n
Does this plugin send my visitors' email addresses anywhere?<\/h3><\/dt>\n
A legitimate customer is being blocked \u2014 what do I do?<\/h3><\/dt>\n
Where does the domain list come from?<\/h3><\/dt>\n
Why does the checkout always show the error message, even in silent mode?<\/h3><\/dt>\n
Does it work with custom WooCommerce registration forms?<\/h3><\/dt>\n
wc_create_new_customer()<\/code> (the WooCommerce standard), because validation runs through the woocommerce_registration_errors<\/code> hook.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n