# MillionVerifier > The Most Comprehensive Email Verification Service from only $39: Email Checker, Email List Verify, Bulk Email Verifier, ESP Integrations, and Automatic Email Verification Public Ghost content for AI and LLM tooling. This file includes a bounded export of public pages first, then recent public posts. Append `.md` to any post or page URL to get the content in Markdown (for example, `/example-post.md`). ## Pages ### Email Checker URL: https://www.millionverifier.com/email-checker/ Last updated: 2026-06-05T12:17:19.000Z MillionVerifier provides the most comprehensive email verification service with the highest accuracy on the market, including [email checker service](https://www.millionverifier.com/). **How to check an email if it is valid?** - Log in to your MillionVerifier account - Go to [https://app.millionverifier.com/email\_verify#single-email](https://app.millionverifier.com/email%5Fverify?ref=millionverifier.com#single-email) - Enter the email you want to check - The result will be displayed under the field --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Email List Verification & Cleaning URL: https://www.millionverifier.com/email-list-verification/ Last updated: 2026-06-05T12:38:10.000Z MillionVerifier aims to go above and beyond when it comes to **email list cleaning**; hence MillionVerifier is the only [email list verification service ](https://www.millionverifier.com/)with 40+ ready-to-use email marketing integrations to verify your email lists. We are simplifying email list verification for you. Once you connect your email service provider to our email list verifying software, you can import your email lists with one click to start email verification. You can remove bad emails without exporting a list and taking manual action in your email account. ### 40+ Email List Verification Integrations We have created seamless integrations with major email service providers and created endpoints for you to connect any CRM or database with us. Currently, you can use MillionVerifier’s #1 email list verifying solution with the following email marketing tools to clean your email lists: - Mailchimp - Sendinblue - Mailgun - Mailjet - Elastic Email - Campaign Monitor - Active Campaign - Zoho CRM - Reply - Getresponse - Hubspot - AWeber - MailerLite - Drip - SendGrid - Apollo.io - Intercom - \+ Custom integration with any database ### Import Email Lists for Verification - Log in to your MillionVerifier account. - Go to [https://app.millionverifier.com/email\_verify#integration](https://app.millionverifier.com/email%5Fverify?ref=millionverifier.com#integration) - Find your email marketing tool and click on connect. - Enter your API key from your marketing platform. - Select the email list you want to verify and click on import. - Click on Start Verification. ### Bulk Email List Verification We download the content of your selected email list from your ESP and automatically upload it for bulk email verification. From this point, the email verification process is the same as [bulk email verification](https://www.millionverifier.com/services/bulk-email-verifier). We verify all your emails in your email list whether they exit. Once your file is completed, you can access the same verification reports as if you have uploaded a file. However, there is a significant difference. Since you have an integration set up, you can remove your bad emails with a couple of clicks from your email marketing tool. ### Remove Bad Emails From Your Email Lists Because you have an integration set up, you have an option to take action from MillionVerifier to your email marketing account based on the verification results. ![](https://www.millionverifier.com/content/images/2026/05/email_list_verification_remove_bad_emails.webp) - Click on Action. - Select the emails (bad emails recommended) you want to remove. - Select desired action: unsubscribe or delete. We will notify your email marketing tool that you want to remove these emails. All this shall happen in the background for you. ### Email List Verification for Custom Databases MillionVerifier is the only email list verification service with an option to connect any CRM or database with three simple endpoints. You can connect multiple custom databases with MillionVerifier. ![](https://www.millionverifier.com/content/images/2026/05/custom_integrations.webp) ### Email List Cleaning Prices MillionVerifier was created to serve email marketers with large email lists; hence we are proud of offering our email list verifier service at the [lowest prices on the market](https://www.millionverifier.com/#prices). ![](https://www.millionverifier.com/content/images/2026/05/email_list_verification_prices.webp) You can verify an email list of 1 million emails for only $389 with MillionVerifier. You can purchase email verification credits in just a minute, and you can pay by a card or using PayPal. Email verification credits never expire, and you can use them for email verifier API and bulk email verification as well. You can also try our email list cleaning system for free. Create an account and get 100 free email verifications. ### Email List Cleaning Reviews We have created the most accurate email list verifier and an intuitive user interface. We have been rated an [excellent email list cleaning service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) on Trustpilot because we always do our best to serve our customers. ### Automated Email List Validation A clean email list is critical in email marketing. Using the same built-in or custom integrations, you can set up an automated email list cleaning as well. We will verify all your emails in your email list every day and remove any bad emails automatically from your account. [Automated email list cleaning](https://www.millionverifier.com/services/automated-email-verification-everclean) needs to be set up once, and your lists will be forever clean. MillionVerifier EverClean is available in a monthly subscription. You can compare the prices here: [email verification prices](https://www.millionverifier.com/#prices). --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Bulk Email Verifier URL: https://www.millionverifier.com/bulk-email-verifier/ Last updated: 2026-06-05T12:38:51.000Z MillionVerifier is well known for its [outstanding accuracy](https://www.millionverifier.com/why-millionverifier/accuracy-rate) and its leading [bulk email verification tool](https://www.millionverifier.com/). One of our expertise is [bulk email verification](https://www.millionverifier.com/solutions/clean-old-email-lists): - High-speed email verification: we can verify 1 million emails per user in just 6 hours. - Super [low email verification prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices): we can verify 100k emails for only $149 or 1 million emails for only $449. - Copy-paste emails or upload contacts in a TXT, CSV, or XLSX file. **How to do bulk email verification?** - Log in to your MillionVerifier account. - Go to [https://app.millionverifier.com/email\_verify#file-upload](https://app.millionverifier.com/email%5Fverify?ref=millionverifier.com#file-upload) - Click & upload or drag & drop your file congaing your contacts. - Click on Start Verification. We will process your file at the highest speed possible, typically verifying 2,700 per minute on your account with 99%+ email verification accuracy. As soon as your file is ready, you can download your results. ![](https://www.millionverifier.com/content/images/2026/05/copy_paste_email_list_hero.webp) **Copy-Paste Email Lists** - Log in to your MillionVerifier account. - Go to [https://app.millionverifier.com/email\_verify#email-list](https://app.millionverifier.com/email%5Fverify?ref=millionverifier.com#email-list) - Copy-paste your emails. - Click on start verification. We will convert your pasted list into a CSV file and verify it with our bulk email verification tool. The process is the same, your file will be verified soon, and you can download your result files. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Email Verifier API URL: https://www.millionverifier.com/email-verifier-api/ Last updated: 2026-06-05T12:39:07.000Z MillionVerifier operates a super-fast API (Application Programming Interface) that allows you to connect your website or application with our service, and you can [verify the emails](https://www.millionverifier.com/solutions/verify-new-emails-in-real-time) of your subscribers in real-time. **Connect to MillionVerifier Email Verification API** Simply send a GET request to our API endpoint containing your API key and the email address you want to verify. - You can find the API documentation here: [https://developer.millionverifier.com/](https://developer.millionverifier.com/?ref=millionverifier.com) - You can find your API keys here: [https://app.millionverifier.com/api](https://app.millionverifier.com/api?ref=millionverifier.com) **Manage Your API Keys** - You can create an unlimited number of API keys on your MillionVerifier account. - You can add a comment to each of them. - You can turn any API key on or off at any time. - You can set up IP restrictions to the whitelist or blacklist any IPs. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Automated Email Verification - EverClean URL: https://www.millionverifier.com/automated-email-verification-everclean/ Last updated: 2026-06-05T12:39:17.000Z ![](https://www.millionverifier.com/content/images/video-thumbnails/1fc659831de48aa3bdde04b5b501c950fa5b427f512bdf3fbe776bad36e43b3d-1280.webp) MillionVerifier offers a unique [automated email verification](https://www.millionverifier.com/) system to keep your email marketing account [clean of bad emails at all times](https://www.millionverifier.com/solutions/keep-email-marketing-account-ever-clean). MillionVerifier EverClean will verify your emails daily and remove bad emails from your email marketing account. MillionVerifier EverClean is currently available with the following email marketing platforms: Mailchimp, Sendinblue, Mailgun, Mailjet, Elastic Email, Campaign Monitor, Active Campaign, Zoho CRM, Reply, Getresponse, Hubspot, AWeber, MailerLite, and Drip. **How to keep my email marketing account clean automatically?** - Log in to your MillionVerifier account. - Go to [https://app.millionverifier.com/integrations/everclean](https://app.millionverifier.com/integrations/everclean?ref=millionverifier.com) - Select your email marketing tool and click on connect. - Enter your API key from your marketing platform. - Select the email list(s) you want to keep ever clean. - Set-up automatic action. E.g., unsubscribe bad emails. MillionVerifier is going to verify the selected email lists every day for you and take the action you set up in the background. **Which emails can you automatically remove for me?** When you set up MillionVerifier EverClean, you will have the option - Bad emails, such as invalid and disposable emails. - Risky emails, such as unknown and catch-all emails. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. ### Clean Old Email Lists URL: https://www.millionverifier.com/clean-old-email-lists/ Last updated: 2026-06-05T12:39:28.000Z When sending an email campaign to an existing email list, you are risking your email reputation. If you haven’t emailed your list for longer than two months, it is likely that a small % of the emails no longer exist. The longer this period is, the more bad emails you have on your list. **How to verify email lists?** MillionVerifier offers the most comprehensive [email list verification](https://www.millionverifier.com/) system: - Upload your contacts in a TXT, CSV, XLSX file. - Copy-paste your emails. - Import from your email marketing tool. - Set up automatic email verification with your email marketing tool. - Integrate your databases with bulk email verification API. **Upload your contacts in a TXT, CSV, XLSX file** You can upload your contact emails in a TXT, CSV, or XLSX file. Your files may contain additional data columns. They will be included in your results files. **Copy-paste your emails.** You can copy-paste your emails into our [email verification tool](https://www.millionverifier.com/solutions/clean-old-email-lists) that we will convert into a CSV file. Once started, it is the same bulk email verification as the upload version. **Import from your email marketing tool.** Connect your email marketing tool with MillionVerifier and import your contacts with a single click to start bulk email verify. This integration allows you to take action from your MillionVerifier account. You can remove bad emails from your marketing tool with a few clicks. **Set Up Automatic Email Verification** The first step is the same, connect your email marketing tool. However, in this case, you not just import your list but set up an automation to verify your email lists every day from now on. ![](https://www.millionverifier.com/content/images/2026/05/setup_automatic_email_verifiaction.webp) **Integrate with Bulk API** This option is for users who have a regular need to clean new databases automatically. You can send us CSV files for email verification programmatically, and you can retrieve their results without human interaction. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Verify New Emails in Real-Time URL: https://www.millionverifier.com/verify-new-emails-in-real-time/ Last updated: 2026-06-05T12:39:39.000Z Verify emails on your website as long as your visitors are still there. [Real-time email verification](https://www.millionverifier.com/) has three main benefits: - You could prompt your subscriber if they provided a bad email address so they can quickly fix it. - You don’t add bad emails to your email lists. This way, you are protecting your email reputation. - You cannot be fooled by fake or disposable emails if you give anything in return for their contact details. **How to Verify Emails in Real-Time?** For real-time email verification, you need to program MillionVerifier’s single email verifier API into your website. Your webmaster or developer should be able to connect to our API using any programming language. To help them, we have also published some sample codes in common programming languages. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Block Temporary / Disposable Emails URL: https://www.millionverifier.com/block-temporary-emails/ Last updated: 2026-06-05T12:39:52.000Z To access free or limited features or information, we regularly ask for contact details, including email addresses. Many emails provided for free access are either fake emails or disposable emails. **What are disposable emails?** Disposable or temporary emails are emails created only to get free access. These email accounts exist for a brief period. Usually for less than one day. They use this email to get access, and the next day you will have hard bounces. **Increasing Threat of Temporary Emails** There are millions of searches every month for temporary email address providers. Those who provide freemium services or give access to software or information in return to users’ email addresses face an increasing threat of these users. **Temporary/Disposable Email Detection** MillionVerifier recognizes the importance of fighting these dishonest subscribers. Hence, we are operating the broadest disposable email protection for our users. Using any [email verification method](https://www.millionverifier.com/) on MillionVerifier, you will be protected from disposable email addresses. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Keep Email Marketing Account Forever Clean URL: https://www.millionverifier.com/keep-email-marketing-account-ever-clean/ Last updated: 2026-06-05T12:40:13.000Z MillionVerifier is offering a [unique automatic email verification service](https://www.millionverifier.com/) called MillionVerifier EverClean. EverClean will verify your emails every day and remove any bad emails from your email marketing account. **MillionVerifier EverClean Integrations** We are integrated with 15 large email marketing platforms. You can keep your account ever clean by setting up automatic email verification with the following: - Mailchimp - Sendinblue - Mailgun - Mailjet - Elastic Email - Campaign Monitor - Active Campaign - Zoho CRM - Reply - Getresponse - Hubspot - AWeber - MailerLite - Drip **How Automatic Email Verifications Works?** The advantage of setting up automatic email verification is that your email account will be cleared of any bad emails every day. Set up one, and we will verify your email lists every day and remove any bad emails in the background. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### 99%+ Accuracy Rate URL: https://www.millionverifier.com/accuracy-rate/ Last updated: 2026-06-05T12:40:26.000Z During email verification, MillionVerifier completes a deep-level [email verification](https://www.millionverifier.com/). We check if the email syntax is correct and create an SMTP connection with the recipient email server to find out if the email address exists. MillionVerifier’s verification accuracy is higher than 99%; hence we are [rated excellent](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) on Trustpilot. ![](https://www.millionverifier.com/content/images/2026/05/accuracy_rate_2.webp) **The email verification process** MillionVerifier completes a comprehensive email verification process to provide our users with the highest email verification accuracy possible. - Duplicate removal: when you upload your contacts for verification in a CSV, TXT, or XLSX file, we first remove any duplicates from your file. - Email syntax check: we check if your email contains allowed characters only, a prefix, an @ sign, and a domain. - Domain check: we check if the email domain exists and has published DNS required to accept emails. - SMTP test: we connect to the email server of the email address and ask the recipient server if the email address exists. - Smart verify: we complete further email verification tests to eliminate false-positive and false-negative results. - Greylisting tests: some emails return a soft bounce to re-test them later. We complete an automated re-verification progress. - Typo correction: in real-time API, if the email address provided is likely to be a typo of a large email provider, we return a correction recommendation. - Catch all tests: we test if the email server is set to accept mail sent to invalid emails. - Disposable test: we test if a known temporary email address provider hosts the email address. - Free detection: we check if the email domain is a known free email service provider, such as Gmail. - Role detection: we check if the email account (prefix) is linked to a role rather than a person, such as info@ or admin@. **Outstanding accuracy** We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. Hence, we are the only email verifier offering a truly 100% money-back guarantee on our results. **Smart Verify** At MillionVerifier, we aim to go above and beyond when it comes to accuracy. We have kept improving our accuracy for more than six years, and we never stop improving. Smart Verify is a new technology keeping our accuracy rate one step ahead of our competition and providing our users a higher than 99% email verification accuracy. MillionVerifier extends its verification with actual life email sending data, which reduces the number of unknowns and catch-all results, and minimizes the number of false-negative and false-positive results. ![](https://www.millionverifier.com/content/images/2026/05/accuracy_rate_1.webp) **Less Unknown and Catch-All Results** With the help of Smart Verify, we significantly cut down the number of unknown and catch-all emails in 2021\. Hence, we are the only email verifier to refund your email verification credits for both unknown and catch-all emails. **Less False Negative/Positive Results** Email marketing, including email verification, is not exact. SMTP allows email servers to use any custom response that makes email verification impossible to be a 100% accurate service. On the other hand, email communication depends on a stable connection between the email servers. If the connection cannot be created or breaks for any reason, it can lead to inaccurate results. Smart Verify reduces the % of false results, allowing us to be the most accurate email verification service on the market. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Best Email Verification Prices URL: https://www.millionverifier.com/best-email-verification-prices/ Last updated: 2026-06-05T12:40:37.000Z We have created MillionVerifier to provide the [best email verification service](https://www.millionverifier.com/) possible for email marketers with higher email verification needs. Hence, we aim to keep our prices as low as possible. You can see what [our customers have said](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service). **What Do You Pay For?** At MillionVerifier, you only pay for good and bad emails and not for risky (unknown and catch-all) emails. Some email verifiers don’t charge for unknown emails, but MillionVerifier is the only email verifier not charging you for catch-all emails either. ![](https://www.millionverifier.com/content/images/2026/05/best_email_verification_prices_2.webp) **Million Ever Green Promotion** For every 5 million email verification credits purchased, we give you 1 million extra credits for free. In this promotion, we take into account any past payments as well. E.g., If you have purchased 3 million email verification credits last year when you buy 2 million credits, we give you another 1 million credits for free. **Auto Top-Up Promotion** Make sure you never run out of credits and set up auto top-up. With MillionVerifier auto top-up, you can purchase email verification credits automatically when your credits are running low. It is up to you how many credits to buy and when. If you have an auto top-up set up, you will get 10% extra credits on every payment you make, whether you make them manually or automaticly. ![](https://www.millionverifier.com/content/images/2026/05/best_email_verification_prices_1.webp) **100% Money-Back Guarantee** We trust our results; hence, MillionVerifier is the only email verifier offering a truly 100% money-back guarantee on its results. Keeping your hard bounce rate below 4% is critical in email marketing. If, for any reason, we go wrong and following the email verification, you experience a higher than 4% hard bounce rate, we refund your last payment. Most email verifiers offer no guarantee on their results. Some may provide a refund of credits of the emails they miss-verified. But no other email verifier than MillionVerifier guarantees the results can be trusted. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Excellent Email Verification Service URL: https://www.millionverifier.com/excellent-email-verification-service/ Last updated: 2026-06-05T12:40:57.000Z Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [MillionVerifier](https://www.millionverifier.com/) is rated excellent on Trustpilot. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### 40+ Ready-to-Use Integrations URL: https://www.millionverifier.com/ready-to-use-integrations/ Last updated: 2026-06-05T12:41:09.000Z We have a ready-to-use integration with 15 email marketing providers to improve your [email verification experience](https://www.millionverifier.com/why-millionverifier/best-user-experience). Currently, we are integrated with the following email marketing platforms, and we continue connecting new services: - Mailchimp - Sendinblue - Mailgun - Mailjet - Elastic Email - Campaign Monitor - Active Campaign - Zoho CRM - Reply - Getresponse - Hubspot - AWeber - MailerLite - Drip ![](https://www.millionverifier.com/content/images/2026/05/custom_integrations--1-.webp) **Import Your Contacts** Once you have connected your favorite email marketing platform with us, you can import your email list with one click for email verification. Once the verification is completed, you will have the option to unsubscribe or delete bad or risky emails from your account. **Keep Your Account Ever Clean** With MillionVerifier’s unique EverClean (automatic email verification) function, you can always keep your email marketing account clean of bad emails. Connect your email marketing platform, and we will automatically verify your email lists every week and will automatically remove bad emails from your account. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Free EmailAcademy PRO URL: https://www.millionverifier.com/free-emailacademy-pro/ Last updated: 2026-06-05T12:41:22.000Z MillionVerifier is partnered with [EmailAcademy](https://emailacademy.com/?ref=millionverifier.com) to provide our users with a practical email marketing toolkit. All MillionVerifier customers get a coupon applied on EmailAcademy to get a PRO account for free. **All You Ever Need Toolkit** EmailAcademy PRO users get access to the following tools: Email Backlist Checker, [Email Blacklist Monitor](https://emailacademy.com/blacklist-monitor?ref=millionverifier.com), Email Verification Service, Inbox Tester, Bounce Code Analyzer, HTML Email Editor, [HTML Email Templates](https://emailacademy.com/email-templates?ref=millionverifier.com), [Image Hosting for HTML Emails](https://emailacademy.com/email-image-hosting?ref=millionverifier.com), Website Monitor, RNDS Tester, SPF & DKIM Tester. Let’s see the most incredible tools. **Email Blacklist Monitor** Reputation is vital in email marketing. EmailAcademy PRO users can set up 5 IPs or domains to monitor against 50+ email blacklists. They will receive an email and text notification if any of them gets blacklisted. **Image Hosting for HTML Emails** When sending your email campaigns, you must ensure the highest possible user experience as well. Make sure your images are delivered in the correct size from the nearest location possible. Using EmailAcademy’s Image Hosting Service, you can convert your images to the correct size and format, and you can host them on its CDN. **HMTL Email Templates** With your free EmailAcademy PRO account, you will also access HTML email templates that you can use in your email campaigns. EmailAcademy is publishing new templates regularly. ![](https://www.millionverifier.com/content/images/2026/05/html_email_templates.webp) **Unique Knowledgebase** EmailAcademy PRO users can also access all lessons, including all master lessons on EmailAcademy. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Best User Experience URL: https://www.millionverifier.com/best-user-experience/ Last updated: 2026-06-05T12:41:31.000Z MillionVerifier is not just the most [accurate email verifier](https://www.millionverifier.com/why-millionverifier/accuracy-rate) at [low cost](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) but also invested in providing the best user experience with its easy-to-use web application. MillionVerifier is rated [Excellent on Trustpilot](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service). Beyond the intuitive look, we have developed several useful features to increase transparency and improve user experience. Let’s see some of our unique features. **Transparent Credit Balance** MillionVerifier is the only email verification service where you can keep track of your verification credits online and download them in a CSV file. **Add Sub-Users to Your Account** We are unique in allowing you to share your email verification account with others. You can add your colleagues to your account, so you don’t need to share your password with others. ![](https://www.millionverifier.com/content/images/2026/05/sub_users.webp) **Multiple Email Verification API keys** You are allowed to create an unlimited number of API keys, and you can set up IP restrictions to keep your account safe. **2 Factor Authentication** Keeping your account data safe and secure is our utmost priority. You can set up 2-factor authentication with Google Authenticator to ensure no one but you can access your account. **Low Credit Notification and Auto Top-Up** Never run out of email verification credits. You will receive a notification email when you are running low on credits. You can also set up an automatic top-up to buy more credits when your balance drops below a certain point. ![](https://www.millionverifier.com/content/images/2026/05/low_credit_and_auto_topup.webp) --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Let's Help Ukrainian Refugees Together URL: https://www.millionverifier.com/help-ukrainian-refugees/ Last updated: 2026-06-05T12:41:40.000Z Russia has attacked Ukraine on 21 February 2022, causing a humanitarian disaster in Europe. In a couple of days, almost 400,000 Ukrainian was forced to leave their country, and 44 million people were still in fear as Russian forces continued invasion of their country, including their capital, Kyiv. **Help our Neighbours** MillionVerifier is operated from Hungary, a neighboring country of Ukraine. Refugees are fleeing to Europe to find shelter until the aggressive invasion ends in their homes. **10% of All Income Goes to Ukrainian Refugees** Without taking sides, we thrive on helping people in need. We have already shipped blankets and food into Eastern Ukraine. Now, we offer 10% of all income we receive this week to help Ukrainian refugees. 10% of all income between: 28 February 2022 12pm and 7 March 2022 12pm GMT **Up to 30% Extra Credits** Buy email verification credits and get up to 30% extra credits for free. Take this opportunity to help people in need while getting free credits. - 10% extra credits when buying at least 50k credits - 20% extra credits when buying at least 500k credits - 30% extra credits when buying at least 2 million credits ![](https://www.millionverifier.com/content/images/video-thumbnails/e86791e52df92dfe8ed7bbdb6d83e584f8772155df97f8c74d199ab793d54fdb-1280.webp) Buy credits today: [https://app.millionverifier.com/topup](https://app.millionverifier.com/topup?ref=millionverifier.com) Promotion dates: - Starts: 28 February 2022 12pm GMT - Ends: 7 March 2022 12pm GMT --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. ### Terms of Service URL: https://www.millionverifier.com/terms-of-service/ Last updated: 2026-10-19T10:41:03.000Z Published: 19 October 2026 These Terms are a binding contract governing the use of MillionVerifier, including our website, application, API, email-verification tools and related services (the Services). The service provider is Southern Vector Limited, registered at 26 Applefield Court, Northwood, Christchurch 8051, New Zealand, New Zealand company number 9333930, NZBN 9429052764448 and GST number 145-699-835 (Southern Vector, we, us or our). The other party is the business customer identified in the Account or billing details (Customer or you). Southern Vector acquired the MillionVerifier business assets from GBD Software as a Service Private Limited Company (GBD) and assumed the role of Successor Provider, including valid unused Credits, the Credit Ledger and Recovery Records, in accordance with section 10. MillionVerifier is available only for business, professional, trade, public-sector or organisational use. Personal, family, household and other consumer use is not allowed. A person who creates or uses an Account for a Customer is an Authorized User and confirms that they have authority to act for that Customer. Authorized Users must follow these Terms when using the Services, and the Customer is responsible for them. A new Customer accepts these Terms by selecting the checkbox during Account creation. We may update the Terms when reasonably needed for legal, security, privacy, fraud-prevention, technical, operational or business reasons. An update takes effect when it is published with a new publication date. Existing Customers will see an in-app notice at their next login, and Customers that have purchased Paid Credits will also receive an email notice. These notices are informational and do not delay the effective date.Any access to or use of the Services on or after the publication date—including through the Website, application, API, one-by-one tool, an integration or an automated process using Account credentials—constitutes the Customer’s acceptance of the current Terms. Use by an Authorized User or through the Customer’s API key, integration or other credentials is treated as use by the Customer. A Customer that does not agree with an update must stop all use of the Services and disable automated access.We may keep reasonable records of Account creation, checkbox acceptance, policy notices and use of the Services after publication, including the version, Account, user, date, time, IP address, user agent, API or integration activity and delivery status. An update will not retrospectively cancel, reduce, expire or reclassify valid unused Paid Credits, add a new charge to an existing prepaid entitlement, remove an accrued claim or reduce the protection already applying to Customer Personal Data. ## 1\. Key terms - Account means the business account used by the Customer and its Authorized Users. - Credit means a service-use unit recorded in an Account. Unless stated otherwise, one email-address verification uses one Credit. - Paid Credits are Credits purchased for money. - Promotional Credits are any Credits we choose to provide without a separate charge. If offered, they may include registration, email-confirmation, trial and integration Credits; promotional, bonus and Auto Top-Up extras; percentage-based or “+X%” extras; MillionEvergreen Credits; support and goodwill Credits; and Credits for eligible unknown, catch-all or other risky results. Listing a type of Promotional Credit does not promise that it is currently available or will be available in the future. Promotional Credits have no purchase price and a cash refund value of zero. - Credit Ledger means our record of Credit purchases, additions, use, refunds, corrections, classifications and balances, including the order of those entries. - Inactivity means a continuous period in which no Paid Credits are purchased and no Credits are used. Receiving Promotional Credits does not interrupt Inactivity. - Recovery Record means the limited record kept after an inactive Account is removed. It contains a cryptographically hashed email identifier, the remaining Paid and Promotional Credit balances and the minimum Credit Ledger information needed to restore their classification and FIFO order. - Customer Content means data and material submitted or configured by or for the Customer, including email lists, verification files and results, integrations and support communications. - Personal Data means information relating to an identified or identifiable natural person (including "personal information" as defined in the New Zealand Privacy Act 2020). - Customer Personal Data means Personal Data contained in Customer Content or otherwise processed by us for the Customer. - Website means millionverifier.com and its subdomains. - Business Transfer means a sale, merger, reorganisation or other transfer of all or substantially all of MillionVerifier or the business unit that provides it. The company or other legal entity that acquires and continues the business is the Successor Provider. ## 2\. Business eligibility, Accounts and lawful use The Customer must be a legal entity, public body, organisation, sole trader, self-employed professional or other person acting only for business purposes. The Services are not available to minors or anyone who cannot enter into a binding business contract. A company or organisation must provide its correct legal or trading name and, where applicable, its GST, tax or VAT number. If the billing details contain neither a company or organisation name nor a GST, tax or VAT number, the individual providing them confirms that they are a sole trader or self-employed and will use MillionVerifier only for business purposes. The absence of those details does not permit personal use. The Customer must keep its Account, contact, billing, business and tax information accurate and current. We may request reasonable evidence of business status, self-employment, tax status, identity, authority or Account control. We may reject, restrict, suspend or close an Account if the Customer is ineligible, the information is materially false or misleading, or satisfactory evidence is not provided within a reasonable time. Except where law requires otherwise, we may rely on the information supplied and do not have to verify it independently. The Customer must protect its passwords, recovery details and API keys, control access by Authorized Users and promptly remove access that is no longer needed. The Customer is responsible for activity through its Account and credentials, except to the extent directly caused by our breach of an applicable obligation. A Customer may have one Account unless we approve additional Accounts. Separate Accounts must not be created to obtain repeated registration, trial or other Promotional Credits, avoid limits or bypass a suspension. We may investigate and temporarily suspend related Accounts while reviewing suspected abuse.The Services may be used only lawfully. The Customer must not: - violate any law, third-party right or these Terms; - interfere with, damage, overload, probe or disrupt the Website, Services or another system; - introduce malware or harmful code; - copy, monitor or scrape the Website or its content using automated or manual means without our written permission; - provide false, fraudulent, misleading, abusive, defamatory, obscene or unlawful content; or - use the Services in a way that creates a material legal, security, fraud, operational or reputational risk for Southern Vector or another person. The Customer may verify or clean email addresses obtained directly or from a third party, including a data provider, list owner, broker or licensor. The individuals do not have to be the Customer’s subscribers, and these Terms do not require consent or opt-in unless applicable law requires it for the Customer’s intended use. The Customer must nevertheless acquire and use the data lawfully, have an appropriate lawful basis and authority, comply with applicable privacy, direct-marketing and electronic-communications rules (including, where applicable, the New Zealand Privacy Act 2020 and the Unsolicited Electronic Messages Act 2007), and observe relevant notices, objections, suppression requirements, licences and use restrictions. Buying, renting, licensing, finding publicly available data or merely possessing it does not by itself establish lawful use. We may request reasonable evidence about the source and permitted use of a list, API activity, integration activity or a representative sample. Evidence may include supplier details, agreements, invoices, licence terms, warranties, privacy notices, controller instructions, lawful-basis records, objection or suppression records and audit material. The Customer must provide it within the reasonable period we specify. While reviewing the evidence, we may pause processing, restrict the Account or API, withhold Promotional Credits or suspend access. Using unlawfully acquired or disclosed data, or failing to provide satisfactory evidence, is a material breach. A materially false claim of business status, self-employment or authority is also a material breach. The Customer confirms and agrees that it acquires and uses the Services solely "in trade" (as defined in the New Zealand Consumer Guarantees Act 1993 and Fair Trading Act 1986) for business purposes. To the fullest extent permitted by New Zealand law, the parties agree to contract out of the New Zealand Consumer Guarantees Act 1993 and sections 9, 12A, 13 and 14(1) of the New Zealand Fair Trading Act 1986, and acknowledge that it is fair and reasonable to do so. If mandatory law treats an individual as a consumer despite the business-only restrictions above, any right that cannot lawfully be waived remains unaffected. This does not permit personal use or require us to continue providing an ineligible Account. ## 3\. The Services Subject to these Terms, we grant the Customer and its Authorized Users a limited, revocable, non-exclusive, non-transferable licence to use the Services for the Customer’s business purposes. We may offer free or trial access and may, at our discretion, add Promotional Credits to eligible Accounts. Promotional programmes and free-Credit benefits are offered only as available. A current or previous offer does not create a right to receive the same benefit again or in the future. We may introduce, change, limit, suspend or discontinue any promotional benefit at any time without updating these Terms. This includes registration and trial Credits, extra Credits with purchases, Auto Top-Up bonuses, percentage-based or “+X%” extras, MillionEvergreen Credits, support and goodwill Credits, and risky-result Credits. The amount, eligibility and conditions applying to a particular grant are those shown in the Service, Help Centre or relevant offer when the Credits are granted. A change to future promotional availability does not reduce or reclassify Promotional Credits already added, except where an expiry was disclosed when they were granted or these Terms allow a correction or cancellation for error, breach, fraud or abuse. We may change features, add reasonable limits, add paid services, change future prices, or suspend or discontinue all or part of the Services for legal, security, operational or business reasons. A price change does not alter a completed purchase, and we do not promise that the Services will always remain available on the same terms. Valid prepaid entitlements and mandatory law remain protected. The Customer may upload files, use the API, connect its own website or application, or enable a supported third-party integration. By enabling an integration, the Customer authorises us to access and use the minimum information reasonably needed to operate and secure it. Third-party services remain subject to their own terms and availability. ## 4\. Payments and Credits ### Purchases, taxes and payment processing Credit packages, prices, taxes and payment terms are shown on the Website or at checkout. Paid Credits are normally purchased upfront on a pay-as-you-go basis unless checkout clearly says otherwise. Unless stated otherwise, prices exclude GST, VAT, sales, use, withholding and similar taxes. The Customer must provide accurate billing-country, business and tax information. We may charge, collect or account for GST and other taxes as required by law. If materially false or incomplete information, or an incorrect exemption, zero-rating or reverse-charge claim, causes Southern Vector to incur tax, interest, penalties or reasonable external costs, the Customer must reimburse the resulting amount. This does not apply to costs caused by our own error or legal non-compliance. Payments are handled by the payment processors offered at checkout, which may include Stripe or PayPal. Anyone using a payment method confirms that they are authorised to use it. We do not ordinarily receive full payment-card details from those processors. ### Credit rules Credits are contractual service-use units. They are not cash, legal tender, electronic money, a deposit or a withdrawable stored-value balance, and they do not earn interest. Except for restoration of an inactive Account or a Business Transfer, Credits may not be sold, assigned or transferred between Accounts. A displayed Credit balance does not by itself represent money owed by Southern Vector. The quantity bought for payment is recorded as Paid Credits. Any free amount actually added with a purchase or otherwise is recorded as Promotional Credits. Promotion-specific terms may set eligibility, quantities, use restrictions, combination rules or a clearly disclosed expiry date. A promotional extra offered with one purchase does not create a right to receive it with any later purchase.Paid Credits do not expire merely because time passes. Promotional Credits also do not expire merely because time passes unless an expiry date was clearly disclosed when they were granted. Account inactivity or administrative removal does not itself cause Credits to expire or be forfeited. Credits are used globally on a first-in, first-out (FIFO) basis. The oldest Credit entry is used first, whether it is Paid or Promotional. If entries have the same timestamp, the order in the Credit Ledger applies. To identify the Paid and Promotional portions of the remaining balance, we may work backwards through the Credit Ledger from the most recent unconsumed entries. A goodwill Credit, including one issued for an eligible unknown or catch-all result, is a new Promotional Credit added when it is issued. It does not restore the type or original position of the Credit previously used. We may correct clear ledger errors, duplicate or failed-payment entries, fraud and abuse. Unless urgent security or fraud concerns prevent notice, we will give reasonable notice before a correction materially reduces a valid displayed balance. ### Auto Top-Up If the Customer enables Auto Top-Up, it authorises us and our payment processor to charge the selected payment method and buy the selected Paid Credit package when the balance falls below the chosen threshold. The package, price, taxes and threshold are shown when Auto Top-Up is enabled or changed. Any Promotional Credits offered with Auto Top-Up are a separate, discretionary benefit and are not guaranteed for future charges. We may change or discontinue those promotional extras for future charges without updating these Terms. The Customer may change or disable Auto Top-Up before a charge is triggered. We will give notice before applying a materially changed package price to a future automatic charge. ### Refunds Except for the Money Back Guarantee below and any mandatory legal right, Paid Credit purchases are final and non-refundable. Promotional Credits cannot be exchanged for money and do not increase any cash refund, statutory reimbursement, payment reversal or Money Back Guarantee payment.If we refund a Credit purchase, we may remove unused Paid Credits from that purchase and any Promotional Credits granted with it.A Customer in breach of these Terms is not eligible for a refund, repayment, redemption, reversal or other monetary value for any Credits, including under the Money Back Guarantee. No refund is due merely because an Account is restricted, suspended or closed. We may also cancel Promotional Credits and Credits obtained, retained or generated through the breach, fraud or abuse. These rules apply except where mandatory law requires otherwise. ## 5\. Money Back Guarantee Our 100% Money Back Guarantee applies only if the Customer and Account comply with these Terms and all of the following conditions are met: 1. The addresses were verified by uploading a file through [https://app.millionverifier.com/email\_verify](https://app.millionverifier.com/email%5Fverify?ref=millionverifier.com). API and one-by-one verifications are excluded where we do not retain enough information to verify the claim. 2. The Customer sent an email to every qualifying address returned as OK within 7 days after verification. 3. More than 4% of those qualifying OK addresses hard bounced because the address did not exist. Soft bounces are excluded because they may result from sender reputation, configuration, content or other factors outside the verification result. 4. The percentage is calculated as qualifying hard bounces / qualifying OK addresses × 100\. The qualifying period begins with the most recent successful Paid Credit purchase made before the relevant verifications. 5. The Customer used a professional email sender that provides a detailed breakdown of hard and soft bounces. 6. The Customer provides the reports, exports and reasonable access needed to review the claim. A password should not be shared where a secure export, delegated access or another reasonable method is available. 7. The Customer and Account remain compliant while the emails are verified, the claim is reviewed and any refund is paid. We may reject or cancel a claim if a breach is identified before payment and recover a refund obtained through materially false, incomplete or misleading information. If the conditions are met, we will refund the most recent qualifying payment for Paid Credits. The refund is based only on money paid. Promotional Credits—including registration, bonus, Auto Top-Up, percentage-based, MillionEvergreen, support, goodwill and risky-result Credits—have a cash value of zero and do not increase it. After a refund, we may remove unused Paid Credits connected with that payment and related Promotional Credits. We may also close the Account and delete its data, subject to applicable law and the preservation of any other valid Credits through a Recovery Record. This commercial guarantee does not limit any mandatory legal right. ## 6\. Customer data, content and intellectual property Our Privacy Policy explains how we handle Personal Data for our own Account, billing, security and business purposes. When we process Customer Personal Data on the Customer’s behalf, the Data Processing Agreement and the Customer’s documented instructions apply. The Customer is responsible for Customer Content and for having the rights, authority and lawful basis needed to submit and process it. Customer Content must not infringe another person’s rights, contain unlawful or abusive material, or include special-category or other highly sensitive Personal Data unless we have expressly agreed in writing and the processing is lawful. Files uploaded for verification and their result files are normally deleted automatically after 30 days unless a different period is clearly disclosed for a particular Service. Limited information may be kept where needed for security, audit, backup, disputes, accounting, legal compliance or Credit recovery. The Customer must keep its own copies of important content and results. Permanently deleted data cannot normally be recovered. To the extent permitted by law, Southern Vector is not responsible for loss or destruction of Customer Content.Southern Vector and its licensors own the Services, Website, software, designs, branding, documentation and related intellectual-property rights. The licence in these Terms does not transfer ownership. The Customer must not copy, sell, license, rent, modify, distribute, reverse engineer or create derivative works from the Services or our materials except where these Terms or mandatory law expressly allow it. We may monitor or review Customer Content where reasonably needed to operate and protect the Services, investigate compliance or meet legal obligations, but we are not required to monitor everything submitted.Feedback may be used by Southern Vector without restriction or payment, provided that this does not give us ownership of Customer Content or permit us to disclose the Customer’s confidential information. The Website may display advertising or link to third-party websites and services. A link is not an endorsement. We do not control their availability, content, security or privacy practices, and their own terms apply. ## 7\. Suspension, closure and inactive Accounts The Customer may stop using the Services and request Account closure at any time. We may restrict, suspend or close an Account or any part of the Services if we reasonably believe that the Customer or an Authorized User has breached these Terms, exceeded a limit, is ineligible or used the Services for personal purposes. We may take the same action for material misrepresentation, infringement, unlawful conduct or a legal, security, fraud or operational risk. We may also pause processing, remove content, disable API keys or integrations, and suspend related Accounts used to bypass an existing restriction. We will give notice where reasonably practicable, but may act immediately where needed for security, fraud, legal or operational reasons.If an Account is restricted, suspended or closed for breach, the Customer is not entitled to monetary compensation for remaining Credits. We may cancel Promotional Credits and Credits obtained or generated through the breach. Access to unused Paid Credits may remain suspended or end with the Account, but they are not reclassified as Promotional Credits. Mandatory law continues to apply. We retain information for as long as reasonably needed to meet legal, security, accounting, dispute and enforcement obligations. Subject to those needs, Customer Content and Account information are deleted when no longer required. ### Inactive Accounts We may treat an Account as inactive after 12 continuous months in which no Paid Credits were purchased and no Credits were used. Receiving Promotional Credits, logging in or viewing the Account without using or buying Credits does not interrupt Inactivity. At least one month before removing an inactive Account, we will email the primary Account address with the planned removal date and instructions for keeping the Account active. Using at least one Credit or buying Paid Credits during the notice period prevents removal and restarts the inactivity period. If the Account remains inactive, we may remove it for data-minimisation and storage-limitation purposes and delete information that is no longer needed, including credentials, API keys, integrations and Customer Content. Administrative removal does not expire or forfeit the remaining Credits. We keep a Recovery Record so those Credits can be restored. To restore them, the same Customer must create a new Account and contact support through an authorised representative. We may ask for reasonable evidence of the Customer’s identity and continuity, the representative’s authority, control of relevant business domains or email addresses, prior Account administration, billing or transaction history and security information. Email access, knowledge of a payment or card details is not enough by itself. We do not have to decide internal employment, ownership, shareholder, director or partnership disputes and may wait for satisfactory evidence, consistent instructions or a binding order. Once entitlement is verified, we will restore the recoverable Credits with their Paid or Promotional classification and FIFO order preserved as far as the Recovery Record allows. We may keep the Recovery Record for as long as reasonably needed to honour the Credits, prevent duplicate or fraudulent recovery and comply with law, subject to periodic review and the Privacy Policy. ## 8\. Risky results, service availability and liability Verification results may include unknown and catch-all. Any favourable Credit treatment for these results is a discretionary promotional goodwill programme, not a permanent feature of the Services. We do not promise that it will be available for any result, workflow, Account or period. We may introduce, change, limit, suspend or discontinue it for future verifications at any time without updating these Terms. We may also withhold it, cancel unused related Promotional Credits or withdraw future eligibility where the Customer is in breach, cannot provide satisfactory lawful-source evidence, uses scraping or fabricated data, misuses the Services or materially burdens or harms them. Where the programme is currently available, Credits may first be deducted for an eligible bulk-file verification and Promotional Credits may then be added for eligible unknown and catch-all results. Each is a new goodwill Credit entered into the Credit Ledger at the time it is issued. For an eligible API or one-by-one verification, we may instead avoid deducting a Credit for that result. The treatment currently available for each workflow may be shown in the Service or Help Centre.Risky-result Promotional Credits have a cash refund value of zero. The number or percentage of risky results does not by itself create a right to a cash refund or the Money Back Guarantee. The Services are provided as is and as available. To the extent permitted by law, Southern Vector and its affiliates, personnel, contractors, suppliers and licensors disclaim express, implied and statutory warranties and guarantees, including merchantability, acceptable quality, fitness for a particular purpose, title and security. For the purposes of subpart 1 of Part 2 of the New Zealand Contract and Commercial Law Act 2017, this disclaimer and Clause 9 are intended to confer a benefit on, and be enforceable by, Southern Vector’s affiliates, personnel, contractors, suppliers and licensors. We do not promise that the Services will meet every requirement, be uninterrupted or error-free, produce completely accurate results, correct every defect, be available at a particular time or place, or be free of harmful components. The Customer uses the Services and relies on results, content and advice at its own discretion and risk. We are not responsible for delays, downtime, errors or inaccurate or inconsistent results except to the extent liability cannot lawfully be excluded. Nothing in these Terms excludes a liability, remedy or mandatory right that cannot lawfully be excluded or limited. ## 9\. Indemnity To the extent permitted by law, the Customer will indemnify Southern Vector and its affiliates against third-party claims, reasonable costs, proceedings, losses, damages and liabilities arising directly from: - the Customer’s unlawful use of the Services or material breach of these Terms; - the Customer’s fault, negligence or breach of statutory duty; or - robots, spiders, crawlers or similar tools used by the Customer, or other Customer activity that places an unreasonable burden on infrastructure used by Southern Vector or its affiliates. The Customer is not required to indemnify Southern Vector for loss caused by Southern Vector’s own breach, negligence or unlawful conduct, or where the obligation cannot lawfully apply. ## 10\. Business Transfer By agreeing to these Terms, the Customer gives prior and express consent to Southern Vector transferring its entire contractual position (by assignment and novation) to a Successor Provider as part of a Business Transfer. This consent is given for the purposes of New Zealand law and any equivalent applicable rule. (Where the Customer’s contract was transferred from GBD to Southern Vector as Successor Provider, the protections and allocation of pre-transfer and post-transfer responsibilities in this Clause 10 continue to apply to that transfer: GBD remains responsible for its breaches and unlawful acts before the transfer date stated in the Business Transfer notice, and Southern Vector is responsible for its own performance and assumed obligations from that transfer date.) This consent covers these Terms, the Data Processing Agreement, the Account, purchases, API arrangements, Credits and their classification and FIFO order, Credit Ledger and Recovery Records, prepaid entitlements and other standard online arrangements governing MillionVerifier. The consent is not withdrawable. A separately signed agreement that expressly prohibits transfer or requires separate consent will prevail to the extent of a conflict.The transfer takes effect for the Customer on the date and time stated in the Business Transfer notice. From that time, the Successor Provider replaces Southern Vector as the service provider and contracting party, may exercise the transferred rights and must perform obligations falling due after the transfer. Payments then due must be made to the Successor Provider or its payment processor. Southern Vector remains responsible for its breaches and unlawful acts before the transfer; the Successor Provider is responsible for its own performance after it. A Business Transfer does not, merely because the provider changes: - cancel, expire, reduce or reclassify valid unused Credits; - materially alter their FIFO order; - reduce a prepaid entitlement or add a new charge to it; - remove an accrued claim, refund right, remedy or defence; - reduce an existing service commitment or Money Back Guarantee; - prevent recovery of Credits preserved in a Recovery Record; or - reduce the confidentiality, security or data-protection obligations applying to Customer Content and Customer Personal Data. Promotional Credits continue to have a cash refund value of zero.Where Southern Vector acts as processor, the Customer instructs and authorises Southern Vector to transfer Customer Personal Data and related content as reasonably needed to continue MillionVerifier, maintain Accounts, integrations, Credits and service history, perform the transferred contract, keep security, backup, audit, fraud-prevention and support records, and comply with law.Customer Personal Data will not be made available to the Successor Provider for operational use until it has assumed the relevant processor obligations in writing. Appropriate data-protection and international-transfer safeguards will apply. We will send a Business Transfer notice to the primary Account email address and display it in the Account or dashboard where reasonably available. The notice will identify the Successor Provider, its registration details and address, the transfer date, billing and support details, privacy contact and the policies applying after the transfer. We will give reasonable advance notice where practicable; otherwise, notice may be given on the transfer date. The Customer must keep its Account email address current. Subject to mandatory law, the notice is treated as given when it has been sent to that address and displayed in the Account or dashboard where reasonably available.Except for changes validly made under these Terms, the contract continues after a Business Transfer without substantive change other than the provider’s identity and related administrative, payment, support and privacy details. A Successor Provider may rely on this clause for a later transfer of MillionVerifier, subject to the same requirements and protections. ## 11\. General terms These Terms and related non-contractual obligations are governed by New Zealand law (excluding conflict-of-laws rules and the United Nations Convention on Contracts for the International Sale of Goods (CISG)) and are written in English. If mandatory law treats an individual as a consumer despite the business-only restriction, the choice of law and forum does not remove any protection or jurisdiction right that cannot be waived. These Terms are the entire agreement about use of the Website and Services and replace earlier understandings on the same subject, except for a separately signed agreement that expressly governs a particular matter. If part of a provision is invalid or unenforceable, it will be limited or removed only as far as necessary, and the rest remains in effect. Before starting formal proceedings, the parties will use reasonable efforts to resolve a dispute. The complaining party must send a written notice describing the dispute. A notice to Southern Vector must be emailed to [support@millionverifier.com](mailto:support@millionverifier.com) and sent by post to Southern Vector Limited, 26 Applefield Court, Northwood, Christchurch 8051, New Zealand. Unresolved disputes are subject to the exclusive jurisdiction of the courts of New Zealand. The parties may agree in writing after a dispute arises to use lawful mediation, arbitration or another alternative process. --- Previous versions: [Terms of Service - archived on 19 October 2026Published: 20 July 2026 These Terms are a binding contract governing the use of MillionVerifier, including our website, application, API, email-verification tools and related services (the Services). The service provider is GBD Software as a Service Private Limited Company, registered at 6065 Lakitelek, Szikra tanya 93., Hungary, company registration![](https://www.millionverifier.com/content/images/icon/favicon-9a78bd0e-3e9d-41b8-8262-006fbf632fec.ico)MillionVerifierTamas Ham-Szabo![](https://www.millionverifier.com/content/images/thumbnail/publication-cover-a6fa02b9-def9-475d-a6aa-bbb9c338a2d1.jpg)](https://www.millionverifier.com/terms-of-service-archived-on-19-october-2026/) [Terms of Service - archived - 2023-07-14Last updated: 2023-07-14 Please read this Terms of Service (collectively referred to as: “Terms”) as a binding legal agreement, to understand by accessing or using our Website you agree to be bound by the following terms, conditions, and notices contained or referenced. If you do not accept each![](https://www.millionverifier.com/content/images/icon/favicon-10653026-0618-4e76-b949-35cb615cb110.ico)MillionVerifierTamas Ham-Szabo![](https://www.millionverifier.com/content/images/thumbnail/publication-cover-64ad30ce-2232-4d02-a932-42845a4ebd42.jpg)](https://www.millionverifier.com/terms-of-service-archived-2023-07-14/) ### Privacy Policy URL: https://www.millionverifier.com/privacy-policy/ Last updated: 2026-10-19T10:47:19.000Z Published: 19 October 2026 This Privacy Policy explains how Southern Vector Limited (Southern Vector, we, us or our) collects, holds, uses and discloses Personal Data (personal information under the New Zealand Privacy Act 2020) when someone visits MillionVerifier, creates or uses an Account, buys or uses the Services, communicates with us or otherwise interacts with our business. Southern Vector acquired the MillionVerifier business assets from GBD Software as a Service Private Limited Company (GBD) as Successor Provider pursuant to a Business Transfer. MillionVerifier is a business-only service, but privacy rights under the New Zealand Privacy Act 2020 apply to identifiable natural persons, including sole traders, self-employed professionals, Authorized Users, administrators, billing contacts, support contacts, prospects and individuals whose information a Customer submits for verification. For Account, billing, security and our own business activities, Southern Vector is the agency responsible for holding and handling Personal Data under the New Zealand Privacy Act 2020\. When a Customer submits email addresses or other Personal Data for verification, the Customer is the principal agency responsible for that information and Southern Vector holds and processes it solely as an agent on the Customer’s behalf under section 11 of the New Zealand Privacy Act 2020 (referred to as acting as processor in the Terms of Service and Data Processing Agreement (DPA)) and in accordance with the Customer’s documented instructions. ## 1\. Who is responsible Southern Vector Limited Registered office: 26 Applefield Court, Northwood, Christchurch 8051, New Zealand New Zealand company number: 9333930 NZBN: 9429052764448 GST number: 145-699-835 You can contact our Privacy Officer by emailing [support@millionverifier.com](mailto:support@millionverifier.com) or by post at the address above, marked for the attention of the Privacy Officer. Capitalised words used but not defined here have the meaning given in the Terms of Service. Personal Data means information about an identifiable individual ("personal information" as defined in the New Zealand Privacy Act 2020). Customer Personal Data means Personal Data submitted or otherwise processed for a Customer through the Services. ## 2\. Personal Data we collect Depending on how you interact with us, we may collect: - **Account and business information:** name, email address, password hash, phone number, role, Account identifier, company or trading name, company-registration details, GST, tax or VAT number, business or self-employment status, professional role, authority to act for a Customer and reasonable evidence of identity, business status or Account control. - **Integration and support information:** API keys, tokens, connection details and integration settings used to provide and secure integrations, together with support requests, emails, chats, call records, meeting notes and related metadata. - **Contract and notification information:** service and push-notification preferences, the applicable Terms or policy version and publication date, Account and Authorized User identifiers, a new Customer’s acceptance checkbox, in-app notices, emails, delivery or bounce status, dates, times, IP address, user agent, and Website, application, API or integration activity used to document continued use after publication. - **Billing, payment and Credit information:** billing name and address, tax details, payment method type, limited card information supplied by a payment processor, purchases, invoices, refunds, chargebacks, Paid and Promotional Credit classifications, Credit Ledger and FIFO information, inactivity, Recovery Records and Credit restoration. We do not store full card credentials. - **Compliance evidence:** information reasonably requested under the Terms to verify the lawful source and permitted use of email addresses, such as provider details, agreements, invoices, licence terms, warranties, privacy notices, Customer instructions, lawful-collection records, suppression or objection records, audit records and limited representative samples. - **Usage, device and security information:** IP address, approximate location, browser, operating system, device information, referral source, pages and navigation, dates and duration of use, Account and API activity, authentication events, security events, error logs and cookie or similar identifiers. - **Marketing and business-contact information:** professional contact details, employer, role, source, engagement history, communication preferences, consent, opt-out, unsubscribe and suppression records. We collect this information directly from you or, where permitted by the New Zealand Privacy Act 2020, from another Account administrator, a Customer, payment and fraud-prevention providers, authentication and integration providers, communications and analytics providers, publicly available business sources, B2B data providers, advisers, authorities or a previous provider in a Business Transfer. Where Information Privacy Principle 3A of the New Zealand Privacy Act 2020 requires us to notify an individual about personal information collected from another source, we will take reasonable steps to do so unless a statutory exception applies or the individual has already been informed. ## 3\. How and why we use Personal Data We collect and use Personal Data only for lawful purposes connected with our functions and activities under the New Zealand Privacy Act 2020\. Our purposes are to: - create and administer business Accounts, verify business eligibility, identity or authority, and provide, operate and support the Services; - process purchases, invoices, payments, GST and other taxes, Credits, refunds, disputes, inactivity and Credit restoration; - authenticate users, prevent fraud and abuse, and protect the security and integrity of Accounts, systems and the Services; - check compliance with the Terms of Service, review lawful-source evidence, investigate misuse and apply restrictions or enforcement; - send operational, security, billing, support, contractual and policy communications and keep records of notices; - monitor, analyse, maintain and improve the Website and Services; - send relevant business marketing communications in accordance with the New Zealand Unsolicited Electronic Messages Act 2007 and applicable marketing rules; - maintain business, accounting and tax records, comply with applicable law, respond to lawful requests from authorities and establish, exercise or defend legal claims; and - plan or complete a Business Transfer and maintain service continuity. Supplying Personal Data is generally voluntary, except where tax, accounting or other laws require us to collect specific billing or tax information. However, providing certain information is required to create or administer an Account, process a payment, verify business status or authority, restore Credits or respond to a request. If you choose not to provide required information, we may be unable to open or maintain an Account, complete the relevant transaction or request, or provide access to the Services. ## 4\. Customer Personal Data When Southern Vector holds and processes Customer Personal Data on a Customer’s behalf (acting as an agent for the Customer under section 11 of the New Zealand Privacy Act 2020), we use that data only to provide, secure, support and maintain the Services, follow the Customer’s documented instructions, comply with the DPA and meet legal obligations. Access is limited to authorised personnel and service providers that need it. We do not use Customer lists for our own direct marketing or to build unrelated marketing lists. The Customer is responsible for the lawful source, authority, privacy notices and permitted use of the data it submits. Data may have been collected directly or lawfully obtained from a data provider, list owner, broker or licensor. The individuals do not have to be the Customer’s subscribers and do not have to have opted in unless applicable law requires that for the Customer’s intended use. Uploaded files and result files are normally deleted automatically within 30 days unless another period is agreed or limited information must be kept for security, audit, backup, dispute or legal reasons. If we request compliance evidence under the Terms, we use it only as reasonably needed to assess compliance, protect the Services, apply restrictions or enforcement, prevent fraud and establish or defend claims. Southern Vector is the responsible agency for the resulting Account-level review and enforcement records where we hold and use them for our own compliance and enforcement purposes. The underlying verification processing remains governed by the DPA. If a Customer submitted your Personal Data, you should direct any access or correction request to that Customer. We will assist the Customer as required by the DPA and the New Zealand Privacy Act 2020. ## 5\. Sharing Personal Data We disclose Personal Data only as reasonably needed for the purposes set out in section 3 or as otherwise permitted by the New Zealand Privacy Act 2020\. Intended recipients include: - hosting, cloud, network, backup, security and content-delivery providers; - customer-support, communications, scheduling and transactional-email providers; - payment, billing, accounting and fraud-prevention providers, including Stripe or PayPal where used; - analytics, consent-management, advertising and conversion-measurement providers; - software-development, monitoring, automation, document-storage and business-operations providers; - Southern Vector affiliates, authorised personnel and contractors; - lawyers, accountants, auditors, insurers, banks, financiers and other professional advisers; - regulators, law-enforcement bodies, courts and other legal recipients where disclosure is required or permitted by law, or reasonably needed to enforce agreements, protect the Services, prevent unlawful conduct or establish or defend claims; and - a third party chosen or authorised by the Customer, including through an integration. Service providers that handle Personal Data for us are required to maintain appropriate confidentiality, security and privacy protections. Our current [Service Providers, Recipients and Subprocessors](https://www.millionverifier.com/service-providers-recipients-and-subprocessors/) page identifies the third parties we use and their roles. We do not sell Personal Data as an unrelated data-broker product. ## 6\. Business Transfers and international disclosures In a Business Transfer, we may disclose and transfer Personal Data, Accounts, service history, Credits, Credit Ledger information, Recovery Records, billing and support records as reasonably needed to assess or complete the transaction, continue MillionVerifier, preserve contractual entitlements, maintain security and comply with law. Before completion, we will use aggregated, anonymised or otherwise minimised information where reasonably practical. Identifiable Personal Data will be disclosed before completion only where needed, permitted by law and protected by appropriate confidentiality and privacy terms. Customer Personal Data will not be made available to a Successor Provider for operational use until the transfer is permitted by the Terms and DPA, the Successor Provider has assumed the relevant obligations in writing and appropriate safeguards are in place. We will notify affected Account contacts by email and, where reasonably available, through the Account or dashboard. Notice will normally be given in advance and no later than the transfer date. It will identify the Successor Provider, its registration details and address, the transfer date, the main categories and purposes of the transferred data, intended recipients, billing and support details, privacy contact, applicable access and correction rights and the policies applying after the transfer, including the information required by Information Privacy Principle 3A of the New Zealand Privacy Act 2020 where applicable. For the Business Transfer from GBD to Southern Vector, GBD remains solely responsible for its handling of Personal Data, incidents and regulatory matters before the transfer date, and Southern Vector is responsible only for its own handling of Personal Data and the duties it assumes from the transfer date. In any future Business Transfer, Southern Vector remains responsible for its activities before the transfer date, and the Successor Provider is responsible after that date under its privacy policy. Personal Data may be stored or processed in New Zealand, Hungary, the European Economic Area, the United States and other countries where our hosting infrastructure and service providers operate. Our current Service Providers, Recipients and Subprocessors page identifies those providers and their locations. Where we disclose Personal Data outside New Zealand for our own purposes, we comply with Information Privacy Principle 12 of the New Zealand Privacy Act 2020 by ensuring the overseas recipient is subject to privacy laws providing comparable safeguards to the New Zealand Privacy Act 2020, enters into binding contractual safeguards requiring comparable protection, or another lawful basis under Information Privacy Principle 12 applies. ## 7\. Security and retention We use reasonable technical and organisational security safeguards in accordance with Information Privacy Principle 5 of the New Zealand Privacy Act 2020 to protect Personal Data against loss, unauthorised access, use, modification or disclosure, and other misuse. Safeguards include encryption, firewalls, secure configurations, role-based access, authentication, logging, monitoring, vulnerability management, backups, recovery controls, testing and confidentiality duties. No security measure eliminates all risk. We investigate privacy breaches, take reasonable containment and remediation steps, and notify affected individuals and the Office of the Privacy Commissioner where required for a notifiable privacy breach under Part 6 of the New Zealand Privacy Act 2020 (or other applicable law). We may ask for reasonable evidence of identity and authority before disclosing Personal Data or changing an Account. In accordance with Information Privacy Principle 9 of the New Zealand Privacy Act 2020, we do not keep Personal Data for longer than is required for the purposes for which it may lawfully be used, including contractual, security, accounting, tax, legal and dispute requirements. Unless a different period is required or justified: - **Account Data** is kept while the Account is active. After an inactive Account is removed, ordinary Account Data is deleted or de-identified except for Recovery Records and information needed for legal, security, accounting, tax or dispute purposes. In other cases, Account Data may be kept for up to one year after the Services end. - **A Recovery Record** contains a hashed email identifier, remaining Paid and Promotional Credit balances and the minimum ledger information needed to preserve classification and FIFO order and prevent duplicate or fraudulent restoration. It is kept while reasonably needed to honour recoverable Credits and comply with law, subject to periodic review. - **Uploaded files and result files** are normally deleted within 30 days. - **Business-eligibility, authority, compliance and policy-notice records** are kept as long as reasonably needed to administer the relationship, verify compliance, enforce the Terms and handle claims. - **Support and correspondence records** may be kept for up to 10 years where reasonably needed for records or claims. - **Usage and device information** may be kept for up to 50 months after the relationship ends. - **Billing, invoice, transaction and tax records** are kept for the period required by New Zealand tax and corporate law (normally at least 7 years) or other applicable law. - **Marketing preference and suppression records** are kept as long as needed to respect unsubscribe choices and demonstrate compliance under the Unsolicited Electronic Messages Act 2007. - **Business Transfer records** are kept as long as reasonably needed to document the transaction, maintain continuity, comply with law and resolve claims. When a retention period ends, we delete, de-identify or securely isolate the information unless continued retention is legally required. Deleted data may remain temporarily in restricted backups until overwritten in the normal backup cycle. ## 8\. Cookies, sensitive information and minors We use cookies and similar technologies for essential operation, security, preferences, analytics and, where enabled, advertising or conversion measurement. Choices can be managed through our cookie controls and Cookie Policy. Do not submit sensitive personal information unless Southern Vector has expressly agreed in writing and the collection and use are lawful. This includes government identifiers, full payment-card details, financial-account credentials, health, genetic or biometric information, racial or ethnic origin, religious or philosophical beliefs, political opinions, trade-union membership and information about sexual orientation or practices. The Services are not directed to individuals under 18, and we do not knowingly collect Personal Data from minors. ## 9\. Your rights Under Information Privacy Principles 6 and 7 of the New Zealand Privacy Act 2020, you have the right to: - request access to the Personal Data we hold about you; and - request correction of your Personal Data if you believe it is inaccurate, incomplete or misleading, and if we do not make the correction, request that a statement of the correction sought be attached to the information. You may also opt out of marketing emails at any time by using the unsubscribe facility in the message or contacting [support@millionverifier.com](mailto:support@millionverifier.com). We will retain minimum suppression details to ensure your unsubscribe request is respected. We will respond to access and correction requests within the timeframes set by the New Zealand Privacy Act 2020 (normally within 20 working days). We may require reasonable evidence to verify your identity and authority. We may refuse or withhold access or correction, or impose a reasonable charge where permitted, in accordance with Part 4 of the New Zealand Privacy Act 2020 (for example, where disclosure would breach another person’s privacy, prejudice security or commercial position, disclose a trade secret, or where a request is frivolous or vexatious). For Personal Data held by Southern Vector for its own business purposes, send your request to [support@millionverifier.com](mailto:support@millionverifier.com). Where we hold Customer Personal Data solely as an agent on a Customer’s behalf under section 11 of the New Zealand Privacy Act 2020, please direct your request to the relevant Customer (or we may transfer your request to that Customer in accordance with section 43 of the Act). If you are not satisfied with our response to a privacy concern, you may contact the Office of the Privacy Commissioner of New Zealand (OPC): - **Postal address:** PO Box 10094, Wellington 6143, New Zealand - **Street address:** Level 13, Spark Central, 42–52 Willis Street, Wellington 6011, New Zealand - **Email:** [enquiries@privacy.org.nz](mailto:enquiries@privacy.org.nz) - **Telephone:** +64 4 474 7590 (or 0800 803 909 within New Zealand) - **Website:** [https://www.privacy.org.nz/](https://www.privacy.org.nz/?ref=millionverifier.com) ## 10\. Changes and contact We may update this Privacy Policy for legal, regulatory, security, technical, operational or business reasons. A new version takes effect when published with its publication date, unless applicable law requires otherwise. Customer notices are provided through the Account or by email as described in the Terms of Service. This Privacy Policy is an informational notice. If a change requires your consent or notification under the New Zealand Privacy Act 2020, we will complete that step where required. Questions or requests for our Privacy Officer regarding this Policy or Southern Vector’s handling of Personal Data can be sent to: - **Email (Support & Privacy Officer):** [support@millionverifier.com](mailto:support@millionverifier.com) - **Post:** The Privacy Officer, Southern Vector Limited, 26 Applefield Court, Northwood, Christchurch 8051, New Zealand --- Previous versions: [Privacy Policy - archived on 19 October 2026Published: 26 August 2026 This Privacy Policy explains how GBD Software as a Service Private Limited Company handles Personal Data when someone visits MillionVerifier, creates or uses an Account, buys or uses the Services, communicates with us or otherwise interacts with our business. MillionVerifier is a business-only service, but![](https://www.millionverifier.com/content/images/icon/favicon-2b90c955-4b72-4141-b1a5-65a611acdaf3.ico)MillionVerifierTamas Ham-Szabo![](https://www.millionverifier.com/content/images/thumbnail/publication-cover-75c9eaa1-6806-427b-a8c9-f8266f58f1f2.jpg)](https://www.millionverifier.com/privacy-policy-archived-on-19-october-2026/) [Privacy Policy - archived - v. 20 July 2026Published: 20 July 2026 This Privacy Policy explains how GBD Software as a Service Private Limited Company handles Personal Data when someone visits MillionVerifier, creates or uses an Account, buys or uses the Services, communicates with us or otherwise interacts with our business. MillionVerifier is a business-only service, but![](https://www.millionverifier.com/content/images/icon/favicon-38f80ae8-f208-4223-9bfc-e31b87af8f66.ico)MillionVerifierTamas Ham-Szabo![](https://www.millionverifier.com/content/images/thumbnail/publication-cover-ddad69a9-3b2b-4d28-8bea-b0b0d4e0ac82.jpg)](https://www.millionverifier.com/privacy-policy-archived-v-20-july-2026/) [Privacy Policy - archived - 2025-11-05Last updated: 2025-11-05 Please read this privacy policy carefully to understand how the Data Controller uses the Personal Data we collect from you when you visit or use our Website. By accessing or using the Website or the Services, you agree to this Privacy Policy and consent to![](https://www.millionverifier.com/content/images/icon/favicon-ca7bf815-ac3c-4306-9f96-910e7a38a312.ico)MillionVerifierTamas Ham-Szabo![](https://www.millionverifier.com/content/images/thumbnail/publication-cover-3dfb9179-6fca-46ed-9353-6b6de6700dd0.jpg)](https://www.millionverifier.com/privacy-policy-archived-2025-11-05/) ### Data Processing Agreement URL: https://www.millionverifier.com/data-processing-agreement/ Last updated: 2026-10-19T10:45:46.000Z Published: 19 October 2026 This Data Processing Addendum / Data Processing Agreement (DPA) forms part of the MillionVerifier Terms of Service (Terms) between: Southern Vector Limited, a company incorporated in New Zealand, with its registered office at 26 Applefield Court, Northwood, Christchurch 8051, New Zealand, New Zealand company number 9333930, NZBN 9429052764448 and GST number 145-699-835 (Southern Vector, Provider or Processor); and the business Customer identified in the Account or billing details (Customer). Southern Vector acquired the MillionVerifier business assets from GBD Software as a Service Private Limited Company (GBD) and assumed the role of Successor Provider and processor from the transfer date stated in the Business Transfer notice, in accordance with the Terms and Section 10 of this DPA. This DPA applies when Southern Vector holds and processes Customer Personal Data on the Customer's behalf as a processor or subprocessor. It takes effect when the Customer accepts the Terms or otherwise becomes bound by the current Terms, including through continued use of the Services, API or an integration after publication. Capitalised terms not defined here have the meaning given in the Terms. Because the New Zealand Privacy Act 2020 uses "agency" terminology rather than "controller" and "processor", the following contractual definitions apply in this DPA to provide a clear operational framework under New Zealand law: - **Applicable Privacy Law** means the New Zealand Privacy Act 2020 and any other privacy or data-protection law that directly applies to Southern Vector by operation of law in respect of its processing of Customer Personal Data; - **controller** means the principal agency (under the New Zealand Privacy Act 2020) or equivalent entity that determines the purposes and means of collecting, holding and using Customer Personal Data; - **processor** means an agency that holds and processes Customer Personal Data solely as an agent on behalf of another agency for the purposes of section 11 of the New Zealand Privacy Act 2020 (and does not use or disclose that information for its own purposes); - **subprocessor** means a third-party service provider engaged by Southern Vector to hold or process Customer Personal Data on behalf of the Customer in connection with the Services; - **Personal Data** (or **personal data**) means "personal information" as defined in the New Zealand Privacy Act 2020 (information about an identifiable individual); - **data subject** means the identifiable individual to whom Personal Data relates; - **processing** (and **process**) means any operation performed on Personal Data, including collecting, receiving, holding, storing, organising, validating, transmitting, disclosing, returning or deleting it; - **Personal Data Breach** means any unauthorised or accidental access to, or disclosure, alteration, loss or destruction of, Customer Personal Data, or any action that prevents Southern Vector from accessing Customer Personal Data on either a temporary or permanent basis (a "privacy breach" under Part 6 of the New Zealand Privacy Act 2020); and - **supervisory authority** means the Office of the Privacy Commissioner of New Zealand or any other privacy or data-protection regulator having direct statutory jurisdiction over Southern Vector under Applicable Privacy Law. ## 1\. Scope and order of documents 1. This DPA governs Southern Vector's holding and processing of Customer Personal Data as a processor (acting as an agent on the Customer's behalf under section 11 of the New Zealand Privacy Act 2020) and under Applicable Privacy Law. A privacy or data-protection law that applies only to the Customer does not impose additional contractual obligations on Southern Vector under this DPA unless that law also directly applies to Southern Vector or Southern Vector agrees otherwise in writing. 2. Southern Vector acts as an independent responsible agency (controller) for Account administration, billing, fraud prevention, Account-level compliance and enforcement, legal claims, and security records used to protect its own systems and business, as described in the Privacy Policy. This DPA does not govern those independent activities, but continues to govern processing of Customer Personal Data carried out by Southern Vector on the Customer's behalf to provide, secure, maintain and support the Services. 3. If this DPA conflicts with the Terms, this DPA prevails only to the extent necessary to govern Southern Vector's processing of Customer Personal Data as a processor or subprocessor. The Terms continue to govern all other matters, including commercial terms, suspension, termination, Credits, refunds, warranties, indemnities and liability, except where Applicable Privacy Law mandatorily requires otherwise. ## 2\. Roles and instructions 1. Where the Customer determines the purposes and essential means of processing Customer Personal Data, the Customer is the controller (principal agency) and Southern Vector is its processor (holding and processing the information as the Customer's agent under section 11 of the New Zealand Privacy Act 2020). Where the Customer processes Customer Personal Data on behalf of another controller, the Customer acts as a processor and engages Southern Vector as its subprocessor. In either case, the Customer represents and warrants that it has all authority and authorisations required to engage Southern Vector, issue the instructions under this DPA and authorise Southern Vector's use of subprocessors. 2. The Customer instructs Southern Vector to hold and process Customer Personal Data as reasonably necessary to provide, secure, maintain and support the Services described in the Terms and Annex 1\. The Terms, this DPA, the Customer's use and configuration of the Services, Account settings, uploads, API requests and integration settings constitute the Customer's documented instructions. A written request from an authorised representative of the Customer is an additional documented instruction only to the extent that it is consistent with the Terms and this DPA and falls within the agreed scope or is accepted by Southern Vector under Section 2.5. 3. Southern Vector will process Customer Personal Data only on the Customer's documented instructions, including instructions concerning disclosures or transfers of Personal Data outside New Zealand or to another jurisdiction, unless New Zealand law or another law to which Southern Vector is subject requires otherwise. Where legally permitted, Southern Vector will inform the Customer before carrying out processing required by such law. 4. Southern Vector will promptly inform the Customer if, in Southern Vector's opinion, an instruction infringes Applicable Privacy Law. Southern Vector is not responsible for determining the overall lawfulness of the Customer's collection or processing, legal basis, source of data or intended use. Southern Vector may decline or suspend affected processing until the instruction is withdrawn, changed, confirmed to be lawful or otherwise resolved, and may exercise any related suspension or termination right available under the Terms. 5. Southern Vector is not required to comply with an instruction that is outside the ordinary functionality or agreed scope of the Services unless compliance is expressly required by this DPA or Applicable Privacy Law or Southern Vector accepts the instruction in writing. Southern Vector may condition acceptance of an additional instruction on reasonable technical, operational or commercial requirements and reasonable fees agreed in advance. 6. For the purposes of section 11 of the New Zealand Privacy Act 2020, Southern Vector will not use or disclose Customer Personal Data for its own purposes, will not use Customer Personal Data for its own direct marketing, and will not retain Customer Personal Data in, contribute it to, or use it to build or enrich a persistent reputation database, marketing list or other data product made available to another customer for that other customer's independent use.Southern Vector may retain submitted addresses and verification results in a temporary operational cache for up to seven (7) days where reasonably necessary to provide, secure, optimise or support the Services. Cached data is automatically expired or deleted at the end of the applicable cache period and is not used for model training.This restriction does not prevent processing performed on the Customer's documented instructions, including independently processing information separately submitted by another customer, engaging authorised subprocessors, processing reasonably necessary for a Business Transfer, or using information that has been de-identified or anonymised so that it no longer constitutes Personal Data under Applicable Privacy Law. ## 3\. Customer responsibilities 1. The Customer is responsible for: - the lawfulness, fairness and transparency of its collection, holding, use and disclosure of Customer Personal Data; - complying with privacy, data-protection and electronic-marketing laws applicable to the Customer and its use of the Services; - establishing and documenting an appropriate lawful purpose and legal basis; - obtaining any required consent, permission or authorisation; - providing required privacy notices to individuals; - responding to individual access, correction and other privacy requests and objections; - the accuracy, relevance, minimisation and permitted use of Customer Personal Data; - ensuring that it is authorised to disclose Customer Personal Data to Southern Vector; - where the Customer acts as a processor, ensuring that its instructions to Southern Vector are authorised by the relevant upstream controller; and - ensuring that its instructions comply with applicable law. 2. Customer Personal Data does not have to relate only to subscribers or individuals who opted in to the Customer's communications. The Customer may submit data collected directly or obtained through a third party, including data that was purchased, rented or licensed, provided that the Customer lawfully acquired it, is authorised to disclose it to Southern Vector and may lawfully use it for the Customer's intended purpose. 3. The Customer must not submit sensitive personal information (including special-category personal data, information relating to criminal convictions or offences, government identifiers, full payment-card data, financial-account credentials, health, genetic or biometric information, racial or ethnic origin, religious or philosophical beliefs, political opinions, trade-union membership or information about sexual orientation or practices) unless Southern Vector has expressly agreed in writing and the parties have documented any required lawful basis, instructions and safeguards. Southern Vector has no obligation to inspect Customer Personal Data to determine whether prohibited information has been submitted and may reject, suspend processing of or delete prohibited information where reasonably necessary. 4. The Customer must use reasonable security safeguards to protect its Account, API keys, integrations and access credentials and must promptly notify Southern Vector of suspected unauthorised access that may affect Customer Personal Data. The Customer is responsible for activity performed through its Account, Authorized Users and credentials except to the extent directly caused by Southern Vector's breach of an applicable obligation. 5. The Customer will provide information and cooperation reasonably necessary for Southern Vector to verify the authority, scope or lawfulness of a material instruction where Southern Vector has reasonable grounds to request it. Southern Vector may suspend the affected processing while reasonably required information remains outstanding. ## 4\. Southern Vector's processor obligations Southern Vector will: 1. ensure that persons authorised to process Customer Personal Data are bound by confidentiality obligations or an appropriate statutory duty of confidentiality and process the data only as required for their duties; 2. implement and maintain reasonable technical and organisational security safeguards in accordance with Information Privacy Principle 5 of the New Zealand Privacy Act 2020 (and Applicable Privacy Law), taking into account implementation costs, the nature, scope, context and purposes of processing and the sensitivity and risks of the information. The current categories of safeguards are described in Annex 2; 3. taking into account the nature of the processing, assist the Customer by appropriate technical and organisational measures, insofar as reasonably possible, with fulfilment of the Customer's obligations to respond to requests from data subjects exercising their privacy rights (including access and correction requests); 4. taking into account the nature of the processing and the information available to Southern Vector, reasonably assist the Customer with its statutory obligations regarding: - security safeguards; - Personal Data Breach assessment and notification; - privacy impact assessments; and - consultation with competent supervisory authorities where required by law; 5. maintain records and information required of Southern Vector in its capacity as a processor and, subject to Section 9, make available information reasonably necessary to demonstrate Southern Vector's compliance with its obligations under this DPA; and 6. cooperate with the Office of the Privacy Commissioner of New Zealand and other competent supervisory authorities to the extent required of Southern Vector by Applicable Privacy Law. The Customer will first use the functionality, documentation, reports and compliance materials ordinarily made available through the Services where they reasonably address the relevant request.Where assistance requires bespoke work beyond the ordinary functionality, documentation and compliance materials of the Services, Southern Vector may charge reasonable costs, including for customer-specific questionnaires, technical work, legal review or repeated assistance, unless and to the extent that the assistance is required because of Southern Vector's material breach of this DPA or mandatory law requires otherwise. ## 5\. Personal Data Breaches 1. Southern Vector will notify the Customer without undue delay after becoming aware of a Personal Data Breach affecting Customer Personal Data. 2. The notice will be sent to the primary email address associated with the Customer's Account. The Customer designates that address as its contractual contact address for notices under this Section 5 and is responsible for keeping the address current and appropriately monitored. Southern Vector may use additional notification channels at its discretion but is not required to send a notice to any additional security, privacy, legal or other contact designated by the Customer. 3. To the extent the information is available to Southern Vector, the notice will describe: - the nature of the Personal Data Breach; - the categories and approximate number of affected data subjects and records, where available; - the likely consequences; - the measures taken or proposed to contain, investigate and remediate the breach; and - a contact point for further information. 4. Southern Vector may provide information in phases as its investigation develops. A notification or provision of assistance under this Section does not constitute an admission of fault, negligence, breach or liability. 5. Because Southern Vector holds Customer Personal Data as an agent on the Customer's behalf under section 11 of the New Zealand Privacy Act 2020, the Customer (as principal agency / controller) remains responsible for determining whether the breach is a notifiable privacy breach (or otherwise requires notification to a supervisory authority, affected individuals or another person under laws applicable to the Customer) and for making any notification for which the Customer is responsible. Southern Vector will provide the assistance required of it under Section 4 and Applicable Privacy Law. Nothing in this DPA transfers the Customer's notification obligations to Southern Vector. ## 6\. Subprocessors 1. The Customer gives Southern Vector general written authorisation to engage subprocessors to hold and process Customer Personal Data in connection with the Services. 2. Southern Vector maintains a current list of subprocessors that process Customer Personal Data on the [Service Providers, Recipients and Subprocessors](https://www.millionverifier.com/service-providers-recipients-and-subprocessors/) page. Providers identified with the scope DPA or Both constitute Southern Vector's subprocessor list for purposes of this DPA. 3. Southern Vector will give reasonable advance written notice of an intended addition or replacement of a subprocessor that will process Customer Personal Data through a prominent notification in the Customer's Account. The notice will identify the intended subprocessor and give the Customer an opportunity to object before the subprocessor is engaged.The Customer agrees that the Account is the designated notification channel for notices under this Section 6\. Southern Vector is not required to provide a separate email or notice to another contact. The Customer is responsible for monitoring Account notices, including where the Customer principally accesses the Services through the API, an integration or an automated process. 4. An objection must: - be submitted within the notice period stated in the notification; - follow any reasonable response method stated in the notification; and - identify specific, reasonable and documented privacy or security grounds relating to the proposed subprocessor's processing of that Customer's Personal Data.If the Customer does not object within the notice period, Southern Vector may engage the proposed subprocessor after the stated effective date.Southern Vector will consider a timely objection in good faith and will not engage the proposed subprocessor to process that Customer's Personal Data while the timely objection remains unresolved.If the objection cannot reasonably be resolved, Southern Vector may, at its option: - not use the proposed subprocessor for that Customer; - provide a commercially reasonable alternative; - modify the affected processing; - postpone the proposed change; - suspend the affected part of the Services; or - terminate the affected Services or, where the affected processing cannot reasonably be separated, the Account.The Customer may stop using the affected part of the Services. Any Account closure, suspension, Credit, payment or refund consequence is governed exclusively by the Terms and mandatory law. 5. Southern Vector will impose on each subprocessor, by written contract or other legally binding arrangement, confidentiality, security and privacy obligations substantially protective of Customer Personal Data and consistent with this DPA to the extent applicable to that subprocessor's processing. Southern Vector remains responsible for the subprocessor's performance of those contractual obligations to the extent required by Applicable Privacy Law. ## 7\. International disclosures and transfers 1. Processing under this DPA may involve storage or processing in New Zealand, Hungary, the European Economic Area, the United States or other jurisdictions where Southern Vector's authorised subprocessors operate, as identified on the [Service Providers, Recipients and Subprocessors](https://www.millionverifier.com/service-providers-recipients-and-subprocessors/) page. The Customer's acceptance of this DPA and use of the Services constitutes the Customer's documented instruction and authorisation for Southern Vector to store and process Customer Personal Data in those locations through its authorised subprocessors. 2. Where Southern Vector initiates a cross-border disclosure or transfer of Customer Personal Data that is subject to Applicable Privacy Law (including Information Privacy Principle 12 of the New Zealand Privacy Act 2020 where applicable), Southern Vector will ensure that the overseas subprocessor is subject to privacy laws providing comparable safeguards or is bound by contractual obligations requiring comparable privacy and security safeguards, and will implement supplementary technical or organisational measures where legally required. 3. Where a transfer between the Customer and Southern Vector legally requires a separate transfer mechanism under Applicable Privacy Law directly applicable to Southern Vector or to Southern Vector's receipt or processing of Customer Personal Data, the parties will reasonably cooperate to implement the legally required mechanism (noting that New Zealand is recognised by the European Commission as providing an adequate level of data protection). Southern Vector is not required to enter into a country-specific or customer-specific transfer agreement, addendum or other instrument solely because a privacy law applies to the Customer, unless the instrument is also legally required for the relevant processing by Southern Vector or Southern Vector separately agrees to it in writing. 4. On reasonable request, Southern Vector will provide information reasonably necessary to demonstrate compliance with transfer obligations directly applicable to Southern Vector. Southern Vector may satisfy such requests using standard documentation or compliance materials and may withhold or redact information where reasonably necessary to protect legal privilege, security, trade secrets, another customer's information or confidential third-party information, provided that this does not prevent Southern Vector from meeting a mandatory legal obligation. ## 8\. Return and deletion 1. Customer-uploaded files and result files are normally deleted automatically within 30 days unless a different period is agreed or clearly stated for a particular Service. Southern Vector may apply a shorter retention period where reasonably appropriate for the relevant Service or processing. The Customer is responsible for exporting or retaining any results it requires before deletion. 2. During the term, the Customer should use available Service functionality to access, export or delete Customer Personal Data. Where such functionality is not reasonably sufficient, the Customer may request reasonable assistance from Southern Vector subject to Section 4. 3. When Southern Vector stops providing the relevant processing Services, the Customer may choose to have the remaining Customer Personal Data then held by Southern Vector returned or deleted, unless New Zealand law or another law to which Southern Vector is subject requires retention. Return may be completed using the export functionality ordinarily available through the Services or another format agreed by Southern Vector. Southern Vector is not required to create a bespoke export format, reconstruct data already deleted in accordance with the Services or this DPA, or retain data beyond the applicable retention period solely to facilitate a later export. 4. The Customer may communicate a contrary return or deletion instruction within 30 days after termination of the relevant processing Services. If the Customer gives no contrary instruction during that period, the Customer instructs Southern Vector to delete the remaining Customer Personal Data in accordance with Southern Vector's normal deletion processes. 5. Copies contained in backups or disaster-recovery systems may remain until removed through Southern Vector's ordinary backup lifecycle. While retained, those copies remain subject to the protections of this DPA and will not be used for ordinary business purposes. Southern Vector is not required to alter an ordinary backup cycle or restore a backup solely for the purpose of separately deleting data from that backup, except where Applicable Privacy Law requires otherwise. If a backup containing previously deleted Customer Personal Data is restored, Southern Vector will continue to apply the applicable deletion instruction. 6. This Section does not require deletion or return of information that Southern Vector lawfully holds and uses as an independent responsible agency (controller) under the Privacy Policy, including limited security, audit, billing, compliance, legal or Recovery Record information. ## 9\. Information and audits 1. Southern Vector will make available to the Customer information reasonably necessary to demonstrate Southern Vector's compliance with its obligations under this DPA. Southern Vector may satisfy this obligation through relevant policies, descriptions or summaries of technical and organisational safeguards, compliance questionnaires, independent audit reports, certifications or other reasonably appropriate documentation. 2. The Customer will review information reasonably made available by Southern Vector before requesting an audit. If that information is not reasonably sufficient to demonstrate compliance with the relevant obligation under this DPA, the Customer may conduct or mandate an audit of Southern Vector's relevant processing, subject to the following reasonable safeguards: - the Customer will identify the specific compliance matter to be audited and provide a reasonable audit plan; - the Customer will give at least 30 days' written notice; - ordinary Customer-requested audits are limited to once in any 12-month period; - documentary or remote review will be used first where it can reasonably satisfy the audit purpose; - any inspection will take place at a mutually reasonable time during normal business hours and will minimise disruption to Southern Vector's operations; - the auditor must be independent, appropriately qualified, bound by written confidentiality obligations and not a direct competitor of Southern Vector; - the audit will be limited to systems, records and processing relevant to the Customer's Customer Personal Data and Southern Vector's obligations under this DPA; - the audit must not expose another customer's data or confidential information; - the audit must not require disclosure of source code, credentials, cryptographic secrets, vulnerability details, privileged material, trade secrets or information that Southern Vector is legally or contractually prohibited from disclosing, except to the minimum extent a mandatory legal obligation requires otherwise; - penetration testing, vulnerability scanning, destructive testing, social engineering, physical-security testing or direct testing of production systems requires Southern Vector's prior written agreement and may be subject to separate security conditions; - the Customer and auditor must follow Southern Vector's reasonable security, confidentiality, access and safety requirements; and - the Customer bears all costs of its auditor and its own audit activities.Southern Vector may charge its reasonable internal and external costs of supporting an audit. If the audit establishes a material breach by Southern Vector of an obligation under this DPA relating to the audited processing, Southern Vector will not charge assistance costs reasonably attributable to verifying that established breach. 3. The ordinary notice and frequency restrictions in Section 9.2 do not apply to the extent: - a competent supervisory authority requires an audit or inspection; - Applicable Privacy Law requires an earlier audit; or - the Customer provides reasonable documented grounds indicating a material breach by Southern Vector of its obligations under this DPA and an earlier audit is reasonably necessary to investigate that suspected breach.Even in those circumstances, the parties will use reasonable efforts to minimise unnecessary disruption and protect the confidentiality and security of Southern Vector, its systems and other customers. Nothing in this Section limits the lawful powers of the Office of the Privacy Commissioner of New Zealand or another competent supervisory authority. ## 10\. Term, updates and Business Transfers 1. This DPA remains in effect for as long as Southern Vector holds or processes Customer Personal Data on the Customer's behalf. It cannot be terminated separately from the Terms. Obligations that by their nature must continue after termination survive only to the extent and for the period necessary to govern Customer Personal Data that Southern Vector is required or permitted to retain, to complete return or deletion, to comply with applicable law, or to determine or enforce rights and liabilities arising before termination. 2. Updates to this DPA take effect in accordance with the publication, notice and acceptance mechanism set out in the Terms. The updated DPA will continue to satisfy the mandatory requirements of Applicable Privacy Law applicable to Southern Vector's processing. No separate handwritten signature, separately negotiated amendment or customer-specific acceptance process is required unless mandatory law or a separately signed agreement expressly requires otherwise. 3. In connection with a Business Transfer described in the Terms, the Customer confirms its documented instruction and authorisation for Southern Vector to transfer the DPA, Customer Personal Data and related content as reasonably necessary to complete and implement the Business Transfer and enable continued provision of MillionVerifier by the Successor Provider in accordance with the Terms.This DPA and Southern Vector's processor position may be assigned, novated or otherwise transferred to the Successor Provider together with the Terms without separate Customer consent, subject to the Business Transfer provisions of the Terms and mandatory law. (Where this DPA was transferred from GBD to Southern Vector as Successor Provider, GBD remains solely responsible for its processing, breaches and incidents before the transfer date stated in the Business Transfer notice, and Southern Vector is responsible for its own performance after that transfer date.)Before the Successor Provider processes Customer Personal Data for operational purposes as the successor processor, it must be bound in writing or electronic form by this DPA or other processor obligations satisfying the mandatory requirements applicable to that processing. Any international-transfer safeguard legally required for that processing must also be in place.Except where mandatory law requires otherwise, no additional Customer consent or separate processor agreement is required solely because the identity, registration details, address or jurisdiction of the Provider changes as part of a Business Transfer carried out in accordance with the Terms. ## 11\. General terms and contact 1. The liability, exclusions, remedies, governing law (New Zealand law), jurisdiction (courts of New Zealand), notice, assignment, severability and other general provisions of the Terms apply to this DPA. To the maximum extent permitted by law, contractual claims arising out of or relating to this DPA are subject to the same exclusions, limitations, remedies and allocation of risk that apply under the Terms. This DPA does not create a separate or additional category of uncapped contractual liability. Nothing in the Terms or this DPA limits a responsibility, statutory liability or right that cannot lawfully be limited or excluded under Applicable Privacy Law. 2. This DPA is concluded electronically and does not require a handwritten signature. 3. Privacy and data-processing questions concerning this DPA (including for our Privacy Officer) may be sent to: - **Email (Support & Privacy Officer):** [support@millionverifier.com](mailto:support@millionverifier.com) - **Post:** The Privacy Officer, Southern Vector Limited, 26 Applefield Court, Northwood, Christchurch 8051, New Zealand 4. Except for statutory rights that cannot lawfully be excluded, this DPA does not confer contractual rights on data subjects, supervisory authorities or other third parties under subpart 1 of Part 2 of the New Zealand Contract and Commercial Law Act 2017 or otherwise. 5. The Customer may exercise contractual rights under this DPA only through an authorised representative. Southern Vector may reasonably rely on authenticated Account activity and communications from persons reasonably appearing to be authorised and may request reasonable evidence of authority where appropriate. --- # Annex 1 — Processing details | Item | Description | | --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Subject matter | Email verification, cleaning and related processing through the MillionVerifier Website, application, API and supported integrations. | | Duration | For the period during which the Customer uses the relevant Services, followed by the deletion and backup periods described in this DPA. | | Nature of processing | Receiving, transmitting, temporarily storing, organising, validating, comparing, querying relevant technical systems, classifying, returning results, troubleshooting, securing, backing up and deleting Customer Personal Data as an agent on the Customer's behalf under section 11 of the New Zealand Privacy Act 2020. | | Purpose | To provide, secure, maintain and support the Services according to the Customer's documented instructions. | | Frequency | On demand or continuously, as initiated or configured by the Customer through the Website, application, API or integrations. | | Categories of data subjects | Individuals whose contact information the Customer lawfully submits, which may include business contacts, prospects, customers, subscribers, employees, contractors or other contacts. | | Types of Personal Data | Email addresses; names, company or professional details and other non-sensitive fields supported by the relevant Service and lawfully submitted by the Customer; verification status and result data; and list, file, API and processing metadata needed to provide the Services. | | Sensitive personal information | Not intended or authorised unless Southern Vector expressly agrees in writing and the parties document the lawful basis, instructions and additional safeguards required for the processing. | | Customer's rights and obligations | Where the Customer is the controller (principal agency), it retains control over the purposes of processing, its lawful instructions, lawful basis, individual privacy notices and requests, and use of the results. Where the Customer acts as a processor, those matters remain subject to the instructions and authority of the relevant upstream controller. The Customer may use available Service controls to submit, access, export and delete Customer Personal Data and may issue lawful instructions within the scope of this DPA. | # Annex 2 — Security safeguards Southern Vector maintains a security programme containing reasonable technical and organisational security safeguards appropriate to the risks of the relevant processing in accordance with Information Privacy Principle 5 of the New Zealand Privacy Act 2020 and Applicable Privacy Law.The specific safeguards applicable to a system, component or processing activity may vary according to its purpose, architecture and risk. As appropriate, Southern Vector's safeguards include controls in the following categories: - role-based and least-privilege access controls; - authentication controls and additional protection for privileged access; - encryption in transit and, where appropriate having regard to risk and architecture, at rest; - logical separation of customer data; - secure configuration, patching, vulnerability management and malware protection; - logging, monitoring and controls designed to detect unauthorised access or misuse; - backup, restoration and business-continuity measures; - incident-response and breach-management procedures; - confidentiality obligations and appropriate security awareness for authorised personnel; - subprocessor due diligence and contractual security requirements; and - periodic testing, assessment and review of relevant security safeguards. Southern Vector may modify, replace or update individual security safeguards, technologies, suppliers, controls and implementation methods as the Services, technology and risks evolve, provided that the resulting safeguards remain reasonable and appropriate as required by Information Privacy Principle 5 of the New Zealand Privacy Act 2020 and Applicable Privacy Law.Nothing in this Annex requires Southern Vector to use or retain a particular technology, product, supplier, certification, standard, hosting architecture or implementation method unless expressly agreed by Southern Vector in writing. --- Previous versions [Data Processing Agreement - archived on 19 October 2026Published: 26 August 2026 This Data Processing Addendum (DPA) forms part of the MillionVerifier Terms of Service (Terms) between: GBD Software as a Service Private Limited Company, a company incorporated under the laws of Hungary, with its registered office at 6065 Lakitelek, Szikra tanya 93., Hungary, company registration number 03-![](https://www.millionverifier.com/content/images/icon/favicon-307f34e2-a7f0-4f23-80ed-69b49e0fe14c.ico)MillionVerifierTamas Ham-Szabo![](https://www.millionverifier.com/content/images/thumbnail/publication-cover-727bf0ce-b6d8-4001-bd37-4badf2ab73c1.jpg)](https://www.millionverifier.com/data-processing-agreement-archived-on-19-october-2026/) [Data Processing Agreement - archived - v. 20 July 2026Published: 20 July 2026 This Data Processing Addendum (DPA) forms part of the MillionVerifier Terms of Service (Terms) between: GBD Software as a Service Private Limited Company, a company incorporated under the laws of Hungary, with its registered office at 6065 Lakitelek, Szikra tanya 93., Hungary, company registration number 03-![](https://www.millionverifier.com/content/images/icon/favicon-e07713e5-3765-45f7-a99d-842ecfecdc40.ico)MillionVerifierTamas Ham-Szabo![](https://www.millionverifier.com/content/images/thumbnail/publication-cover-3fb99d33-4277-4c5e-ad84-6f856ea03018.jpg)](https://www.millionverifier.com/data-processing-agreement-archived-v-20-july-2026/) [Data Processing Agreement - Archived - 2025-12-04Thoughts, stories and ideas.![](https://www.millionverifier.com/content/images/icon/favicon-2789d2c1-6037-4613-9a9e-5a6b8d718cf9.ico)MillionVerifierTamas Ham-Szabo![](https://www.millionverifier.com/content/images/thumbnail/publication-cover-c4f5cb7b-6f2d-4683-9519-64ef5d1f5978.jpg)](https://www.millionverifier.com/data-processing-agreement-archived-2025-12-04/) ### Catch-All Email Verifier URL: https://www.millionverifier.com/catch-all-email-verifier/ Last updated: 2026-07-22T12:22:13.000Z ### What is Catch-All Email Verification? Catch-all email verification is an advanced SMTP validation process that determines if a specific mailbox exists behind an "Accept-All" server firewall. While standard verifiers label these addresses as "Risky" or "Unknown," MillionVerifier’s built-in engine actively tests them, successfully resolving 30% to 40% into safe, valid leads without requiring secondary tools. ## The Problem: Why B2B Senders Lose Valid Leads When you verify a B2B email list, you will inevitably encounter "Accept-All" or "Catch-All" domains. These are server configurations designed to accept every email sent to the domain, regardless of whether the specific user exists. - **The Standard Verifier Trap:** Most verification tools hit this firewall, give up, and label the email as "Risky." - **The Marketer's Dilemma:** You are forced to either delete potentially high-value leads or risk sending to them and destroying your sender reputation with hard bounces. - **The Hidden Cost:** To safely email them, you normally have to export that "Risky" segment and pay a premium, third-party pinging service to re-test them. ## The MillionVerifier Solution: Built-In Catch-All Resolution MillionVerifier eliminates the guesswork. Our verification engine includes proprietary Catch-All resolution technology designed to penetrate Accept-All firewalls and confirm mailbox existence. - **30% to 40% Recovery Rate:** We successfully convert up to 40% of your Catch-All emails into definitive "Valid" or "Invalid" statuses. - **Zero Extra Fees:** This deep-level verification is built directly into our core engine. It costs exactly one standard verification credit. - **Seamless CRM Workflow:** Rescued Catch-All emails are placed directly into your standard "Valid" and "Invalid" download columns. No messy sub-tags, no confusing data mapping—just a clean CSV ready for your email marketing platform. ## Stop Paying Double for "Risky" Emails Comparing MillionVerifier to standard bulk email verifiers reveals massive ROI for B2B lead generation and outbound sales teams. | **Feature** | **Standard Verifiers** | **MillionVerifier** | | -------------------- | -------------------------------------- | ---------------------------------- | | **Catch-All Result** | Labeled as "Risky" / "Unknown" | Resolves 30-40% into Valid/Invalid | | **Cost to Verify** | 1 Credit | 1 Credit | | **Cost to Resolve** | Requires external tool ($0.02/email) | **$0.00 (Included)** | | **Workflow** | Export CSV -> Use Second Tool -> Merge | One single dashboard upload | ## Frequently Asked Questions #### Does verifying Catch-All emails cost extra credits? No. MillionVerifier’s Catch-All resolution process is built directly into our standard verification engine. It costs exactly one regular verification credit (as low as $0.00017 per email). #### Do I have to sort the rescued Catch-All emails manually? No. When you download your cleaned list, the resolved Catch-All emails are automatically categorized into your standard "Valid" (safe to send) and "Invalid" (delete immediately) columns for a seamless CRM import. #### What happens to the Catch-All emails that cannot be resolved? The remaining percentage of Catch-All emails that block our deep-level ping are categorized safely as "Risky." MillionVerifier does not charge you credits for any email that results in an "Unknown" or unresolved "Catch-All" status. #### Is the Catch-All verifier covered by your accuracy guarantee? Yes. Every email we successfully resolve from a Catch-All server into a "Valid" status is backed by our 99%+ verification accuracy and 100% money-back guarantee. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ## Posts ### How to Email an Old List Without Wrecking Your Sender Reputation URL: https://www.millionverifier.com/blog/how-to-email-an-old-list-without-wrecking-your-sender-reputation/ Last updated: 2026-10-22T05:36:31.000Z **To email an old list safely, verify every address first, then restart with your most recently engaged contacts in small batches, and grow volume only while bounces and complaints stay low.** Ask the least engaged contacts to reconfirm before you send them anything else. A contact counts as old once they haven't engaged for about six months. Past twelve months, some of the list's dead addresses may already have become spam traps. - **Verify before anything else.** Even a reconfirmation email can damage your reputation if it goes to dead addresses. - **Restart small.** Send to recent, engaged contacts first and add older segments only while results stay healthy. - **Set stop rules below the platforms' limits.** Pause at 1% hard bounces on any batch, and review the message before growing if a small batch draws even one complaint. ## How old is too old for an email list? ![](https://www.millionverifier.com/content/images/2026/10/Section-01---How-Old-Is-Too-Old-selection.png) Treat a contact as old once they haven't engaged for six months. Treat them as high risk after twelve. | Time since last engagement | What has probably happened | What to do | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | | Under 6 months | Some addresses have decayed, but most still work | Verify, then send normally and watch the first send closely | | 6 to 12 months | Engagement has gone cold. AWS advises against mailing subscribers who haven't engaged for 6 months or longer ([AWS](https://aws.amazon.com/blogs/messaging-and-targeting/what-is-a-spam-trap-and-why-you-should-care/?ref=millionverifier.com)), and Apollo doesn't offer the same bounce guarantee for verified emails older than six months ([Apollo](https://knowledge.apollo.io/hc/en-us/articles/4409227148045-Troubleshoot-Bounced-Emails?ref=millionverifier.com)) | Verify, segment, ramp up gradually, and reconfirm unengaged contacts | | Over 12 months | Some dead addresses may now be spam traps. Mailbox providers often let an abandoned address hard bounce for 12 months or more before turning it into a trap ([AWS](https://aws.amazon.com/blogs/messaging-and-targeting/what-is-a-spam-trap-and-why-you-should-care/?ref=millionverifier.com)) | Verify, then send only a reconfirmation email to the oldest segment and keep the contacts who confirm | HubSpot uses the same 12-month line. Its suspension appeal asks whether you have contacts you haven't emailed in over 12 months ([HubSpot](https://knowledge.hubspot.com/marketing-email/why-is-my-email-suspended?ref=millionverifier.com)). Count from the last time a contact engaged, not the last time you sent. A contact you mailed last month who hasn't clicked, replied or bought anything in two years is still an old contact. Don't rely on opens: Apple Mail Privacy Protection loads images automatically, which inflates open rates. ## What goes wrong when you email an old list? ![](https://www.millionverifier.com/content/images/2026/10/Section-02---What-Goes-Wrong-selection.png) Four things, and they compound. A single send to a stale list can trigger all of them at once. 1. **Dead addresses hard bounce.** People change jobs and abandon accounts, so an old list carries more addresses that no longer exist. Brevo can suspend campaigns above a 2% hard bounce rate, and HubSpot, MailerLite and Amazon SES act at 5%. See [What Is a Good Email Bounce Rate?](https://www.millionverifier.com/blog/what-is-a-good-email-bounce-rate-benchmarks-for-newsletters-and-cold-email/) for each platform's limit. 2. **Recycled spam traps accept your mail.** Once a provider turns an abandoned address into a trap, it stops bouncing, so it looks like a working address. Sending to traps can lead to a blocklist listing that blocks much of your mail. 3. **People who forgot you report spam.** Mailchimp warns that even a contact with a valid address may report spam if they don't want to hear from you ([Mailchimp](https://mailchimp.com/help/reconfirm-contacts/?ref=millionverifier.com)). Gmail wants your spam rate below 0.1%, which is one complaint per thousand emails, and treats 0.3%, three per thousand, as the line you must never reach. 4. **The sudden volume looks suspicious.** Going from silence to a full-list blast is a spike. Google warns that increasing volume too quickly can cause delivery issues and recommends consistent sending volumes ([Google](https://support.google.com/mail/answer/15256272?ref=millionverifier.com)). Verification fixes the first problem and shrinks the second: it removes addresses that still bounce before they can turn into traps. It can't detect a trap that already accepts mail, and it can't fix the third or fourth. For more on what verification can and can't catch, see [The Ugly Truth About Spam Traps](https://www.millionverifier.com/blog/the-ugly-truth-about-spam-traps-and-what-email-verification-can-actually-fix/). ## Step 1: Verify the whole list before you send anything ![](https://www.millionverifier.com/content/images/2026/10/Section-03---Step-1-Verify-selection.png) Verify every address before the first email, including the reconfirmation email. Mailchimp notes that a reconfirmation message sent to unengaged contacts can itself affect your sending reputation, so it needs a clean list too. 1. **Export the list without its suppressions.** Leave past unsubscribes, complaints and hard bounces out. Never re-add them, however old the list is. 2. **Run it through the** [**Bulk Email Verifier**](https://www.millionverifier.com/services/bulk-email-verifier/)**.** 3. **Act on each result:** - **Good:** eligible for the restart. - **Risky** (catch-all and unknown): set aside. These go last, in small batches. - **Bad:** remove, and add to your sending platform's suppression list so they can't come back with the next import. For example, suppose an 8,400-contact list comes back with 610 Bad and 940 Risky results. You restart with the 6,850 Good addresses, and the 940 Risky ones wait until the Good segments have gone out cleanly. ## Step 2: Segment by last engagement and signup date ![](https://www.millionverifier.com/content/images/2026/10/Section-04---Step-2-Segment-selection.png) Split the Good results by how recently each contact engaged. Engagement means a click, reply, purchase or login, not an open. If you have no engagement history, use the signup date instead. | Segment | Who is in it | What they get | Send order | | ------- | --------------------------------------------------------------- | ------------------------------------------------------------------------- | ----------------------------------------- | | A | Engaged in the last 6 months | Your normal email, with a short note that you're back | First | | B | Last engaged 6 to 12 months ago | A "we're back" email that reminds them who you are and why they signed up | Second | | C | No engagement for 12 months or more, or never engaged | A reconfirmation email only (Step 4) | Third | | D | Risky verification results, split by age the same way as A to C | The email for their age group, in small batches | Last, and only if A to C went out cleanly | Segment A protects you. Recent, engaged contacts are the most likely to open, click and not complain, and those signals help offset the weaker results from older segments. ## Step 3: Set stop rules before the first send ![](https://www.millionverifier.com/content/images/2026/10/Section-05---Step-3-Stop-Rules-selection.png) Decide in advance when you'll pause, so nobody has to make that call in the middle of a bad send. | Signal | Stop rule | Why this line | | ------------------------------------------- | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | Hard bounce rate on any batch | Pause at 1% | A list you've just verified shouldn't come near 1%. It also leaves room below Brevo's 2% suspension line and the 5% lines elsewhere | | Complaints on a batch of under 1,000 emails | Review the message and the segment before growing if even one complaint comes in | One complaint in a 500-email batch is already 0.2%, so a percentage can't work at this size | | Complaint rate across the whole restart | Pause if the running total reaches 0.05% | Our recommendation: half of the 0.1% line that Gmail, HubSpot and Amazon SES all use | | Block bounces (5.7.x) at one provider | Stop sending to that provider | The provider is refusing your mail, and more volume makes it worse | | Deferrals (4.x.x) | Hold volume flat | Google advises waiting before you increase volume when deferrals appear ([Google](https://support.google.com/mail/answer/15256272?ref=millionverifier.com)) | Your platform's complaint count also undercounts Gmail recipients. Gmail reports spam rates in aggregate through Postmaster Tools instead of passing on each complaint, and Postmaster Tools may show no data at all when your volume to Gmail is low. Treat any complaint you do see as a sign of more you can't see. Check each batch 24 to 48 hours after sending before you send the next one. Some bounces arrive as separate bounce emails, and complaints can come in days after delivery. For how to read the codes behind a block, see [Hard Bounces vs. Spam Complaints](https://www.millionverifier.com/blog/hard-bounces-vs-spam-complaints-how-to-survive-the-gmail-yahoo-outlook-sender-rules/). ## Step 4: Send a reconfirmation email to the oldest segment ![](https://www.millionverifier.com/content/images/2026/10/Section-06---Step-4-Reconfirmation-selection.png) Ask segment C to confirm they still want your emails, and keep only the contacts who do. AWS calls this a permission pass: a one-time campaign that lets recipients confirm they still want your mail, after which only confirmed contacts stay on future lists. A good reconfirmation email has five parts: 1. **Who you are and where they signed up.** "You joined our newsletter at the 2024 Leeds trade show" beats "You're on our list". 2. **What they'll get and how often.** One line is enough. 3. **One clear button** that confirms the subscription. 4. **An easy way out.** A visible unsubscribe link, so leaving is easier than reporting spam. 5. **A deadline.** Say when you'll remove anyone who doesn't confirm, then do it. Here's a short version you can adapt: > **Subject:** Do you still want our emails? > > Hi Anna, you signed up for our product updates in 2024, and we haven't written in a while. We're restarting with one email a month. Want to stay on the list? > > \[Yes, keep me subscribed\] > > If we don't hear from you by 15 November, we'll remove you. No hard feelings. > > Not interested? \[Unsubscribe\] and you won't hear from us again. Send it to segment C in small batches, under the same stop rules as everything else. Email marketing laws vary by country, so check the rules that apply to your contacts before you send. **If you use Mailchimp,** its process works the other way round. You export the audience, unsubscribe the subscribed contacts, and send them a link to your signup form so they can opt back in. In that case, the button links to your signup form, and the deadline line can go, because nobody stays subscribed unless they sign up again. Mailchimp also suggests sending reconfirmations from your business's own email client or another service, where permitted, because a reconfirmation sent to unengaged contacts can affect your Mailchimp sending reputation. Be careful with that for large segments. A staff mailbox has its own daily sending limits and shares your domain's reputation, so use a separate sending service, or keep the batches small. ## Step 5: Ramp up volume gradually ![](https://www.millionverifier.com/content/images/2026/10/Section-07---Step-5-Ramp-Up-selection.png) Start with a small batch of your most engaged contacts and grow each send by 25% to 100%. That range comes from Google's own guidance for raising volume after delivery problems, and it works just as well for a restart. Here's how the 6,850 Good addresses from Step 1 could go out, split into segment A (2,300), segment B (2,850) and segment C (1,700): | Send | Who gets it | Batch size | Change on the previous send | | --------- | ---------------------------------------------------- | ------------ | --------------------------- | | 1 | Segment A, most recently engaged first | 500 | Start | | 2 | Segment A | 1,000 | +100% | | 3 | Rest of segment A, plus the start of segment B | 1,500 | +50% | | 4 | Rest of segment B | 2,150 | +43% | | 5 | Segment C, reconfirmation email | 850 | Smaller | | 6 | Rest of segment C, reconfirmation email | 850 | Same | | 7 onwards | Risky results, split by age, in batches of about 300 | 940 in total | Smaller | Leave at least 24 hours between sends, and 48 if the previous batch came close to a stop rule. Move to the next row only when the previous batch has stayed under every stop rule. If a batch comes close to a limit, repeat that batch size instead of growing it. Once the restart is done, keep sending at a steady rhythm. Google recommends consistent volumes over random spikes. ## How do you keep the list from going stale again? ![](https://www.millionverifier.com/content/images/2026/10/Section-08---Keep-the-List-Fresh-selection.png) Send regularly, remove people who stop engaging, and verify any data before it enters the list. - **Run a sunset policy.** Decide when an unengaged contact gets one last re-engagement email and then leaves the list. A common rule for weekly senders is no click in 90 days. Klaviyo recommends sunset flows for exactly this reason: they remove unengaged recipients before their mailboxes become invalid ([Klaviyo](https://help.klaviyo.com/hc/en-us/articles/115005250408?ref=millionverifier.com)). - **Verify before every import.** Event lists, partner lists and CRM exports go through the [Bulk Email Verifier](https://www.millionverifier.com/services/bulk-email-verifier/) before they reach your sending platform. - **Verify at signup.** The [Email Verifier API](https://www.millionverifier.com/services/email-verifier-api/) checks addresses when people submit your form, so typos and disposable addresses never get in. - **Don't go quiet for months.** A list you mail steadily never needs a restart plan. ## Frequently asked questions #### Can I email a list I haven't used in two years? Yes, but not with a normal campaign. Verify it first, then send only a reconfirmation email and keep the contacts who confirm. After 12 months, some abandoned addresses may have been turned into spam traps, so the people who confirm are the only part of the list you can trust. #### When does an email list become stale? Treat contacts who haven't engaged for six months as old, and anything over twelve months as high risk. AWS advises against mailing subscribers who haven't engaged for 6 months or longer, and recycled spam traps often bounce for 12 months or more before they go live. #### Will email verification remove spam traps? No. Verification removes addresses that still bounce, before they can become traps, and it flags risky ones. A trap that already accepts mail looks like a working address, so no verifier can detect it. #### Should I send the reconfirmation email from my email platform? Check your platform's guidance. Mailchimp suggests sending reconfirmation messages from your business's own email client or service where permitted, because reconfirmations sent to unengaged contacts can affect your sending reputation on Mailchimp. A staff mailbox has its own daily sending limits and shares your domain's reputation, so for anything beyond a small segment, use a separate sending service or keep batches small. Wherever you send it, verify the list first. #### How fast can I ramp up sending to an old list? Grow each send by 25% to 100%, starting with your most engaged contacts. Google uses the same range in its guidance for raising volume after delivery problems. Only move up while every batch stays under your bounce and complaint stop rules. #### What should I do if bounces spike during the restart? Pause that segment and read the bounce codes. 5.1.x codes mean dead addresses, which point to a list problem. 5.7.x codes mean the provider refused your mail, which points to a sender problem. [550 5.1.1 and Other Hard Bounce Codes](https://www.millionverifier.com/blog/550-5-1-1-and-other-hard-bounce-codes-when-to-suppress/) explains each code. ## Restart with a clean list The safest restart starts before the first email. Run your old list through MillionVerifier, remove the dead addresses, and send your first batch knowing that every Good address can still receive mail. See how it works for dormant lists on the [Clean Old Email Lists](https://www.millionverifier.com/solutions/clean-old-email-lists/) page. [Create your free account](https://app.millionverifier.com/register?ref=millionverifier.com) to get 100 free credits, no credit card needed. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### What Is a Good Email Bounce Rate? Benchmarks for Newsletters and Cold Email URL: https://www.millionverifier.com/blog/what-is-a-good-email-bounce-rate-benchmarks-for-newsletters-and-cold-email/ Last updated: 2026-10-19T11:11:54.000Z **A good email bounce rate is under 2% of emails sent, with hard bounces under 1%.** Investigate as soon as your total reaches 2%. Most email platforms that publish a limit act at 5%, and at least one acts at 2%. Cold email doesn't get a looser limit. - **2% is a market benchmark, not an official rule.** Gmail, Yahoo and Outlook.com don't publish a bounce threshold. - **Benchmarks disagree because they measure different things.** Check what your platform counts as a bounce before you compare yourself with an "industry average". - **The cheapest fix is before you send.** Verifying a list removes addresses that would hard bounce. It doesn't remove policy blocks, which are a sender problem. ## What is email bounce rate? ![](https://www.millionverifier.com/content/images/2026/10/Section-1---Bounce-Rate-selection.png) Email bounce rate is the percentage of sent emails that the receiving server rejected or couldn't deliver. ``` Bounce rate = (bounced emails / emails sent) x 100 ``` For example, a campaign sent to 12,500 addresses with 175 bounces has a bounce rate of 1.4%. If 75 of those bounces were hard bounces, the hard bounce rate is 0.6%. - **A hard bounce** is a permanent failure. The address doesn't exist, the mailbox is disabled, or the domain can't receive mail. Suppress the address. - **A soft bounce** is a temporary failure, such as a full mailbox or a busy server. Your platform retries it. - **A block bounce** is a policy rejection. The address exists, but the provider refused your mail because of authentication or reputation. Many platforms report it as a hard bounce. To read the codes behind each type, see [550 5.1.1 and Other Hard Bounce Codes](https://www.millionverifier.com/blog/550-5-1-1-and-other-hard-bounce-codes-when-to-suppress/). ## What is a good bounce rate for newsletters and cold email? ![](https://www.millionverifier.com/content/images/2026/10/Section-2---Good-Bounce-Rate-selection.png) Aim for under 2% total and under 1% hard bounces on both channels. Cold email doesn't get a looser limit. The difference is how often cold lists drift above the line, because they're built from data that ages. | Channel | Aim for | Investigate at | Act immediately at | Where the line comes from | | ------------------------------- | ------------------------------------- | -------------------------------------------- | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | Newsletters and marketing email | Under 2% total, under 1% hard bounces | 2% total, or a hard bounce spike on one send | 5%, where several platforms act | 2% is the common market benchmark. See the platform table below | | Cold email | Under 2% total, under 1% hard bounces | 2% total | Consistently above 5% | [Apollo's help center](https://knowledge.apollo.io/hc/en-us/articles/4409227148045-Troubleshoot-Bounced-Emails?ref=millionverifier.com) | The 1% hard bounce target is our recommendation, not a platform rule. It leaves room for the bounces verification can't prevent: catch-all domains that accept every address during the check, and mailboxes disabled between verification and send. Cold lists need re-checking more often. Apollo says it doesn't provide the same bounce rate guarantee for verified emails it delivered more than six months ago ([Apollo](https://knowledge.apollo.io/hc/en-us/articles/4409227148045-Troubleshoot-Bounced-Emails?ref=millionverifier.com)). If a data provider won't stand behind a six-month-old address, re-verify it before you add it to a new sequence. ## At what bounce rate do email platforms take action? ![](https://www.millionverifier.com/content/images/2026/10/Section-3---Platform-Limits-selection.png) Most platforms that publish a limit act at 5%. Brevo acts at 2%. Others publish no number at all, and none of the big mailbox providers do. | Platform | Published bounce limit | What happens | Source | | ------------------------- | --------------------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Amazon SES | Review at 5% hard bounces; possible pause at 10% | Account placed under review, then sending may be paused until fixed | [AWS reputation metrics](https://docs.aws.amazon.com/ses/latest/dg/reputationdashboardmessages.html?ref=millionverifier.com) | | HubSpot | 5% hard bounces in a month | Marketing email sending may be suspended | [HubSpot Knowledge Base](https://knowledge.hubspot.com/marketing-email/why-is-my-email-suspended?ref=millionverifier.com) | | MailerLite | More than 5% bounces | Account may be suspended immediately and investigated | [MailerLite anti-spam policy](https://www.mailerlite.com/legal/anti-spam-policy?ref=millionverifier.com) | | Brevo | Hard bounce rate above 2% on recent campaigns | Campaigns and account can be suspended | [Brevo Help Center](https://help.brevo.com/hc/en-us/articles/209408165-Reactivate-your-email-campaigns-after-a-suspension?ref=millionverifier.com) | | Apollo | Under 2% acceptable; investigate if consistently above 5% | Hard-bounced addresses are removed; sequences can be auto-paused | [Apollo help center](https://knowledge.apollo.io/hc/en-us/articles/4409227148045-Troubleshoot-Bounced-Emails?ref=millionverifier.com) | | Mailchimp | No published number | Automatic suspension when a single send exceeds "industry thresholds" | [Mailchimp: About Bounce Suspension](https://mailchimp.com/help/about-bounce-suspension/?ref=millionverifier.com) | | Klaviyo | No account-level percentage | Suppresses an address after a hard bounce or 7 consecutive soft bounces | [Klaviyo Help Center](https://help.klaviyo.com/hc/en-us/articles/115005250408?ref=millionverifier.com) | | Gmail, Yahoo, Outlook.com | No published bounce threshold | Filtering and rejections based on overall reputation | [Hard Bounces vs. Spam Complaints](https://www.millionverifier.com/blog/hard-bounces-vs-spam-complaints-how-to-survive-the-gmail-yahoo-outlook-sender-rules/) | We checked each platform's own policy pages on 19 October 2026 and found no published bounce threshold in Mailchimp's or Klaviyo's. Policies change: HubSpot last updated its suspension page on 23 September 2026. Complaint limits are far stricter than bounce limits. HubSpot and Amazon SES both act at a 0.1% spam complaint rate, and MailerLite and Brevo at 0.2%. A list can stay under every bounce limit and still get an account suspended on complaints alone. ## Why do bounce rate benchmarks disagree? ![](https://www.millionverifier.com/content/images/2026/10/Section-4---Benchmarks-Disagree-selection.png) Published "average bounce rates" range widely because each source measures something different. Constant Contact, for example, reported an all-industries average bounce rate of 10.4% in data published in January 2024, five times the 2% benchmark ([Smart Insights' compilation of Constant Contact data](https://www.smartinsights.com/email-marketing/email-communications-strategy/statistics-sources-for-email-marketing/?ref=millionverifier.com)). Constant Contact measures bounce rate as emails sent compared with emails delivered, so every email that wasn't delivered counts, whatever the reason. That doesn't make 10% normal for your list. It shows how much the definition moves the number. Before you compare yourself with any average, check these five differences: 1. **The denominator.** Most platforms divide bounces by emails sent. Some reports divide by emails delivered or accepted, which gives a different figure for the same campaign. 2. **What counts as a bounce.** Some platforms count policy blocks (5.7.x codes) as hard bounces. A sudden authentication problem can then look like a list problem. See [Hard Bounces vs. Spam Complaints](https://www.millionverifier.com/blog/hard-bounces-vs-spam-complaints-how-to-survive-the-gmail-yahoo-outlook-sender-rules/) for how to tell them apart. 3. **Hard or total.** Amazon SES bases its bounce rate on hard bounces only, and HubSpot's limit is a hard bounce limit. A benchmark that reports total bounces isn't comparable with either. 4. **The time window.** A single campaign, a rolling window and a calendar month give different numbers. HubSpot assesses its limits cumulatively over a month. 5. **Whose lists.** Industry averages mix opt-in newsletters, cold outreach and lists nobody has mailed in years. Data published by verification companies also skews high, because people tend to verify the lists they already suspect. The benchmark that matters is your own hard bounce rate, measured the same way after every send. ## Which bounce rate should you track: hard, soft or block? ![](https://www.millionverifier.com/content/images/2026/10/Section-5---Track-Bounce-Types-selection.png) Track all three, but act on them differently. | Bounce type | What it tells you | What to do | | --------------------------- | --------------------------------------------- | --------------------------------------------------------------------------- | | Hard bounces (5.1.x, 5.2.1) | Your list contains dead addresses | Suppress them, then find the import, form or lead source they came from | | Block bounces (5.7.x) | A provider refused your mail | Fix authentication or reputation. Don't suppress the addresses | | Soft bounces (4.x.x) | Temporary trouble, sometimes an early warning | Let your platform retry. Repeated 4.7.x deferrals often come before a block | Split each rate by receiving domain as well. A spike at one provider on one day usually means a block. Bounces spread across many domains usually mean bad data. ## What should you do if your bounce rate is too high? ![](https://www.millionverifier.com/content/images/2026/10/Section-6---High-Bounce-Rate-Steps-selection.png) Stop sending to the affected segment, find out which kind of bounce caused the spike, and fix that cause before you resend. Work through these steps in order: 1. **Pause the affected segment, not the whole program.** Keep sending to engaged contacts on other lists while you investigate. 2. **Export the bounces with the full SMTP response.** A "hard bounce" label isn't enough. You need the code and the provider's error text. 3. **Split them by code.** 5.1.x and 5.2.1 are dead addresses. 5.7.x are policy blocks. 4.x.x are temporary. [550 5.1.1 and Other Hard Bounce Codes](https://www.millionverifier.com/blog/550-5-1-1-and-other-hard-bounce-codes-when-to-suppress/) has a decision table for each code. 4. **If blocks dominate, fix the sender.** Check SPF, DKIM and DMARC, and look at your complaint rate. Re-cleaning the list won't help. 5. **If dead addresses dominate, find the source.** A cluster usually traces back to one import, one form or one lead source. Fix it there. 6. **Verify the rest of the list before the next send.** Remove Bad results and send to Risky results in small batches. 7. **Resume gradually, most engaged contacts first,** and watch your platform's dashboard after each send. ## How do you keep your bounce rate low? ![](https://www.millionverifier.com/content/images/2026/10/Section-7---Keep-Bounce-Rate-Low-selection.png) Verify addresses before they reach a campaign. A verifier checks each address with the receiving mail server without sending an email, so dead addresses are removed before they can bounce. - **Before every import and every cold campaign:** run the list through the [Bulk Email Verifier](https://www.millionverifier.com/services/bulk-email-verifier/). Send to Good results, test Risky results in small batches and remove Bad results. - **At signup:** check addresses in real time with the [Email Verifier API](https://www.millionverifier.com/services/email-verifier-api/), so typos and disposable addresses never enter your list. - **Before you mail an old list:** verify the whole list first. Addresses decay as people change jobs and abandon accounts. - **For catch-all-heavy B2B lists:** the [Catch-All Email Verifier](https://www.millionverifier.com/catch-all-email-verifier/) resolves part of the catch-all segment into valid or invalid. - **For a single address that bounced:** check it with the free [Email Checker](https://www.millionverifier.com/services/email-checker/) before you suppress it. Verification lowers hard bounces. It doesn't prevent policy blocks or spam complaints, which depend on your authentication, your content and whether recipients want your mail. ## Frequently asked questions #### Is a 5% email bounce rate bad? Yes. 5% is where several platforms act: MailerLite may suspend an account above 5%, HubSpot may suspend marketing email at a 5% monthly hard bounce rate, and Amazon SES places accounts under review at 5%. Brevo is stricter and can suspend campaigns above a 2% hard bounce rate. Investigate at 2%. #### What is the average email bounce rate? There isn't one reliable average, because platforms count bounces differently. Constant Contact reported 10.4% across all industries in data published in January 2024, counting every email that wasn't delivered. Figures based on hard bounces alone are far lower. Compare yourself with the 2% line and with your own past sends instead. #### What is a good bounce rate for cold email? Under 2%. Apollo calls a bounce rate under 2% acceptable and tells users to investigate immediately if it stays above 5%. Cold lists drift above the line faster than newsletters, so verify every export before it goes into a sequence. #### Does Gmail have a bounce rate limit? Gmail doesn't publish one. Its sender guidelines publish spam complaint limits instead: keep spam rates below 0.1% and never reach 0.3%. High bounce rates still hurt your reputation with Gmail, and your sending platform may enforce its own limit. #### Is a 0% bounce rate possible? Rarely, and it isn't a useful target. Catch-all domains accept every address during verification, and some mailboxes are disabled between verification and send. A near-zero hard bounce rate on a verified list is realistic. #### Do soft bounces count toward the bounce rate? It depends on the platform. Amazon SES bases its bounce rate on hard bounces, and HubSpot's limit is a hard bounce limit. Other platforms report total bounces, so check which number you're looking at. #### How often should I verify my email list? Before every import, before mailing any list you haven't mailed recently, and before every cold campaign. For data from a lead provider, re-verify any export older than a few months before you add it to a new sequence. ## Check your list before your next send Your bounce rate is decided before you click send. Run your next list through MillionVerifier, remove the addresses that would hard bounce, and keep your rate well under the 2% line. [Create your free account](https://app.millionverifier.com/register?ref=millionverifier.com) to get 100 free credits, no credit card needed. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### A New Chapter for MillionVerifier with Southern Vector URL: https://www.millionverifier.com/blog/a-new-chapter-for-millionverifier/ Last updated: 2026-10-19T13:03:21.000Z Dear MillionVerifier customers, Today marks the start of a new chapter for MillionVerifier. After years under GBD Software as a Service Ltd, **MillionVerifier is now operated by Southern Vector Limited,** a company based in New Zealand. This change is part of an internal restructuring. **The ultimate ownership of MillionVerifier remains unchanged, and I continue to lead the company as its founder and CEO.** I know that trust is everything when it comes to your data and your business, so I want to be clear about what this means for you: **the same leadership, the same team, and the same commitment to accuracy and affordability.** Your service continues exactly as before. Bringing MillionVerifier under Southern Vector gives us a stronger foundation to **invest even more in the tools you rely on every day.** ### What's ahead In the coming months, you can look forward to **a refreshed MillionVerifier app and webinars.** We’re also preparing something special before the end of the year, and I look forward to sharing it with you soon. ### What stays the same **Your account, credits, API keys, integrations and prices** all remain exactly as they are, and our 100% Money Back Guarantee continues as always. ### What’s changing **Invoices and taxes.** From today, invoices are issued by Southern Vector Limited and show its company details. Customers in Europe will no longer be charged VAT, and customers in New Zealand will be charged GST in line with local tax requirements. **Payment methods.** **PayPal is no longer available.** If you’ve been paying with PayPal, please select another payment method for your next purchase. **Policies.** Our [Terms of Service](https://www.millionverifier.com/policies/terms-of-service/), [Privacy Policy](https://www.millionverifier.com/policies/privacy-policy/) and [Data Processing Agreement](https://www.millionverifier.com/policies/data-processing-agreement/) now name Southern Vector Limited as the service provider. Protecting your data remains one of our highest priorities, and our commitment to privacy and security is unchanged. ### We’re here for you Have a question? Our team is always happy to help at support@millionverifier.com. Thank you for your continued trust in MillionVerifier. I’m grateful to have you with us, and the best is yet to come. **Tamás Hám-Szabó** Founder and CEO, MillionVerifier P.S. I promised the best is yet to come, and we will do just that, starting tomorrow. 🚀 That’s when we’re launching **willdo, our new agentic platform** from the Southern Vector family. [Sign up for early access](https://willdo.ai/early-access/?ref=millionverifier.com) to be among the first to try it. ### 550 5.1.1 and Other Hard Bounce Codes: When to Suppress URL: https://www.millionverifier.com/blog/550-5-1-1-and-other-hard-bounce-codes-when-to-suppress/ Last updated: 2026-10-14T12:16:44.000Z Only one kind of bounce should be suppressed after a single send: one that tells you the address itself is dead. The mailbox doesn't exist, it has been disabled, or its domain can't receive mail. This guide shows what those bounces look like at Gmail, Microsoft, Yahoo and iCloud, plus other ISPs and the corporate gateways that sit in front of most B2B mailboxes. It also covers how to tell them apart from the temporary failures and policy blocks that share the same 4xx or 5xx label. If your bounces carry 5.7.x codes, the provider is usually refusing your mail, not the address. That's a sender problem, covered in Hard Bounces vs. Spam Complaints (and Block Bounces). A few providers are exceptions, and they're listed below. - **Suppress based on the enhanced status code and the response text, not the 550.** The same 550 can mean a dead mailbox or a policy block. - **Most address bounces happen at the RCPT TO step, before your message is sent.** A verifier checks the same step, so it can find these addresses before you send. - **A full mailbox or an oversized message is not a reason to suppress.** Neither says the address is dead. - **Provider wording differs.** Not every provider uses 550 or 5.1.1 for a missing mailbox, and a few use 5.7.x. Read the full response text. ## Where address bounces come from: the RCPT TO step ![](https://www.millionverifier.com/content/images/2026/10/Section-1---RCPT-TO-Step-selection.png) An invalid address is rejected before your message is sent. Every delivery attempt is a short conversation between your sending server and the receiving server, and the receiving server answers each step with a code: 1. **Connect and EHLO.** Your server connects and introduces itself. The receiving server replies 220, then 250\. Some IP-reputation and blocklist rejections already happen here. 2. **MAIL FROM.** Your server names the sender (the return-path). This is usually accepted with 250. 3. **RCPT TO.** Your server names the recipient. The receiving server checks whether that mailbox exists. A dead address gets a 5xx here, typically 550 5.1.1\. A live one gets 250. 4. **DATA.** Only after a recipient is accepted does your server send the headers and body. 5. **End of message.** The receiving server checks the message itself: authentication, content and your reputation. Authentication-based blocks (5.7.x) come here, because DKIM needs the body to check the signature. That order is why verification works. A verifier opens the same conversation, asks the RCPT TO question, records the answer and disconnects before DATA. No email is sent, and the recipient never sees anything. It's also why verification can't predict policy blocks. Those depend on your message and your sending reputation, which a verifier never presents. Not every server gives its answer at RCPT TO. Catch-all domains accept every recipient. Yahoo's own sample bounce shows its "user doesn't have a yahoo.com account" rejection arriving after the message was sent (Yahoo SMTP error codes). Other servers accept everything and send a separate bounce email later. These are the addresses a verifier may return as unknown or risky instead of good or bad. ## How to read a bounce: three parts ![](https://www.millionverifier.com/content/images/2026/10/Section-2---Reading-a-Bounce-selection.png) Every bounce response has three parts, and the middle one decides what you do with the address. Here's a typical Gmail response, with the trailing help link and server ID cut: `550 5.1.1 The email account that you tried to reach does not exist. Please double-check the recipient's email address for typos or unnecessary spaces.` - **550 is the basic reply code (RFC 5321).** The first digit says whether the failure is temporary (4) or permanent (5). It tells you the attempt failed, not why. - **5.1.1 is the enhanced status code (RFC 3463).** Its middle digit names the category: 0 is other or undefined, 1 is addressing, 2 is the mailbox, 3 is the mail system, 4 is network and routing, 5 is the delivery protocol, 6 is message content, and 7 is security or policy. - **The text is the provider's explanation.** Wording varies by provider, and it sometimes changes the meaning of the code. Gmail shows why the text matters. It uses 550 5.2.1 both for an inactive account and for a mailbox that is receiving mail too fast to accept more (Gmail SMTP errors and codes). The first is a dead address. The second is a busy one. Providers don't always pick the category you'd expect, either. Outlook.com reports a missing mailbox with 5.5.0, a protocol-class code, and Microsoft 365 sometimes uses 5.4.1 or 5.7.x. Match on the text, not just the digits. The basic codes you'll see on address bounces are 550 (mailbox unavailable), 551 (user not local), 552 (storage exceeded), 553 (mailbox name not allowed) and 554 (transaction failed). None of them alone tells you whether to suppress. A 550 can be a dead mailbox or a policy block, and some providers report a missing mailbox with 554. ## Hard bounce codes at Gmail, Microsoft, Yahoo and iCloud Each major provider words a dead address differently, and two of the four usually report a missing mailbox with something other than 5.1.1\. Match on the response text as well as the code. | Provider | Response (shortened) | What it means | What to do | | ------------------------------------ | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------- | -------------------------------------------------------------------------------------- | | Gmail | 550 5.1.1 The email account that you tried to reach does not exist. | Mailbox doesn't exist | Suppress | | Gmail | 550 5.2.1 The email account that you tried to reach is inactive. | Account disabled (older bounces say "disabled") | gmail.com: suppress. Company domain on Google Workspace: pause, suppress if it repeats | | Gmail | 550 5.2.1 The user you are trying to contact is receiving email at a rate that prevents additional messages… | Mailbox is flooded, not dead | Retry later; don't suppress | | Gmail | 552 5.2.2 The recipient's inbox is out of storage space and inactive. | Full and abandoned | Suppress | | Outlook.com, Hotmail, Live | 550 5.5.0 Requested action not taken: mailbox unavailable | Address not found | Suppress | | Microsoft 365 | 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup | Recipient doesn't exist | Suppress | | Microsoft 365 | 550 5.4.1 Recipient address rejected: Access denied | Recipient doesn't exist in the company's directory | Suppress | | Microsoft 365 | 550 5.7.504 Recipient address rejected: Access denied, or 5.7.505 Access denied, banned recipient | Recipient isn't valid | Suppress | | Yahoo, AOL | 554 delivery error: dd This user doesn't have a yahoo.com account | Account doesn't exist | Suppress | | iCloud (icloud.com, me.com, mac.com) | 550 5.1.1
: user does not exist | Mailbox doesn't exist | Suppress | | iCloud | 550 5.1.1
: inactive email address | User has deactivated this address | Pause; suppress if it repeats | Sources: [Gmail SMTP errors and codes](https://knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes?ref=millionverifier.com), [Exchange Online NDR reference](https://learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/ndr/non-delivery-reports-in-exchange-online?ref=millionverifier.com), [Yahoo SMTP error codes](https://senders.yahooinc.com/smtp-error-codes/?ref=millionverifier.com), [Postmastery iCloud page](https://www.postmastery.com/icloud-postmastery-page/?ref=millionverifier.com). Five exceptions are worth knowing: - **Some providers use 5.7.x for a dead address.** Microsoft's 5.7.504 and 5.7.505 both mean the recipient isn't valid, even though 5.7.x normally signals a sender problem. Yandex and Proofpoint do the same; see the next section. - **Microsoft uses 5.4.1 for two things.** "Recipient address rejected: Access denied" means the recipient doesn't exist. "Relay Access Denied" means the receiving server doesn't accept mail for that domain at all, usually a server or DNS misconfiguration. That one says nothing about the mailbox, so check the domain's MX record instead of suppressing. - **Microsoft's 5.1.10 has a different standard meaning.** RFC 7505 assigns 5.1.10 to a domain that publishes a "null MX", meaning it accepts no mail at all. Either way, the address can't receive mail. - **Gmail's 5.2.1 "inactive" can come back on company domains.** A Google Workspace admin can suspend an account and restore it later, for example during leave or an offboarding review. On a consumer gmail.com address, treat it as dead. On a company domain, pause the address and suppress it if the bounce repeats. - **iCloud uses 5.1.1 for two things.** "User does not exist" is permanent. "Inactive email address" is a user-paused address that can come back. If 5.1.1 bounces suddenly spike across icloud.com, me.com and mac.com together, check for an Apple-side incident before you suppress in bulk. You won't usually see a domain-not-found bounce (5.1.2) from these providers. When a domain doesn't exist, your own ESP's server generates the bounce after its DNS lookup fails. Gmail's 553 5.1.2 "We weren't able to find the recipient domain" is the version you see when sending through Gmail or Google Workspace. The decision table below covers both. ## Other providers and corporate gateways Outside the big four, wording varies even more, and several providers use unexpected codes for a dead address. B2B lists add another layer: many company domains sit behind a security gateway that answers before the real mail server does. **Other mailbox providers** | Provider | Response (shortened) | What it means | What to do | | ------------------------------------------------------ | ---------------------------------------------------------------------- | --------------------------------------------- | ---------------------- | | Comcast | 550 5.1.1 Not our Customer | Address doesn't exist | Suppress | | Comcast | 550 5.1.1
recipient mailbox unallocated | Mailbox doesn't exist | Suppress | | AT&T (att.net, sbcglobal.net and other legacy domains) | 550 5.2.1
... Addressee unknown | Address doesn't exist, despite the 5.2.x code | Suppress | | Zoho | 550 5.1.1
User unknown | Mailbox doesn't exist | Suppress | | Yandex | 550 5.7.1 No such user! | User doesn't exist, despite the 5.7.x code | Suppress | | Mail.ru | 550 Message was not accepted -- invalid mailbox. … account is disabled | Account disabled | Suppress | | GMX, Web.de | 550 Requested action not taken: mailbox unavailable | Doesn't exist, or disabled for inactivity | Suppress if it repeats | | Orange (orange.fr) | 550 5.1.1 … Invalid recipient. OFR\_416 | Address doesn't exist | Suppress | | Free (free.fr) | 550 5.2.1 This mailbox has been blocked due to inactivity | Blocked for inactivity | Suppress | GMX and Web.de return a bare 550 with no enhanced code for missing mailboxes, full mailboxes and policy blocks alike. Only the text tells them apart. **Corporate email gateways** | Gateway | Response (shortened) | What it means | What to do | | ----------------------------- | ----------------------------------------------------------------------------------------- | ---------------------------------------------- | ------------------------------------------- | | Proofpoint | 550 5.1.1
: Recipient address rejected: User unknown | User doesn't exist | Suppress | | Proofpoint | 550 5.7.1
: Recipient address rejected: User email address is marked as invalid. | Address marked invalid, despite the 5.7.x code | Suppress | | Proofpoint | 550 5.7.1 Relay access denied | Gateway doesn't accept mail for that domain | Check the domain's MX; suppress if it stays | | Barracuda | 550 cuda\_nsu 5.1.1
... User unknown, or 550 No such user | User doesn't exist | Suppress | | Broadcom Email Security.cloud | 550 Invalid recipient
(#5.1.1) | Recipient doesn't exist | Suppress | | Mimecast | 550 Envelope blocked - User Entry, or 550 Administrative prohibition - envelope blocked | The company's admin blocked your mail | Don't suppress. Ask to be allowlisted | A gateway sits in front of the real mail server and sometimes passes on its answer. Proofpoint, for example, can quote the downstream server's "user unknown" inside its own bounce. Read the innermost response. Source: [Bento SMTP 550 field manual](https://bentonow.com/smtp/550?ref=millionverifier.com), adapted from the SMTP Field Manual by ActiveCampaign and Postmark. ## The in-between cases ![](https://www.millionverifier.com/content/images/2026/10/Section-4---In-Between-Cases-selection.png) Five kinds of bounce look serious but don't prove the address is dead. Suppressing them throws away people who can still receive your mail. - **Full mailbox.** Gmail returns 452 4.2.2 when an inbox is out of storage, and iCloud says "user is overquota". Both are temporary. Gmail's permanent version, 552 5.2.2 … out of storage space and inactive, is different: the account is full and abandoned, so suppress it. A common rule for the temporary version is to suppress after the same address comes back full on three consecutive sends. - **Oversized message.** Gmail returns 552 5.3.4 when a message exceeds its size or header limits. It's permanent for that message, but the address is fine. Shrink the message or host the attachment, then resend. - **Flooded mailbox.** Gmail's 450 4.2.1 and its rate-limit 550 5.2.1 mean the mailbox is receiving too much mail right now. Microsoft 365 uses 5.2.121 and 5.2.122 when a recipient's hourly receiving limit is hit. These are 5xx at Microsoft, but the address is live. Send less often to that recipient. - **Expired deferrals.** A 4.4.7 Message expired bounce means a server kept retrying after 4xx deferrals and gave up. Many ESPs log it as a hard bounce. Look at the deferrals that came before it: 4.7.x deferrals mean the provider was throttling you, which is a sender problem. - **Catch-all domains.** A catch-all server accepts every address at RCPT TO, so a dead address may never bounce at all, or may bounce later as a separate email. Treat these addresses as uncertain: send to them in small batches and watch the results. Sources: [Gmail SMTP errors and codes](https://knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes?ref=millionverifier.com), [Exchange Online NDR reference](https://learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/ndr/non-delivery-reports-in-exchange-online?ref=millionverifier.com), [Postmastery iCloud page](https://www.postmastery.com/icloud-postmastery-page/?ref=millionverifier.com). ## Suppress, retry or investigate: a decision table ![](https://www.millionverifier.com/content/images/2026/10/Section-3---Decision-Table-selection.png) Suppress 5.1.x addresses and disabled mailboxes, retry 4.x.x, fix the message for 5.3.x, and fix your sending for most 5.7.x. This table covers any provider, including the ones not listed above. Always confirm with the response text. | Enhanced code | Standard meaning | What it says about the address | Action | | --------------------- | ------------------------------------------------------ | ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | 5.1.1 | Bad destination mailbox address | Mailbox doesn't exist | Suppress. Exception: iCloud's "inactive email address" | | 5.1.2 | Bad destination system address | Domain doesn't exist or can't be found | Fix obvious typos (gmial.com), otherwise suppress. Usually generated by your own ESP's server | | 5.1.3 | Bad destination mailbox address syntax | Address is malformed | Fix the record, or suppress if it can't be fixed | | 5.1.6 | Mailbox has moved, no forwarding address | Person has left that address | Suppress and look for a new contact | | 5.1.10 | Recipient has null MX (Microsoft: recipient not found) | Can't receive mail | Suppress | | 5.2.1 | Mailbox disabled | Account suspended or inactive | Suppress, unless the text says the mailbox is rate-limited. On a Google Workspace company domain, pause and suppress if it repeats | | 4.2.2 or 5.2.2 | Mailbox full | Address is valid | Retry; suppress after repeated sends. Gmail's "full and inactive": suppress | | 5.3.4 | Message too big | Nothing; the message is the problem | Fix the message, keep the address | | 5.4.1 | No answer from host (Microsoft: see text) | Depends on the text | "Recipient address rejected": suppress. "Relay Access Denied": check the domain's MX | | 5.4.4 | Unable to route | Domain has no working mail server | Check the domain; suppress if it has no MX record | | 4.4.7 | Delivery time expired | Unknown; retries ran out | Read the earlier deferral codes before deciding | | 5.5.0 | Other protocol status (Outlook.com: address not found) | Depends on the text | "Mailbox unavailable" from Outlook.com: suppress | | 4.x.x (other) | Temporary failure | Nothing yet | Let your ESP retry | | 5.7.x | Security or policy | Usually nothing; the provider refused you | Don't suppress. Fix your sending. Exceptions: Microsoft 5.7.504 and 5.7.505, Yandex "No such user!", Proofpoint "marked as invalid" | | 550, no enhanced code | Mailbox unavailable | Depends on the text | Read it. "Mailbox unavailable" or "invalid mailbox": suppress if it repeats. "Blocked" or "policy": fix your sending | | 554, no enhanced code | Transaction failed | Depends on the text | Read it. Yahoo's "dd This user doesn't have…": suppress | For the 5.7.x codes and how to fix them, see Hard Bounces vs. Spam Complaints (and Block Bounces). Standard meanings follow [RFC 3463](https://www.iana.org/assignments/smtp-enhanced-status-codes/smtp-enhanced-status-codes.xhtml?ref=millionverifier.com) and RFC 7505. ## Checking a single bounced address ![](https://www.millionverifier.com/content/images/2026/10/Section-5---Checking-a-Bounced-Address-selection.png) When one important address bounces, such as a key account or an active customer, check it before you suppress it. It takes two minutes: 1. Copy the full response from your ESP's bounce log, not just its "hard bounce" label. 2. Match it to the tables above. A 5.7.x code usually means the address is fine and your sending needs attention, unless the text says the user doesn't exist. 3. Look for typos. Check for a misspelled domain (gmial.com, outlok.com), a stray space or a trailing period. 4. Run the address through MillionVerifier's free Email Checker. It checks the address with the receiving mail server without sending a message. 5. Compare the two answers: - **The checker says bad and the bounce was 5.1.x or 5.2.1:** the address is dead or disabled. Update the CRM record and find a new contact. - **The checker says good but the bounce was 5.1.1:** the address may have been reactivated, or the bounce came from a provider-side incident. Resend once and watch it. - **The checker says good but the bounce was 5.2.1 on a company domain:** the admin may have restored the account. Resend once and watch it. - **The checker says good and the bounce was 5.7.x:** the provider refused your mail. Fix your sending and leave the address alone. - **The checker returns catch-all or unknown:** the server won't confirm either way. Confirm the address with the person through another channel. ## Prevent invalid-address bounces before you send Most addresses that would return 5.1.1 or 5.2.1 can be found before you send, because a verifier asks the receiving server the same question your send would. It matters beyond the bounce itself: Yahoo, for example, treats a server that sends to many unknown recipients as a possible open relay and stops accepting its mail. Verify any list you haven't mailed recently, anything imported from an event, partner, CRM migration or lead source, and every cold outbound list. Do it as close to send time as you can, since mailboxes keep getting disabled. 1. Export the segment from your ESP or CRM, or connect it through one of the 40+ integrations. 2. Run it through the Bulk Email Verifier. 3. Send to Good results. 4. Send to Risky results (catch-all and unknown) separately, in small batches that you watch closely. 5. Remove Bad results and add them to your ESP's suppression list, so they can't be re-imported. 6. Keep new signups clean with the real-time verification API, and re-verify existing lists before each large send. Catch typo domains at signup, not after the bounce. Many common misspellings of popular domains are registered by third parties and set up to accept mail, so a message to a typo like gmial.com may never bounce at all. It just goes to someone else. A "did you mean gmail.com?" prompt on your signup form catches most of these, and real-time verification flags domains that accept every address as risky rather than good. Verification finds dead addresses. It can't predict policy blocks, full mailboxes or oversized messages, because those depend on your message, your reputation or the recipient's storage on the day you send. That's why the bounce log still needs reading after every send. ## Frequently asked questions #### ****What does 550 5.1.1 mean?** The receiving server says the mailbox doesn't exist. It's a permanent failure about the address itself, so suppress it. The one common exception is iCloud's "inactive email address", which the user can reactivate. #### ****Is every 550 a hard bounce?** No. A 550 can mean a dead mailbox or a policy block. Read the enhanced code: 5.1.x means the address is dead, and 5.7.x usually means the provider refused your mail. A few providers, including Microsoft, Yandex and Proofpoint, also use 5.7.x for an address that doesn't exist, so read the text too. #### ****Should I suppress an address after one hard bounce?** Yes, if the response clearly says the mailbox doesn't exist: Gmail and iCloud's "user does not exist", Microsoft's 5.5.0, 5.1.10, or 5.4.1 with "Recipient address rejected", and Yahoo's "dd" bounce. Yahoo explicitly tells senders to remove those addresses. For anything else, read the response text first. #### ****Is 554 a hard bounce?** It's a permanent failure, but not always an address problem. Yahoo uses 554 for accounts that don't exist, while other servers use it for spam or policy rejections. The response text tells you which. #### ****Why did a verified address hard bounce?** Usually for one of four reasons. The mailbox was deleted between verification and send. The domain is catch-all, so the server never confirmed the mailbox. The provider only checks recipients after the message is sent, as Yahoo does. Or the bounce was really a policy block with a 5.7.x code. ## Find dead addresses before your ESP does Most 5.1.1 bounces in your log are addresses you could have removed before sending. Run your next list through MillionVerifier, and the bounces that remain will point to problems you can fix, not data you should have cleaned. [Create your free account to get 100 free credits, no credit card needed.](https://app.millionverifier.com/register?ref=millionverifier.com) --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. [99%+ Accuracy Rate](https://www.millionverifier.com/why-millionverifier/accuracy-rate) ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. [Best Email Verification Prices](https://www.millionverifier.com/why-millionverifier/best-email-verification-prices) ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. [Excellent Verification Service](https://www.millionverifier.com/why-millionverifier/excellent-email-verification-service) ### Hard Bounces vs. Spam Complaints: How to Survive the Gmail, Yahoo & Outlook Sender Rules URL: https://www.millionverifier.com/blog/hard-bounces-vs-spam-complaints-how-to-survive-the-gmail-yahoo-outlook-sender-rules/ Last updated: 2026-10-08T11:30:43.000Z Most deliverability problems appear in bounce logs or spam complaint rates. Teams often confuse them. Since Gmail started rejecting non-compliant mail in November 2025, there's a third type: the block bounce. It looks like a hard bounce in your ESP but says nothing about whether the address exists. Here's what Gmail, Yahoo and Outlook require, how these failures differ, and which fix applies. - Gmail's target spam rate is below 0.1%. 0.3% is the line you must never reach, not the goal. - Crossing 0.3% isn't a permanent blacklist. The damage is real but recoverable. - Three failures, three causes: hard bounces mean the address doesn't exist; block bounces mean the provider refuses your mail; spam complaints follow successful delivery. - Email verification fixes only the first. Block bounces need authentication and reputation work. Complaints need better targeting and easier unsubscribes. ## The Sender Rules in 2026: What Gmail, Yahoo and Outlook Actually Demand ![](https://www.millionverifier.com/content/images/2026/10/Provider-Rules-Image-selection.png) All three providers now require bulk senders to authenticate their mail, make unsubscribing easy, and keep complaints low. Bulk senders are those sending roughly 5,000+ messages a day to the provider's users. The recent change is enforcement. Failures now come back as rejections, rather than just quietly sending your mail to spam. | Requirement | Gmail | Yahoo | Outlook.com | | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | | Who counts as a bulk sender | About 5,000+ messages a day to personal Gmail accounts, counted per primary domain. Once classified, the status is permanent. | Yahoo publishes no exact number. Plan for the same line as Gmail. | 5,000+ messages a day to Outlook.com, Hotmail.com and Live.com addresses | | Authentication | SPF and DKIM, plus DMARC at p=none or stricter. The From: domain must align with SPF or DKIM. | SPF and DKIM, plus a DMARC policy of at least p=none that passes. Relaxed alignment is fine. | SPF, DKIM and DMARC (at least p=none) | | Unsubscribe | One-click List-Unsubscribe headers (RFC 8058) on marketing mail. Honor requests within 48 hours. | One-click List-Unsubscribe header plus a clearly visible unsubscribe link in the body. Honor within 2 days. | Functional unsubscribe links recommended | | Spam complaint limit | Keep it below 0.1%. Never reach 0.3%. | Keep it below 0.3%, measured against inbox-delivered mail | No published number | | What non-compliance looks like | Temporary (4.7.x) or permanent (5.7.x) rejections, or spam-folder placement. Above 0.3%, no mitigation. | Negative delivery impact, enforced gradually | 550 5.7.515 rejections since May 5, 2025 | Sources: Gmail sender guidelines FAQ, Yahoo Sender Requirements, Microsoft's high-volume sender announcement. ### What actually happens above 0.3% ![](https://www.millionverifier.com/content/images/2026/10/Spam-Rate-Image-selection.png) Crossing 0.3% does not permanently blacklist your domain. Google describes the impact as graduated: a spam rate above 0.1% already hurts inbox placement, and 0.3% or higher hurts more. Above 0.3%, you also lose access to mitigation, Google's process for fixing delivery problems on request. You become eligible again once your spam rate stays below 0.3% for 7 consecutive days. Until then, mail lands in spam and engagement drops. Watch how the rate is measured. Yahoo calculates your complaint rate against mail delivered to the inbox, not total sends. If some of your mail already lands in spam, your ESP's complaint rate will look lower than the number Yahoo enforces. Yahoo Sender Hub's Insights dashboard shows the inbox-based rate Yahoo actually uses. It doesn't require CFL enrollment. ### What changed in November 2025 Gmail announced a ramp-up in enforcement from November 2025, with temporary and permanent rejections for non-compliant traffic. Microsoft has rejected non-compliant high-volume mail with 550 5.7.515 since May 2025. That changes how you read your bounce report: compliance failures now appear alongside invalid addresses. Both arrive as bounces, but they need different fixes. For the full setup walkthrough (SPF, DKIM, DMARC, reverse DNS and TLS), see The Ultimate Guide to Email Deliverability & Sender Reputation. ## Hard Bounces vs. Block Bounces vs. Spam Complaints: The Technical Difference ![](https://www.millionverifier.com/content/images/2026/10/Three-Failures-Image-selection--1-.png) A hard bounce is an addressing failure. A block bounce is a policy decision. A spam complaint is a recipient's verdict after delivery. They tell the mailbox provider different things, so each needs its own fix. | | Hard bounce (invalid address) | Block bounce (policy rejection) | Spam complaint | | ---------------------------- | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | What it means | The mailbox or domain doesn't exist | The mailbox exists, but the provider refuses your mail | The mail arrived, and the recipient reported it | | Who decides | The receiving server, automatically | The provider's filters, based on your authentication and reputation | A person clicking "Report spam" | | When it happens | During the SMTP session, before delivery | During the SMTP session, before delivery | After successful delivery, sometimes days later | | Typical codes | Gmail 550 5.1.1 (account doesn't exist), 553 5.1.2 (domain not found) | Gmail 550 5.7.26 (unauthenticated), 550 5.7.1 (likely unsolicited or low reputation). Outlook 550 5.7.515. | No SMTP code. Shows up as a spam rate in Postmaster Tools or in a feedback loop. | | Scope | One address at a time | Often every message to that provider until fixed | Raises the spam rate that governs all your mail to that provider | | What it signals | Your list has bad data, often old, bought or scraped | Your setup or reputation fails the provider's rules | Recipients don't want this mail | | Fixed by email verification? | Yes | No | No | | The real fix | Verify before sending and suppress the address | Fix SPF, DKIM, DMARC, reverse DNS or TLS. For reputation blocks, cut complaints and volume. | Better targeting, visible unsubscribes, sunset policies | Both bounce types happen during the SMTP session, but at different steps. An invalid address is rejected at the RCPT TO step, before any message content is sent. That's why a verifier can check whether an address exists without sending an email (here's how that works). Authentication blocks usually come later, after the message body is sent. DKIM needs the body to check the signature. ### Read the middle number, not the 550 ![](https://www.millionverifier.com/content/images/2026/10/Status-Code-Image-selection.png) "550 means the address doesn't exist" is the most common misreading of a bounce log. Gmail returns 550 for invalid addresses, failed authentication and spam-related blocks. To tell them apart, read the enhanced status code that follows it. In a code like 5.1.1, the first digit tells you whether the failure is permanent (5) or temporary (4). The second identifies the category, as defined in RFC 3463: - x.1.x – addressing. The address or domain is invalid. This is a list problem. - x.2.x – mailbox. The mailbox is disabled or full. Gmail's 5.2.1, for example, means the account is inactive. - x.7.x – security or policy. The provider rejected you, not the address. This is a sender problem. A 4.7.x is a deferral: Gmail is rate-limiting you for the same policy reasons. Treat it as an early warning that a permanent 5.7.x block may follow. Spam complaints never appear in the bounce log. For Gmail, you only see an aggregate spam rate in Postmaster Tools. To see individual complaints, you need a feedback loop: Yahoo's Complaint Feedback Loop (CFL) or Microsoft's Junk Mail Reporting Program (JMRP). JMRP requires a dedicated sending IP, so shared-IP senders depend on their ESP for that data. ## Block Bounces: The 5xx Errors Email Verification Can't Fix Since Gmail's November 2025 enforcement ramp, a sudden spike of 5xx bounces at one provider is more likely a policy block than a wave of dead addresses. Many reports don't distinguish between the two. Many ESPs label every permanent (5xx) failure a "hard bounce," and some suppress those addresses automatically. Others list "blocks" separately. Before acting on the number, check how your platform labels these failures. ### The block codes to know | Code | Provider | What it means | Where the fix lives | | ----------- | ----------- | ------------------------------------------------------------- | ------------------------------------------ | | 550 5.7.26 | Gmail | Unauthenticated, or failed the sending domain's DMARC policy | SPF and DKIM setup, From: alignment | | 550 5.7.27 | Gmail | SPF didn't pass (bulk senders) | SPF record and ESP includes | | 550 5.7.30 | Gmail | DKIM didn't pass (bulk senders) | DKIM signing in each sending platform | | 550 5.7.40 | Gmail | No DMARC record, or no policy in it | Publish DMARC at p=none or stricter | | 5.7.32 | Gmail | From: domain isn't aligned with the SPF or DKIM domain | DMARC alignment: sign with your own domain | | 550 5.7.25 | Gmail | Sending IP has no valid PTR (reverse DNS) record | Your ESP or IP owner | | 550 5.7.29 | Gmail | Message not sent over TLS | Your ESP or mail server | | 550 5.7.1 | Gmail | Likely unsolicited, or very low domain or IP reputation | Complaints, engagement and volume | | 550 5.7.28 | Gmail | Unusual rate of unsolicited mail from your IP | Complaints, engagement and volume | | 550 5.7.515 | Outlook.com | Sending domain doesn't meet the required authentication level | SPF, DKIM and DMARC | Source: Gmail SMTP errors and codes. Gmail's error text names the exact requirement that failed, so always read the full response, not just the code. Most of these are configuration problems. Fix the DNS or ESP setting and the block lifts. The two exceptions are 5.7.1 and 5.7.28\. These reputation blocks only lift once complaints and unwanted volume come down. ### Why misdiagnosis is expensive A wrong diagnosis costs you either way: - **Treating a block as a list problem.** Your ESP suppresses thousands of valid subscribers in one send. You re-clean a list that wasn't the problem, then resend into the same rejection. - **Treating a list problem as a block.** You spend days on DNS records while invalid addresses keep bouncing. Yahoo's sender recommendations specifically tell senders to monitor hard bounces and remove invalid recipients promptly. ### The tell An address that accepted your mail last month and returns 5.7.x today hasn't stopped existing. Block bounces cluster around one provider on one day, affecting many addresses that previously delivered. Invalid-address bounces spread across many domains and track where the list came from. ## How to Triage Your Bounce Log After Every Send ![](https://www.millionverifier.com/content/images/2026/10/Triage-Image-selection.png) Ten minutes of triage after each send tells you whether you have a list problem, a sender problem, or both. Work through these steps in order: 1. **Export bounces with the full SMTP response.** Your ESP's "hard/soft" label isn't enough. You need the code and the provider's error text. 2. **Split by enhanced status code.** 5.1.x and 5.2.1 are address problems. 5.7.x are policy blocks. 4.x.x are deferrals. 3. **Group the 5.7.x bounces by receiving provider and by day.** One provider, one day, many addresses means a block. 4. **Read the error text.** Gmail's tells you exactly which requirement failed: SPF, DKIM, DMARC, reverse DNS, TLS or reputation. 5. **Fix the cause before resending.** Resolve authentication codes in DNS or ESP settings. For reputation codes (5.7.1, 5.7.28), pause low-engagement segments, reduce volume and check your spam rate in Postmaster Tools. 6. **Recover contacts your ESP suppressed by mistake.** If block-bounced addresses were auto-suppressed, export them and run them through a bulk email verifier. Once the block is fixed, valid addresses can return to your list. Reintroduce them gradually, most engaged first. Invalid ones stay suppressed. 7. **Suppress true hard bounces for good, then find their source.** A cluster of 5.1.1 bounces usually traces back to one import, one form or one lead source. Fix it there with verification before import or real-time verification at signup. Step 6 is where verification helps even with a block. It can't lift the block, but it separates "the provider refused me" from "the address is dead." That keeps a DNS mistake from costing you good subscribers. ## How to Eliminate Invalid-Address Hard Bounces Before Sending (The Infrastructure Fix) Email verification removes addresses that would return 5.1.1 before you send. Those bounces never reach your reputation. ### Why hard bounces still matter Gmail's rules focus on spam complaints and publish no bounce threshold. That doesn't make bounces harmless: - **Providers ask for it directly.** Yahoo's sender recommendations tell senders to monitor hard and soft bounces and remove invalid recipients promptly. Microsoft's high-volume sender announcement recommends list hygiene and bounce management, advising senders to remove invalid addresses monthly or quarterly. - **Your ESP enforces its own limits.** Most sending platforms monitor bounce rates and can pause or suspend accounts that exceed them. - **Bounces come with other risks.** Lists that bounce are usually old or poorly sourced. They also tend to carry recycled spam traps and people who no longer remember signing up, which feeds complaints. ### When to verify - Before mailing any list you haven't mailed recently - Before importing a list from an event, a partner, a CRM migration or a lead-gen source - Before every cold outbound campaign - After a block event, to recover wrongly suppressed contacts - Continuously, at the point of signup ### The verification workflow 1. Export the segment from your ESP or CRM, or connect it through one of the 40+ integrations. 2. Run it through the MillionVerifier Bulk Email Verifier. 3. Send to Good results. 4. Handle Risky results (catch-all and unknown) separately, in small batches that you monitor closely. See How to Handle Catch-All and Risky Emails. 5. Remove Bad results and add them to your ESP's suppression list so they can't be re-imported. 6. Keep new data clean with the real-time verification API on signup forms, and existing lists clean with EverClean automated verification. For the full method, see The Ultimate Guide to Email Verification & List Cleaning. ### Set a realistic target: near-zero, not zero No verifier can promise a 0% hard bounce rate. Catch-all domains accept every address during the SMTP check, so the mailbox can't be confirmed in advance. Mailboxes also get deactivated between verification and send. Verify as close to send time as you can. MillionVerifier backs its results with a money-back guarantee: if you send to addresses it returned as OK within 7 days of verification and your hard bounce rate exceeds 4%, your last payment is refunded. Terms apply, including a detailed bounce report from your ESP. ### What verification won't fix Verification confirms that an address exists. It doesn't fix block bounces or stop a recipient from clicking "Report spam." It also can't detect pristine spam traps, which are real, valid addresses. Reducing complaints matters just as much as cleaning your list. ## How to Lower User Spam Complaints (The Human Fix) No verifier can stop a person from clicking "Report spam." Work through these five workflows, in this order to lower complaints at the source: 1. **Find out where complaints come from.** Gmail shows only an aggregate spam rate in Postmaster Tools. Split your sends by stream (newsletter, promotions, onboarding) to see which one drives it.Enroll every DKIM domain in Yahoo's Complaint Feedback Loop, and register any dedicated sending IPs in Microsoft's JMRP. Both send back individual complaints, so you can suppress complainers automatically. On shared IPs, your ESP has to process Microsoft's reports for you. Microsoft moved SNDS and JMRP to a new portal in June 2026, and JMRP reports now carry headers only, not the original message. If you identified complainers from the message body or To: address, switch to a VERP return-path, Message-ID or a custom header. Then check the list source. Imports, co-registration and unconfirmed signups are the usual culprits. 2. **Send relevant mail to segmented audiences.** Stop sending generic copy to your whole list. Segment by interest, behavior or purchase history.Honor the frequency people signed up for. Yahoo explicitly warns against turning a weekly list into a daily one. Set expectations at signup and confirm opt-ins. 3. **Make unsubscribing easier than reporting spam.** One-click List-Unsubscribe headers are required, but don't rely on them alone. Gmail only shows its native unsubscribe button for messages that pass automated eligibility checks. Yahoo requires a clearly visible link in the body.If recipients can't find your link, "Report spam" becomes the easiest exit—and costs you far more than an unsubscribe. Never require a login, and process requests within 48 hours. 4. **Sunset unengaged subscribers.** Define engagement by clicks, replies, purchases or logins, not opens alone. Apple Mail Privacy Protection loads images automatically, which inflates open rates.A common rule for weekly senders: no click in 90 days triggers one re-engagement email, and non-responders are suppressed. Monthly senders can use a longer window. 5. **Keep sending volume steady.** Sudden spikes look like a compromised account or a bought list. Ramp up new domains and large campaigns gradually, starting with your most engaged contacts. Our guide to sender reputation covers reputation repair in more depth if your spam rate is already above 0.1%. ## The Gmail, Yahoo & Outlook Deliverability Compliance Checklist ![](https://www.millionverifier.com/content/images/2026/10/Compliance-Checklist-Image-selection.png) Run this audit before launching any new campaign. Every item maps to a requirement or failure type covered above. ### Authentication and infrastructure - SPF and DKIM both pass for every platform that sends as your domain, and the From: domain aligns with at least one of them. - DMARC is published at p=none at minimum, with a rua address receiving reports. Once the reports are clean, plan the move to quarantine or reject. - Sending IPs have valid forward and reverse DNS (PTR) records, and mail goes out over TLS. Your ESP usually handles both, but confirm it. ### Unsubscribe - One-click unsubscribe headers (List-Unsubscribe and List-Unsubscribe-Post, per RFC 8058) are active on all marketing mail, with an HTTPS URL. - A clearly visible unsubscribe link sits in the email body and requires no login. Requests are processed within 48 hours. ### List quality - The audience was run through bulk verification within 7 days of sending. Bad results are removed and Risky results are segmented. - The last send's bounce log was triaged: 5.1.x addresses suppressed, 5.7.x blocks investigated, and wrongly suppressed contacts re-verified. - A sunset policy based on clicks, not opens, is running. ### Monitoring - The Gmail spam rate in Postmaster Tools is below 0.1%, and the Compliance status dashboard shows every requirement passing. Don't look for domain or IP reputation there: Google retired those dashboards in Postmaster Tools v2. - Yahoo Sender Hub Insights is activated for each DKIM domain. It shows the inbox-based complaint rate Yahoo enforces and doesn't require CFL enrollment. - Every DKIM domain is enrolled in Yahoo's Complaint Feedback Loop, and complainers are suppressed automatically. - If you send from dedicated IPs, they're registered in Microsoft SNDS (IP reputation and complaint data) and JMRP (individual junk reports). On shared IPs, ask your ESP how it handles Outlook.com complaints. ## Frequently Asked Questions #### Is a hard bounce the same as being marked as spam? No. A hard bounce is a server rejection during delivery because the address doesn't exist. A spam complaint comes from a recipient after the email was delivered successfully. They have different causes and need different fixes. #### Does Gmail penalize hard bounces? Gmail publishes no hard bounce threshold, but bounces still count against you. Yahoo and Microsoft both ask senders to remove invalid addresses, and most ESPs enforce their own bounce limits. #### What happens if my spam rate goes above 0.3%? Your domain isn't permanently blacklisted. You lose eligibility for Gmail's delivery mitigation until your spam rate stays below 0.3% for 7 consecutive days. Inbox placement suffers in the meantime—and already starts to slip above 0.1%. #### Why is my ESP reporting hard bounces from addresses that worked last month? They're most likely block bounces. Check the full SMTP response: a 5.7.x code means the provider rejected your mail for policy or reputation reasons, not because the address stopped existing. #### Can email verification lower my spam complaint rate? Not directly. Verification removes invalid addresses and prevents hard bounces. Complaints come from real recipients, so reducing them takes the targeting, unsubscribe and sunset practices described above. ## Verify Before Your Next Send Hard bounces are the one failure type you can remove before a single email goes out. Run your next list through MillionVerifier. Then you can send knowing that most bounces left in your report point to fixable sender problems, not bad data. Create your free account to get 100 free credits, no credit card needed. [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) ### Why Outbound Fails Twice: What Soumya Surabhi Finds When She Audits It URL: https://www.millionverifier.com/blog/why-outbound-fails-twice-what-soumya-surabhi-finds-when-she-audits-it/ Last updated: 2026-09-29T12:05:34.000Z Most companies that come to GTM Walnut have already tried outbound twice. First they ran it in-house. Then they paid an agency. Neither worked. Soumya Surabhi, co-founder of GTM Walnut, audits those programs for a living. In a July 23, 2026 conversation with Zsófia Cséfai, General Manager of MillionVerifier, she explained what she usually finds. It is rarely the copy. It is three things that break before anyone writes a word: the sending infrastructure, the list, and a kind of personalization that stopped working once everyone started doing it. ## **Who is giving the advice** Soumya spent almost five years heading demand generation at Y Combinator- and Sequoia-backed startups. About a year and a half ago, she co-founded GTM Walnut with Prashant. The company builds AI-native revenue pipelines for B2B companies. Inbound, outbound and revenue operations usually run in separate silos. GTM Walnut puts them into one AI system. It has worked with more than 30 clients around the world. Her advice comes from volume. The system GTM Walnut built is designed to run 50,000 to 100,000 emails a day. At that scale, a small mistake does not stay small. It repeats tens of thousands of times. ## **Failure #1: The infrastructure was never built for cold email** ![](https://www.millionverifier.com/content/images/2026/09/image1-1.png) When Soumya audits a failed program, the first cracks are usually in the sending setup. Campaigns run from the company's primary domain. New mailboxes go live without being warmed up. Her rule is blunt: "Never ever run your campaigns from primary domains." **Her setup looks like this:** - Buy a secondary domain and create new email IDs on it. - Warm those mailboxes for 14 days before any campaign goes out. - Start at low volume from the new mailboxes, then scale. - Check domain reputation and blacklists once a month. The mistake teams discover too late is links. A website link or a Calendly link in a cold email feels harmless. Soumya's advice: "When you're doing a cold reach-out, please don't ever use links." Links push emails into spam and junk folders. That burns domain reputation, and reply rates drop with it. Inbox providers track all of these signals when they judge your domain. Infrastructure is the first thing she thinks about for every client campaign. Copy comes later. ## **Failure #2: The list went straight from the vendor into the sequence** The second finding is the list. "They would just buy data from a certain database provider and they would never verify the list," Soumya said. The step they skip, she added, is the one MillionVerifier does: run the list through verification before it goes into a sequence. The cost shows up twice. Reply rates and interest rates stay low, because many messages never reach a real person. And the invalid addresses damage the domain's reputation, which hurts every campaign after it. Verification is not a one-time setup task either. "It does not matter if you have verified the list two months back," she said. "The list might have gotten stale." Her cadence: verify whenever a campaign runs. If she reruns the same list a month later, she verifies it again. Some teams re-verify weekly. She prefers monthly. ![](https://www.millionverifier.com/content/images/2026/09/image4.png) At high volume, she named list verification as one of the two things that matter most. The other is automation. ## **Failure #3: Personalization that everyone else is also sending** Tools like Clay made intent signals easy to find. The result, Soumya says, is that everyone now personalizes the same way: "Congratulations on raising your Series A, let's have a chat." "When everybody is using that same kind of intent signal, that's not personalization anymore." She avoids the usual triggers entirely: funding news, new hires, "congratulations on the promotion," "congratulations on the new job." Her rule has two parts: 1. Find the one signal that is highly relevant for your niche. 2. Only if you can't find it, fall back to funding or new-hire signals. ![](https://www.millionverifier.com/content/images/2026/09/image2-1.png) Messaging also expires. "The messaging that has worked six months back might not work for you right now," she said. Her fix is to revise messaging every three months. ## **How she scales without sounding automated** Soumya doesn't treat automation and personalization as a trade-off. "They're not polar opposites of each other, but rather they're complementary," she said. "Automation is something that does the heavy lifting for you." The split is clear. Automation researches accounts, finds signals and enriches contacts. A human decides whether the signal the system picked is relevant, and whether the messaging angle fits this persona at this account. The numbers show why both are needed. One person researching and writing each email by hand can't get past about 50 emails a week. ![](https://www.millionverifier.com/content/images/2026/09/image5-1.png) Her model works differently: 1. AI agents draft emails for around 10,000 contacts. 2. A person reviews 10 to 20 of them. 3. If the messaging fits, the campaign gets the go-ahead. 4. The data flows into sequencers such as Instantly and EmailBison. The human review is what keeps volume from turning into spam. In her words, automation handles outbound at volume, but human judgment keeps the emails from being classified as spammy. ## **The full stack, stage by stage** During the interview, Soumya shared her screen and walked through the in-house system GTM Walnut runs for itself and its clients. Here is every stage and every tool she named. ![](https://www.millionverifier.com/content/images/2026/09/image6-1.png) The last two stages are where most outbound programs stop too early. Booking the meeting is not the finish line. The SDR walking into the call with context is. ## **The order matters** None of Soumya's fixes are exotic. What sets her approach apart is the order she does them in: 1. Secondary domain, 14-day warm-up, no links. 2. A verified list, re-verified before every run. 3. One signal that matters to this niche. 4. A small batch reviewed by a human. 5. Only then, volume. ![](https://www.millionverifier.com/content/images/2026/09/image3.png) The companies that come to her after two failed attempts usually did step five first. **Follow Soumya:** [LinkedIn](https://www.linkedin.com/in/soumya-surabhi-42638444/?ref=millionverifier.com) · [GTM Walnut](https://gtmwalnut.com/?ref=millionverifier.com) **Before your next campaign, verify your list with MillionVerifier** --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- ### How Lead Gen Agencies Protect Client Domains with Bulk Email Verification URL: https://www.millionverifier.com/blog/how-lead-gen-agencies-protect-client-domains-with-bulk-email-verification/ Last updated: 2026-09-29T14:38:05.000Z ![](https://www.millionverifier.com/content/images/video-thumbnails/e61dfd7146da121ce789f0dfdbc8708673402c50fc1ce178705d91c347200d3e-1280.webp) The call usually starts the same way: a client opens with "we need to talk," and by the second sentence you know your agency is the problem. Their domain is throttled at Gmail, parked in the Yahoo junk folder, or flagged on a blocklist, and the campaign you launched three days ago is the reason. Recovery from that point is slow, political, and expensive — pausing sends, auditing every list you touched, and rebuilding trust with a client who is now shopping for a new agency. The outcome in any single case depends on list source, spam-trap exposure, complaint rate, authentication setup, mailbox provider, and send volume — there is no universal number that predicts it. But the practical rule that prevents the call in the first place is simple: **verify every address before it enters a sending platform, and document the decision.** This guide gives lead-generation agency owners, account managers, and deliverability operators a practical system for reducing bounce and complaint risk while making pre-send hygiene visible to clients. ![](https://www.millionverifier.com/content/images/2026/09/Section---Agency-Risk-Factor-selection.png) ## The Agency Risk Factor: Why Burning a Client's Domain is a Firing Offense When a client says, "My agency ruined my email domain," they usually mean the agency allowed poor list quality, excessive volume, or weak targeting to damage inbox placement and sender reputation. Recovery can require pausing campaigns, reducing volume, investigating complaints, and rebuilding trust. It can also interrupt legitimate employee email if the client's core domain is involved. ### Burner domain versus core corporate domain A **burner (secondary) domain** is a separate sending identity used to contain campaign risk. It must still be registered, authenticated, warmed responsibly, and governed by client approval, legal requirements, and brand standards. It is not permission to send recklessly. A **core corporate domain** powers employee mail, support, invoices, notifications, and executive communication. Sending questionable data from it can create consequences far beyond one campaign. Domain separation is only one layer of defense; it does not replace verification, relevance, opt-out handling, authentication, conservative ramping, or monitoring. ![](https://www.millionverifier.com/content/images/2026/09/Section---4-Step-Onboarding-Workflow-selection.png) ## The 4-Step Client Onboarding Workflow for Cold Email Data Add this SOP to the client onboarding checklist. Do not load a lead file into Instantly, Smartlead, or another sending tool until all four steps are complete. ### Step 1: Isolate client-provided "legacy" lists Preserve the original file for audit, then create a read-only intake copy. Store the working copy in a client-specific location with controlled access. Never accept "already clean" as a verification result. Legacy lists may still contain stale addresses, role accounts, recycled spam traps, duplicates, prior bounces, or contacts with unclear permissions. Record the source, acquisition date, owner, intended purpose, collection method, lawful-basis or consent record, prior bounce/complaint/unsubscribe data, and file version or hash. Apply known unsubscribes and global suppressions before processing. If provenance or lawful-use documentation is missing, pause and escalate rather than treating uncertainty as approval. ### Step 2: Run deep SMTP bulk verification before sending Run the working list through **MillionVerifier as the required verification step** — which connects to 40+ tools — before importing leads into a sending platform. "Deep SMTP verification" means the check connects directly to the recipient's mail server over SMTP and reads the mailbox-level response, rather than stopping at syntax or DNS/MX lookups — that's what separates a real verification pass from a superficial format check. Keep the job ID, timestamp, file version, and exported results. Review syntax, DNS/MX availability, mailbox-level SMTP responses where available, disposable, or role-based, duplicates, suppressions, catch-all classifications, and unknown responses. One point worth stating plainly, once: verification is a risk signal, not proof of consent, interest, or inbox placement. It tells you whether an address is safe to attempt, not whether the recipient wants to hear from you or whether the message will land in the inbox. Re-run verification when a list ages materially, its source changes, or monitoring shows unusual bounce behavior. For agencies running this on a schedule rather than ad hoc, the MillionVerifier Bulk API lets you wire re-verification directly into your own onboarding or CRM workflow: upload a file programmatically, poll it for progress, and pull the finished report without anyone touching the dashboard. The Single API covers the other half of the problem — real-time validation at the point of capture, so a typo or disposable address never enters the client's list in the first place. Either way the credit rules are the same: you're charged for good and bad results, not for risky ones. ### Step 3: Segment by verification status Never upload one undifferentiated file: | Result code | Group | Default action | Operational note | | ----------- | ----- | ------------------------------- | -------------------------------------------------------- | | ok | Good | Eligible for controlled testing | Confirm suppression and relevance first. | | invalid | Bad | Suppress | Do not retry merely because volume is low. | | disposable | Bad | Suppress | Temporary/throwaway domains; no exceptions. | | catch\_all | Risky | Isolate | Separate conservative policy; see the catch-all section. | | unknown | Risky | Hold and recheck | Do not treat unknown as valid. | Free and role are returned as separate flags on any result, not as statuses of their own — filter on them independently. Apply role-based policy (info@, sales@, etc.) as manual review, and treat free-provider addresses as allow-with-judgment, segmenting them out if the campaign is strictly B2B. Remove duplicates and previously suppressed contacts as a separate step before finalizing the send-ready file, preserving the removal reason for auditability. MillionVerifier groups the five statuses above as Good, Risky and Bad in the export, so an account manager can act on the group without reading every code. Via the Bulk API, these segments can be downloaded as separate files directly — the download endpoint filters by status, so the send-ready file and the isolated catch-all file come out of the API already separated. Keep both the raw result and send-ready file. Define every status in a shared data dictionary so account managers apply labels consistently. ### Step 4: Establish sending thresholds Before launch, document the authentication requirements: SPF, DKIM, DMARC alignment, the tracking domain, and reverse DNS where applicable. These aren't arbitrary hygiene items — they're baseline requirements under [Google's bulk sender guidelines](https://support.google.com/a/answer/81126?ref=millionverifier.com) and [Yahoo's bulk sender requirements](https://senders.yahooinc.com/?ref=millionverifier.com), and they align with the anti-abuse practices [M3AAWG](https://www.m3aawg.org/?ref=millionverifier.com) publishes for senders operating at scale. Also record the ramp plan, per-mailbox and per-domain limits, monitoring cadence, stop conditions, and named owners. Pause sending when hard bounces, complaints, provider deferrals, authentication failures, blocklist alerts, or unusual engagement cross the agreed thresholds. Base those limits on provider behavior, account age, warm-up evidence, and client risk — not a universal number. **Copy-paste approval gate:** "The verified, segmented file is approved; suppressions are applied; authentication is checked; thresholds and stop conditions are documented; and the designated operator may pause sending immediately." ![](https://www.millionverifier.com/content/images/2026/09/Section---Verification-Economics-selection.png) ## Bulk Verification Economics: Protecting Agency Margins at Scale Verification is campaign infrastructure, not an optional line item. We built MillionVerifier around two commitments: some of the most competitive per-verification pricing in the category, and a 99%+ accuracy guarantee on results. That guarantee has teeth: if hard bounces exceed the agreed threshold after verification, you get your money back. For an agency, that's the difference between absorbing a bad-list incident and having recourse for it. Pricing is tiered and volume-based — 1,000,000 verifications run $449, with bulk discounts stacking at higher volumes — and credits never expire, full stop, so a quiet month never means losing what you already paid for. Because published rates and plan terms do change over time, confirm the current tier and overage terms on the pricing page before you lock a number into a client contract. When you're budgeting a retainer, the full cost of hygiene isn't just the per-credit price — it's verification credits + operator time + QA/reporting + recheck allowance. A 100,000-contact monthly list and a 1,000,000-contact monthly list scale very differently on that formula: the larger volume typically earns a materially better per-credit rate, but it also demands more account-management time for QA, exception review, and reporting. Agencies commonly build one verification cycle for an agreed volume into the retainer, then bill separately for extra imports or re-verification runs. [See current per-credit pricing](https://www.millionverifier.com/#pricing) to plug real numbers into that formula for your own client mix. Compare the resulting hygiene cost against the cost of a paused campaign, a remediation project, lost deliverability, and reputational damage — using your own incident data, not an industry average. ![](https://www.millionverifier.com/content/images/2026/09/Section---Catch-All-Handling-selection--1-.png) ## How MillionVerifier Handles Client Catch-All Emails A catch-all (or "accept-all") domain is configured to return a positive response for any mailbox name sent to it, whether or not that specific mailbox actually exists. During a deep SMTP check, MillionVerifier's verification engine detects this server-level behavior and classifies the result as Catch-All rather than valid — because the SMTP handshake alone cannot confirm that one particular address on that domain is real. That's a different failure mode than an Unknown result, which usually means the receiving server didn't respond in time or blocked the check outright. Here's the part that matters for your budget: **you are not charged for Catch-All or Unknown results.** Credits spent on those risky classifications are automatically returned once the check completes, for accounts in good standing — so you only pay for addresses that come back valid or invalid.MillionVerifier is the only verifier that doesn't charge for catch-all. That changes the economics of a legacy client list full of accept-all domains: running it through verification costs you nothing extra for the addresses the check can't fully resolve. MillionVerifier also goes further than a plain SMTP check on this exact problem. Our Catch-All Verifier resolves an estimated 30–40% of risky addresses that a standard check would otherwise leave classified as Catch-All or Unknown, cutting catch-all and business-unknown results by up to 70–80% — at no additional charge. That's the piece that actually earns its keep for an agency: fewer addresses stranded in the "can't tell" bucket, and fewer usable leads thrown away out of caution. What this classification enables operationally: segment every Catch-All result out of the primary verified send, and don't fold it into your "clean" numbers. For background on the broader cleaning workflow, see [The Ultimate Guide to Email Verification & List Cleaning](https://www.millionverifier.com/blog/the-ultimate-guide-to-email-verification-list-cleaning/). If the client wants to test Catch-All addresses rather than discard them outright, run a dedicated, conservative campaign with its own tracking and stop conditions, sent only from an approved secondary domain — never the core corporate domain. Monitor bounces, complaints, deferrals, and replies on that campaign separately from the main send, and pause at the first adverse signal. Secondary-domain use doesn't eliminate legal or provider risk, and it must never bypass opt-outs or client approval. ## Client Reporting: How to Prove the Value of Pre-Send Hygiene Explain the outcome in business terms, but keep the technical evidence behind it. Do not say the process "protected" a deliverability score unless you have a defined baseline, measurement method, and evidence linking the work to that result. ### Account-manager reporting script **Subject: Pre-send verification completed for \[Campaign/Client\]** We processed the \[source/version\] list of **\[total\] contacts** through our protocol on **\[date\]**. Before loading eligible records into \[tool\], we applied suppressions and separated results by status. **Results:** \[verified\] eligible; \[invalid\] suppressed; \[risky\] held or suppressed; \[catch-all\] isolated; \[unknown\] held for recheck; \[duplicates/suppressions\] removed. This process is designed to reduce avoidable bounces and protect sender reputation. We will begin at **\[threshold\]**, monitor **\[metrics\]**, and pause if **\[stop conditions\]** occur. Job reference: **\[ID\]**. Send-ready file: **\[filename/version\]**. An illustrative example — not a benchmark — might say: "We processed 10,000 contacts, suppressed 1,500 invalid addresses, isolated 50 risky records, and held 300 catch-all results." Replace every number with the actual export and retain the evidence. ## Frequently Asked Questions #### ****What is a catch-all email address?** It's an address on a domain configured so the mail server accepts (or appears to accept) mail sent to any username at that domain, even ones that don't correspond to a real mailbox. A successful server response for a catch-all address doesn't confirm that specific mailbox is monitored or safe to contact. #### ****How often should agencies re-verify a list?** Re-verify when the list ages materially (most agencies treat 30–90 days as a reasonable trigger depending on volume and source), when the source or acquisition method changes, or as soon as monitoring shows unusual bounce or complaint behavior — not on a fixed calendar regardless of signals. Teams that want this automated rather than manual can wire re-verification through the [MillionVerifier API](https://developer.millionverifier.com/?ref=millionverifier.com) instead of relying on someone to remember. #### ****What counts as a verification credit for a catch-all result?** Nothing extra. Catch-All and Unknown are risky classifications, and MillionVerifier automatically returns the credits spent verifying them once the check completes, for accounts in good standing — you're only charged for addresses that resolve to valid or invalid. The Catch-All Verifier also resolves 30–40% of these risky addresses outright, at no additional cost, before they ever reach that refunded bucket. #### ****Should catch-all addresses be deleted or used?** Neither, by default. Isolate them from the primary verified send. If the client approves testing them, run a separate, conservative campaign from a secondary domain with its own monitoring and stop conditions — don't fold them into the main list or send them from the client's core domain. ## Final Pre-Send Checklist - Operator authorized to pause the campaign. - Client report and verification evidence stored. - Thresholds, monitoring, and stop conditions approved. - Authentication and tracking configuration checked. - Re-verification trigger defined (manual cycle or API). - Results segmented; unknown and catch-all records isolated. - Deep SMTP bulk verification completed in MillionVerifier. - Suppressions and unsubscribes applied. - Original file preserved; working copy versioned. - Source and lawful-use documentation recorded. Protecting a client domain takes more than one tool or a lucky send. It requires a repeatable control: isolate, verify, segment, set thresholds, monitor, and report. If your current onboarding process still lets a raw list reach a sending tool unverified, that's the gap to close first — [claim your free 100 MillionVerifier credits](https://app.millionverifier.com/register?ref=millionverifier.com) and run your next client list through deep SMTP verification before it ever touches a campaign. ### Calculating the Financial Cost of Poor List Hygiene URL: https://www.millionverifier.com/blog/calculating-the-financial-cost-of-poor-list-hygiene/ Last updated: 2026-09-29T14:34:40.000Z - **Bad email data is a RevOps leak**. Invalid, duplicate, decaying, and unsubscribed contacts can inflate platform costs and shrink the pipeline you can actually reach. - **The bill shows up in three places**. You pay for unused contact capacity, lose opportunities when campaigns are filtered or throttled, and absorb the operational cost of repairing a damaged sending domain. - **A transparent model makes the problem measurable**. Use list size, a sourced decay rate, marginal platform cost, and attributable campaign revenue — not a vague claim that you should "clean your list." - **The remedy also has a measurable return**. Compare an annual verification cost with annual contact overage, remediation, and labor costs. Validate every pricing and deliverability assumption before approving the spend. ![](https://www.millionverifier.com/content/images/video-thumbnails/9a83da760dfc2d09c78a2d326e279c6d970b42128daf85c984edbd845015e9f0-1280.webp) ## How Much Money Is Bad Email Data Leaking From Your Pipeline? The most credible financial hook is one you can reproduce from your own systems. For example, if a company holds 20,000 invalid or nonresponsive contacts in billable marketing capacity and its platform charges a marginal rate of $0.05 per contact per month, that unused capacity costs **$1,000 per month**, or **$12,000 per year**. This figure excludes lost revenue, labor, and domain remediation. It also assumes those records are actually billable — a condition worth checking before you assume the cost exists at all. The executive question is broader: **how much does bad CRM data cost** **once you include platform capacity, reachable demand, and operational recovery?** A high bounce rate is more than a marketing nuisance. It can consume paid capacity, weaken sending signals, limit campaigns, and leave sales and marketing working around a damaged domain. Start with the estimate below, then replace each input with data from your CRM, ESP, finance team, and sales operations. **A note on the numbers.** Decay rates and mailbox-provider thresholds in this guide are sourced and cited. Prices and revenue figures are illustrative and must be replaced with your own contract and CRM data. A bounce rate does not automatically cause a specific spam-folder outcome, and a lower open rate does not translate directly into an equivalent decline in closed-won revenue. ![](https://www.millionverifier.com/content/images/2026/09/slide-06-three-pathways.png) ## The Three Direct Financial Costs of a High Bounce Rate The direct costs fall into three categories: paid data capacity, lost reachable revenue, and domain-recovery operations. | Cost category | How poor hygiene creates the cost | What to measure | | -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | CRM and ESP overage "dead weight" | Invalid, bounced, catch-all, duplicate, or unsubscribed contacts occupy **billable** contact capacity and push you across tier thresholds. | Billable contacts by status, tier thresholds, and incremental monthly and annual fees. | | Lost sales revenue from throttled campaigns | Hard bounces and poor engagement can contribute to filtering, throttling, or reduced inbox placement, limiting exposure to otherwise valid prospects. | Delivered volume, inbox placement by provider, conversion rate, attributable closed-won revenue, and affected campaigns. | | Domain replacement and blacklist remediation | A damaged sending domain may require a new domain, new inboxes, a warm-up period, monitoring, and SDR workarounds. | Domain and mailbox costs, warm-up duration, paused sends, SDR hours, and recovery spend. | ![](https://www.millionverifier.com/content/images/2026/09/slide-08-find-threshold.png) ### 1\. CRM Seat Licenses and ESP Overage Fees (The "Dead Weight" Tax) Invalid contacts can push a company into a higher billing tier even though they have no realistic path to conversion. HubSpot, Salesforce, Mailchimp, and similar platforms all package and bill differently. Charges may depend on contact volume, records, seats, sends, or some combination. Check your contract rather than assuming the same pricing logic applies to every platform. **Marginal cost is higher than most teams assume, but fewer records are billable than they fear.** On HubSpot, additional marketing contacts run roughly $50 per month per 1,000 on Starter and $250 per month per 5,000 on Professional — about $0.05 per contact per month at both tiers, falling toward $0.01 at Enterprise volumes. That is the number to use, not a rounded-down $0.02. The offsetting fact matters just as much: HubSpot bills only *marketing* contacts. Records moved to non-marketing status remain in the CRM at no contact cost, so a database can hold 100,000 records while billing for 5,000\. If your platform works this way, the cost of a dead record is not "it sits in a paid tier." The cost is that tier thresholds move in one direction. Importing 50 contacts at 7,000 pushes you to 7,050 and triggers the next block immediately, and platforms generally do not downgrade you automatically when the count falls back. That asymmetry — automatic upgrade, manual downgrade — is where most contact spend is quietly stranded. So the question is not "how many bad records do I have?" It is "how many bad records are billable, and which threshold are they holding me above?" Imagine a database with 100,000 records, including 20,000 confirmed invalid, bouncing, or otherwise unavailable for legitimate outreach. If suppressing or removing those records takes the account below a billing threshold, the saving is the difference between the current and lower tiers — not the result of applying a universal per-contact price. If the platform uses incremental pricing, calculate the marginal cost of the billable subset and annualize it. Count duplicates and unsubscribed contacts only if your platform includes them in its billing calculation. **Audit method:** export contact counts by status and by billable flag, map them against the current tier, identify the next threshold down, confirm the downgrade process, and ask the vendor or account owner to confirm pricing in writing. Cutting costs never overrides consent, suppression, or retention requirements. ![](https://www.millionverifier.com/content/images/2026/09/slide-04-model-opportunity.png) ### 2\. Lost Sales Revenue from Throttled Campaigns A deliverability penalty limits access to valid contacts, not just the invalid addresses behind the bounces. This is the part of the loss that actually has revenue attached to it, and it is worth being precise about the mechanism. Google publishes thresholds for bulk senders, but they govern *user-reported spam complaints*, not bounces. Gmail's guidance is to keep the spam rate below 0.1% and to prevent it from ever reaching 0.3% or higher; senders above 0.3% become ineligible for mitigation until they hold below that line for seven consecutive days (Google, Email sender guidelines FAQ). Yahoo and Microsoft apply the same 0.3% enforcement threshold, though Yahoo's denominator excludes spam-foldered mail, which makes the same complaint volume score worse. Google publishes no equivalent bounce-rate threshold. Bounces matter indirectly: hard bounces from invalid addresses signal poor list quality, and a list with a high invalid share tends to produce the complaints and engagement patterns that do breach published limits. There is no formula that converts a bounce rate into a spam-placement rate, and any vendor offering one is guessing. That means the opportunity cost belongs to your **reachable** audience, not to the dead addresses: 1. Establish the attributable revenue base — closed-won revenue influenced by email campaigns to this audience over a defined period. Say $500,000 over 12 months, or $41,667 per month (illustrative). 2. Estimate the performance impairment as a relative change, after controlling for audience, subject line, offer, seasonality, and send volume. A 10% relative reduction in engagement means a decline from 30% to 27% opens, not from 30% to 20%. 3. Apply it as a screening estimate: $41,667 × 10% = $4,167 of exposed monthly revenue opportunity. 4. Test that estimate against downstream clicks, meetings, opportunities, and closed-won records. The $4,167 figure is neither proof of causation nor a forecast. It is a way to decide whether the problem deserves further investigation. For a more conservative model, use only incremental opportunities attributable to email and apply the historical close rate. Keep the impairment percentage visible so executives can challenge it, then replace the estimate with an experiment or matched cohort when possible. ![](https://www.millionverifier.com/content/images/2026/09/slide-05-recovery-cost.png) ### 3\. The Cost of Domain Replacement and Blacklist Remediation A burned sending domain creates real recovery costs, even when no invoice calls them "list hygiene." The work may include buying a replacement domain, configuring authentication, paying for Google Workspace or Microsoft 365 inboxes, monitoring reputation, and warming the new infrastructure gradually. A 3–4 week warm-up is a reasonable planning assumption, but the actual timeline may be shorter or longer depending on mailbox-provider requirements and sending history. Include these line items: - Domain registration, DNS, authentication, monitoring, and specialist support. - Three to four weeks of mailbox licenses and inbox setup during warm-up; verify current Google Workspace or Microsoft 365 pricing. - SDR labor spent pausing sequences, manually validating records, rerouting outreach, and waiting for approved sending capacity. - Campaign delays, reduced send volume, and opportunity cost while the new domain builds a trustworthy history. For example, if 10 SDRs each spend 4 hours on remediation at a fully loaded hourly cost of $60, the labor estimate is 10 × 4 × $60 = $2,400\. This is an illustration, not a benchmark. List hygiene is also only one possible cause of a blacklist listing or poor reputation. Authentication failures, complaints, compromised accounts, and content issues may also be responsible, so investigate the full sending system before replacing a domain. ![](https://www.millionverifier.com/content/images/2026/09/slide-09-roi-formula.png) ## The List Hygiene ROI Formula: Model Your Loss Two costs, one time period. Keep them separate and keep them monthly: Monthly cost of inaction \= (Billable unusable contacts × marginal ESP cost per contact per month) - (Monthly attributable email revenue × estimated performance impairment %) Three rules make this defensible: - **Both terms are monthly.** Decay rates are annual; convert them before use. Annualize by multiplying the whole result by 12, not by mixing a monthly platform cost with an annual revenue figure. - **The platform term applies only to billable records.** Contacts your plan does not charge for contribute zero here, however dead they are. - **The revenue term applies only to valid, reachable contacts.** A bounced address cannot generate pipeline, so assigning it a "missed pipeline value" invents money. The loss lives with the good contacts whose mail is being filtered. ### Worked example Inputs (illustrative except where sourced): | Input | Value | Basis | | ------------------------------------------- | ----------------------- | ----------------------------------------- | | Total list size | 50,000 | Your CRM | | Months since last verification | 12 | Your records | | Annual decay rate | 22.5% | HubSpot / MarketingSherpa; see note below | | Estimated decayed contacts | 11,250 | 50,000 × 22.5% | | Share of decayed contacts that are billable | 100% | **Assumption — check your plan** | | Marginal ESP cost | $0.05 / contact / month | Published HubSpot block pricing | | Remaining reachable contacts | 38,750 | 50,000 − 11,250 | | Attributable email revenue | $41,667 / month | $500,000 over 12 months | | Estimated performance impairment | 10% relative | **Assumption — measure this** | Calculation: Platform term: 11,250 × $0.05 = $562.50 / month Revenue term: $41,667 × 10% = $4,166.70 / month \------------------ Total $4,729.20 / month $56,750 / year Run it at three impairment levels before presenting it. At 3% impairment the revenue term falls to $1,250/month and the total to $1,813/month. At 15% the revenue term rises to $6,250 and the total to $6,813/month. The spread between those scenarios is the honest answer, and it tells you the platform term is rounding error — the case for verification rests almost entirely on deliverability, so that is the number to defend. **On the 22.5% decay rate.** This is one of the better-supported figures in email marketing. MarketingSherpa research put B2B contact decay at 2.1% per month, which annualizes to 22.5%, and HubSpot maintains it in its Database Decay Simulation. ZeroBounce's independent analysis of its own verification data found at least 22.71% of a typical list goes bad each year. Two different methods landing within a quarter-point of each other is reasonable grounds for using the number. Note that it is a cross-industry aggregate: B2C lists tend to sit at 20–25% annually, while B2B lists commonly run 25–30% because job changes drive most of the churn. If your database skews B2B or toward fast-moving sectors, 22.5% is the conservative end. ![](https://www.millionverifier.com/content/images/2026/09/slide-02-roi-breakdown.png) ## How Bulk Email Verification Pays for Itself (The ROI Breakdown) Verification is a recurring cost, not a one-time purchase. If a list decays at roughly 2% per month, a single clean run is stale within a quarter. Compare annual to annual. MillionVerifier credit packages start at 10,000 credits for $39, with per-credit rates falling at higher volumes and credits that never expire. Check the current pricing page for the rate at your list size before budgeting. Quarterly verification of a 50,000-contact list is 200,000 verifications per year. At the entry-tier rate of $3.90 per 1,000, that is a ceiling of about $780 per year; volume pricing brings it lower. Set that against the platform term from the worked example: Avoided contact cost: $562.50 × 12 = $6,750 / year Verification cost: $780 / year (ceiling) \----------------- Net difference $5,970 / year This produces a positive return only if the records count toward a paid tier, the $0.05 marginal cost is correct, and you can actually cross a threshold downward. If the records are not billable, the business case rests instead on deliverability protection, time saved, and recovered campaign performance — which, per the model above, is where most of the value sits anyway. **One note on scope.** No verifier can guarantee inbox placement, and no verifier can fully resolve catch-all domains, which accept mail at the SMTP layer regardless of whether the mailbox exists. That is a property of how those servers respond, not a gap in any one tool. Decide in advance how you will treat catch-all and unknown results — send with lower volume, route to a separate warm-up sequence, or hold back entirely — and record the bounce outcomes so the policy improves with evidence rather than guesswork. For implementation guidance, see The Ultimate Guide to Email Deliverability & Sender Reputation. Pair it with your authentication, consent, complaint, suppression, and monitoring procedures. Before every run, confirm data-handling, retention, and vendor terms with the relevant privacy and security owners. ![](https://www.millionverifier.com/content/images/2026/09/slide-01-repeatable-model.png) ## RevOps Deliverability Budgeting Checklist Run this checklist at least quarterly and before any major campaign or database migration: - Audit current ESP contact-tier limits, marginal costs, send limits, downgrade procedures, and renewal terms. - Separate total records from **billable** records; identify which bounced, invalid, duplicate, dormant, unsubscribed, and suppressed contacts actually carry a charge. - Identify the next tier threshold below your current position and the exact record count needed to reach it. - Export CRM and ESP status counts and reconcile differences before estimating savings. - Calculate the time SDRs spend manually validating scraped or aged lists versus the cost of one bulk verification run. - Record current hard-bounce, complaint, delivery, and engagement baselines **by mailbox provider**, and check spam complaint rates against the 0.1% target and 0.3% enforcement ceiling in Google Postmaster Tools. - Model conservative, base, and upside scenarios; treat the performance-impairment percentage as an assumption until measured, and label the decay rate with its source and whether you have adjusted it for a B2B skew. - Include domain, DNS, mailbox, monitoring, warm-up, and SDR labor costs in a remediation reserve. - Budget verification annually at your real re-verification cadence, and confirm current vendor and platform pricing rather than reusing an old figure. - Define suppression, deletion, consent, and retention rules with legal, privacy, and security stakeholders. - Recalculate ROI after verification using delivered volume, meetings, opportunities, and closed-won revenue — not opens alone. ## Frequently Asked Questions #### How much does bad CRM data cost a B2B company? It depends on contact-tier pricing, how many unusable records are billable, labor, and attributable revenue. Start with billable records that are invalid, duplicate, bounced, or suppressed, and apply your marginal ESP cost — around $0.05 per contact per month on common HubSpot tiers. Model the deliverability opportunity cost separately, against your reachable audience. In most models the second term dominates by an order of magnitude, so a business case built only on contact fees understates the problem while being easier to verify. #### Does a 5% bounce rate automatically send email to spam? No. Google's published bulk-sender thresholds govern user-reported spam complaints, not bounces: keep the spam rate below 0.1% and never let it reach 0.3%, above which you lose access to mitigation until you hold below the line for seven consecutive days. There is no published bounce-rate threshold. Bounces still matter, because invalid-heavy lists tend to generate the complaint and engagement patterns that breach the limits that are published. Mailbox providers also weigh authentication, content, volume, and sender history, and Yahoo calculates complaint rates on a stricter denominator than Google. Measure inbox placement and downstream conversions by provider before attaching a financial loss. #### What should we actually budget for verification? Budget your annual re-verification cadence, not a single run. Credit packages start at 10,000 for $39 and the per-credit rate falls at higher volumes, so a quarterly cadence on a 50,000-contact list sits well under $780 a year at the entry rate and lower at scale. Credits do not expire, which means the cadence can follow your decay rate rather than a billing cycle. Set that figure against your real ESP overage, SDR validation hours, and remediation reserve — and confirm privacy and data-processing requirements before uploading a list. #### How should teams calculate the cost of a performance decline? Start with attributable revenue and apply the impairment as a relative percentage. If email influences $500,000 of closed-won revenue a year — $41,667 a month — a 10% relative impairment implies roughly $4,167 a month of exposed opportunity. Do not apply the percentage to bounced contacts; they cannot convert, and counting them double-counts the loss. Treat the result as a hypothesis until matched cohorts or experiments connect delivery and engagement with meetings, opportunities, and wins, and always present it alongside a conservative and an upside scenario. #### How long does a replacement domain need to warm up? A 3–4 week warm-up is a planning assumption, not a guarantee. The actual period depends on volume, authentication, recipient engagement, complaint rates, mailbox-provider policy, and domain history. Budget for Google Workspace or Microsoft 365 inboxes, monitoring, and SDR labor during the transition. Resume sending at scale only when performance and reputation evidence support it. ### The Ugly Truth About Spam Traps (And What Email Verification Can Actually Fix) URL: https://www.millionverifier.com/blog/the-ugly-truth-about-spam-traps-and-what-email-verification-can-actually-fix/ Last updated: 2026-09-29T14:14:50.000Z ![](https://www.millionverifier.com/content/images/video-thumbnails/d3666edb359cf75209a2d8f296f3f0ff75e9fa3f2f05401a52cfcd97fffbd81f-1280.webp) - **Pristine traps can pass SMTP checks as Valid**: deliverability is not the same as permission. - **A trap hit can damage reputation:** it may contribute to filtering, throttling, or a blocklist listing, depending on context. - **MillionVerifier has a defined scope:** it removes undeliverable and disposable addresses and flags risky ones, which shrinks the pool of records where recycled and typo traps hide, but it does not detect spam traps of any type. - **The durable prevention controls are operational:** reject scraped lists, enforce double opt-in, and sunset unengaged subscribers after a window matched to your sending frequency. ![](https://www.millionverifier.com/content/images/2026/09/image9.png) Spam traps look like email addresses, but they exist to detect poor list acquisition and maintenance. A hit can damage your sender reputation, push campaigns toward the spam folder, or contribute to a blocklist listing. The uncomfortable part is that verification has a hard technical limit. A pristine trap can behave like a real inbox and return Valid during an SMTP check. No verifier can honestly promise to remove every one — trap operators never publish their addresses, and [Spamhaus states plainly that it does not share its trap feeds with any third parties](https://www.spamhaus.org/news/article/810/you-cant-buy-data-hygiene?ref=millionverifier.com). MillionVerifier can remove addresses that no longer accept mail and flag risky ones, but it cannot repair missing consent or identify a honeypot. That leaves three practical defenses: never use scraped lists, enforce double opt-in, and sunset subscribers once they stop engaging. ![](https://www.millionverifier.com/content/images/2026/09/image20.png) ## What Is a Spam Trap, and Does One Hit Really Get You Blacklisted? A spam trap is an email address that mailbox providers, blocklist operators, and anti-abuse organizations use to spot careless list acquisition and maintenance. No person is waiting to read the campaign. Instead, the address reveals senders that contact recipients who never subscribed, abandoned an inbox, or entered an address with an obvious error. [Spamhaus defines them simply](https://www.spamhaus.org/glossary/?ref=millionverifier.com) as addresses "which have not opted into any email," and notes that their owners never reveal them. One trap hit can attract disproportionate scrutiny. The outcome depends on the trap type, provider, sending volume, and sender history. A listing is not always instant, and different datasets work differently: Spamhaus's SBL is maintained by investigators, while its [Combined Spam Sources (CSS) set is automatically produced](https://www.spamhaus.org/blocklists/combined-spam-sources/?ref=millionverifier.com) from "multiple events and heuristics" — 300,000 to 400,000 new listings every 24 hours — so the same behavior can produce a manual listing on one dataset and an automatic one on another. ### What happens if I email a spam trap? The address may accept the message as if nothing is wrong. Behind the scenes, its operator can record your domain, IP, authentication signals, and campaign context. Those signals may contribute to throttling, spam-folder placement, reputation damage, or a blocklist listing. One delivery does not guarantee an instant listing. Still, treat a suspected hit seriously: stop the affected stream, suppress the address, and trace how it reached your database. ### Why did my domain get listed on Spamhaus? A Spamhaus listing does not point to one universal cause. It may involve trap hits, unsolicited traffic, compromised accounts, malware, or wider infrastructure and reputation problems. Start with the exact record and its delisting guidance. Then audit your acquisition sources, consent evidence, bounce and complaint trends, authentication, and recent sending changes. List cleaning may be part of the response, but it will not explain every listing — and Spamhaus is blunt that it "frequently sees mail in its spamtraps from 'cleaned' lists." **Work through these questions:** - **Which asset is listed?** Use the IP and Domain Reputation Checker at check.spamhaus.org to confirm whether the record is tied to your domain, IP address, or another sending component, and which dataset holds it — SBL, CSS, XBL or PBL for IP addresses, DBL for domains. The record type determines the remediation path. - **When did the problem begin?** Compare the listing or reputation change with imports, forms, vendors, and campaign launches. - **Can you identify the recipient source?** Trace suspicious addresses to a list upload, web form, integration, or legacy segment. - **Are hard bounces or complaints rising?** These patterns can expose stale or improperly acquired data even when no trap is confirmed. - **Did the operator provide a specific record or reason?** Follow that evidence instead of guessing. ![](https://www.millionverifier.com/content/images/2026/09/image19.png) ## What Are the Three Types of Spam Traps: Pristine, Recycled, and Typo? Pristine, recycled, and typo traps come from different failures, so one control cannot address them all. Use this table as a diagnostic framework, not as proof that a particular address is a trap. | How They Are Created | How They Enter Your List | Severity Level | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | Pristine traps: Created and published solely for detection by an ISP, blocklist operator, or anti-abuse group; they may be hidden in web-page source so scrapers discover them. | Scraped or purchased lists, indiscriminate harvesting, copied web data, insecure directories, or a bot submitting an address to a form. | High to critical. A hit strongly suggests acquisition or permission failure; consequences depend on operator and sender context. | | Recycled traps: Previously legitimate mailboxes — typically consumer accounts whose owners stopped using them years ago — that hard-bounce for a long period and are then reactivated by the provider or an anti-abuse operator so that hits can be recorded. Validity puts the qualifying window at a minimum of 12 months of inactivity. | Old CRM records, long-retained subscribers, role addresses, unmaintained segments, and senders that ignore bounces or engagement decay. | Medium to high. Signals stale-data governance problems and repeated sending can increase filtering risk. | | Typo traps: Addresses containing a user or domain misspelling. Some misspelled domains simply have no mail server and bounce; others are registered specifically to catch misdirected mail and can be monitored. Not every typo address is a trap. | Manual checkout or signup errors, imports without validation, forms lacking domain correction, and APIs accepting malformed addresses. | Low to medium per address, but meaningful at scale; they also create ordinary bounces and reveal weak capture controls. | ## Can Email Verification Remove 100% of Pristine Spam Traps? No. A pristine trap is a working inbox, so an SMTP verifier may correctly report it as deliverable. In a deep SMTP check, the receiving server can complete the handshake and confirm that the mailbox exists. The result may be Valid even though no person requested your messages and the inbox is being monitored as a honeypot. ![](https://www.millionverifier.com/content/images/2026/09/image8.png) **This is the line between deliverability and permission:** - SMTP can tell you, roughly, "This server will accept mail for this address." - It cannot tell you, "A real person asked to receive these messages." - It therefore cannot reliably expose a valid-looking pristine trap. The same limit applies to a live recycled trap. Once a provider reactivates a long-dormant mailbox, it accepts mail again — that is the point of reactivating it — so it verifies as Ok exactly like a pristine trap. Verification catches such an address only during the period when it is still hard-bouncing. ![](https://www.millionverifier.com/content/images/2026/09/image10.png) Any promise of "100% spam trap removal" is misleading. Marking every working mailbox as invalid would also remove legitimate subscribers. The reliable defense happens before verification: acquire addresses transparently, record consent, protect forms from bots, retain source and timestamp evidence, and remove data that no longer shows healthy engagement. ## What Can MillionVerifier Actually Do About Recycled and Typo Risk? MillionVerifier does not detect spam traps, and no verifier honestly can — ISPs and blocklist operators never publish, share, or leak their trap addresses. What verification does is shrink the population of records where recycled and typo traps are found: it removes addresses that no longer accept mail, flags catch-all and unknown domains as risky, and catches malformed or misspelled addresses at the point of capture. It cannot replace permission controls or guarantee protection from a pristine trap. Verification works best as one layer of a wider deliverability program. For the rest of that program, see \[The Ultimate Guide to Email Deliverability & Sender Reputation\](INTERNAL LINK — add URL before publishing). Results are grouped as Good (**Ok**), Bad (**Invalid**, **Disposable**), and Risky (**Catch-All**, **Unknown**), with `free` and `role` flags available through the API. There is no trap-detection status, and there is no honest way to add one. ### What can MillionVerifier do about recycled-trap risk? Verification can flag Invalid results and other risk signals while a dormant mailbox is still bouncing, which is the only window in which a verifier can see it at all. Run these checks on legacy lists, re-engagement audiences, and imports before you send. The results indicate risk; they are not forensic proof, and a mailbox that has already been reactivated as a trap will return Ok. Review them alongside consent, source, bounce history, and the age of the recipient's last engagement. To manage lifecycle health effectively, establish a routine list-cleaning schedule rather than waiting for bounce rates to spike. By regularly running your CRM and marketing lists through the MillionVerifier Bulk Email Verifier, you can proactively identify and remove bad or risky addresses. For the remaining hard-to-verify addresses, the Catch-All Email Verifier gives you a definitive decision on the risky bucket instead of a coin flip. ![](https://www.millionverifier.com/content/images/2026/09/image2.png) ### How can MillionVerifier help with typo traps? Syntax and domain analysis can catch malformed addresses and suspicious spellings. A misspelling such as gmial.com usually has no mail server at all and comes back Invalid, while other typo domains — misspellings of the large consumer providers, for example — do publish mail servers and accept whatever arrives. MillionVerifier's real-time API can reject or quarantine both kinds at signup, while batch verification checks records already in your database. This keeps obvious entry errors from becoming bounces or polluting segments. It does not prove that the owner gave permission. **Use each check where it fits:** - **At capture:** call the real-time API to block or quarantine malformed addresses before CRM insertion. - **Before campaigns:** batch-check new imports and risky legacy cohorts. - **After results:** suppress risky records, investigate their source, and document decisions. - **For pristine risk:** rely on acquisition, consent, bot protection, and engagement policy; do not represent verification as a complete solution. ![](https://www.millionverifier.com/content/images/2026/09/image6.png) ## What Three-Step Workflow Keeps Spam Traps Out of Your List Without Software? Use this operational workflow to keep pristine traps out of your CRM and reduce exposure to recycled and typo traps. It does not depend on verification software. Give each step a clear owner and keep the supporting evidence. 1. **Never buy scraped lists.** Scrapers collect hidden pristine traps from website source code along with addresses whose owners never gave permission. Reject purchased, harvested, and supposedly "opt-in" lists when their provenance cannot be verified — as Spamhaus puts it, "no legitimate company will ever sell or rent a list of 'confirmed-opt-in' email addresses," because permission is not transferable. Build your audience through transparent forms, clear consent language, and source-level records. 2. **Enforce double opt-in (DOI) alongside bot defenses.** Do not activate a subscriber until the recipient clicks the confirmation link. Note what this does and does not buy you: the confirmation request is itself a message to the address, so a scraped pristine trap in a DOI flow still receives one email. DOI caps your exposure at a single confirmation attempt instead of an ongoing campaign stream. Most bots cannot complete the click, but not all — automated link scanners follow links in email, and subscription-bombing attacks are built to push addresses through forms — so rate limits, CAPTCHA or honeypot fields, and retained timestamp, source and consent evidence carry as much weight as the click itself. Under GDPR-style rules that evidence is also what makes consent demonstrable: who confirmed, when, from where, and what wording they saw. 3. **Implement an unengaged sunset policy.** Set the window against your sending frequency — roughly 90–120 days for a weekly program, longer where the natural buying, renewal, or seasonal cycle is longer — and apply it consistently. Judge engagement on clicks, replies, purchases, and site or app activity first; Apple Mail Privacy Protection preloads tracking pixels whether or not a message was read, so opens are inflated by default and belong in a weak secondary role. Use a measured re-engagement sequence where appropriate, then suppress nonresponders automatically. This reduces repeated mail to an inbox that its owner has abandoned and that may later be reactivated as a recycled trap. ![](https://www.millionverifier.com/content/images/2026/09/image5.png) ## What Pitfalls and Edge Cases Should You Troubleshoot? A clean verification result cannot repair a bad acquisition source, and a trap signal will not explain its own cause. Check these common failure points before and after remediation. | Situation | Likely mistake | Safer response | | ----------------------------------------------- | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | A Valid result is treated as permission | Confusing SMTP acceptance with consent | Check DOI evidence, source, timestamp, and engagement history. | | A vendor promises 100% trap removal | Relying on an absolute product claim | Ask which trap types and signals are covered; retain acquisition controls. | | A legacy segment produces complaints or bounces | Sending without age and engagement review | Pause it, inspect source cohorts, verify risk, and apply your sunset window. | | A typo correction silently changes an address | Treating a suggestion as permission | Ask the user to confirm the corrected address; never silently subscribe a different mailbox. | | A Spamhaus listing remains after cleanup | Assuming verification resolves blocklisting | Identify the exact record, stop the offending stream, secure infrastructure, document remediation, and follow the operator's process. CSS listings expire roughly three days after the last detection but re-list immediately if the underlying problem continues. | Do not "test" a suspected trap by sending to it again. Suppress the address, preserve it for investigation, and trace its source. Read patterns in context, too. A recycled-trap signal may expose a lifecycle failure, while a cluster of typos may point to a broken form or integration rather than malicious subscribers. ## What Is the Practical Takeaway for Email Marketers? Spam-trap prevention starts with acquisition and lifecycle discipline, not verification alone. MillionVerifier can remove undeliverable, disposable, and malformed addresses during import and capture, which shrinks the pool where recycled and typo traps hide — but it does not detect traps, and it cannot make a live honeypot look invalid. The durable approach combines consent-first acquisition, DOI, source traceability, targeted verification, and timely suppression of unengaged records. ## Frequently Asked Questions #### Can a pristine spam trap return Valid in an email verification check? Yes. A pristine trap is designed to function like a real mailbox, so its server may complete an SMTP handshake and return a Valid-style result. That status describes server acceptance, not consent or human ownership. No verifier can promise pristine-trap detection without risking false positives against legitimate subscribers. #### Does MillionVerifier guarantee that my domain will never hit a spam trap? No. MillionVerifier removes undeliverable and disposable addresses and flags risky ones through batch checks and its real-time API, but it does not detect spam traps: a live trap accepts mail and verifies like a legitimate inbox. Pair verification with DOI, source controls, bot defenses, and a sunset policy to reduce risk; no responsible provider can eliminate it entirely. #### Why might a Spamhaus listing remain after I verify my email list? It depends on the listing record and its cause. Verification may reduce risky recipients, but it cannot undo unsolicited acquisition, compromised infrastructure, malware, complaint patterns, or a prior trap hit. Inspect the exact Spamhaus record, stop the offending stream, secure sending systems, document remediation, and follow the operator's delisting process — with Spamhaus, the only route off a list is fixing the problem that caused it, and removal is never charged for. #### How does double opt-in protect a list from pristine traps? DOI requires the recipient to click a confirmation link before activation, so an address that never consented receives one confirmation request rather than a campaign stream. Most scraped or bot-submitted addresses never complete that step, though automated link scanners sometimes do. Store the consent timestamp and source, add rate limits and bot protection, and suppress unconfirmed records. DOI protects acquisition; it does not replace bounce and complaint monitoring. #### Should I keep sending to an old subscriber who still passes SMTP verification? No. SMTP acceptance does not demonstrate current engagement, permission, or safety from recycled-trap risk — and a mailbox that has already been reactivated as a trap will pass verification. Apply your sunset window, offer measured re-engagement where appropriate, then suppress nonresponders. MillionVerifier may add useful risk signals, but lifecycle decisions should also use consent evidence, source provenance, and observed engagement. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. ### Inbound vs. Outbound Email Verification: Strategic Differences URL: https://www.millionverifier.com/blog/inbound-vs-outbound-email-verification-strategic-differences/ Last updated: 2026-09-11T09:35:37.000Z Inbound verification should optimize for conversion at the point of entry, which means fast checks, typo correction, disposable-domain handling, and selective free-mail filtering when the workflow requires it. Outbound verification should optimize for sender-domain safety before the first send, which means stricter screening, zero reliance on user intent, and deep SMTP checks to catch hard-bounce and reputation risk. A clean operating model is simple: use the MillionVerifier API for inbound forms, MillionVerifier Bulk Email Verifier before outbound campaigns, and to maintain CRM hygiene over time. ![](https://www.millionverifier.com/content/images/video-thumbnails/e55304a7365b3e2cafe7e40da11a4dec593eea729a7ca9ded5dacec140091f67-1280.webp) ## Why do inbound and outbound email workflows require different rules? Inbound and outbound email verification should not use the same policy because the user intent and risk model are different. In inbound, a real person is actively trying to convert. In outbound, there is no live user at all. That single difference changes what the verification layer should protect. In an inbound workflow, someone is filling out a demo form, starting a trial, or submitting a landing page. Verification has to improve data quality without disrupting the conversion moment. In an outbound workflow, there is zero user intent at the moment of verification. You are evaluating a stored record before cold outreach starts. No one is waiting on a form. The goal is not UX preservation. The goal is to protect the sender domain. That is why one shared rule set causes damage: - Too strict on inbound creates form friction, rejects recoverable leads, and increases abandonment. - Too loose on outbound lets risky records into campaigns and raises bounce, blacklist, and reputation risk. The rule is simple: verification policy should follow workflow context, not just the email field. ## How should inbound email verification work at the point of entry? Inbound verification should run in real time on forms, signups, and landing pages. The job is to protect data quality while keeping the conversion path smooth. For this workflow, the natural fit is the MillionVerifier API. It belongs at the moment the email is captured, not later after bad data has already entered the CRM. ## How fast should inbound verification be, and why does typo correction matter? Inbound verification should feel almost invisible. In practice, that means low-hundreds-millisecond response times, with sub-200ms often being the target on high-intent forms. Speed matters, but correction matters just as much. Many bad inbound addresses are not malicious. They are ordinary typing mistakes. **Example:** - User enters: `jane@gmai.com` - Form responds: *Did you mean jane@gmail.com?* That kind of correction saves legitimate demand, keeps CRM data cleaner, and prevents needless form drop-off. ## When should B2B SaaS teams block disposables or free-mail addresses? Inbound filtering should be selective rather than blunt. For many B2B SaaS teams, blocking disposable domains on demo requests, contact-sales forms, or free-trial flows is a sensible guardrail. It reduces junk submissions and fake signups. Free-mail addresses are more contextual. Some teams need a corporate domain for routing, enrichment, qualification, or ownership assignment. In those cases, it can make sense to block or flag free-mail on specific forms. A practical inbound policy often looks like this: - block disposable domains, - correct obvious typos, - optionally block or flag free-mail on selected B2B forms, - route edge cases into review or nurture paths instead of automatically discarding them. The aim is not maximum strictness. The aim is better data quality without punishing legitimate intent. ## How should outbound email verification protect the sender domain before send? Outbound verification should happen before the first email is sent to a stored list. This is a pre-send deliverability control, not a UX layer. When you prepare a cold outbound list, there is zero user intent behind the verification event. That means the correct posture is stricter from the start. The main risks are: - hard-bouncing inboxes, - invalid domains, - sender-domain reputation damage. That is why the right fit here is MillionVerifier Bulk Email Verifier. ![](https://www.millionverifier.com/content/images/2026/08/image3.png) ## Why are deep SMTP handshakes better than surface pings for outbound? Shallow checks are not enough when domain reputation is at stake. A syntax pass or surface ping may show that an address appears normal, but outbound verification needs stronger evidence before a campaign launches. That is where deep server/SMTP handshakes matter. MillionVerifier Bulk Email Verifier uses deep SMTP-based checks to identify: - invalid domains, - hard-bouncing inboxes, without sending an email. That is the right standard for outbound because the workflow is not trying to preserve a live conversion event. It is trying to prevent sender-domain damage before it happens. ## What is the difference between inbound and outbound verification workflows? The table below shows why the same email field requires two different operating models. | Workflow Factor | Inbound Strategy | Outbound Strategy | | ------------------------- | -------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | **User Intent** | A real user is actively submitting a form or signup | No live user is present; the address is a stored record | | **Primary Goal** | Protect conversion while improving data quality | Protect the sender domain before outreach begins | | **Latency Requirement** | Real-time validation in low hundreds of milliseconds; ideally sub-200ms on high-intent forms | No live UX constraint; prioritize verification depth and safety over speed | | **Primary Threat** | Form abandonment, typo-driven bad records, disposable signups, and CRM pollution | Hard bounces, invalid domains, blacklist exposure, and reputation damage | | **Typo Correction** | Essential; support "Did you mean?" prompts such as gmai.com → gmail.com | Usually not relevant; list records should be cleaned and screened, not interactively corrected | | **Implementation Method** | Point-of-entry verification on forms, signups, and landing pages | Pre-send bulk verification before cold outreach or campaign launch | | **Best-Fit Tool** | MillionVerifier API | MillionVerifier Bulk Email Verifier | ![](https://www.millionverifier.com/content/images/2026/08/image7-1.png) ## How should you handle catch-all emails in inbound vs. outbound workflows? Catch-all handling should change with context. A catch-all result does not mean the same thing in inbound and outbound verification. In inbound, a catch-all typed directly by a user is often worth accepting because there is a live intent signal behind it. In outbound, a catch-all pulled from a scraped or purchased list is riskier because there is no intent signal at all. A safer outbound policy is to: - segment catch-all records, - keep them out of your safest send tier, - test them with a cautious drip strategy, - monitor results before scaling. The principle is consistent: user-entered ambiguity is different from list-sourced ambiguity. ![](https://www.millionverifier.com/content/images/2026/08/image2-1.png) ## How do you maintain CRM hygiene after initial verification? Verification is not a one-time event. Once records enter systems like HubSpot, Apollo, or Mailchimp, they begin to decay. People change jobs. Domains expire. Previously valid inboxes go stale. That is why teams need a routine hygiene schedule after capture and before future sends. This is where scheduling regular cleanups with the MillionVerifier Bulk Email Verifier fits naturally. By routinely exporting and verifying your active lists, you keep CRM and marketing data healthy over time so teams do not wait for bounce problems to reveal that the database has drifted. Ongoing hygiene supports: - cleaner routing, - better segmentation, - more dependable campaign performance, - stronger lifecycle reporting. ## What is the simplest policy to implement? If you need one practical operating model, use the MillionVerifier API at the point of entry for inbound forms, and use the MillionVerifier Bulk Email Verifier before cold outbound sends and for routine CRM maintenance. That approach matches the real difference between the workflows: inbound is conversion-sensitive (blocking bad data before it enters), while outbound and long-term CRM hygiene are sender-risk-sensitive (ensuring your lists remain safe to send to). ## Frequently Asked Questions #### ****Should B2B SaaS teams block free-mail addresses on every inbound form?** No. Free-mail filtering should be selective, not universal. If your routing or qualification model depends on a corporate domain, blocking or flagging free-mail on specific high-intent forms can make sense. If not, a softer approach is safer because some legitimate buyers still convert with Gmail or similar addresses. #### ****When is MillionVerifier API the right choice instead of Bulk Email Verifier?** Use MillionVerifier API when the address is being captured live on a form, signup, or landing page. It fits inbound workflows because speed and typo correction matter at the point of entry. MillionVerifier Bulk Email Verifier fits stored outbound lists that need stricter pre-send screening rather than real-time UX protection. #### ****Why are deep SMTP checks more important for outbound than inbound?** Because outbound verification is about sender-domain protection before a campaign goes live. With no live user waiting, deeper checks are worth the extra rigor. MillionVerifier Bulk Email Verifier uses deep SMTP-based verification to surface hard-bounce and invalid-domain risk before the first email is sent. #### ****How should teams treat catch-all emails from scraped outbound lists?** Treat them cautiously. Catch-all records from scraped outbound lists should usually be segmented away from the safest send pool, tested slowly, and monitored before scaling. They do not carry the same trust signal as a catch-all address entered directly by a real user on an inbound form. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. ### How to Block Disposable Emails in SaaS Signups (Without Killing Conversions) URL: https://www.millionverifier.com/blog/how-to-block-disposable-emails-in-saas-signups-without-killing-conversions/ Last updated: 2026-09-01T10:53:40.000Z - Disposable emails distort SaaS signup metrics, increase free-trial abuse, and quietly hurt deliverability when temporary inboxes vanish mid-onboarding. - The safest implementation is a hybrid approach: real-time verification on the frontend for fast feedback, plus backend enforcement so the rule cannot be bypassed. - MillionVerifier helps teams detect burner domains, catch-all risk, and ambiguous signup cases in real time without turning onboarding into a conversion bottleneck. ![](https://www.millionverifier.com/content/images/video-thumbnails/b4e02faa3016d2b2c5c6abccca0740869bc15d3ca750cd1d591e2fe544aa4d58-1280.webp) Disposable emails look harmless until the downstream damage starts piling up. A signup lands, your top-of-funnel dashboard goes up, and your free-trial numbers seem healthy. But if those accounts were created with self-destructing inboxes, the growth signal is misleading from the start. That is why burner-email blocking is not just a list-hygiene task. It is a growth-quality decision. Left unchecked, disposable emails skew conversion reporting, waste CRM seats, distort product-market-fit signals, and create a delayed bounce problem that weakens sender reputation over time. The good news is that you do not have to choose between fraud control and smooth onboarding. With a real-time email verification API, thoughtful UI timing, and backend enforcement, you can stop low-quality signups without adding visible friction for legitimate users. ![](https://www.millionverifier.com/content/images/2026/08/image7.png) ## **Why Do Users Sign Up With Temporary Emails (And What It Costs Your SaaS)?** Temporary emails are usually used to bypass commitment, extend free access, or protect privacy, but they create misleading growth signals for SaaS teams. Users typically sign up with burner emails when they want to: - start a free trial without using a real inbox - avoid lifecycle emails or sales follow-up - create multiple accounts after a trial expires - bypass paywalls, seat limits, or product usage caps - access gated content without leaving a durable lead record At first, that can look like harmless signup noise. In practice, it creates compounding cost across the funnel. Disposable-email signups can lead to: - inflated top-of-funnel metrics - lower activation and onboarding quality - weaker lead scoring and segmentation accuracy - wasted CRM seat licenses and automation spend - repeated free-trial abuse that never becomes revenue - the illusion of product-market fit when demand quality is actually weak This is why founders, product teams, and RevOps leaders should treat disposable-email abuse as a data-quality problem, not just a signup annoyance. If low-intent accounts enter the funnel unchecked, the entire business starts optimizing around the wrong signal. ![](https://www.millionverifier.com/content/images/2026/08/image6.png) ### **The Hidden Impact on Deliverability and Sender Reputation** Disposable emails can also create a delayed deliverability problem that is easy to misread. A temporary inbox may accept the first welcome email or account confirmation message. Then the inbox disappears. On Day 2 or Day 3, the rest of your onboarding sequence starts hard bouncing because the mailbox no longer exists. That delayed bounce effect can quietly damage: - sender reputation - inbox placement with Google and Yahoo - onboarding email performance for legitimate users - confidence in lifecycle metrics and experimentation results In other words, disposable-email abuse does not only corrupt acquisition data. It can also weaken the email channel your SaaS depends on to activate real accounts. ![](https://www.millionverifier.com/content/images/2026/08/image8.png) ## **How a Real-Time Email Verification API Detects Burner Domains** A real-time email verification API detects burner emails by evaluating domain, mailbox, and delivery signals instead of relying only on static blocklists. That distinction matters because a static open-source list may catch obvious domains like Mailinator or 10MinuteMail, but it will miss the new domains that disposable-email operators register constantly. A dynamic verification workflow is built to evaluate the address as it exists now, not only against yesterday's blacklist. MillionVerifier fits this model by helping teams verify whether an address behaves like part of a temporary-email ecosystem instead of trusting a domain-name match alone. ### **Static Regex Blacklists vs. Dynamic SMTP Verification** | Criteria | Static Regex / Domain Blacklist | Dynamic SMTP / Real-Time Verification API | | ------------------ | ----------------------------------------------- | --------------------------------------------------------------- | | Detection method | Matches a known burner domain or naming pattern | Evaluates live domain, mailbox, and delivery signals | | Coverage | Limited to what is already listed | Better at identifying newly seen or zero-day disposable domains | | Maintenance | Requires manual or scheduled updates | Uses refreshed verification logic and network intelligence | | Adaptability | Weak against fast domain rotation | Stronger against disposable infrastructure churn | | Catch-all handling | Often trusts accept-all behavior too easily | Can use deeper checks beyond the first positive response | | Accuracy over time | Degrades quickly | Holds up better as burner tactics change | | Engineering effort | Easy to start, expensive to maintain | Slightly more setup, stronger long-term protection | | Best use case | Basic first-pass filtering | Production-grade signup protection | Static lists fail because burner providers adapt faster than most SaaS teams can maintain their own rules. Thousands of new domains can appear constantly, and disposable operators intentionally rotate patterns to avoid simplistic regex filters. Dynamic verification is stronger because it checks the address in context, which is exactly what production signup protection requires. ![](https://www.millionverifier.com/content/images/2026/08/image9.png) ### **Why "Catch-All" Servers Trick Basic Pings (And How Advanced APIs Handle It)** A catch-all or accept-all domain is configured to accept mail for almost any mailbox name. That can fool basic SMTP checks. If your verification logic only asks whether the mail server will accept a message, the answer may look positive even when the address belongs to a disposable-email provider. That is why catch-all behavior is often used as camouflage. Advanced APIs handle this by looking beyond the first acceptance signal. MillionVerifier's deeper checks are designed to identify disposable network footprints, infrastructure patterns, and temporary-email behavior even when a domain appears catch-all on the surface. The key takeaway is simple: a catch-all response is not the same as a trustworthy mailbox. ![](https://www.millionverifier.com/content/images/2026/08/image2.png) ## **Frontend vs. Backend: Where Should You Implement the API?** For most SaaS products, the correct answer is both: frontend for user experience and backend for security. **Frontend (Browser)**Use frontend verification to keep the flow fast and clear. - highlight the field immediately when a burner address is detected - show a specific inline message before the user hits a hard failure - reduce confusion and retry loops - run validation while the user is still filling out the rest of the form **Backend (Server)**Use backend verification for final enforcement. - prevent users from bypassing the check by disabling JavaScript - apply the same policy across web, mobile, and API-driven signup flows - keep decision logging available for support, analytics, and fraud review - make disposable-email blocking a real rule instead of a UI suggestion **Recommended hybrid workflow**Run the check in the browser for immediate feedback, then repeat or confirm it on the server before account creation succeeds. If you maintain technical documentation, this section is also the natural place to internally link to your **Developer's Guide to Real-Time Email Verification & APIs**. ## **How to Maintain Zero-Friction Onboarding When Blocking Emails** You can block disposable emails without hurting signup conversion if verification runs asynchronously and enforcement happens server-side. A strong verification API should return a result in milliseconds, so the real UX issue is timing, not just speed. The best implementations do not make users wait after they click **Submit**. Instead, they verify in the background while the user is still completing the form. Best practices include: - trigger the check on blur or after a short typing pause - run the request while the user is entering their password or completing the next field - avoid blocking the entire form unless the email truly needs correction - preserve all other form inputs if the address is rejected - keep feedback inline, specific, and visually close to the email field When done well, verification feels invisible to legitimate users. ### **Handling False Positives and Custom Company Domains** A newly registered company domain is not automatically a disposable domain. That is why strong verification does not rely on age alone. MillionVerifier-style detection works by looking at a broader signal set: delivery behavior, infrastructure patterns, domain characteristics, and whether the environment resembles a real monitored mailbox or a temporary-email network. This multi-signal approach is what helps reduce false positives while still flagging suspicious signups. When you do reject an address, the message shown to the user should be specific and actionable. Use: **Please use your primary work email to continue.** Avoid: - Error - Invalid request - This email is not allowed - Email rejected Clear messaging reduces abandonment and keeps the correction step from feeling like a broken form. ## The Ideal Implementation Strategy For the best results, hand these three requirements to your engineering team: - Trigger verification in the background when the user clicks out of the email field (on blur). - Provide immediate, inline feedback if a burner domain is detected, asking for a work email without clearing the rest of their form data. - Enforce the rule on the server side so tech-savvy users cannot bypass the filter by disabling JavaScript. ## **Can Users Bypass Filters? (Apple's "Hide My Email" and Edge Cases)** Yes, some users can bypass weak filtering, and some edge cases are not abuse at all. Here is the right way to separate them: - **Gmail aliases** such as user+test@gmail.com still route to a real inbox - **Apple Hide My Email** forwards to a real monitored inbox, even though it masks the underlying address - **Forwarding privacy services** may hide identity without being disposable - **True burner inboxes** are specifically designed to be short-lived and non-durable That is why blocking Apple's privacy relay addresses is a business decision, not a purely technical limitation. MillionVerifier can provide the signal to flag them, but Product and RevOps should decide whether to allow or restrict them based on audience expectations, abuse exposure, and signup policy. ## **Frequently Asked Questions** #### ****Can I block disposable emails without hurting SaaS signup conversion rates?** Yes. If verification runs in the background and final enforcement happens on the backend, most legitimate users will never feel the extra step. MillionVerifier-style real-time verification works best when it is timed around natural form behavior instead of being triggered only after submission. #### ****Why do disposable emails damage SaaS metrics so much?** Because they inflate signup counts while lowering real activation quality. They also waste CRM capacity, distort trial-to-paid reporting, and can create false product-market-fit confidence. MillionVerifier helps reduce that noise by filtering low-quality addresses before they enter the funnel. #### ****What is the difference between a disposable email and a catch-all domain?** A disposable email is designed for short-term use and often disappears quickly. A catch-all domain simply accepts mail for many or all mailbox names. Not every catch-all result is disposable, which is why deeper verification logic matters more than a basic SMTP acceptance check. #### ****Should I run email verification on the frontend, backend, or both?** Both. Frontend verification improves user experience with immediate inline feedback. Backend verification is mandatory for true enforcement because users can bypass browser-side checks. MillionVerifier is most effective when teams combine both layers in the same signup workflow. #### ****Should Apple Hide My Email be blocked by default?** It depends. Apple's relay addresses forward to a real inbox, so they are not the same as self-destructing disposable emails. MillionVerifier can flag the signal, but the final decision should reflect your audience, abuse risk, and whether privacy-preserving addresses are acceptable in your product motion. ## **Conclusion** Blocking disposable emails is not about making signup harder. It is about protecting trial integrity, improving data quality, and preventing hidden deliverability damage without creating friction for real users. If you want a practical next step, review your MillionVerifier API documentation, test verification on blur plus server-side enforcement, and measure the impact on trial abuse, onboarding bounce rates, and signup quality over time. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. ### The Safest B2B Cold Email Workflow to Verify Scraped Leads URL: https://www.millionverifier.com/blog/the-safest-b2b-cold-email-workflow-to-verify-scraped-leads/ Last updated: 2026-09-01T08:59:13.000Z Raw scraped lead lists are one of the fastest ways to create bounce risk in outbound email. Even without relying on proprietary benchmarks, the pattern is well understood: unverified scraped data often includes invalid addresses, abandoned inboxes, formatting errors, and catch-all domains that can hurt deliverability if you send to them too quickly. ![](https://www.millionverifier.com/content/images/video-thumbnails/d80fe56e210a91e87a835b47e4e36b5d1f04b427a553ed3130576204c002879d-1280.webp) If you send cold emails directly to a raw scraped list, you are not just risking a few bounces. You are putting your sending domain, inbox placement, and future campaign performance at risk. ![](https://www.millionverifier.com/content/images/2026/07/image4-1.png) ## What Happens to Your Domain When You Send to Raw Scraped Leads? When you send to raw scraped leads, mailbox providers and spam-filtering systems evaluate list quality through real-world signals such as: - Hard bounces - Engagement rates - Spam complaints - Replies - Sending consistency - Domain and IP reputation A high bounce rate signals poor list hygiene. That matters because major inbox providers such as Google and Yahoo may throttle, junk, or otherwise limit mail from senders that continue sending to low-quality lists. A practical operating rule for cold outreach is to treat a **2% bounce rate as a danger threshold**. Once campaigns drift above that level, you should assume sender reputation is under pressure. That does not mean every provider uses 2% as a fixed published cutoff in every situation. It means crossing that line is a strong warning sign that your list quality or sending process needs attention. In plain terms, sending to raw scraped leads can trigger: - lower inbox placement - more emails landing in spam - temporary throttling - domain reputation damage - account warnings from your ESP or outbound platform - blocked sending on future campaigns That is why the safest workflow is not “scrape and send.” It is **scrape, sanitize, verify, segment, and only then launch**. ## The 3-Step Zero-Bounce Workflow for Scraped Lists ![](https://www.millionverifier.com/content/images/2026/07/image3-2.png) ### Step 1: Format and Sanitize the Raw Export 1. Import the scraped file into a spreadsheet or CSV editor. 2. Standardize the email column so every record uses the same field format. 3. Remove rows with missing @ symbols. 4. Remove rows with spaces before, inside, or after email addresses. 5. Convert all addresses to lowercase. 6. Delete duplicate emails. 7. Delete blank rows and malformed entries. 8. Flag role-based accounts such as info@, support@, admin@, sales@, and contact@ if your campaign does not target them. 9. Separate obviously risky records before verification. 10. Save the cleaned file before running verification to avoid wasting credits on broken or duplicate entries. This step matters because bad formatting creates avoidable failure volume. If you clean obvious junk before verification, you preserve credits and improve the quality of the results you get back. ![](https://www.millionverifier.com/content/images/2026/07/image7-1.png) ### Step 2: Run Deep SMTP Verification with MillionVerifier 1. Upload the sanitized list to **MillionVerifier**. 2. Let **MillionVerifier** check email syntax first. 3. Let it validate DNS and MX records to confirm the domain can receive mail. 4. Let it perform deep SMTP verification to test mailbox-level acceptability. 5. Use the verification result without sending a live email to the recipient. 6. Wait for the list to finish processing before exporting the results. At this stage, MillionVerifier is doing more than a basic pattern match. - **Syntax validation** checks whether the address is structurally correct. - **DNS and MX validation** checks whether the domain exists and is configured to receive email. - **Deep SMTP handshakes** test whether the receiving mail server appears to accept the mailbox, without sending the recipient an actual email message. That distinction is critical. A regex-only check might confirm that name@company.com looks like an email address. It does **not** tell you whether the mailbox exists or whether the domain is set up to receive mail. | Check Type | What It Confirms | Limitation | | ---------------------- | --------------------------------------------------------------- | ---------------------------------------------------------------------- | | Simple regex check | The address format looks valid | Cannot confirm domain readiness or mailbox status | | Deep SMTP verification | Syntax, domain mail setup, and mailbox-level acceptance signals | Some catch-all or protected servers may still return uncertain results | ![](https://www.millionverifier.com/content/images/2026/07/image9-1.png) ### Step 3: Segment the Results into Three Sending Tiers 1. Export the verified CSV from MillionVerifier. 2. Create separate filters or lists for **Valid**, **Invalid**, and **Unknown/Catch-All** emails. 3. Send all **Valid** emails to your primary cold email sequence. 4. Hard delete all **Invalid** emails. 5. Isolate all **Unknown/Catch-All** emails into a separate list. 6. Send the isolated **Unknown/Catch-All** segment only through a lower-risk drip strategy. 7. Do not mix **Unknown/Catch-All** records into your main verified campaign. 8. Review bounce and engagement data separately for each segment. Use this tiering exactly: - **Valid →** push to your primary cold email sequence - **Invalid →** hard delete immediately - **Unknown/Catch-All →** isolate for drip strategy This is where most outbound teams either protect their domain or quietly damage it. The mistake is not scraping the data. The mistake is treating every verification result the same. ![](https://www.millionverifier.com/content/images/2026/07/image2-1.png) ## How Should I Handle Catch-All Emails from a Scraped Batch? Catch-all domains accept mail for many or all inbox names at the server level, which means verification cannot always confirm whether a specific mailbox is truly active. That makes catch-alls inherently riskier than standard valid addresses, even after a verification pass. Use this rule: **Never exceed 15% catch-alls in a single daily send volume.** That means if you are sending 1,000 emails in a day, no more than 150 should come from your catch-all segment. Best practice for scraped batches: - Keep catch-alls in a separate segment - Send them after your fully valid addresses, not before - Use a slower drip strategy - Monitor bounce rate independently - Pause the segment if performance deteriorates Learn more about [**How to Handle Catch-All and Risky Emails**](https://www.millionverifier.com/blog/how-to-handle-catch-all-and-risky-emails-without-ruining-deliverability/) here. ![](https://www.millionverifier.com/content/images/2026/07/image1-3.png) ## Pre-Send Deliverability Checklist Before sending from your ESP, confirm the following: | Check | What to Confirm | | -------------------------- | ----------------------------------------------------------------------------------------- | | SPF | Your sending domain has a valid SPF record configured for the platform you use | | DKIM | DKIM signing is active and passing for your outbound mail | | DMARC alignment | DMARC is configured and aligned with your visible From domain | | Verified list status | Only the cleaned and verified list is uploaded to the live campaign | | Invalid emails removed | All invalid records have been hard deleted before launch | | Catch-alls isolated | Unknown and catch-all emails are excluded from the primary sequence | | Bounce threshold awareness | Your team is operating with a strict goal to stay below the 2% bounce-risk line | | ESP readiness | The campaign is being sent only after authentication and list hygiene checks are complete | ## Final Takeaway The safest B2B cold email workflow for scraped leads is simple: 1. Sanitize the raw export 2. Verify it deeply with MillionVerifier 3. Segment by risk before sending That process helps you avoid wasting credits, protects your domain from unnecessary bounce damage, and gives your primary sequence the best chance to land in inboxes. If you scrape first and verify second, you can still run outbound safely. If you scrape and send without verification, you are effectively asking your domain to absorb preventable risk. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. ### How to Handle Catch-All and Risky Emails (Without Ruining Deliverability) URL: https://www.millionverifier.com/blog/how-to-handle-catch-all-and-risky-emails-without-ruining-deliverability/ Last updated: 2026-09-01T08:47:57.000Z If you send B2B cold email, sooner or later you run into the same problem: a large chunk of your list gets labeled catch-all or risky. Those contacts may still be real, valuable prospects—but sending to them blindly can damage deliverability, waste budget, and increase bounce-related risk. ![](https://www.millionverifier.com/content/images/video-thumbnails/c46d50eee4e44aa73eb661e2422d36db8e009f26944b874de018ec2b8ce0ec36-1280.webp) The good news: you do not have to choose between deleting everything risky and spraying the whole list. With the right process, you can separate opportunity from danger and keep your sender reputation intact. ![](https://www.millionverifier.com/content/images/2026/07/image12.png) ## **What is a Catch-All Email Address?** A catch-all email address exists on a domain using an Accept-All server firewall that temporarily accepts nearly any mailbox request, even when the exact inbox cannot be verified in real time. This makes standard validation inconclusive, because the server masks whether the mailbox truly exists or is simply being provisionally accepted during verification checks. In practical terms, a catch-all domain is set up to accept incoming mail for any address on that domain, or at least to respond in a way that prevents basic mailbox verification tools from confirming whether a specific inbox truly exists. That creates a gray area for marketers: - The address may be valid - The address may be invalid - The server may be masking the answer on purpose For B2B senders, this matters because many legitimate companies use catch-all setups—especially larger organizations with strict IT controls. ![](https://www.millionverifier.com/content/images/2026/07/image28.png) ## **Why B2B Companies Use Catch-All Configurations** Catch-all configurations are not automatically a red flag. In many cases, they are a deliberate choice by corporate IT teams. Common reasons B2B companies use catch-all settings include: - Security and anti-harvesting protection: Accept-All behavior makes it harder for spammers and scrapers to discover valid inboxes. - Server-level firewalling: Some companies intentionally obscure mailbox status at the mail server level to reduce verification exposure. - Centralized inbox management: Messages sent to variations of employee names or departmental aliases can still be routed internally. - Legacy infrastructure: Older enterprise environments often preserve broad mail acceptance rules for compatibility. - Missed-opportunity prevention: Businesses do not want potentially valuable inbound emails rejected because of a typo, alias, or routing rule. So if your verifier marks a contact as catch-all, that does not mean “bad lead.” It means: handle carefully. ![](https://www.millionverifier.com/content/images/2026/07/image23.png) ## **Decoding the "Risky" Category** “Risky” is often misunderstood. It does not mean all addresses in the category should be treated the same way. In fact, some risky segments are worth testing, while others should usually be excluded immediately. ### Catch-All A catch-all address belongs to a domain that accepts or appears to accept all mailbox queries, making final mailbox confirmation difficult. From a pricing and operations standpoint, many verification platforms treat catch-all detection as a specialized problem and may charge more for deeper checks. That is why it is important to know whether your provider includes advanced recovery inside standard verification workflows—or turns it into a premium upsell. ### Unknown An unknown result means the verifier could not get a reliable server response at the time of the check. This can happen because of: - Temporary server timeouts - Greylisting - Connection throttling - Misconfigured mail servers - Strict filtering rules Unknown does not always equal invalid. But it does mean uncertainty is higher. Because these records are technically unusable for safe cold outreach, a fair verification partner should not charge credits for them. ### Disposable A disposable email is a temporary inbox, often created through a 10-minute email service. These addresses should always be deleted because: - They are not built for ongoing business communication - They rarely represent durable buying intent - They add unnecessary risk to outreach quality ### Role-Based A role-based email is tied to a function rather than a person, such as: - info@ - sales@ - support@ - admin@ These addresses may still be valid, but they are usually poor targets for personalized cold outreach because they are shared, filtered, or handled by multiple people. ![](https://www.millionverifier.com/content/images/2026/07/image15-1.png) ## **The Hidden Danger of Blasting a Catch-All List** The main danger with catch-all sending is the asynchronous bounce—also called a delayed hard bounce. Here is what happens: 1. Your email is accepted at the server’s front door. 2. Your sending platform reads that as successful delivery. 3. The receiving system then checks whether the specific inbox actually exists. 4. If it does not, the message is rejected internally after the initial acceptance. 5. That rejection is recorded as a hard bounce after the fact. This is why catch-all lists can be so deceptive. At first, everything looks fine. Then bounce signals begin to appear and your domain reputation can drop fast. For agencies and outbound teams, this matters because delayed hard bounces can: - Hurt sender trust with major mailbox providers - Reduce inbox placement - Trigger platform warnings - Damage your metrics inside Google Postmaster Tools - Compromise an otherwise healthy sending domain In short: server acceptance is not the same as safe deliverability. ## **The Agency Playbook: 3 Ways to Safely Send to Catch-Alls** If you absolutely must test unresolved catch-all emails, the goal is not volume. The goal is damage control. ### 1\. The 90/10 Ratio Never send a campaign made up entirely of catch-all emails. Instead: - Keep catch-alls at a strict 10% maximum of the total send - Mix them with clearly Valid emails - Use the strong base of valid contacts to dilute bounce risk ![](https://www.millionverifier.com/content/images/2026/07/image10-1.png) ### 2\. Warm Domains Only Never test catch-all segments on a fresh domain. Only use domains that have: - At least 30+ days of clean sending history - Stable engagement patterns - Strong existing reputation - No recent bounce-related warnings ![](https://www.millionverifier.com/content/images/2026/07/image22.png) ### 3\. The "Guaranteed Formatting" Rule Pattern consistency matters. If confirmed valid contacts from the same company follow a strict pattern such as: - first.last@company.com Then: - Keep catch-all contacts that match that exact structure - Discard anomalies like firstname123@company.com or odd alias variations - Treat formatting mismatches as higher risk This simple filtering step helps remove guesswork when catch-all data cannot be fully resolved. ### Stop Paying Premium Ping Services A common industry tactic is to label large blocks of email addresses as “Risky,” then force marketers to export those records and pay again for secondary pinging or deeper verification. That model gets expensive fast, especially for agencies and high-volume B2B teams managing large prospect databases. The better alternative is a verification workflow where deeper analysis is built into the process—not sold as a penalty every time you upload a difficult list. ### The MillionVerifier Advantage: Deep-Level Verification MillionVerifier’s Smart Verify positioning is simple: help teams recover more value from risky datasets without creating a billing trap. Key advantages include: - Recover up to 30%–40% of catch-all leads through deep-level verification - Zero extra fees for advanced catch-all handling - One standard credit per email, even for deeper analysis - Seamless workflow with no need for separate premium ping services - Recovered emails are automatically sorted into standard Valid and Invalid columns - 99%+ accuracy across validation outcomes - 100% money-back guarantee for added confidence For B2B SaaS teams, agencies, lead gen operators, and outbound teams, that means you can test more intelligently without overpaying to do it. Instead of treating every catch-all as dead weight, you can process the list through a system built to identify where the real opportunities still exist. ![](https://www.millionverifier.com/content/images/2026/07/image27.png) ## **When to Walk Away: The "Delete" Threshold** Not every risky email deserves another chance. There should be a clear point where deleting records is the smarter business decision. A strong delete threshold usually includes addresses that are: - Disposable - Obviously malformed - Repeatedly unresolved as unknown after proper verification attempts - Role-based, if they fall outside your outreach policy - Attached to poor-quality sources - Unnecessary to your ICP targeting You should also walk away when: - The list source is questionable - The domain shows multiple risk indicators - The segment would require too much sending risk for too little upside - The economics do not justify more effort - Your overall domain reputation is slipping - Your sending platform warns of high bounce rates Hard rule: if your domain reputation is declining or your sending platform starts warning you about bounce risk, delete all remaining catch-all emails until your sender score stabilizes. The goal is not to save every record. The goal is to maximize safe revenue potential while minimizing reputation damage. Good list hygiene is not about being aggressive or conservative. It is about being selective. ## **FAQ** #### Are catch-all emails always bad? No. Many catch-all emails belong to legitimate B2B companies using protective mail server configurations. The issue is not that they are automatically bad—it is that they cannot be confirmed with the same certainty as standard valid inboxes. #### Can catch-all emails bounce later even if they seem accepted at first? Yes. That is one of the biggest risks. Some failures happen asynchronously, meaning the server initially accepts the message before rejecting it later. #### Should I send to all risky emails? No. Risky categories are not equal. Disposable emails should be removed, while some catch-all emails may still be worth testing carefully. Unknown and role-based emails require policy-based decisions. #### What is a safe way to send to catch-all emails? Use a limited ratio, send only from warm domains, and make sure your records are clean and correctly formatted. A controlled testing approach is far safer than a full-volume blast. #### Why do some email verification tools charge more for catch-all checks? Because catch-all verification is more complex and often requires deeper logic or additional server analysis. Some providers pass that complexity on as premium pricing. #### Should providers charge for Unknown emails? No. Because Unknown results are technically unusable for safe cold outreach, a fair verification provider should not charge credits for them. #### How can Smart Verify help with risky lists? Smart Verify helps identify recoverable opportunities inside risky segments, including catch-all emails, without forcing you into separate premium ping workflows. It is designed to improve list value while protecting deliverability economics. #### What should I delete immediately? In most B2B workflows, you should strongly consider deleting disposable emails, malformed addresses, low-quality imports, and any risky segments that do not match your targeting or sending policy. ![](https://www.millionverifier.com/content/images/2026/07/image17-1.png) --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. ### How Email Verification Works: The MillionVerifier Process URL: https://www.millionverifier.com/blog/how-email-verification-works-the-millionverifier-process/ Last updated: 2026-09-01T08:42:36.000Z ## **What You’ll Learn** - What deep-level email verification really means - Why regex and simple syntax checks are not enough - How MillionVerifier verifies every email step by step - What happens during the SMTP handshake - How greylisting is resolved automatically - Why Smart Verify improves accuracy on hard-to-classify emails - How the same engine supports both bulk uploads and real-time API use - Why MillionVerifier backs its results with a 100% money-back guarantee ![](https://www.millionverifier.com/content/images/video-thumbnails/8e2df7bd3c3b2888a1bfcb94ae04cb0ba0fa1089736972a48814fb89b9a84fa8-1280.webp) Email verification is easy to misunderstand because many people assume an address is valid if it simply looks correct. In reality, a properly formatted email address can still bounce, belong to a disposable inbox, point to a dead domain, or sit behind a strict mail server that weak tools cannot interpret. MillionVerifier was built to solve that problem at a deeper level. This guide explains exactly how the MillionVerifier process works behind the scenes, from basic syntax cleanup to deep SMTP-level checks, greylisting resolution, and Smart Verify accuracy enhancements. If you want to understand how professional email verification actually protects sender reputation, campaign ROI, and deliverability, this is the process. ## **What Is Deep-Level Email Verification?** Deep-level email verification is the process of checking not only whether an email address is properly formatted, but whether the domain is live, the mail server is configured correctly, and the inbox can actually receive messages. Unlike simple syntax validation, deep-level verification uses DNS, MX record analysis, SMTP server checks, disposable email detection, role-account detection, and retry logic to determine whether an email is truly safe to send to. ![](https://www.millionverifier.com/content/images/2026/07/image7.png) ## **The Myth of Regex: Why Simple Syntax Checks Fail** A surprising number of developers still try to validate emails using regular expressions. The logic seems reasonable at first glance: if an address contains an @ sign, a domain, and a valid-looking structure, it must be okay. But that approach fails in real-world sending. A regex check can only answer one question: **Does this email address look valid?** It cannot answer the questions that actually matter for deliverability: - Does the inbox exist? - Is the domain active? - Does the domain accept mail? - Is this a temporary disposable address? - Is this a role-based inbox that may hurt outreach performance? - Is the server temporarily rejecting verification attempts? - Is the domain protected by catch-all behavior or strict firewall rules? For example, an address like john@company-example.com may pass a regex test perfectly. But if the domain is inactive, the MX record is missing, or the receiving server rejects the user as nonexistent, that address is not sendable. That is why syntax-only validation is dangerously inadequate. A syntax check tells you whether an address **looks right**. Deep verification tells you whether the inbox is **actually real and usable**. For businesses sending cold email, onboarding users, cleaning CRM databases, or protecting marketing deliverability, that difference is everything. ![](https://www.millionverifier.com/content/images/2026/07/image1-1.png) ## **The 5-Step Verification Engine (Behind the Scenes)** MillionVerifier processes every email through a chronological multi-layer verification workflow. This is what builds trust in the result. Instead of stopping at surface-level checks, the engine works through a full decision system to determine whether the email should be marked safe, risky, or invalid. Here’s what happens behind the scenes. ### **Step 1: Syntax and Formatting Validation** This is the baseline layer. Before deeper verification begins, MillionVerifier first checks whether the email address is structurally sound and normalized properly. This includes: - Removing accidental spaces - Correcting common formatting inconsistencies - Catching obvious fat-finger mistakes - Ensuring the address follows recognized IETF-compliant formatting standards - Identifying malformed local or domain parts This step is important, but it is only the starting point. A cleaned and properly formatted email still may not be deliverable. That is why the process immediately moves to domain and mail-server checks. ### **Step 2: Domain and MX Record DNS Checks** Once the email structure passes the first stage, MillionVerifier checks the domain itself. This happens through DNS inspection. The engine verifies: - Whether the domain is active - Whether the domain resolves correctly - Whether valid MX (Mail Exchange) records are present - Whether the domain is technically able to receive email If the domain is dead, misconfigured, or missing valid MX records, the email is immediately marked **Invalid**. This is a critical step because many bounced emails are not caused by bad usernames. They come from domains that simply cannot receive mail anymore. A regex validator will completely miss this. MillionVerifier does not. ### **Step 3: Disposable & Role-Based Account Detection** Next, MillionVerifier checks whether the email belongs to a category that may be technically reachable but strategically low-value. This includes two important types of addresses. #### **Disposable Email Addresses (DEAs)** Disposable email addresses are temporary inboxes created for short-term use, often through 10-minute mail providers or throwaway inbox services. MillionVerifier checks the address against a continuously updated database of disposable email providers to identify these accounts before they pollute your list. Why this matters: - Disposable users are rarely long-term customers - They distort conversion and engagement data - They lower list quality - They create noise in SaaS signups and lead capture funnels #### **Role-Based Emails** MillionVerifier also flags role-based accounts such as: - admin@ - support@ - sales@ - info@ - contact@ These addresses are often real, but they can skew campaign results in cold outreach and B2B prospecting. Why? Because role-based inboxes: - Are shared by multiple people - Often produce lower reply rates - Can trigger spam filtering more easily in some workflows - Rarely behave like direct personal contacts in outbound campaigns This step helps users separate technically valid emails from strategically ideal ones. ![](https://www.millionverifier.com/content/images/2026/07/image14.png) ### **Step 4: The Invisible SMTP Handshake (Deep Pinging)** This is the core of deep-level verification. At this stage, MillionVerifier’s servers connect directly to the recipient’s mail server, whether it is run by Google, Microsoft, Yahoo, or a private business mail infrastructure. The goal is to simulate the beginning of a real email delivery attempt without actually sending an email. In simple terms, the process works like this: - MillionVerifier opens a connection to the recipient mail server - It starts the SMTP conversation exactly as a real sender would - The receiving server is asked whether the specific mailbox exists - If the server confirms the recipient is valid, MillionVerifier records that signal - The connection is then dropped before any actual message content is transmitted No email is delivered to the target inbox. No message is seen by the recipient. No actual send occurs. This “deep pinging” approach is what allows MillionVerifier to move beyond guesswork and check real mailbox existence directly at the server level. This is also the point where weaker verification tools start to fail. Many tools stop too early, rely on shallow heuristics, or return uncertain classifications. MillionVerifier continues deeper. ![](https://www.millionverifier.com/content/images/2026/07/image9.png) ### **Step 5: Advanced Greylisting Resolution** Some mail servers are intentionally strict. Instead of giving a clear answer immediately, they temporarily reject requests from unknown IP addresses or unfamiliar senders. This behavior is known as **greylisting**. Greylisting is not a permanent rejection. It is a delay tactic. The server is essentially saying: **“Come back later, and I may give you a proper answer.”** Many verification systems mishandle this moment. They either: - Give up too quickly - Return an inconclusive status - Mark the result as Unknown by default MillionVerifier handles it differently. Its engine automatically: - Detects greylisting behavior - Pauses the verification attempt - Waits the appropriate amount of time - Retries the connection in the background - Continues until it gets a more definitive response whenever possible This retry logic is a major reason why MillionVerifier can produce stronger, more usable results than tools that stop at the first temporary roadblock. In plain English: if a strict server says “not now,” MillionVerifier does not assume “never.” It waits, retries, and works to get the real answer. ![](https://www.millionverifier.com/content/images/2026/07/image4.png) ## **How “Smart Verify” Achieves 99%+ Accuracy** The five-step engine is the foundation, but MillionVerifier’s accuracy advantage goes further. Smart Verify is the proprietary layer that helps classify emails that other tools struggle with, especially: - Catch-all domains - Strict corporate mail servers - B2B environments with aggressive filtering rules - Servers that produce ambiguous or inconsistent responses Instead of relying only on a single live response, Smart Verify uses a broader intelligence model built from: - Real-life sending data - Historical server behavior - Pattern recognition from past verification outcomes - Response trends across similar environments This matters because not every server behaves in a simple yes-or-no way. Some domains accept all RCPT checks during SMTP and then silently bounce later. Others obscure mailbox-level truth behind security layers. Still others behave differently depending on timing, IP familiarity, or infrastructure policies. Smart Verify helps MillionVerifier make better judgments in these edge cases. That is how the platform pushes beyond generic verification logic and reaches **99%+ accuracy**, particularly where lower-grade tools fall back to guesswork or overuse “Unknown” results. ![](https://www.millionverifier.com/content/images/2026/07/image10.png) ## **Bulk vs. API: How the Engine Adapts to Scale** Email verification needs are rarely one-size-fits-all. Some users need to clean enormous databases before launching campaigns. Others need to verify addresses in real time inside signup forms, CRMs, lead capture flows, or product workflows. MillionVerifier is designed for both. ### **For Bulk Verification** Lead generation teams, agencies, and data vendors can upload massive CSV files, including lists with millions of rows. This is ideal for: - List cleaning before cold outreach - Database hygiene projects - CRM maintenance - Re-engagement campaigns - Acquisition list preparation ### **For Real-Time API Verification** SaaS companies and high-volume platforms often need instant verification the moment a user submits an email. This is ideal for: - Signup forms - Trial registration flows - CRM enrichment pipelines - Product onboarding systems - Marketplace and platform user validation ### **Same Engine, Same Logic** The important reassurance is this: Whether you upload a 2-million-row CSV or call the API hundreds of times per second, the same five-step verification engine is applied. That means users get: - The same deep SMTP-level logic - The same DNS and MX checking - The same disposable and role-based screening - The same greylisting resolution methodology - The same Smart Verify intelligence layer In other words, scale does not mean reduced rigor. The process remains consistent, fast, and engineered for high-volume reliability. ![](https://www.millionverifier.com/content/images/2026/07/image3-1.png) ## **The 100% Money-Back Guarantee: Putting Our Engine on the Line** Most verification platforms talk about accuracy. Very few are willing to financially stand behind it. MillionVerifier does. Because its five-step verification engine and Smart Verify system are built to deliver exceptionally accurate outcomes, MillionVerifier offers a **100% money-back guarantee** tied directly to result quality. This is not just a marketing promise. It is a confidence signal grounded in the technology itself. For agencies and senders, that matters. If you are paying to clean a list, you do not just want theoretical protection. You want real financial safety tied to performance. MillionVerifier’s position is simple: - If an email is marked **Ok**, it should perform as expected within the platform’s guarantee framework - If hard bounce rates exceed the expected threshold on those validated emails, the customer is protected - The guarantee aligns product claims with measurable outcomes That creates a rare level of trust in the verification market. The message is clear: MillionVerifier is confident enough in its engine to put money behind the results. ## **Why This Process Matters for Senders** When verification is shallow, the damage shows up later: - Higher hard bounce rates - Lower sender reputation - Lost inbox placement - Wasted outreach spend - Dirty CRM data - Distorted conversion metrics When verification is deep, those risks drop. MillionVerifier’s process helps businesses: - Protect deliverability - Improve outreach efficiency - Clean lead databases - Reduce wasted sends - Improve campaign reporting accuracy - Verify at scale without sacrificing technical rigor ## **Final Takeaway** Email verification is not just about finding an @ sign and a valid-looking domain. It is about determining whether an inbox is truly real, reachable, and worth sending to. That is why MillionVerifier goes far beyond syntax checks. From formatting validation and DNS inspection to SMTP deep pinging, disposable detection, greylisting retries, and Smart Verify intelligence, the platform is built to produce decisions you can actually trust. If your sender reputation, campaign ROI, and data quality matter, deep-level verification is not optional. It is infrastructure. ## **Ready to Verify with Confidence?** Use MillionVerifier to clean your lists, validate signups in real time, and reduce bounce risk with a verification engine built for accuracy. **Start verifying your emails with MillionVerifier and use a platform confident enough to back its results with a 100% money-back guarantee.** ## **FAQ** #### What is the difference between syntax validation and deep email verification? Syntax validation checks whether an email address is formatted correctly. Deep email verification goes further by checking whether the domain is active, whether mail servers are configured properly, whether the inbox exists, and whether the address is risky due to disposable, catch-all, or role-based behavior. #### Can regex verify whether an email inbox exists? No. Regex can only check formatting patterns. It cannot confirm that the inbox exists, that the domain can receive mail, or that the receiving server recognizes the mailbox. #### What is an MX record in email verification? An MX record is a DNS record that tells the internet which mail server is responsible for receiving email for a domain. If a domain has no valid MX record, it usually cannot receive email properly. #### Does MillionVerifier send a real email during verification? No. During deep SMTP verification, MillionVerifier simulates the beginning of a delivery conversation with the recipient server, then disconnects before any actual message is sent. #### ****What is greylisting?** Greylisting is a mail server defense mechanism that temporarily rejects unknown senders or connections. Legitimate systems often retry later, so a proper verification engine must detect this behavior and retry instead of returning an immediate inconclusive result. #### ****What are disposable email addresses?** Disposable email addresses are temporary inboxes created for short-term use through throwaway email services. They are often low-value for SaaS onboarding, lead generation, and long-term customer communication. #### ****Why are role-based emails flagged?** Role-based addresses like support@, sales@, or admin@ are often shared inboxes. While they may be valid, they can reduce outreach precision and skew cold email metrics compared to direct person-level contacts. #### ****What is a catch-all domain?** A catch-all domain is configured to accept email for many or all mailbox names, even if the exact inbox may not truly exist as a normal user mailbox. These domains are harder to classify accurately, which is why Smart Verify is important. #### ****Is the same verification process used for bulk uploads and API calls?** Yes. Whether you upload a very large CSV list or verify emails in real time via API, MillionVerifier applies the same deep verification logic and core process. #### ****Why does the money-back guarantee matter?** The guarantee shows that MillionVerifier is willing to financially stand behind the quality of its verification results. It turns technical confidence into practical business protection. ### The Developer’s Guide to Real-Time Email Verification & APIs URL: https://www.millionverifier.com/blog/the-developers-guide-to-real-time-email-verification-apis/ Last updated: 2026-08-07T12:04:47.000Z - Real-time email verification helps validate addresses at the point of entry, before bad data reaches your database. - For developers, the main value is operational: fewer bounced emails, cleaner CRM records, lower fraud risk, and better signup quality. - API-based verification can support common enforcement rules such as blocking disposable domains, flagging free email providers, and suggesting typo corrections. - A well-designed integration balances latency, UX, and reliability by combining synchronous checks with asynchronous follow-up where needed. - Response payloads matter: developers should interpret fields like result, free, and didyoumean in the context of product policy. - Implementation is typically straightforward: capture the email, call the API, evaluate the JSON response, and decide whether to allow, warn, or block. [Get Your API Key](https://app.millionverifier.com/email%5Fverify?ref=millionverifier.com#api) & [Read the Documentation](https://developer.millionverifier.com/?ref=millionverifier.com) ![](https://www.millionverifier.com/content/images/video-thumbnails/0f045f3bcd103ccf3597dc143bb1fb3ba7c6ba11d62d35dcc9a6439d1483d197-1280.webp) ## **What is Real-Time Email Verification?** Real-time email verification is an API-driven process that validates an email address at the exact moment of entry—typically on a signup or checkout form. It returns a sub-second JSON response, allowing systems to block invalid, disposable, or high-risk emails before they enter the database. For developers, this is fundamentally a data-quality and risk-control layer. Instead of accepting every submitted address and cleaning the list later, your application can evaluate the email during signup, checkout, lead capture, or account creation. In practice, a real-time verification API is often used to answer questions like: - Is the email syntactically valid? - Does the domain appear to accept mail? - Is the address associated with a disposable email provider? - Is it a free email account when your workflow requires a business domain? - Is there a likely typo in the domain, such as gmal.com instead of gmail.com? The exact checks and response times vary by provider, and claims such as sub-second responses or 99.9% SLA uptime should be treated as product positioning unless confirmed in the official documentation. But the architectural pattern is consistent: submit an email, receive a JSON response, and apply your business rules immediately. ![](https://www.millionverifier.com/content/images/2026/07/image7-59.png) ## **The Hidden Cost of Post-Signup Bulk Cleaning** Bulk email cleaning has its place, especially for legacy databases. But relying on it as your primary defense means bad records have already entered your systems. **That creates downstream costs:** - **Wasted acquisition spend**: You pay to acquire users or leads that were never reachable. - **Broken lifecycle automation**: Invalid addresses trigger failed onboarding, abandoned nurture flows, and incomplete customer journeys. - **Dirty analytics**: Conversion rates, activation metrics, and funnel attribution become less trustworthy. - **Support overhead**: Teams spend time investigating “missing emails” that were undeliverable from the start. - **Fraud exposure**: Disposable or low-quality signups can consume free-trial resources before they are ever reviewed. From an engineering perspective, post-signup cleaning is reactive. Real-time verification is preventive. It reduces the need for later remediation jobs, manual review queues, and CRM cleanup projects. **A practical strategy is often hybrid:** 1. Verify new emails in real time. 2. Periodically clean older records in bulk. 3. Feed both workflows into the same suppression and risk logic. That approach keeps new data clean while improving the quality of historical records over time. ## **Defeating SaaS Free-Trial Abuse: Blocking Disposable Emails** If you run a SaaS product with a free trial, disposable email detection is one of the most immediately useful controls you can add. Temporary inbox services make it easy for users to create repeated accounts, bypass trial limits, and consume free-tier resources with little friction. A real-time email verification API can help by checking whether the submitted domain belongs to a known disposable email provider. In the MillionVerifier positioning provided in the brief, this is framed as a real-time database of 10-minute mail domains that can be used to reject temporary signups before an account is created. **That matters because disposable signups can distort core SaaS metrics:** - trial-to-paid conversion rate - user activation rate - product-qualified lead counts - onboarding completion metrics - infrastructure usage per trial cohort **A typical implementation pattern is sim**ple: 1. user submits signup form 2. backend sends email to verification API 3. API returns a disposable-email signal 4. application blocks the signup or routes it to manual review Example policy: JavaScript ``` if (verification.result === "disposable") { return res.status(400).json({ error: "Please use a permanent business email address." }); } ``` This is one of the clearest examples of why real-time verification is not just about deliverability—it is also about abuse prevention. ## **Enforcing B2B Signups: How to Block Free Email Providers** Many B2B companies do not want demo requests, lead forms, or account applications submitted with personal inboxes like @gmail.com, @yahoo.com, or @outlook.com. That is not because free email accounts are inherently invalid. It is because they often reduce lead quality, complicate account qualification, and make firmographic enrichment less reliable. If the verification API returns a field such as `free: true`, developers can use that signal to enforce a work-email-only policy. Example backend logic: JavaScript ``` if (verification.free === true) { return res.status(400).json({ error: "Please enter your corporate email address to continue." }); } ``` This is especially useful when your product or sales motion is explicitly B2B-only. It helps: - improve lead routing - reduce unqualified demo requests - preserve cleaner account data - increase the accuracy of company-level enrichment One important nuance: not every form should use the same rule. A newsletter signup may allow free email accounts, while an enterprise demo request may require a corporate domain. ![](https://www.millionverifier.com/content/images/2026/07/image6-4.png) ## **API Architecture & Latency (Built for Scale)** Developers care about one thing before almost anything else: will this API slow down my application? For real-time verification to work in production, latency must be low enough that users do not feel friction during form submission. The brief positions MillionVerifier as delivering sub-second responses with 99.9% SLA uptime and the ability to handle concurrent requests during high-traffic events. **Those are the right architectural goals for this category of API:** - low median response time - predictable tail latency - graceful degradation under load - stable uptime - concurrency support for signup spikes, launches, and campaigns **In implementation terms, you should still design defensively:** - set client-side and server-side timeouts - avoid blocking critical flows indefinitely - log latency and failure rates - define fallback behavior for uncertain responses Even when a provider advertises strong performance, your application should assume that networks fail, upstream services degrade, and edge cases will happen. ## **Handling Greylisting & Timeouts (Synchronous vs. Asynchronous)** One of the biggest concerns with email verification APIs is SMTP-level uncertainty. Some receiving mail servers use greylisting, a behavior that temporarily delays or rejects unfamiliar verification attempts. If an API waits too long trying to get a definitive answer from the remote server, your frontend can stall and your signup flow can suffer. That is why a good real-time verification architecture does not aim for perfect certainty on every request. It aims for fast, usable answers within a strict latency budget. **The pattern developers want is this:** - return a definitive result quickly when possible - return an unknown or equivalent status when certainty would take too long - avoid holding the request open for 10–15 seconds just to chase an edge-case SMTP response **A practical routing model looks like this:** - valid -> allow - invalid -> block - disposable -> block or review - free\_email -> block only on B2B-gated forms - unknown / timeout -> allow cautiously, then recheck asynchronously This protects both UX and system reliability. Your application remains responsive, and your operations team can still review uncertain addresses later if needed. ## **Interpreting the API Response: The JSON Payload** The exact response schema depends on the provider, but developers typically wire their logic around a small set of high-value fields. Here is an example payload structure matching MillionVerifier's v3 API response: JSON ``` { "email": "alex@gnail.com", "quality": "bad", "result": "invalid", "resultcode": 6, "subresult": "string", "free": false, "role": false, "didyoumean": "alex@gmail.com", "error": "" } ``` Here is how to think about the key fields: - **result**: The primary verification outcome. Values include `ok`, `catch_all`, `unknown`, `error`, `disposable`, or `invalid`. - **quality**: A high-level assessment of the email (e.g., good, bad, risky). - **free**: Indicates whether the mailbox provider is a consumer/free provider rather than a corporate domain. - **role**: Indicates if the email is a role-based address (e.g., admin@, support@). - **didyoumean**: A suggested correction when the domain appears mistyped. - **subresult**: Provides granular diagnostic insight into why a specific result was returned. **Example routing logic:** JavaScript ``` switch (verification.result) { case "invalid": block("Please enter a valid email address."); break; case "disposable": block("Disposable email addresses are not allowed."); break; case "unknown": case "error": allowWithReview(); break; case "ok": case "catch_all": if (verification.free === true) { block("Please use your work email address."); } else { allow(); } break; default: allowWithReview(); } ``` This is where the API becomes operationally useful: the JSON payload maps directly to product rules. ## **Improving UX with Real-Time Typo Correction** A hard rejection is not always the best user experience—especially when the user’s intent is valid but the domain is mistyped. For example, if someone enters alex@gnail.com, the best outcome may be to catch the likely typo and suggest alex@gmail.com before the form is submitted. **That helps you:** - rescue legitimate leads - reduce frustration - improve form completion rates - prevent avoidable bounce events A frontend prompt might look like this: JavaScript ``` if (verification.didyoumean) { showSuggestion(`Did you mean ${verification.didyoumean}?`); } ``` This is one of the strongest arguments for combining backend enforcement with frontend guidance. The backend protects the system; the frontend improves the user journey. ## **Frontend vs. Backend Integration Strategies** Developers often ask whether email verification should happen in the browser or on the server. The answer is straightforward: backend verification is required for enforcement. Frontend validation can improve responsiveness and UX, but it is not a security boundary. A malicious actor can bypass JavaScript checks, replay requests, or submit directly to your backend. **The safest architecture is:** - **Frontend**: basic syntax validation, loading states, typo suggestions, inline messaging - **Backend**: API authentication, verification request, final allow/block decision, audit logging **This is especially important when you are:** - blocking disposable domains - enforcing B2B-only signup rules - protecting free trials - preventing abuse at scale If the rule matters to the business, enforce it on the server side. ![](https://www.millionverifier.com/content/images/2026/07/image1-428.png) ## **Security, Rate Limiting, and GDPR Compliance** Any external verification API introduced into your signup flow should be reviewed like any other infrastructure dependency. At minimum, developers and IT teams will want to evaluate: - **API key security** - Store API keys server-side only. - Never expose secret credentials in frontend JavaScript. - Rotate keys according to your internal security policy. - **Rate limiting** - Expect rate limits and handle them gracefully. - Retry only when the provider’s guidance allows it. - Use exponential backoff for transient failures. - Define fallback behavior for quota exhaustion. - **Privacy and compliance** - The brief calls for strict GDPR compliance and no long-term data storage from API endpoints. Those are important claims, but they should be confirmed directly in the provider’s official compliance and privacy documentation. From an implementation standpoint, you should still: - minimize the personal data you transmit - document the processor/subprocessor relationship if applicable - review retention behavior - align your privacy notice and vendor review process accordingly Security and compliance are not afterthoughts. They are part of production readiness. ![](https://www.millionverifier.com/content/images/2026/07/image8-1.png) ## **Getting Started: The 5-Minute Implementation** A minimal implementation can usually be broken into five steps. **1\. Get credentials** Create an account, generate an API key, and review the authentication method in the docs. **2\. Decide your enforcement policy** Before writing code, define what each signal means in your application. For example: - invalid email -> block - disposable email -> block free trial - free email -> block enterprise demo form - typo suggestion -> prompt user to confirm - timeout -> allow and recheck asynchronously **3\. Add the API call** Integrate the verification request in your signup, checkout, or lead form flow. **4\. Parse the JSON response** At minimum, inspect: - result - free - role - didyoumean **5\. Instrument and iterate** Track: - verification success/failure rates - block rates by reason - typo correction acceptance - timeout frequency - conversion impact A simple backend pseudocode example: JavaScript ``` async function handleSignup(email) { const verification = await verifyEmail(email); if (verification.result === "invalid") { return { allowed: false, message: "Please enter a valid email address." }; } if (verification.result === "disposable") { return { allowed: false, message: "Please use a permanent email address." }; } if (verification.free === true) { return { allowed: false, message: "Please use your work email address." }; } if (verification.didyoumean) { return { allowed: true, suggestion: verification.didyoumean }; } return { allowed: true }; } ``` From there, you can refine the logic by form type, customer segment, and risk tolerance. ## **Frequently Asked Questions** #### Is real-time email verification better than bulk email cleaning? For new signups, yes - because it prevents bad data from entering your systems in the first place. Bulk cleaning is still useful for historical databases, but it is not a substitute for point-of-entry validation. #### Can I block disposable email addresses during signup? Yes. If your verification provider returns a disposable-email signal (such as result: "disposable" in MillionVerifier's API), you can intercept it. Whether you hard block or soft warn depends on your product policy. #### How do I block free email providers for B2B forms? Use the API response field that distinguishes consumer mailbox providers from business domains (in MillionVerifier, this is checking if free: true), then enforce that rule only on the forms where it matters. #### What does a "catch\_all" result mean? A catch\_all result indicates that a domain accepts mail for any and all recipient names at that domain, even if the specific inbox doesn't technically exist. This can make verification less definitive. It is usually best treated as a caution flag rather than an automatic rejection. #### Should verification happen on the frontend or backend? For most production systems, backend enforcement is the safer default. Frontend validation is useful for UX, but final decisions should usually be enforced server-side. #### What if the API times out? Do not let every timeout become a lost conversion. Many teams allow the submission, mark the record for asynchronous review, and apply downstream controls if needed. --- [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) --- Why Choose Millionverifier ![99%+ Accuracy Rate](https://www.millionverifier.com/content/images/2026/06/accuracy_rate_hero-1.webp) We have kept improving our email verification software for over six years now, and we are incredibly proud of our outstanding 99%+ email verification accuracy. ![Best Email Verification Prices](https://www.millionverifier.com/content/images/2026/06/best_email_verification_prices_hero-1.webp) We have created MillionVerifier to provide the best email verification service possible for email marketers with higher email verification needs. ![Excellent Verification Service](https://www.millionverifier.com/content/images/2026/06/excellent_email_verification_service_hero--2-.webp) Our customers love what we do. We work hard to deliver the best results and user experience for our customers. ### The Ultimate Guide to Email Deliverability & Sender Reputation URL: https://www.millionverifier.com/blog/the-ultimate-guide-to-email-deliverability-sender-reputation/ Last updated: 2026-09-18T09:35:12.000Z - **Email deliverability is about inbox placement, not just accepted delivery.** A message that reaches the server but lands in spam is not a deliverability win. - **Sender reputation is earned over time** through strong authentication, clean data, and positive subscriber engagement. - **Modern mailbox providers reward trustworthy senders** and filter senders with high complaints, poor hygiene, or weak technical setup. - **The practical path to better deliverability** is straightforward: authenticate your domain, clean your list, monitor reputation, reduce complaints, and test before sending. ![](https://www.millionverifier.com/content/images/video-thumbnails/991c2e4f0db19552e0c346bf80ebaa22960a6acf63f7b13ceec373d997d9f0e8-1280.webp) ## What is Email Deliverability? Email deliverability is the rate at which your emails successfully reach the intended recipient’s primary inbox, not merely whether a receiving server accepts the message. True deliverability measures inbox placement, visibility, and trust. Server “delivery” alone is not enough if your campaigns land in spam, promotions, or get blocked. For marketers, this distinction matters. Your ESP may report that 99% of emails were “delivered,” but that only means the receiving server accepted them. It does **not** mean subscribers saw them in the inbox where they were likely to engage. Real deliverability is about **earned inbox placement**. ![](https://www.millionverifier.com/content/images/2026/06/image9.png) ## The 3 Pillars of Sender Reputation Sender reputation is the trust score mailbox providers assign to your sending domain, IPs, and mail streams. Most reputation systems revolve around three core pillars: ### 1\. Technical Authentication Mailbox providers want proof that your email is genuinely from you. This requires properly configured: - SPF, DKIM, and DMARC - TLS connection encryption - Valid forward and reverse DNS records ### 2\. List Hygiene A clean list protects your reputation, while a dirty list creates hard bounces. This is where verification matters. The MillionVerifier Bulk Email Verifier can help you identify invalid or risky addresses before campaigns go out and maintain ongoing CRM hygiene to keep your hard bounce risk low over time. ![](https://www.millionverifier.com/content/images/2026/06/image7.png) ### 3\. Subscriber Engagement Providers increasingly use **engagement-based filtering**, focusing on behavior over "spam trigger words." - **Positive signals:** Opens, clicks, replies, and moving messages from spam to the inbox. - **Negative signals:** Spam complaints, deleting without reading, and low engagement over time. ![](https://www.millionverifier.com/content/images/2026/06/image1-1.png) ## The 2026 Sender Guidelines (Google, Yahoo, & Microsoft) By 2026, bulk senders must prove identity, respect recipients, and maintain low complaint rates. ### Core Expectations Bulk senders should authenticate mail (SPF, DKIM, DMARC), use TLS encryption, maintain valid DNS records, and support one-click unsubscribes. ### Complaint Rate Thresholds A critical benchmark for bulk senders is the spam complaint rate: - **Maintain a spam complaint rate consistently below 0.10%** - **Strictly never exceed 0.30%** Exceeding these thresholds can cause inbox placement to deteriorate quickly, leading to throttling or routing to the spam folder. ![](https://www.millionverifier.com/content/images/2026/06/image2-1.png) ## Email Authentication: SPF, DKIM, and DMARC Authentication is the foundation of sender trust, ensuring messages are authorized and untampered with. - **SPF (Sender Policy Framework):** Specifies which servers are allowed to send email on behalf of your domain. - **DKIM (DomainKeys Identified Mail):** Adds a cryptographic signature to verify the message was authorized and not altered in transit. - **DMARC (Domain-based Message Authentication, Reporting, and Conformance):** Ties SPF and DKIM to the "From" domain and tells providers what to do if authentication fails (None, Quarantine, or Reject). ![](https://www.millionverifier.com/content/images/2026/06/image11.png) ### How to Fix Email Authentication 1. **Audit DNS records:** Confirm SPF, DKIM, and DMARC are published correctly. 2. **Check alignment:** Ensure the visible "From" domain aligns with SPF/DKIM. 3. **Avoid SPF bloat:** Consolidate vendors to avoid too many DNS lookups. 4. **Enable signing:** Ensure every sending platform (CRM, ESP) signs mail properly. 5. **Start DMARC with monitoring:** Use p=none first, then move toward enforcement. 6. **Verify transport:** Ensure TLS encryption and valid reverse DNS are in place. ## How to Monitor and Repair Domain Reputation Reputation is dynamic and should be reviewed on a **rolling 30-day basis**. ### Tools and Monitoring **Google Postmaster Tools** is a vital free resource for monitoring domain reputation, IP reputation, spam rates, and authentication status for Gmail users. ### How to Repair Reputation If your reputation slips: 1. **Reduce complaints immediately:** Pause sends to cold segments and keep complaints below 0.10%. 2. **Remove invalid addresses:** Clean lists and suppress hard bounces. 3. **Tighten segmentation:** Send only to your most recent openers and clickers. 4. **Review acquisition:** Eliminate purchased or scraped data. 5. **Confirm technicals:** Re-verify SPF, DKIM, and DMARC. 6. **Warm up carefully:** Gradually increase volume by starting with your most engaged users. ## Avoiding the Spam Folder: Why Good Emails Get Filtered Creative quality alone doesn't protect you. Emails are often filtered due to weak authentication, sudden volume spikes, or poor domain reputation. **Engagement-based filtering beats spam-word myths.** Modern filters care more about sender reputation and recipient behavior than specific "trigger words" like "Free" or "Urgent." To improve placement, prioritize engaged users, maintain a consistent sending cadence, and make unsubscribing effortless. ![](https://www.millionverifier.com/content/images/2026/06/image6.png) ## The One-Click Unsubscribe Rule (RFC 8058) Under **RFC 8058**, senders can support one-click unsubscribe through the **List-Unsubscribe** HTTP header. This allows the unsubscribe button to appear natively in the Gmail/Yahoo UI. **The Risk:** If you trap users by making them log in or click through multiple pages to unsubscribe, they will likely click "Report Spam" instead, instantly damaging your domain reputation. ## Spam Traps & Blocklists: The Silent Killers ### Spam Traps Email addresses used to identify poor acquisition practices. Hitting traps suggests you are using purchased lists or failing to remove inactive contacts. ### Blocklists Databases like **Spamhaus** identify suspicious senders. Being listed can lead to outright blocking or heavy filtering. To resolve this, you must fix the root cause (e.g., cleaning the list) before requesting delisting. ## How List Hygiene Drives Deliverability (The MillionVerifier Solution) List hygiene is a controllable lever. By removing invalid and risky addresses, you reduce hard bounces and spam trap exposure. **MillionVerifier** provides the **Bulk Verifier,** which validates large lists before sending to reduce hard bounces. ## A 5-Step Deliverability Audit Framework Use this actionable checklist to maintain your sender health: 1. **Authenticate:** Verify SPF, DKIM, DMARC, TLS, and DNS records. 2. **Clean List:** Use verification tools to remove invalid and risky addresses. 3. **Check Postmaster:** Monitor rolling 30-day trends via Google Postmaster Tools. 4. **Sunset Users:** Suppress long-term inactive subscribers. 5. **Test Placement:** Run pre-send inbox placement and blacklist checks. ![](https://www.millionverifier.com/content/images/2026/06/image5-1.png) ## Frequently Asked Questions #### What is the difference between delivery and deliverability? Delivery is when the server accepts the mail; deliverability is when the mail actually reaches the inbox. #### What is a good spam complaint rate? Consistently below 0.10%, and strictly never exceeding 0.30%. #### Do spam trigger words still matter? Far less than before. Reputation, authentication, and engagement are now the primary drivers. #### Can list verification guarantee inbox placement? No, but it reduces the risk of hard bounces and spam traps, which supports a healthier reputation. ## Ready to clean your list? Verify your emails with MillionVerifier and send your next campaign with more confidence, fewer bounces, and better results. [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com) ### The Ultimate Guide to Email Verification & List Cleaning URL: https://www.millionverifier.com/blog/the-ultimate-guide-to-email-verification-list-cleaning/ Last updated: 2026-08-31T12:26:51.000Z - Email lists decay fast - by **22.5% every year -** which means even a good database can quietly become a deliverability risk. - **Email verification** checks whether an address exists and can safely receive mail **without sending an email**. - **List cleaning** removes invalid, disposable, duplicated, and risky addresses before they hurt your sender reputation. - Strong verification helps reduce bounces, improve inbox placement, protect domain health, and increase campaign ROI. - MillionVerifier combines **99%+ accuracy**, **greylisting handling**, **Smart Verify**, and a built-in **Catch-All Verifier** that can resolve **30% to 40% of risky emails**. - It’s also **GDPR compliant**, and **no credits are charged for Unknown or Catch-All** results. ## TL;DR ![](https://www.millionverifier.com/content/images/video-thumbnails/b3a6bc76f6d9e187827b84f75b49992e85dce138b88d6fec02bcc3d0a2dcd128-1280.webp) If you send email marketing, cold outreach, newsletters, or lifecycle campaigns, list hygiene is not optional. Email addresses go bad constantly due to job changes, abandoned inboxes, typos, domain issues, and disposable signups. Email verification helps you remove dangerous addresses before you hit send. The result: fewer bounces, better deliverability, stronger sender reputation, and more revenue from the same list. If you want a fast, accurate, and privacy-conscious way to clean your database, MillionVerifier gives you **99%+ accuracy**, advanced **greylisting handling**, **Smart Verify** for deeper checks, and a built-in **Catch-All Verifier** that can resolve **30% to 40% of risky emails**—while charging **no credits for Unknown or Catch-All**. ## What is Email Verification? **Email verification is a technical process that checks if an email address exists and is safe to receive mail, without actually sending a message. It removes invalid, disposable, and risky emails from your database to protect your sender reputation.** In practical terms, email verification helps you answer questions like: - Does this email address have the correct format? - Does the domain exist and accept email? - Is the mailbox active? - Is it disposable or temporary? - Is it a risky catch-all address? - Could it trigger bounces or harm deliverability? Instead of blasting your full list and hoping for the best, verification gives you a safer, data-backed way to decide who should receive your campaigns. ![](https://www.millionverifier.com/content/images/2026/06/image1.png) ## Email Validation vs. Email Verification: What’s the Difference? These terms are often used interchangeably, but they are not the same. ### Email validation Email validation is a basic front-end or formatting check. It looks at whether an address appears to be written correctly. For example, validation can detect: - Missing @ symbols - Invalid characters - Bad syntax - Obvious formatting mistakes Validation is useful, but it only checks the surface. ### Email verification Email verification goes much deeper. It checks whether the address is actually connected to a real, reachable mailbox and whether it is safe to mail. Verification can assess: - Domain existence - MX records - SMTP response behavior - Mailbox availability - Disposable status - Catch-all risk - Temporary server issues like greylisting ### The simplest way to think about it - **Validation** asks: “Is this email formatted correctly?” - **Verification** asks: “Can this email really receive mail safely?” If you care about deliverability, sender reputation, and campaign performance, verification is the one that matters most. ## Why Email List Cleaning Matters A dirty email list costs more than most senders realize. Email databases naturally degrade over time. In fact, email lists decay by around **22.5% per year**. That means even a healthy list can become unreliable surprisingly quickly. People change jobs. Companies shut down domains. Users abandon inboxes. Typos slip into forms. Temporary addresses get used once and disappear. If you keep mailing those addresses, the damage adds up: - Higher bounce rates - Lower inbox placement - Weaker sender reputation - More spam complaints - Reduced engagement - Wasted ad spend and sending costs - Poor reporting accuracy Clean lists perform better because they remove hidden friction from every campaign. When you only send to real, reachable, lower-risk contacts, your metrics become more trustworthy and your revenue per send tends to improve. ![](https://www.millionverifier.com/content/images/2026/06/image2.png) ## How Email Verification Works Modern email verification is a multi-step process, not a single check. A robust verifier typically looks at several technical signals to classify each address accurately. ### 1\. Syntax and formatting check The system checks whether the email is correctly structured. This catches obvious issues like: - Misspellings - Missing characters - Invalid formatting ### 2\. Domain check The verifier confirms that the domain exists and is properly configured to receive email. If the domain is inactive, parked, or broken, the address is not safe to send to. ### 3\. MX record check MX records show whether a domain has mail servers set up to handle incoming email. If valid MX records do not exist, deliverability is highly unlikely. ### 4\. SMTP and mailbox-level checks This step helps determine whether the mailbox exists and can receive mail. A high-quality provider performs these checks carefully, without sending an actual email. ### 5\. Disposable email detection Some users sign up with temporary addresses that expire quickly or are created only to access a gated asset. These addresses rarely provide long-term value and can distort engagement data. ### 6\. Catch-all analysis Catch-all domains are configured to accept messages for many or all addresses on the domain, even when a specific mailbox may not truly exist. That makes them harder to classify and riskier to send to blindly. MillionVerifier includes a built-in **Catch-All Verifier** that can resolve **30% to 40% of risky emails**, giving you more actionable data than a basic verifier. ### 7\. Greylisting handling Some mail servers temporarily reject verification attempts as an anti-spam tactic. This is called **greylisting**. If a verifier doesn’t handle greylisting properly, it may misclassify valid addresses as risky or unknown. MillionVerifier includes advanced **greylisting handling** to improve result quality and reduce false uncertainty. ![](https://www.millionverifier.com/content/images/2026/06/image3.png) ## What Makes a Good Email Verification Service? Not all verifiers are equal. If you are choosing a platform, look for more than just low pricing. A strong email verification service should offer: - **High accuracy** so you can clean lists confidently - **Fast processing** for large databases - **Catch-all intelligence** to reduce risky gray areas - **Greylisting handling** to improve classification quality - **Clear result categories** for easier decision-making - **GDPR compliance** for privacy-conscious operations - **Fair billing** that does not punish uncertainty MillionVerifier is built around these priorities, including **99%+ accuracy**, **Smart Verify**, catch-all resolution, and **no credits charged for Unknown or Catch-All** results. ## Key Benefits of Email Verification When done consistently, email verification improves performance across your entire email program. ### Better sender reputation Mailbox providers pay close attention to bounce patterns and overall list quality. A cleaner list helps protect your reputation over time. ### Lower bounce rates Removing invalid or non-existent addresses before sending reduces hard bounces and keeps your campaigns healthier. ### Improved deliverability Lower bounce risk and better sender signals can help more of your emails land in the inbox instead of the spam folder. ### Higher campaign ROI Every send becomes more efficient when fewer messages are wasted on dead or risky addresses. ### More accurate reporting A cleaner list gives you a more realistic picture of opens, clicks, conversions, and true audience engagement. ### Better segmentation and targeting When your database is healthier, your automations and segmentation logic become more reliable too. ![](https://www.millionverifier.com/content/images/2026/06/image4.png) ## When Should You Verify an Email List? The short answer: more often than most teams do. Here are the best times to verify: ### Before sending a campaign This is the most important use case. If you’re about to launch a major campaign, verify first. ### After collecting leads Any form, popup, webinar registration, giveaway, or lead magnet can introduce typos, fakes, and disposable addresses. ### Before importing old lists into your ESP If a list has been sitting untouched for months, it should be cleaned before use. ### During regular database maintenance Verification should be part of ongoing hygiene, not a one-time fix. ### Before cold outreach at scale In outbound email, list quality directly affects domain reputation and reply performance. Verification is essential. ## How Often Should You Clean Your Email List? There is no single rule for every business, but a few practical guidelines work well. You should clean your list: - **Before every major send** - **At least monthly** for active email programs - **Immediately before re-engagement campaigns** - **Any time you import a third-party or older database** - **Continuously**, if your lead flow is high-volume Because list decay averages **22.5% annually**, waiting too long between cleanings can quietly erode campaign performance. ## What Do Email Verification Results Mean? Verification platforms usually sort addresses into categories so marketers can decide what to do next. ### Valid The email appears safe to send. ### Invalid The address is not deliverable and should be removed. ### Disposable The address comes from a temporary email provider and is typically not worth keeping. ### Catch-All The domain accepts many addresses, making the specific mailbox harder to confirm. These can be risky, but they should not be treated the same as obviously invalid addresses. ### Unknown The verifier could not reach a confident conclusion, often due to server behavior, restrictions, or temporary responses. With MillionVerifier, **no credits are charged for Unknown or Catch-All**, which makes large-scale cleaning more cost-efficient and transparent. ## What Is Smart Verify? **Smart Verify** is MillionVerifier’s enhanced verification approach designed to improve decision-making on more difficult email addresses. Instead of relying only on basic checks, Smart Verify helps provide deeper insight where standard verification may leave too many addresses in a grey area. This is especially useful when you want: - Better confidence at scale - More actionable list-cleaning results - Improved handling of edge cases - Stronger performance on risky segments Combined with MillionVerifier’s built-in **Catch-All Verifier** and **greylisting handling**, Smart Verify helps turn more uncertain records into usable intelligence. ## Catch-All Emails: Why They Matter Catch-all emails are one of the biggest blind spots in email verification. A catch-all domain is configured to accept messages sent to many or all addresses, even if a mailbox is not clearly verifiable. That means a standard verifier may label them as risky or ambiguous. Why this matters: - Some catch-all emails are real and valuable - Others are role-based, dormant, or effectively undeliverable - Sending to too many unresolved catch-all addresses can increase risk MillionVerifier’s built-in **Catch-All Verifier** can resolve **30% to 40% of risky emails**, helping you recover more usable contacts without increasing unnecessary risk. ## Is Email Verification GDPR Compliant? It can be -if you use the right provider and the right processes. MillionVerifier is **GDPR compliant**, making it a strong fit for teams that care about privacy, responsible data handling, and European regulatory standards. That said, GDPR compliance also depends on how your business collects, stores, and uses personal data. Verification should be one part of a broader compliant email marketing practice. ## Common Email Verification Mistakes to Avoid Even good teams make preventable list-cleaning mistakes. ### 1\. Verifying only once Email hygiene is ongoing. A one-time cleanup is not enough because data keeps decaying. ### 2\. Treating all risky emails the same Not every catch-all or unknown email should be handled identically. Smarter categorization leads to better decisions. ### 3\. Ignoring old lists Older databases usually contain more invalid, abandoned, or outdated addresses. ### 4\. Choosing a tool based only on price Cheap verification is expensive if it hurts deliverability or gives unreliable results. ### 5\. Skipping verification before important sends Large campaigns increase the cost of every list-quality mistake. ![](https://www.millionverifier.com/content/images/2026/06/image5.png) ## How to Choose the Right Email Verification Tool If you are comparing providers, use this checklist: - Is the accuracy consistently high? - Does it handle catch-all domains intelligently? - Does it account for greylisting? - Is the pricing transparent? - Is it GDPR compliant? - Does it scale for large uploads? - Are the result categories easy to act on? - Does it support efficient workflows for marketers and sales teams? For many teams, MillionVerifier stands out because it combines: - **99%+ accuracy** - **Smart Verify** - Built-in **Catch-All Verifier** - **Greylisting handling** - **GDPR compliance** - **No credits charged for Unknown or Catch-All** That combination makes it especially attractive for businesses that want both performance and fairness. ## Best Practices for Ongoing List Hygiene Verification works best when it is part of a broader email quality strategy. ### Use real-time checks on forms Prevent bad addresses from entering your system in the first place. ### Verify lists before large sends Do not wait until bounce rates become a problem. ### Remove or suppress invalid emails quickly Once an address is confirmed bad, stop sending to it. ### Review risky segments carefully Use catch-all and unknown classifications strategically rather than blindly. ### Monitor deliverability metrics Watch bounce rates, open rates, spam complaints, and inbox placement trends. ### Make cleaning a recurring process Healthy sender reputation is built through consistency. ## Frequently Asked Questions #### Does email verification send an actual email? No. Email verification checks whether an address exists and is safe to receive mail without actually sending a message. #### What’s the difference between email validation and verification? Validation checks formatting. Verification checks whether the address, domain, and mailbox are actually deliverable and safe to send to. #### Why should I clean my list if people opted in? Because opt-in lists still decay. On average, email databases degrade by 22.5% per year, even when they were originally collected legitimately. #### How accurate is MillionVerifier? MillionVerifier offers 99%+ accuracy, helping teams clean lists with confidence and reduce unnecessary bounce risk. #### What are catch-all emails? Catch-all emails come from domains that accept mail for many or all addresses, making individual mailbox verification harder. MillionVerifier’s built-in Catch-All Verifier can resolve 30% to 40% of risky emails. #### What does greylisting mean? Greylisting is when a mail server temporarily rejects a verification attempt as an anti-spam measure. MillionVerifier includes greylisting handling to improve verification quality. #### What is Smart Verify? Smart Verify is MillionVerifier’s enhanced verification capability for deeper analysis, especially useful for difficult or uncertain addresses. #### Is MillionVerifier GDPR compliant? Yes. MillionVerifier is GDPR compliant. #### Do I pay for every result? No. With MillionVerifier, no credits are charged for Unknown or Catch-All results. ## Final Thoughts Email verification is no longer just a technical nice-to-have. It is a core part of protecting deliverability, preserving sender reputation, and getting better returns from every campaign you send. With lists decaying by **22.5% every year**, doing nothing is expensive. The longer you wait, the more invalid and risky contacts build up in your database. If you want a smarter, more accurate way to clean your email list, MillionVerifier gives you the tools to do it with confidence: **99%+ accuracy**, **Smart Verify**, advanced **greylisting handling**, a built-in **Catch-All Verifier** that resolves **30% to 40% of risky emails**, **GDPR compliance**, and **no credits charged for Unknown or Catch-All**. ## Ready to clean your list? Verify your emails with MillionVerifier and send your next campaign with more confidence, fewer bounces, and better results. [Create Your Free Account Now](https://app.millionverifier.com/register?ref=millionverifier.com)