| 开发者 | marco00petrucci |
|---|---|
| 更新时间 | 2026年10月26日 06:37 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
mailto: link and plain-text email across your entire layout.@ symbol, the regex engine is completely bypassed in 0ms, and frontend JS is loaded non-blockingly via defer.isTrusted events, and Same-Origin headers.mailto: immediately on the first click. Icon and button links always launch mailto: immediately.admin-ajax.php endpoint against flooding attacks using spoof-resistant IP verification (REMOTE_ADDR) and Object Cache support.Tab + Enter / Space) and screen-reader friendly attributes./wp-content/plugins/crypto-mailto-defender directory, or install the plugin directly through the WordPress Plugins > Add New screen.mailto: links and plain-text emails across your website.Absolutely! The plugin intercepts and encrypts every single email address or mailto: link on the page. Plus, thanks to client-side in-memory caching, if the same email appears multiple times on a page, it only queries the server once!
Yes. Because Crypto Mailto Defender operates via global output buffering at the template level, it captures and protects emails regardless of how your theme or page builder renders them—including headers, footers, popups, and custom SVG icon buttons.
No. Version 1.1.0+ uses a cache-resilient verification mechanism that combines hardware interaction proofs with WordPress security headers, ensuring emails always unlock smoothly even on pages cached for weeks.
The email addresses remain securely encrypted and visually masked (e.g., ********@domain.com). Non-JS scrapers and raw HTML harvesters see zero email addresses in the source code.
Please note: JavaScript is required to reveal an address. Without JavaScript, nobody can reveal or use a protected email address, including legitimate visitors. If those visitors must be able to reach you, offer an alternative contact method, such as a contact form.
Not at all. Search engines like Google do not rank pages based on plain-text email addresses, and the plugin automatically adds rel="nofollow noindex" to masked links to follow SEO best practices.
No. It stops harvesters that read page source and common headless browsers. A determined attacker driving a real browser can still reveal an address. If an address must never be exposed, use a contact form instead.
The rate limiter uses REMOTE_ADDR. If your server only sees the proxy's IP, restore the real visitor IP at server level or return it from the cryptomail_client_ip filter. The per-minute limit can be changed with the cryptomail_rate_limit filter.
PHP with the OpenSSL extension, and HTTPS (the proof-of-work uses the browser's Web Crypto API, available only in secure contexts).
Protection is skipped in the block editor, the Customizer and the preview/editing modes of common page builders. Use the cryptomail_skip_request filter to exclude others.
Sec-Fetch-Site/Mode/Dest, X-Requested-With, Origin validation, and an expanded automated-agent User-Agent blocklist.cryptomail_skip_request, cryptomail_client_ip, and cryptomail_rate_limit filters for advanced integrations.init (priority 1) and transparently handles HTML, JSON, and AJAX/REST fragments, protecting emails rendered by page builders and dynamic widgets.customize_preview and ~70 known query params) to prevent encrypting emails inside editing UIs.<head> slicing before PCRE, eliminating regex scanning over styles/scripts.wp_enqueue_script with the defer strategy instead of inline <script> injection.init_runtime()), so settings and secrets are only loaded when actually needed.mb_substr, and unified sanitization for all settings through sanitize_setting().(*SKIP)(*F) regex now correctly skips head, script, style, textarea, pre, code, option, select, noscript, template, svg, iframe, object, and HTML comments, preventing accidental masking inside non-visible contexts.REMOTE_ADDR (spoof-resistant); proxy environments should use the cryptomail_client_ip filter.TreeWalker/non-anchor→anchor DOM rewriting in favor of a lighter reveal path.@) are present in the response HTML, dramatically reducing CPU overhead.