CekEmail Email Validation
| 开发者 | cekemail |
|---|---|
| 更新时间 | 2026年9月30日 01:55 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Invalid addresses are always blocked.
- Disposable addresses are blocked, or allowed, as you prefer.
- Catch-all domains, unverifiable mailboxes and API errors each get their own allow or block policy, so a hiccup at the API never has to lock visitors out.
- WordPress user registration.
- WordPress comments.
- WooCommerce checkout, both the classic shortcode checkout and the block checkout.
- WooCommerce account registration.
- Contact Form 7 email fields, required and optional.
- An optional front-end widget, bundled with the plugin and never loaded from a CDN, that checks every email field on the page when visitors leave the email field and shows the result before the form is submitted. It uses a public widget key, never your API key. The bundled widget is open source: https://github.com/cekemail/widget
- Typo suggestions ("did you mean ...") in the error message.
- Result caching, so the same address is not billed twice within the cache lifetime.
- A "Test connection" button that validates your API key without spending credits.
- A log of the 50 most recent checks, with addresses masked.
- Admin notices when your key is rejected or your credits run out.
- Filters and actions so developers can extend or override every decision.
- Form submissions: when an API key is configured, the plugin sends the email address entered in each covered form (WordPress registration, WordPress comments, WooCommerce checkout and account registration, Contact Form 7 email fields), together with your API key, from your server to the CekEmail API at https://api.cekemail.com. Nothing is sent while no API key is configured.
- Front-end widget: when the optional front-end widget is switched on, the bundled widget script sends the address a visitor enters, when they leave the email field, from the visitor's browser to the same CekEmail API at https://api.cekemail.com, using your public widget key.
安装:
- Upload the plugin folder to
/wp-content/plugins/, or install it through the WordPress plugins screen. - Activate the plugin through the Plugins screen.
- Create an API key in your CekEmail dashboard.
- Go to Settings > CekEmail, paste the key, save, then press "Test connection".
- Choose your policy and the forms you want checked.
- To use the front-end widget, paste your public widget key under "Front-end widget" and switch it on.
屏幕截图:
常见问题:
Do I need a CekEmail account?
Yes. The plugin talks to the CekEmail API, which requires an API key from https://cekemail.com. Verification stops as soon as the key is removed with "Remove the saved API key" under Settings > CekEmail.
What happens when the API is unreachable?
Nothing is blocked by default. The "API errors" policy on the settings screen decides whether submissions are allowed or blocked while the API cannot be reached, and an admin notice tells you when your key was rejected or your credits ran out.
Why did an address get through with "Error: network" in Recent checks?
The plugin waits a limited time for a reply from the CekEmail API, 15 seconds by default, and treats anything slower as an API error. Because the "API errors" policy allows submissions by default, the address is accepted and the check is logged with the status Error: network. Raise "Request timeout" under Settings > CekEmail, up to 30 seconds, if your server needs longer to reach the API, or set the "API errors" policy to block if you would rather turn a visitor away than accept an unverified address.
Does the plugin store email addresses?
Only in masked form. The recent checks log keeps entries such as j***@example.com, never the full address, and results are cached under a hash of the address.
Are credits used for every submission?
Results are cached for the cache lifetime you configure, so repeated submissions of the same address inside that window do not reach the API. The connection test uses no credits at all.
Should I change the API URL?
Only change this if you use a self-hosted CekEmail instance; self-hosted instances use the /api/v1 prefix automatically. An address on an api. host, like the default https://api.cekemail.com, is called at /v1. Any other address, such as https://mail.example.com or the old default https://cekemail.com, is called at /api/v1. The address must use https; plain http is only accepted for localhost and 127.0.0.1, so your API key is never sent unencrypted.
Can I change the messages or the decisions?
Yes. Use the cekemail_decision filter to override any allow or block decision, and the cekemail_after_check action to log or report checks yourself.
更新日志:
- First release on WordPress.org.
- Translations are now delivered through translate.wordpress.org; bundled language files and the load_plugin_textdomain() call were removed (WordPress.org review).
- Plugin and author URIs now point to different pages (WordPress.org requirement).
- WordPress.org submission fixes.
- Tested up to WordPress 7.1.
- Contact Form 7 input sanitisation.
- A saved API key can now be removed from the settings screen.
- Admin notices about a rejected key, missing credits or a forbidden key clear as soon as the API answers successfully again.
- The widget description now says it checks an address when visitors leave the email field.
- The API URL must use https, so the API key is never sent unencrypted; plain http is only accepted for localhost and 127.0.0.1.
- API responses with unexpected field types are ignored.
- Local parts of one or two characters are masked completely in the recent checks log.
- Uninstall removes the plugin's options and notice transients on every site of a network, without flushing the object cache.
- The API URL now defaults to https://api.cekemail.com, which serves the API at
/v1. - Self-hosted instances, and sites that saved the old https://cekemail.com default, keep using the
/api/v1paths automatically. No settings need to change.
- Initial release.
- Email verification through the CekEmail API with result caching.
- WordPress registration and comment integrations.
- WooCommerce integration for the classic checkout, the block checkout and account registration.
- Contact Form 7 integration for email fields.
- Bundled front-end widget that checks email fields in the browser.
- Allow or block policies for disposable, catch-all, unverifiable and API error outcomes.
- Connection test, recent checks log and admin notices.
- Indonesian (id_ID) translation.