EASYDMARC EMAIL VERIFICATION
EasyDMARC Email Verification compatibility with REEID Translate
EasyDMARC Email Verification compatibility with REEID Translate is being reviewed using official plugin documentation. Server-side email verification of submitted form email fields via the EasyDMARC API before accepting the submission No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What EasyDMARC Email Verification does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
EasyDMARC Email Verification is documented in the Security category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How EasyDMARC Email Verification compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Server-side email verification of submitted form email fields via the EasyDMARC API before accepting the submission
- Configurable allow/block behavior per EasyDMARC verification status (e.g., deliverable, risky, undeliverable, unknown) with visitor-facing error messages under the email field
- Optional fail-open behavior: when the verification service/API is unavailable, form submissions can be allowed to pass through normally if enabled
- Integration coverage for multiple form/user flows, including Elementor Pro Forms, Contact Form 7, WPForms, Ninja Forms, Fluent Forms, Gravity Forms, SureForms, WooCommerce checkout billing email, and WordPress user registration (single-site and Multisite)
- Bulk email verification via CSV upload (up to 500,000 addresses) with the ability to export filtered results
- Debug logging support that writes errors to debug.log when WP_DEBUG_LOG is enabled, with email addresses redacted
- Credential handling and transport: verification requests are sent to https://sender-api.easydmarc.com and credentials are encrypted using the site’s AUTH_KEY with AES-256
TRANSLATION BOUNDARY
EasyDMARC Email Verification capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
EasyDMARC Email Verification and REEID Translate FAQ.
What does EasyDMARC Email Verification do?
EasyDMARC Email Verification has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does EasyDMARC Email Verification have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from EasyDMARC Email Verification?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate EasyDMARC Email Verification in a multilingual WordPress workflow.
REEID documents EasyDMARC Email Verification functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.