Article
Best WordPress Plugins for Email Validation in 2026 (Compared)
By Unlimited Verifier Team ·

Summary
Most WordPress email validation plugins only check whether an address is well formed, so the strongest setup pairs a signup check with a bulk mailbox verifier. Unlimited Verifier is the top pick for cleaning an existing list, since its standard checks are unlimited on every plan, including Free. This guide compares nine options and shows how to clean a large user table step by step.For WordPress sites, most "email validation" plugins only check whether an address is well formed, so the best setup pairs a signup check with a bulk mailbox verifier. For cleaning an existing user list, Unlimited Verifier is our top pick, because its standard checks are unlimited on every plan, including Free. It is a standalone web tool rather than a WordPress plugin, so cleanup runs through export, import or its API.
This guide is for WordPress site owners, newsletter publishers, WooCommerce and membership operators, and agencies that manage client sites. It compares nine options, explains which validation layer each one reaches, and walks through cleaning a 40,000-user table. For budget-first options, see our pillar guide to free and cheap email verifiers.
Quick answer
- Top pick for cleaning an existing WordPress list: Unlimited Verifier, used through CSV export and re-import, or its API on Pro.
- Best if you want the check inside the signup form: a verifier connector or a developer-built filter on a form plugin such as Gravity Forms.
- Best free route: Contact Form 7 with a validation filter for signups, plus WP-CLI for batch cleanup.
- Baseline you already have: WordPress core's
is_email(), which checks format only. - Rule of thumb: verify at signup, re-verify the full list quarterly, and keep hard bounces under 1% per send.
Which WordPress email validation options are best?
Most of these options fall into two groups. Some check the format of an address on a form, and others send the address to an external verifier that tests the mailbox. Only the second group tells you whether a mailbox can receive mail, so the picks below separate the two.
Quick picks
- Best overall for cleaning: Unlimited Verifier.
- Best for a team already on a premium form builder: Gravity Forms, with a verifier connected by a developer.
- Best free developer route: Contact Form 7 with a validation filter.
- Best for newsletters that sync to Mailchimp: Mailchimp for WordPress, with verification done before the sync.
- Best WordPress-native CRM: FluentCRM.
- Best free batch method: WP-CLI.
- Best baseline you already have: WordPress core's
is_email().
| Tool | Starting price | Free tier | Catch-all handling | Best for |
|---|---|---|---|---|
| Unlimited Verifier | $0; Pro $29/mo ($25/mo billed annually) | Yes: 25 lists/mo of up to 150 emails, 750 deep verifications, no API | Detects catch-alls and sorts them into Risky | Cleaning and weekly re-checks of WordPress lists |
| Gravity Forms | Paid license (varies) | Varies | Depends on the connected verifier | Developer-built signup checks |
| WPForms | Free version plus paid tiers | Yes (free version) | Depends on the connected verifier | Visual form building with a later verification path |
| Contact Form 7 | Free | Free | None built in; depends on your code | Free, developer-controlled signup checks |
| Mailchimp for WordPress | Plugin free; Mailchimp pricing varies | Varies | Depends on your verifier and Mailchimp | Forms feeding a Mailchimp audience |
| FluentCRM | Free and paid tiers | Varies | Varies | Contacts and sending inside WordPress |
| Verifier connectors (ZeroBounce, NeverBounce, Kickbox, Bouncer, Emailable) | Varies | Varies | Varies by vendor | Real-time mailbox checks inside forms |
| WP-CLI workflow | Free | Free | None; uses your verifier's output | Developers and agencies managing many sites |
WordPress core is_email() |
Included | Included | None (format only) | Baseline format checking |
Bottom line: a plugin that only checks format will not catch a closed mailbox, so choose a bulk verifier for the list and decide separately where the signup check happens.
How we compared (and limitations)
We judged each option on criteria that matter to WordPress owners, not on feature counts:
- Validation layer. Does it check format only, or also domain/MX and the SMTP mailbox?
- Where it runs. At form submission, on an exported file, or from the command line?
- Catch-all handling. Does it separate catch-all domains from confirmed-valid addresses?
- Cost at weekly frequency. Does each re-check add a charge?
- Data footprint. Does it leave copies of addresses in form entries, logs or third-party systems that your cleanup must also cover? Free tiers can carry their own retention limits, so see are free email verifiers safe for your data.
- WordPress effort. How much custom code or command-line access does it require?
Limitations. This comparison is based on public documentation and vendor-published information. We did not run accuracy tests on any tool. Accuracy figures are each vendor's own claims. We did not verify every WordPress connector or add-on, since those change often, and free allowances shift too; for current options see top email verifiers with free monthly credits. Pricing is marked "varies" where we did not confirm current terms. Nothing here is legal advice, and no verifier can predict whether a reader will open your email.
Bottom line: treat this as a map of options and trade-offs, then confirm current plans and connectors before buying.
What does email validation mean on a WordPress site?
Email validation is three separate checks, and many WordPress tools perform only the first. A format check confirms the string looks like an address. A domain and MX check confirms the domain can receive mail. An SMTP mailbox check asks the receiving server whether that specific address is accepted. WordPress core's is_email() function, as its developer reference describes, verifies that a string is a well-formed address. It does not confirm that a domain accepts mail or that a mailbox exists.
Catch-all domains complicate the third check. They accept mail for any address, so a mailbox check cannot confirm a specific person. A useful verifier returns Risky for these rather than Valid. Our catch-all detection guide explains how that category is handled.
Timing matters too. Checks at form submission must answer in a second or two, so they are shallower or time-limited. Bulk checks run on exported files and can take longer. For the trade-off, read our explainer on real-time email validation.
Bottom line: a plugin that passes is_email() has checked the spelling of an address, not the mailbox behind it.
Why do WordPress lists go bad faster than expected?
A WordPress list usually grows from four places: registrations, form plugins, checkout (on WooCommerce stores, a frequent source covered in our guide to email verification for ecommerce and SaaS), and older lists imported during a migration. Each path needs a check, and most sites guard only the newest one.
Decay compounds over time. Estimates of annual list decay vary widely, so treat any single rate as a planning assumption rather than a fact. Mailbox providers watch how senders behave. Google's sender guidelines set a spam-rate ceiling of 0.3% in Postmaster Tools and recommend keeping it under 0.1%. Bounces are not spam complaints, but a list with dead addresses often contains abandoned inboxes that generate complaints.
Bounce targets differ across sources. Many ESPs use thresholds around 2% hard bounces as a warning level. We recommend a stricter target: under 1% hard bounces per send, which leaves room before an ESP or mailbox provider intervenes.
Bottom line: the list grows from several entry points, so checks have to cover all of them, not just the newest form.
What are the 9 best WordPress email validation options, reviewed?
1. Unlimited Verifier (best overall for cleaning)
Unlimited Verifier is a bulk verification tool that runs outside WordPress. You upload a CSV or Excel file of up to 10MB, and the email column is detected automatically. It checks syntax, domain, MX records and the SMTP mailbox, then sorts every address into Valid, Risky or Invalid. Catch-all domains go to Risky rather than being passed as valid.
On a WordPress site, the loop runs beside the site. You export users or form entries, verify them, export the results, and apply the changes back. Results export as CSV, Excel or JSON. JSON is the most convenient format for a script, because each row can be matched to a user ID without reformatting.
Key features
- Syntax, domain, MX and SMTP mailbox checks
- Catch-all detection with Risky sorting
- Disposable and role-based address flagging
- Deep verification, which the company states is 99.5% accurate
- REST API with keys for single checks and bulk batches of up to 10,000 emails per request (Pro)
- Free single-email checker and free domain blacklist checker
Pros
- Standard verification is unlimited on every plan, so a weekly signup pass adds no per-email fees.
- Valid/Risky/Invalid maps directly to actions: keep, tag, delete.
- The engine is open source on GitHub, so you can read how checks are carried out. Our guide to open source email verification tools covers other options in that category.
Cons
- It is not a plugin. There is no WordPress admin screen and no native WooCommerce, Gravity Forms or Zapier integration.
- Free results are kept for 24 hours, so you must download them the same day.
- The API is Pro-only, so real-time signup checks need a paid plan.
- Files are capped per list (150 emails on Free, 25,000 on Pro), so large user tables must be split.
Best for: site owners who need to clean an existing list and re-check it weekly without metering every check.
Where it falls short: sites that want verification inside the signup form with no developer work.
Pricing: Free ($0) includes 25 lists a month of up to 150 emails each, plus 750 deep verifications a month, with no API access. Pro is $29 per month, or $25 per month billed annually, and adds unlimited lists of up to 25,000 emails each, 25,000 deep verifications a month, and API access for 100,000 emails a month. You can sign up free to run your first file.
Tip: spend deep verifications on Risky addresses only. Spending them on addresses already marked Valid wastes allowance on checks that rarely change a decision.
Bottom line: the strongest cleanup engine on this list, with the trade-off that it runs beside WordPress rather than inside it.
2. Gravity Forms (best for developer-built signup checks)
Gravity Forms is a premium form builder. Its email field can require a confirmation field, which catches typos at entry. It does not check whether a mailbox exists on its own. Mailbox verification needs a developer to hook into its validation filter (gform_validation) and call an external verifier before the entry is saved, or a third-party add-on that does the same.
Key features
- Email field with a confirmation option
- Validation filters for custom logic before an entry is saved
- Entries stored in the WordPress database and exportable as CSV
- A Zapier add-on for connecting to other apps
Pros
- Entry export makes it straightforward to pull signups out for cleaning.
- A developer can decide per result what happens: accept Valid, tag Risky, reject Invalid.
Cons
- Mailbox checks need custom code or a third-party add-on.
- Saved entries keep the same addresses after you clean the user table, so the entries need their own cleanup.
- The Zapier add-on cannot call Unlimited Verifier, since that tool has no native Zapier integration.
Best for: sites already on Gravity Forms with developer support.
Where it falls short: teams that want a verification toggle in form settings with no code.
Pricing: a premium plugin sold with paid licenses. Check current terms.
Tip: for Risky addresses, accept the entry but tag the user for a confirmation email rather than rejecting it. Rejecting every catch-all address can lose real readers at company domains.
Bottom line: the most flexible premium option, and the most setup work.
3. WPForms (best visual builder with a verification path)
WPForms is a drag-and-drop form builder with a free version and paid tiers. Its email field handles format validation, and it can store and export entries. As far as its public documentation indicates, mailbox-level checks depend on connecting an external service, so confirm which integrations your tier includes before relying on them.
Key features
- Visual form builder for non-developers
- Email field format validation
- Entry storage and export (confirm which entry features your tier includes)
- Integrations for connecting to other tools
Pros
- The visual builder is quick for non-developers to learn.
- You can add a verification step later without rebuilding the form.
Cons
- Mailbox checks are not part of the core product, so expect to add a connector.
- Entries hold the same addresses as your user table, so cleaning one does not clean the other.
- Integration availability depends on your tier, so check the current list before committing.
Best for: non-developer teams that want a visual builder and an upgrade path.
Where it falls short: real-time mailbox checks without any setup work.
Pricing: a free version plus paid tiers. Check current terms.
Tip: on an existing site, export entries first and verify them in bulk. This reverses the usual order, but it shows how large the problem is before you change the live form.
Bottom line: easy to adopt, with verification as an add-on decision rather than a default.
4. Contact Form 7 (best free developer route)
Contact Form 7 is a free, lightweight form plugin. Its validation can be extended through filters, including wpcf7_validate_email, which lets a developer add an external check. It does not save submissions on its own; the companion plugin Flamingo stores them.
Key features
- Free and lightweight
- Validation filters for custom checks
- Works with Flamingo for storing submissions
Pros
- It costs nothing and gives you full control over validation logic.
- Because you write the check, you decide the fallback when the verifier is slow or unreachable.
Cons
- No built-in verifier, so every check is custom code you maintain.
- Submissions are not saved by default, so you need Flamingo or your own storage to find signups later.
- You own failure handling: if the verifier is down, the form must still work.
Best for: developers and small sites that want a free, controllable signup check.
Where it falls short: non-technical owners who need a dashboard.
Pricing: free.
Tip: keep the verifier timeout to a few seconds, and fail open. If the check does not answer in time, accept the submission and queue the address for a bulk check. A slow verifier should never block a signup.
Bottom line: the cheapest way to add signup checks, provided someone on your team can maintain the code.
5. Mailchimp for WordPress (best for Mailchimp audiences)
Mailchimp for WordPress connects your forms to a Mailchimp audience. The plugin does not verify mailboxes. Double opt-in is set in the plugin or in your Mailchimp audience settings, so confirm which one applies to your setup. If you want invalid addresses kept out, verification has to happen before the sync.
Key features
- Connects WordPress forms to Mailchimp audiences
- Double opt-in settings for new subscribers
- Sends subscriber data to Mailchimp on submission
Pros
- The plugin is free and fits a Mailchimp-based newsletter.
- You clean one audience rather than several, once the sync is in place.
Cons
- It does not validate addresses itself, so a mailbox check needs a custom filter before the API call.
- Mailchimp prices plans by contact count, so invalid addresses that sync cost money until they are removed.
- Cleanup happens in two places, your WordPress users and the Mailchimp audience.
Best for: newsletters that already run on Mailchimp.
Where it falls short: sites that want validation and sending inside one WordPress database.
Pricing: the plugin is free. Mailchimp pricing varies by plan and contact count.
Tip: when you clean the Mailchimp audience, export the Invalid list and suppress it there. Removing addresses from WordPress alone leaves them in Mailchimp.
Bottom line: a clean fit for Mailchimp users, but validation has to be added deliberately.
6. FluentCRM (best WordPress-native CRM)
FluentCRM is a contact and email marketing plugin that stores contacts inside your WordPress database. Its contacts, tags and lists live alongside your site's users, so cleaning a list changes the sending list directly. Confirm how any verifier integration works in its current settings before you plan around it.
Key features
- Contacts, tags and lists stored in the WordPress database
- Imports from WordPress users
- Email sending from the same site
Pros
- One database means cleanup applies to the sending list with no export step.
- Tags make it easy to segment Risky addresses for controlled sends.
Cons
- You carry the full deliverability load. Sending runs through your server or your configured mailer, so list hygiene and sending reputation are your responsibility.
- Verification does not fix content, cadence or engagement problems that cause complaints.
- Free and paid tiers differ, so confirm which features each includes.
Best for: WordPress-only operators who want users, contacts and sends in one place.
Where it falls short: teams that want verification built into the sending workflow without custom work.
Pricing: free and paid tiers. Check current terms.
Tip: run imported WordPress users through a bulk verifier before the first send. A first campaign to an unverified list is a common route to a bounce-heavy start.
Bottom line: the cleanest data model on this list, but you own the sending side entirely.
7. Verifier connectors (ZeroBounce, NeverBounce, Kickbox, Bouncer, Emailable)
This is a category rather than a single product. Each of these hosted verifiers publishes an API that a WordPress form or hook can call, and their public documentation describes different result models. ZeroBounce describes granular statuses, including catch-all, spamtrap and abuse. NeverBounce describes five result categories, including catchall, plus automated sync integrations. Kickbox provides a Sendex quality score from 0 to 1. Bouncer offers a Toxicity Check. Emailable returns reason codes. Check each vendor's current integrations page for WordPress-specific options, since we did not confirm which exist.
Key features (as described in public documentation)
- Hosted APIs callable from form submissions
- Vendor-specific result categories or scores
- Real-time and bulk verification options (varies by vendor)
Pros
- Real-time mailbox checks at signup are the main reason to choose this category.
- The result models range from granular statuses (ZeroBounce) to a tunable score (Kickbox), so you can match the model to your decision rules.
Cons
- Each signup check and each re-check consumes paid volume. Our guide to best pay as you go email verification services covers that billing model in more depth.
- The same address can map to different actions across vendors, so a rule written for one result set will not transfer to another.
- A Sendex score cannot be compared with another vendor's score, so calibrate any threshold on your own bounce data.
Best for: teams that want mailbox checks at signup and are comfortable paying per check.
Where it falls short: low-cost weekly re-checks of a large existing list.
Pricing: varies by vendor and by credit or subscription model. ZeroBounce advertises a small free monthly allowance; check current terms.
Tip: before installing any connector, ask three questions: what does a catch-all return, what happens when the API times out, and is the connector actively maintained? The answers matter more than the feature list.
Bottom line: the strongest real-time option for forms, priced for per-check use.
8. WP-CLI workflow (best free batch method)
WP-CLI is WordPress's command-line interface, documented at wp-cli.org. It lets you export users, tag them with verification results and delete records from a terminal, with no plugin required. It is free, repeatable, and can run on a staging copy before production.
A typical export looks like this: wp user list --role=subscriber --fields=ID,user_email --format=csv > users.csv. Repeat it for other roles you email, such as customer on WooCommerce stores. After verification, tag Risky users with wp user meta update <ID> email_status risky.
Key features
- Exports users with IDs and any fields you specify
- User meta updates for tagging verification results
- Scriptable deletion with safety flags such as
--yes
Pros
- Free, scriptable and auditable. You can rerun the same steps every quarter.
- Matching by user ID avoids errors caused by email case or stray spaces.
Cons
- It needs command-line access, which some managed hosts restrict.
- Deletion is destructive, so one wrong ID costs real data.
- You must map verifier output back to user IDs yourself.
Best for: developers and agencies that manage several WordPress sites.
Where it falls short: owners without SSH or command-line access.
Pricing: free.
Tip: lowercase and trim every email before you match it to verifier output. Mismatched case is a frequent reason a clean file fails to line up with the database.
Bottom line: the most controllable free method, provided someone is comfortable in a terminal.
9. WordPress core is_email() (the baseline you already have)
WordPress checks new registrations with is_email(), which validates format. It catches missing @ signs and invalid characters, but it cannot tell whether a domain accepts mail or whether a mailbox exists. A typo like gmial.com is well formed, so it passes.
Key features
- Built into WordPress
- Format checking on registration and comments
- Filterable through code
Pros
- Free, already active, and requires no setup.
- Blocks the most obviously malformed entries.
Cons
- Format only: no DNS check, no mailbox check, no catch-all or disposable detection.
- Accepts many addresses that will bounce.
- A passed check is easily misread as "deliverable," which is the most common mistake with it.
Best for: a baseline that keeps malformed entries out of your database.
Where it falls short: anything about deliverability.
Pricing: included with WordPress.
Tip: keep it on, but read a passed check as "well formed," not "deliverable." Our guide to free tools to check if an email will bounce covers how to test individual addresses beyond format.
Bottom line: necessary, but nowhere near sufficient.
How do you clean a WordPress user list with Unlimited Verifier?
This process takes one full clean and then a small weekly pass. It assumes a current database backup and a staging copy to test on. The steps use WP-CLI for export and deletion. If you lack command-line access, use an export tool that includes user IDs and apply the same logic by hand.
- Back up first. Take a full database backup and rehearse the procedure on staging. The delete steps are irreversible without one.
- Export users with IDs. Run
wp user list --role=subscriber --fields=ID,user_email --format=csv > users.csv, then repeat for each other role you email. - Normalize. Lowercase and trim every address, and remove duplicates. Do this before upload so results match your database.
- Split to fit the plan. On Pro, keep each file at or under 25,000 emails and 10MB. On Free, keep each file at or under 150 emails.
- Create an account and pick the plan that fits your list size.
- Upload and verify each file. The email column is detected automatically.
- Review the three buckets. Valid stays active. Invalid goes to a deletion queue. Risky goes to a tagged segment.
- Deep-verify Risky addresses where the extra check changes the decision. For spot checks on single addresses, use the free email checker.
- Export the results as CSV, Excel or JSON. On Free, download the same day, since results are kept for 24 hours. On Pro, results are kept for 30 days.
- Apply Invalid results carefully. Match each address to its user ID, then delete with a reassignment target so posts keep an owner:
wp user delete <ID> --reassign=1 --yes, where1is an administrator account. Do not delete customers with WooCommerce orders. Keep their records and suppress them from marketing sends, for example with a tag. - Tag Risky users, for example with
wp user meta update <ID> email_status risky, and exclude them from general sends or send only to engaged readers. - Sync your ESP or CRM. Unlimited Verifier has no native integrations, so import the cleaned list into your ESP and add Invalid addresses to its suppression list. Otherwise the next import brings them back.
- Weekly: export this week's registrations, with
user_registeredincluded in the fields so you can filter by date, and verify them. On Pro, the email verification API can check signups in batches of up to 10,000 per request. Use the API key page to generate keys. - Quarterly: repeat the full-list pass.
Worked example: a 40,000-user WordPress site adding 600 registrations a week
- On Pro:
- Quarterly full pass: 40,000 ÷ 25,000 means 2 files of about 20,000 each.
- Weekly: 600 signups in one upload.
- Per year: (4 × 40,000) + (52 × 600) = 160,000 + 31,200 = 191,200 standard checks.
- Cost: $25 × 12 = $300 per year, whatever the check volume. That works out to about $1.57 per 1,000 checks at this volume.
- On Free:
- Full pass: 40,000 ÷ 150 = 267 files. At 25 lists a month, that is about 10.7 months of allowance, so a full monthly pass is not possible.
- Weekly: 600 ÷ 150 = 4 lists a week, or about 17 a month (4 × 4.33). That fits within 25.
- Deep checks (illustrative): if 3% of 40,000 (1,200 addresses) came back Risky, that would exceed the 750 monthly deep verifications on Free. Spread them across two months, or move to Pro's 25,000.
Bottom line: one full clean and then small weekly deltas keeps bounces low with a few hours of work a quarter.
Which option should you choose?
| Your situation | Pick | Why |
|---|---|---|
| Clean an existing user list and re-check weekly | Unlimited Verifier | Unlimited standard checks on every plan |
| Checks inside the signup form | Verifier connector, or Gravity Forms with a developer | Real-time mailbox checks |
| Free, developer-controlled signups | Contact Form 7 with a validation filter | No license cost |
| Newsletter runs on Mailchimp | Mailchimp for WordPress, verified before sync | One audience to clean |
| WordPress-only newsletter and CRM | FluentCRM | Contacts and sends share one database |
| Many sites, command-line access | WP-CLI workflow | Free, scriptable, repeatable |
| Small list with low volume | Free plan or low-volume verification tools | Fits the per-list cap |
For a structured way to decide, our guide on how to choose an email verifier walks through the criteria.
Bottom line: the cleanup layer and the signup layer are separate decisions, so choose each on its own terms.
What mistakes do WordPress owners make with email validation?
- Trusting
is_email(). A passed format check is not a deliverable address. Keep it, but do not stop there. - Rejecting catch-all addresses at signup. Catch-alls often include real readers. Tag them and confirm by email instead.
- Cleaning only one copy of the list. Users, form entries, FluentCRM contacts and the ESP audience each hold addresses. Clean all of them, or invalid addresses come back.
- Deleting customers. WooCommerce customers with orders need their records kept. Suppress them from marketing instead.
- Confusing WordPress's privacy tools with list cleaning. The Tools menu includes personal data export and erase tools for individual requests. They are not built for bulk cleanup.
- Losing results. Free results expire after 24 hours and Pro results after 30 days. Archive every export.
- Choosing on per-check price alone. Cheap credits multiplied by weekly re-checks can cost more than a flat plan. Compare the full email verification pricing model, not just the unit price.
- Treating verification as permission. Verification does not create consent to email someone. The FTC's CAN-SPAM compliance guide is a starting point for US senders, and our guide to email verification compliance and hygiene covers the wider framework.
- Skipping the protocol basics. Mail servers handle addresses according to standards such as RFC 5321. Knowing the basics makes SMTP results easier to read.
- Ignoring engagement. A valid address that never opens still counts against you. Pair verification with the routine in our guide to email list maintenance best practices.
Bottom line: most WordPress validation failures come from gaps in scope and process, not from the tool.
What is the verdict for WordPress email validation?
The best WordPress setup separates two jobs. Use a form-level check to stop bad addresses at signup, and use a bulk verifier to clean the list you already have and re-check it weekly. For the bulk job, Unlimited Verifier is our top pick. Standard verification is unlimited on every plan, its Valid/Risky/Invalid output is easy to act on, and its CSV and JSON exports fit a WP-CLI workflow.
Its main limitation is that it is not a WordPress plugin. Expect to export, verify and re-import, or to build an API call on Pro. If you need a check inside the form, add a verifier connector or a developer-built filter. For the wider market, see our best email verification tools guide.
Bottom line: start by cleaning your existing list on the Free plan, then move to Pro ($25/month billed annually) when your lists outgrow the per-file cap or you want API checks at signup.
Cleaning a 40,000-user table
- Back up the users table and export user_email, user_id and registration date to CSV with WP-CLI (wp user list --fields=ID,user_email --format=csv > users.csv).
- Remove duplicates and obvious format failures locally, using is_email() as the first filter.
- Upload the cleaned list to Unlimited Verifier in batches and download the results.
- Sort results into valid, risky (catch-all) and invalid.
- Suppress invalid addresses from marketing sends; keep risky addresses in a re-verify segment.
- Re-import the statuses into WordPress with a custom meta field, then re-verify the full list on a quarterly schedule.
- Track hard bounces per send and keep them under 1 percent.
Frequently asked questions
Does WordPress validate email addresses by default?
WordPress core checks only the format of an email address, using the is_email() function. It confirms the address looks valid but does not test whether the mailbox exists or can receive mail. To confirm deliverability you need a mailbox verifier, either through a plugin connector or a bulk tool.
Can Unlimited Verifier be used as a WordPress plugin?
No. Unlimited Verifier is a standalone web tool, not a WordPress plugin. You run cleanup by exporting your user list as CSV, verifying it, and re-importing the results, or by calling its API on the Pro plan.
What is a catch-all email address?
A catch-all domain accepts mail for any address at that domain, so a verifier cannot confirm whether a specific mailbox exists. Verifiers typically label these as risky rather than valid. Treat them cautiously and watch engagement and bounce rates after sending.
Should I verify emails at signup or only clean the list later?
Do both. Verifying at signup stops most bad addresses from entering your database, and periodic bulk cleaning catches addresses that go stale over time. Re-verifying the full list roughly quarterly is a common practice among list managers.
What bounce rate is considered safe?
Many email service providers and deliverability guides recommend keeping hard bounces well below 2 percent per send, and a common internal target is under 1 percent. Check your own provider's policy, since thresholds vary.
Is WP-CLI a free way to clean a WordPress user list?
Yes. WP-CLI is free and can export user emails in bulk to a file, which you then send through a verifier. You still pay for any verification service you use, but the WordPress side costs nothing.
Will email validation slow down my signup form?
Real-time mailbox checks add a network call, so they can add a short delay to form submission. Many teams run format checks instantly and send only suspicious addresses to a mailbox check, or run the check asynchronously after submission.
Which option works best for WooCommerce stores?
For WooCommerce, verify addresses at checkout or account creation with a verifier connector or a developer-built filter, and clean the existing customer list in bulk. Customer emails are often used for order and transactional mail, so bounces there affect more than marketing.
Do I need a developer to add email validation to WordPress forms?
Not always. Some form plugins offer verifier integrations through add-ons or connectors. Free setups like Contact Form 7 usually need a short code snippet using a validation filter, so a developer or a confident site owner is helpful.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.