Linux 软件免费装
Banner图

WPCoreTools Disposable Email Guard

开发者 wpcoretools
更新时间 2026年5月10日 05:37
PHP版本: 7.4 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

anti spam disposable email temporary email email validation burner email

下载

1.0.2

详情介绍:

This plugin refuses sign-ups, comments, checkouts, and form submissions when the email address belongs to a disposable, burner, or temp-mail service. All checks run on your own server against domain lists that ship inside the plugin file — no email address is ever sent to a third-party service, and the plugin does not contact any external server in its default configuration. Five well-known community-maintained disposable-email lists are bundled as snapshots. Two are active out of the box (around 9,800 unique domains combined); three larger lists are available as opt-in for stricter coverage. An optional auto-update from the upstream GitHub URLs is also available, off by default. What it detects Where it checks WordPress core: WooCommerce: Form plugins: Three modes Domain lists Five bundled snapshots are available, each toggled independently: Each ships as a snapshot inside the plugin (data/sources/{id}.txt) and is loaded from disk; no network call is required for any of them to function. If you want the snapshots refreshed on a schedule from their GitHub raw URLs, an optional auto-update feature is available. It is off by default. See "External services" below for what is contacted and what is sent. Tools Privacy

安装:

  1. Upload the plugin folder to /wp-content/plugins/, or install it via Plugins → Add New.
  2. Activate the plugin.
  3. Visit Settings → WPCoreTools Disposable Email Guard. The first-time setup wizard runs automatically.
The bundled domain lists are active immediately on activation; the plugin works fully offline. Anonymous-provider blocking, plus-addressing checks, dead-domain MX checks, and the optional auto-update of source snapshots are all off by default and must be enabled explicitly.

常见问题:

Does this send my visitors' email addresses to an external service?

No. Every check runs locally against domain lists that ship inside the plugin file. By default the plugin makes no outbound connections at all.

Does the plugin contact GitHub or any other server in its default configuration?

No. The bundled snapshots are loaded from disk. The optional auto-update feature, which would contact GitHub to refresh those snapshots, is off by default and must be enabled in the setup wizard or the Lists tab. See "External services" for the full disclosure.

Will this block legitimate Proton Mail or Tutanota users?

Only if you turn on the "Anonymous / privacy providers" toggle. It is off by default for exactly that reason.

How are the disposable lists kept up to date?

Two ways. Either install a fresh version of the plugin (each release bundles updated snapshots), or opt into the auto-update feature, which lets WP-Cron fetch the source URLs from GitHub on a schedule (hourly, twice-daily, daily, or weekly).

Can I dry-run before I switch on blocking?

Yes. Set Mode to "Log only" — emails are recorded but no submissions are rejected. Or use "Flag" mode to allow signups but tag the user / order / comment for admin review.

What is "Flag" mode?

A non-destructive alternative to outright blocking. Submissions go through, but matching users get a wpcdeg_flagged user meta and a "Flagged" column on the Users list, comments get a meta tag, and WooCommerce orders get an order note plus a "Flagged" column on the Orders list. Useful when you do not want to lock out potential Proton or Tutanota customers but still want to triage them.

Does it work with WooCommerce HPOS?

Yes, both the legacy posts-table orders list and HPOS are supported.

Does it work with Contact Form 7 and Gravity Forms?

Yes, built-in integration on both. For other form plugins (WPForms, Elementor Forms, Forminator, Fluent Forms, etc.), call the wpcdeg_check filter from your form's email-validation hook.

What happens if a remote list URL is unreachable when auto-update runs?

The previous successful copy is kept (no data loss); the failure is recorded in the per-source meta. If no fetch has ever succeeded, the bundled snapshot continues to be used.

Will it slow down my site?

No. Each email check is an O(1) lookup against an in-memory map, loaded once per request and cached for an hour.

Does the MX record check slow down sign-ups?

Only the first lookup per domain — results are cached for 24 hours on success and 1 hour on failure. Most sign-ups hit the cache immediately. The check is opt-in and off by default.

更新日志:

1.0.2 Initial public release.