Tests we ran ourselves on verification, deliverability and cold outreach.
Verification stops bounces, not spam placement. If a clean list still lands in junk, the cause is authentication, sending patterns, content or engagement. Here is how to find which one.
Insurance leads arrive from web forms, lead vendors, referrals and old books of business. Here is how agents and agencies keep email addresses and phone numbers usable without burning their sending reputation.
How to name secondary domains for cold email, the patterns that read as legitimate, what to avoid, and how to check availability for a whole list at once.
Waitlists collect typos, fake signups and disposable addresses for months. Here is how to clean one before launch day so the most important email you send actually arrives.
Why email lists match poorly on Google Customer Match, Meta Custom Audiences and LinkedIn Matched Audiences, what list cleaning can improve, and what it cannot.
Aged and expired domains for cold email: what you inherit, how to check blocklists and past use, and why a fresh domain registered early is often safer.
Keep bounces out of Close sequences by verifying lead emails: export a Smart View, verify, write status back to a custom field, and filter sequences to valid contacts.
Newsletter platforms can review imports and watch early bounce rates. Here is how to clean and verify a subscriber list before importing it into beehiiv, Kit or Substack.
Domain age vs warm-up for cold email: what providers publish, why brand-new domains look risky, and a two-to-four-week plan before real sends.
ZoomInfo publishes no prices, so comparing it starts with what the others do publish. Lusha, UpLead, FullEnrich, Apollo and Cognism on price, credits, rollover and what you pay when nothing is found, plus the renewal terms to check and a 300-contact test to run first.
Yahoo's Sender Hub takes delivery tickets for mail to Yahoo and AOL mailboxes. Yahoo says to file one when you're having difficulty delivering, are a new sender or on a new IP, or expect trouble with a large launch, and to include the error and diagnostic codes from your logs. What to fix before you file, what to put in it, and why it isn't a way round high complaints.
Yahoo's Sender Hub lists 'excessive unknown recipients' as its own class of error: your server is sending to a large number of invalid Yahoo addresses. After a bad list it usually arrives alongside 554 'This user doesn't have a yahoo.com account' bounces and TS deferrals. What Yahoo says each means, and the order to fix them.
Amazon SES, HubSpot and Mailgun ask for much the same thing when an account is reviewed or suspended: what caused it, what you've already changed, and how that stops it happening again. How to do the cleanup first, write the reply with numbers instead of promises, and avoid the things that sink an appeal, such as listing steps you only plan to take.
Verifying a list only lowers your email platform bill if the platform stops counting the dead addresses. Mailchimp counts unsubscribed contacts but not cleaned ones; Klaviyo bills on profiles that can be emailed; HubSpot bills marketing contacts and only downgrades at renewal; ActiveCampaign's rule depends on when the account was created.
Two ways to verify the emails in a Google Sheet without the download, upload and re-import loop: paste the sheet's link into the verify page for a one-off list, or run the Apps Script menu inside the sheet for a list you keep adding to. Steps, sharing settings, and limits.
Verifying 500,000 email addresses once costs about $299 to $2,199 on the vendors' own pricing pages, checked 12 October to 3 November 2026. One-off and monthly prices side by side, when a pack beats a plan, how to split the file, and how long half a million careful checks take.
Verifying 5,000 email addresses once costs about $7 to $69 on the vendors' own pricing pages, checked 12 October to 3 November 2026. Prices side by side, which vendors make you buy 10,000, when free tiers are enough, and the cheapest route for a one-off list versus a monthly one.
Verifying 250,000 email addresses once costs about $169 to $1,299 on the vendors' own pricing pages, checked 30 October to 3 November 2026. The one-off prices, when a monthly plan wins, why the file needs splitting, and how many days 250,000 checks really take.
Verifying 25,000 email addresses once costs about $27.50 to $274 on the vendors' own pricing pages, checked 30 October to 3 November 2026. The one-off prices, what a monthly plan changes, how long 25,000 checks take, and how to shrink the list before you pay.
Verifying 2,500 email addresses once costs about $3.50 to $69 on the vendors' own pricing pages, checked 12 October to 3 November 2026. Who sells exactly 2,500, whose smallest pack is bigger, when free tiers get you close, and the cheapest route for a one-off list versus a monthly one.
Verifying 1,000,000 email addresses once costs about $449 to $3,199 on the vendors' own pricing pages, checked 12 October to 3 November 2026. The one-off prices, whether a pack or a monthly plan is cheaper, how to split the file, and why a million careful checks take weeks.
UpLead says its emails are 95% accurate and gives credits back below that, but what you're charged depends on the download option: Valid Only, Valid and Accept All, or All Available Emails. What each option charges by UpLead's help article, what 'guaranteed at the time of download' covers, and what to check before the send.
No mailbox provider publishes an unsubscribe limit, and Mailchimp's published average is 0.22% across its users (data from December 2023). How to calculate your rate, compare a campaign with your own normal, and work through the five usual causes of a spike before the next send.
The exact unsubscribe tag each platform documents: *|UNSUB|* in Mailchimp, {{ unsubscribe_link }} in HubSpot, %UNSUBSCRIBELINK% in ActiveCampaign, and two different tags in SendGrid depending on whether you send through Marketing Campaigns or the Email API. Plus the address tags and what a footer link doesn't cover.
systeme.io plans are capped by contacts, not sends: 2,000 on Free, 5,000 on Startup, 10,000 on Webinar. Its own import guide says to remove duplicates, invalid and inactive addresses first, use a verification service, keep bounces under 2%, and warm up lists over 5,000. How to prepare the CSV so every slot is a real person.
Export Smartlead campaign leads and the bounced inbox view, split out everyone who bounced, unsubscribed, replied or said no, then load the file into Smartlead's Global Block List and every other tool. With the client-association and domain-format rules that make blocks silently miss.
Before you recycle old prospects or change sequencers, export from Reply.io, Woodpecker or Saleshandy, split out bounced, opted-out, replied and not-interested people, and load the file into each tool's blacklist or Do Not Contact list. With what each export leaves out.
Before you recycle old campaign leads or move sequencers, pull out everyone who bounced, unsubscribed, replied or said no. How to export from lemlist and Instantly, which statuses go on the suppression list, where to load it, and what each export misses.
Stripe's failed-payment, expiring-card and trial-ending emails go to the customer's email field, so a mistyped or dead address means the customer never hears their card failed. How to export Stripe customers, find the bad addresses, add a billing contact, and fix the field before the next renewal run.
A one-cell address has to become separate street, city, state and zip fields for a CRM import, mail merge or direct mail. Why Text to Columns gets it wrong, how reading the address from the end works, what to do with units and addresses without commas, and what a split doesn't check.
SparkPost's suppression list API takes up to 10,000 recipients (50 MB) per bulk PUT, holds up to 1,000,000 imported or manual entries per account, and can partially write a batch on a 5xx error. How to chunk, type and retry a migration's bounces, complaints and unsubscribes, and verify the send list before the first campaign.
Bird, which now runs SparkPost, suppresses hard bounces for all mail and complaints for non-transactional mail, per workspace. Soft bounces don't suppress, unsubscribes are stored as preferences rather than suppressions, and its acceptable use policy names purchased, rented or scraped lists that don't comply with the law. How to carry your old provider's history across and verify the rest.
Spamhaus published consolidated sender guidelines in October 2026: confirmed opt-in, forward-confirmed reverse DNS, a resolving HELO, SPF/DKIM/DMARC alignment, bounces under 5%, unsubscribes processed within 2 days. What each requirement means and how to check it.
From November 2026 Spamhaus is gradually requiring every sending IP to have a valid HELO, a PTR record and a matching A record. Who this affects (self-hosted mail servers, VPS senders, dedicated IPs), the three DNS checks, and the common mistakes.
After a bad lead list, Smartlead can pause the campaign at your High Bounce Rate Auto Protection threshold, and mailboxes can show up under Mailbox Issue Found or lose warmup after a warmup bounce. What each signal means in Smartlead's own docs, how to find the cause per mailbox, and what to clean before the campaign restarts.
Shopify suppresses an address after it bounces, but its help pages describe no check before the first send. What Shopify's subscriber list article says about bounces, imports, role addresses and cleaning, why the first bounce still counts, and how to check a customer list before a Shopify Messaging campaign.
Every new SES account starts in the sandbox: verified recipients only, 200 messages a day, one per second, per Region. How to request production access, AWS's 96-hour first response, what to have ready before you submit, and the mistakes that lead to follow-up questions or a denial.
If Twilio SendGrid reviews or suspends your account over bounces or spam reports, here is how to find the cause, respond, clean the list and bring your rates back down.
Size your secondary domains from daily volume, pick lookalike names you can still register with the cold email domain generator, and keep each one authenticated and monitored.
Seamless.AI verifies an email when you research a contact and refunds the credit automatically if the server confirms it invalid. Its own article says the check is only true at that moment and that deliverability isn't guaranteed. What counts as invalid, what doesn't (full inboxes, role addresses), and how to keep an older export from bouncing.
With a daily sending cap, the first few hundred emails should go to the best-fit people on the list. How to rank a CSV with transparent rules (seniority from the title, target departments, company vs free webmail, role addresses, target countries), grade it A to D, and check the A and B leads' addresses before the sequence starts.
A Salesforce report export doesn't carry Email Opt Out into Instantly, Smartlead or lemlist unless you put it there. Which columns to add, how to split opted-out and bounced contacts into a suppression file, and what Salesforce's bounce fields can't see.
RocketReach grades every email A, A-, B or F and publishes its own estimate for each: about 98% for A, about 90% for A-, 75 to 85% for B. B and F cost no credits. What each grade means, what to do with each in a cold campaign, and how to split an export by grade before it reaches your sequencer.
No mailbox provider or ESP publishes a recovery schedule. A cautious restart that leans on what they do publish: a day to stop and clean, a week to 30-day engaged contacts, a week adding 90-day engaged, then verified older contacts as a small share of each day, with every send gated on bounces under 2% and complaints under 0.1%.
Resend asks every account to keep bounces under 4% and spam complaints under 0.08%, and may pause sending or close the account above them. Where those numbers come from, what the suppression list does and doesn't do, and how to keep fake and mistyped signups from pushing you over.
One soft bounce says nothing about an address. The same address soft-bouncing in send after send, with no delivery in between, is a mailbox nobody empties. How to count soft bounces per address across several campaigns, where platforms draw the line (Mailchimp: 7 for inactive contacts, 15 for active), and what to suppress.
Lead exports carry the registered company name, so a {{company}} merge field prints NORTHWIND TRADERS, INC. How to clean the column in one pass: suffixes, taglines, ALL CAPS, placeholders like Self-employed, and the rows a cleaner can't decide for you.
Blank rows break CSV imports or create empty contacts. The three kinds a spreadsheet export leaves, why Excel's Go To Special misses some, how to drop rows with no email, and what to check before the file goes into your CRM or email tool.
Each feedback loop report is one spam complaint in Abuse Reporting Format (RFC 5965), or a JSON notification if you send through Amazon SES. How to collect them, pull out the complainant, group them by subject, Feedback-ID, IP and your own campaign header, and suppress everyone at once, including when the provider has redacted the address.
A re-permission email asks people to confirm they still want your mail. In the UK and EU it can itself count as marketing: the ICO fined Flybe and Honda for exactly that. Who you can send one to, what to write, and how to clean the list first.
QuickMail imports comma-delimited CSVs only, reads the first sheet, auto-maps Email, Firstname, Lastname and Company, and emails admins an Import Report listing rejected rows. It doesn't verify on its own: verification runs through add-ons like NeverBounce, BriteVerify, ZeroBounce or Bouncer. How to prepare a prospect file so the first step of a campaign doesn't do the checking.
Postmaster Tools' spam rate is the share of mail delivered to engaged Gmail inboxes that recipients then reported as spam. Gmail asks senders to stay under 0.1% and never reach 0.3%; bulk senders above 0.3% can't get mitigation until the rate stays under it for 7 consecutive days. What to do in the week after a bad send.
Pipedrive's marketing status has seven values, and only one of them means someone asked you to stop. What each means, how to export People with the column showing, how to pull Unsubscribed and Bounced contacts into a suppression file, and what to check before the list goes to another tool.
"Loved your post on {{recent_post}}" is a great opener for the rows that have a post and a broken sentence for the rest. How to turn the columns you already have into one first line per contact with if-then rules and a default, review every line before it's sent, and import it as {{personalization}} or {{icebreaker}}.
A team sends newsletters from news.example.com through one ESP, then adds a second tool on the same subdomain, and placement drops on both. Why domain reputation is shared across providers, what Spamhaus now tells ESPs, and how to split streams by subdomain.
Omnisend sets each channel's status at import from a checkbox or opt-in and opt-out dates, so a wrong column can import a whole list as non-subscribed or unsubscribed. Its migration guide says to bring consent timestamps, leave out bounced and inactive contacts, and ramp 25 to 35% a day. Step-by-step prep for the email and phone columns.
VP Sales, Vice President, Sales, Sales VP and SR. VP, SALES @ ACME are one role, but a merge field prints each as written and a CRM report splits them five ways. How to standardise a title column in a few minutes, what pattern-based cleaning can and can't fix, and where the email check fits.
A segment for United States misses USA, U.S. and America; a state rule for CA misses California and Calif. How to turn country and state columns into one form (ISO 3166 codes or names, USPS and Canada Post codes), handle shared codes like WA and Georgia, and meet import formats such as Mailchimp's two-letter country codes.
A domain a few months old, a handful of one-to-one emails a week, perfect authentication, and still the spam folder. Why authentication isn't reputation, the checks worth doing (domain history, links, the banner Gmail shows), and the fixes that work at low volume.
Microsoft 365's 550 5.7.124 means the address you sent to is a distribution group that only accepts mail from listed senders, and you aren't on the list. What Microsoft's page says (updated August 2026), why cold and marketing lists hit it, what the group owner would have to change, and why these addresses belong on your suppression list.
Exchange Online returns 550 5.1.10 RESOLVER.ADR.RecipientNotFound when SMTP address lookup can't find the recipient, and 550 5.5.0 'mailbox unavailable' for the same case on outlook.com and hotmail.com. For a sender these mean the address is gone, with two exceptions: a recipient's broken forwarding rule, and backscatter you never sent.
In Salesforce Marketing Cloud Engagement, a subscriber moves to Held after the third soft bounce or after too many hard bounces. Salesforce's fix is to export them, set them to Active and re-import, which also resets the bounce count to zero. That's exactly why to verify the Held list first.
Mailgun disables a sending domain automatically when too many messages bounce as invalid, and shows the error 'Poor mailing list'. What Mailgun asks for before it re-enables the domain: a cleaned list, how you collected the addresses, what you send and whether it's double opt-in. Plus how business verification and suppressions fit in.
Klaviyo's Mailchimp integration syncs subscribers, unsubscribes and cleaned contacts, plus 90 days of engagement, but not tags. Suppression depends on timestamps, cleaning in Mailchimp before removing the integration suppresses those contacts in Klaviyo, and a Shopify link left in place can send double opt-in emails. The migration order that avoids all three.
Lusha charges 1 credit per email and 5 per phone, so 400 credits can mean 400 emails or 80 phone numbers. How that compares with UpLead, FullEnrich, Apollo and Cognism on published terms, when each fits, and how to test them on your own contacts.
Lead411's published plans, then UpLead and Cognism on the same points: where intent data sits, technographics, how credits work, and what each says about accuracy. Plus the split-stack option, and a 300-row test to run before you sign anything.
ZoomInfo and UpLead say 95%, RocketReach publishes an estimate per grade, Lusha and Cognism give no email percentage, and Seamless.AI says its check is true only at that moment. What each vendor claims about its own emails, read on 2 November 2026, what none of them measure, and a 300-row test to get your own number.
Contacts from your B2B data vendor bounce more than they used to. How to measure email quality on a random sample without sending, how big the sample needs to be to tell a real drop from noise, what to separate (old exports vs fresh pulls), and what to take to the renewal call.
Klenty has paid, built-in email validation that can keep invalid and risky prospects out of cadences; its credits expire a month after purchase. Mixmax removes a recipient after a hard bounce, so the bounce has already happened. How to prepare and verify a prospect CSV for either tool.
Klaviyo can disable a new account for a one-time compliance review, usually the first time it sends to an uploaded list, and can disable any account after repeated hard bounces, unsubscribes or spam complaints. What each state means, what stops while you wait, and how to clean the imported list so the review and the next campaign go well.
systeme.io's migration guide says to remove long-inactive contacts, unsubscribes and spam reporters, use a verification tool, tag the source and wait 24 to 48 hours before a big send. Kit exports by status and emails you a link that lasts five days; beehiiv's lasts 24 hours. The order of operations for a newsletter moving to systeme.io.
Iterable's migration guide asks you to export hard bounces and unsubscribes from your old service and unsubscribe them in Iterable, and its deliverability guide recommends a list validation tool before import. Hard bounces unsubscribe automatically after the fact; soft bounces don't. How to prepare the files so the first Iterable campaign isn't the cleanup.
ZeroBounce is an established email verifier run by Hertza L.L.C., a Nevada company based in Santa Barbara. What it costs per 1,000, the 30-day money-back terms on ZeroBounce ONE, why credit packs are final sale, when credits expire, and who it suits. From its own pages, read 3 November 2026.
Verifalia is a long-running email verifier operated by Cobisi Research, an Italian company. What it costs per 1,000, why its packs never expire but daily credits do, how quality levels change the credit cost, its refund wording and 30-day maximum retention. From its own pages, read 3 November 2026.
Truelist is a working email verifier run by Truelist, Inc., with an address in Erie, Pennsylvania. What it costs per 1,000, credits that never expire, what its catch-all enhanced validation costs, the commitment on its Unlimited plan, and who it suits. From its own pages, read 3 November 2026.
Reoon is a real, low-priced email verifier with public pricing, credits that never expire and a free daily allowance. Who runs it, what its terms and privacy policy say, how refunds and unknown results work, and the catches. Sourced from its own pages, read 3 November 2026.
QuickEmailVerification is a long-running email verifier with credits that never expire, small packs from $4 and a 90-day automatic deletion rule. Its terms name no company or address, and all sales are final. Prices per 1,000, the fine print and who it suits. From its own pages, read 3 November 2026.
NeverBounce is a long-running email verifier owned by ZoomInfo since DiscoverOrg bought it in 2019. What it costs per 1,000, why its pay-as-you-go credits expire, when Growth is cheaper, and what to read before relying on its guarantee. Sourced, with read dates.
MailerCheck is a working email verifier run by MailerCheck, Inc., under Delaware law, which says it partners with MailerLite for customer support. What it costs per 1,000, its narrow refund terms, what happens to credits if you close your account, and who it suits. From its own pages, read 3 November 2026.
Kickbox is run by J2 Martech Corp, a Ziff Davis company, publishes a full pay-as-you-go price ladder and refunds unknown results. What it costs per 1,000, why its credits expire after a year, and who it suits. From its own pages, read 3 November 2026.
Hunter is an established email finder and outreach platform run by Hunter Web Services, Inc., a Delaware company, and its verifier is part of the same credit pool. What a verification costs per 1,000 on each plan, its refund wording, monthly credit resets, and who it suits. From its own pages, read 3 November 2026.
EmailListVerify is a working, low-cost email verifier run by EmailListVerify s. r. o., a company registered in Bratislava, Slovakia. What it costs per 1,000, its refund wording, where EU data is stored, and who it suits. From its own pages, read 3 November 2026.
Emailable is run by Emailable, LLC under Florida law, gives 250 free credits, refunds unknowns and duplicates, and its credits never expire. What it costs per 1,000, what its refund terms and 24-hour guarantee require, and who it suits. From its own pages, read 3 November 2026.
DeBounce is a working, low-cost email verifier with credits that never expire, a 7-day list deletion policy and a guarantee paid mostly in extra credits. Who runs it, what it costs per 1,000, what its guarantee requires, and the catches. From its own pages, read 3 November 2026.
Clearout is a working email verifier run by Clearout Inc, with a San Francisco notice address and California law in its terms. What it costs per 1,000, its no-refund rule, what its terms say about idle credits, how long it keeps uploaded files, and who it suits. From its own pages, read 3 November 2026.
Bouncify is a working, low-cost email verifier with packs that never expire and a 30-day list retention policy. Its terms name no company, address or governing law, and payments are non-refundable. Prices per 1,000, the fine print and who it suits. From its own pages, read 3 November 2026.
Bouncer is a Polish email verifier run by Bouncer Sp. z o.o. in Wrocław, hosted in the EU, with credits that never expire and no charge for duplicates or unknowns. What it costs per 1,000, what its terms say about refunds, and who it suits. From its own pages, read 3 November 2026.
Gmail, Microsoft 365 and Spamhaus all ask more of IPv6 senders: a PTR record on the sending address, SPF or DKIM passing, and a /64 or larger allocation. The exact errors (550-5.7.1, 450 4.7.25, 450 4.7.26, 550 5.2.1), what each means, and when to send over IPv4 instead.
Instantly's warmup health score is the share of warmup emails that landed in the inbox over the last 7 days, and Instantly wants it above 90% before campaigns. It measures warmup placement only, so it can lag or miss damage from a bad campaign list. How to read it after a bounce spike, and the order to fix things in.
Gmail supports a style block in the head, but not in the body, not past 16 KB, and not in its apps for non-Google accounts. When inlining still matters, what to leave in the head, and how to inline a template in a minute.
Since 26 October 2026 you can't create a new legacy private app in an existing HubSpot account. What still works, how to create a service key with the right scopes, what changes for verification and enrichment tools, and the September 2027 date to plan for.
HubSpot suspends marketing email when monthly hard bounces pass 5%, spam reports reach 0.1% or unsubscribes pass 3%, among other triggers. The appeal in the Health tab can be submitted only once, and removing the bounced contacts alone won't restore sending. What to clean before you start it, and what free accounts can't appeal.
A hotel's PMS export mixes real guest addresses with booking-site relay aliases such as @guest.booking.com. Booking.com says it doesn't share private addresses and limits messaging to seven days after check-out. How to separate the aliases, verify the direct-booking addresses, and send a clean list.
HVAC, plumbing, roofing and cleaning companies collect customer emails in the field, on a phone, often typed by a tech. Before the seasonal tune-up promo or a review-request blast, export the customer list from Jobber or Housecall Pro, remove placeholders and duplicates, and verify what's left.
HighLevel's LC Email Validation costs $2.50 per 1,000 and runs before a contact's first email, with a re-check after 90 days. What it checks, what it costs at 10k, 50k and 100k contacts, where rebilling markups apply, and when checking a list before it's imported is the better choice.
HighLevel's ESP block is separate from its bounce lock: it counts mailbox providers rejecting your mail for reputation, authentication or content. The 3% warning, the 5% block, the 12- and 24-hour pauses, the 7-day reset, where the articles disagree, and what to fix in the first 48 hours.
When a HighLevel sub-account's mail lands in Gmail spam even though authentication passes and the domain is on no blocklist, the cause is usually the shared IP, a warm-up that isn't moving, engagement or the list. What HighLevel's own articles say about each, in the order to check them, and what to send support.
HighLevel has tracking switches in more than one place. For LC Email, open and click tracking are set per dedicated sending domain under Email Services, and links stay wrapped through a tracking redirect until that switch is off. Where both settings live, how to confirm in a delivered email, and what you lose when tracking is off.
HighLevel warns at a 3% bounce rate and blocks LC Email sending at 5%, twice for 12 hours, then permanently. The minimum volume since August 2026, how the fixed-stage domain warm-up works, why rushing a stage with an old list backfires, and what to do before the send.
Publishing a plain mailto link puts your address on harvester lists. What email obfuscation still stops, what it can't, the trade-offs of each method (HTML entities, JavaScript, split addresses, [at] text, CSS), Cloudflare's built-in option, and when a contact form is the better answer.
Fix '504 5.5.2 Helo command rejected: need fully-qualified hostname' and 'Host not found' errors: find the name your server announces, change it in Postfix, Exim or Exchange, add the A record, match the PTR, and confirm it from a real Received header.
Domain enrichment works on work emails and returns nothing on Gmail, Outlook and Yahoo signups. What you can and can't learn about a personal-email signup, the signals that work (ask, invites, usage, billing), what to avoid, and how to route them.
Google lets bulk senders request mitigation when Gmail misclassifies their mail, but only if they meet every sender guideline and keep user-reported spam below 0.3% for 7 days. Who qualifies, what the form asks for, and what to fix before you send it.
Feedback-ID: a:b:c:SenderId. Up to three identifiers of your choice (campaign, customer, mail type) and a 5 to 15 character SenderId that stays the same across the stream, on DKIM-signed mail from a domain verified in Postmaster Tools. Google's rules, how to pick the fields, and why per-message values never show up.
Gmail hides everything past roughly 102 KB of HTML behind a View entire message link, and that can include your footer, your unsubscribe link and the open-tracking pixel. What counts toward the size, what doesn't, and the order to cut things in.
Gmail returns 550 5.2.1 'The email account that you tried to reach is inactive' for mailboxes that exist but can't receive mail, often personal accounts that went unused for a long time. Google's own table also uses 550 5.2.1 for a recipient receiving mail too fast. How to tell them apart, why old lists produce lots of these, and what to remove.
Gmail's 450 4.2.1 says the recipient is receiving mail too quickly or at a rate that prevents more being delivered. It's temporary and about that one mailbox, usually one getting floods of mail. What Google's text says, the Workspace receiving limits (60 a minute, 3,600 an hour, 86,400 a day), the 550 5.2.1 and relay-limit variants, and when to stop retrying.
Freshsales has a built-in contact list validation, in beta on Growth and higher plans and on by default, that checks a bulk email's contacts before it sends. What its help article says it does, what it doesn't say (method, sequences, one-to-one email), how it fits Freshsales' 5% and 10% bounce limits, and when an outside check is still worth it.
You have names, companies and domains for 20,000 leads and need verified work emails. How to cut the job down by domain before you pay a finder, where pattern-plus-verify works and where it can't (catch-all domains), and what published finder prices look like at this volume.
A campaign's overall bounce rate says something went wrong; the rate per lead source, list, tag or import date says what to stop mailing. How to export the send with a source column, group it, read hard bounces, blocks and complaints separately, and clean the group that's over 2%.
Website columns hold https://www., paths, UTM tags, LinkedIn pages and myshopify.com stores. How to reduce each to the company's root domain (co.uk-aware), which rows to set aside, and what to do with the domains next: find email formats, match customers, suppress by domain.
How to export Contacts from Zoho CRM's Data Administration and from Close's Leads page so each person gets a row, carry Email Opt Out and unsubscribes with them, split out a suppression file, and check the rest before a campaign. With the export limits each CRM publishes.
Whova has a basic attendee export and a custom report with check-in data. Which one to use (per Whova's help centre), what the custom export contains, how to handle speakers, exhibitors and repeat tickets, and how to clean the file before the follow-up goes out.
Patreon's Relationship Manager exports a CSV of whoever matches your current filters. How to export (per Patreon's help centre, updated October 2026), what Active, Declined, Canceled, Refunded and Fraud mean for an email list, why some emails are missing, and how to clean the file before it goes into Mailchimp or another tool.
Luma's Guests tab downloads a CSV of every registration. How to export it (per Luma's help centre), what the approval and check-in columns mean for your follow-up, why group tickets create repeat rows, and how to clean the file before it goes into your email tool.
Gumroad has two exports: a sales CSV of customers and purchases, and a subscribers CSV of followers. How to download each (per Gumroad's help centre, read 3 November 2026), why one buyer appears on many rows, what to do with refunds, unsubscribes and gift recipients, and how to clean the list before it goes into another email tool.
How to export a HighLevel Smart List with the DND column, set aside opted-out and duplicate contacts, check the addresses, and import the clean list back with a tag, so a campaign to an old sub-account list doesn't trip HighLevel's bounce lock.
How to get an email list out of Eventbrite: the Attendees report for one or many events, the Purchasers subscriber list of people who opted in at checkout, and the Unsubscribed users list. Steps from Eventbrite's help centre (read 3 November 2026), the 250-a-day default send limit, and how to clean ticket rows into one row per person.
Download a Clay table as CSV, pick the right email column, read the validation results, drop rows where enrichment found nothing, merge repeats and check what's left before it goes into Instantly, Smartlead or Lemlist.
Divide hard bounces by emails sent and complaints by emails delivered, then compare with the line your platform publishes: Brevo 2% hard bounces, HubSpot 5% in a month, Amazon SES review at 5% and possible pause at 10%. How to run the check before the next send, why your dashboard shows a different number, and what to do if you're over.
How to run email verification for a team without sharing one password or paying twice for the same list. What a seat gives a teammate, how SimpleVerifier's Business (5 seats) and Agency (15 seats) plans work, how to add people, and what to agree on before several people upload lists.
An email verification API bill is calls a month times the price per call, minus whatever the plan includes. How to count your real calls (signups, imports, retries), SimpleVerifier's included calls and overage on Pro, Business and Agency, where each plan becomes cheaper, and how to stop paying for calls you didn't need.
Brevo, Klaviyo and others now publish MCP servers, so an AI assistant can build segments, draft campaigns and add contacts. What to let it do, what to keep human, how to scope the key, and why every contact it adds should be verified first.
Classic Outlook for Windows draws email with Microsoft Word's engine, which ignores flexbox, floats, positioning, CSS background images and max-width. What it drops, how to tell which Outlook your readers use, and how to fix a template without rebuilding it.
Nine checks that make an HTML email readable with a screen reader or low vision: a lang attribute, role=presentation on layout tables, real alt text, 4.5:1 contrast, headings in order, descriptive links. What each one fixes, and what an automated check can't tell you.
Elastic Email includes its Email Verification Service with paid plans: up to 1x your contact limit on Email Marketing Starter, 5x on PRO, 1x your sending limit on Email API, resetting monthly. Free plans get single checks only and sub-accounts can't use it. Its help centre says your ESP isn't a list-cleaning tool and a poor list risks suspension. When the included checks are enough and when they aren't.
Email platforms check the format of an address on import and stop sending after a hard bounce. None of the four big ones we read confirms a mailbox exists before the first send. Mailchimp's Omnivore gives a group-level risk warning and no list of bad addresses. What each platform does, and when a separate verifier is worth paying for.
Instantly, Smartlead, lemlist and Apollo all check emails in some way. When the built-in check is enough, when a separate verifier pays for itself, and what each tool's own help pages say about cost, statuses and catch-alls, with read dates.
SES doesn't send an EventBridge event when it pauses your whole account, and the SendingEnabled flag doesn't change. Poll GetAccount's EnforcementStatus instead, alarm on PROBATION and SHUTDOWN, and stop your queue before mail piles up.
Inbox placement drops, so you change the copy, the domain, the warm-up tool and the volume in the same week, and now nothing can be measured. How to break the loop: freeze, log, change one variable, and judge it over two weeks.
Run Cvent's Invitee Details report, sort invitees by status (accepted, waitlisted, no response, cancelled, declined), honour opt-outs, set aside speakers and exhibitors if you need to, and check the addresses before next year's invitation goes out.
Customer.io's own deliverability guide says to verify any email address imported into Customer.io before you send to it, to leave out recipients who previously hard bounced, and to keep bounces under 5% (under 2% is ideal). Its suppressions are per sending domain. How to prepare a migration CSV so the first broadcast doesn't do the checking.
Excel drops the zero from 02108, the plus from +44 and the last digits of 16-digit IDs when you double-click a CSV. Why it happens, the three fixes Microsoft documents, and how to send a file that opens correctly for everyone.
A city column that's 60% filled means 40% of the list gets the fallback, and a title column full of dashes looks filled to COUNTA but prints a dash. How to measure every column's real fill rate, including placeholders like n/a and #N/A, decide which merge fields the copy can use, and set fallbacks where it can't.
Leads arrive from forms, CSV imports, enrichment tools and sync apps, and each path matches records differently. How HubSpot actually deduplicates (email for contacts, domain for companies, with exceptions), the gaps that create duplicates, and a matching order that prevents them.
How many contacts came from each lead source, country or status? How to count distinct values in a CSV column, why Excel and Sheets show five spellings of the same source, how to count tag cells, and how to compare sources by reachable contacts, not rows.
Bulk senders whose Postmaster Tools spam rate reaches 0.3% can't get mitigation until it has stayed below 0.3% for 7 consecutive days. How to log the daily rate, count the streak correctly (missing days don't count), and what the count does and doesn't mean.
{{firstName}} in Instantly is {{first_name}} in Smartlead, *|FNAME|* in Mailchimp, {{ contact.firstname }} in HubSpot and {FirstName} in GMass. Paste a template into the wrong tool and the tag goes out as text or a blank. The syntax each tool documents, how fallbacks differ, and a step-by-step conversion.
APIs and some platforms export contacts as JSON, not CSV. How to find the records inside the response, how nested fields and lists become columns, when JSON Lines is involved, and how to get the result into Excel or an email tool.
Instantly's analytics define reply rate as replies divided by total sent, so every follow-up you add lowers it. How to work out reply rate per prospect, per delivered email and per step, what to leave out (bounces, auto-replies), and how to tell which step is doing the work.
Cognism says a phone-verified (Diamond) contact is one whose mobile number its process has called to confirm the right person picks up. That's a check on the phone number on the day it was called. It isn't a mailbox check on the email, and it doesn't follow the person after a job change. What to check before you dial or send.
Close's native forms accept any properly formatted address, with no verification and no typo correction, and a form submission can start a Workflow straight away. How to put a check between the form and the sequence with Zapier and an email verification API, what to do with risky results, and what a check doesn't stop.
Export a Snov.io prospect list with the email status field, set aside not-valid and role addresses, treat unknown (yellow) as risky, decide what to do with Email 2, and check the file live before the first send. What Snov.io charges for each colour, and where the export falls short.
Account Engagement marks a prospect Undeliverable after one hard bounce or five soft bounces; Marketo Engage sets Email Invalid on certain hard bounces and it only resets by hand. Both learn about a dead address by mailing it. How to verify an event, webinar or data-vendor file before it goes into either platform.
linkedin.com/in/Jane-Doe/, https://uk.linkedin.com/in/jane-doe?trk=public_profile and .../in/jane-doe/details/experience/ are one person, but a plain dedupe sees three, and Jane gets three cold emails. How to normalise a LinkedIn column, match people across exports, and what can't be cleaned (Sales Navigator links, short links, renamed profiles).
A Hunter leads or Bulk Email Finder file mixes valid, accept-all, unknown and generic addresses. What each status means, how Hunter suggests using the confidence score, which rows to drop, and the order to clean and check the file before the first send.
Facebook and Instagram lead forms often return old personal emails, typos and fake entries. Here is how to verify emails, clean phone numbers and improve lead quality at the form.
Importers match columns by header name or position, and merge fields use the header as the variable. How to get the names, order and values right without opening the file in Excel: rename and reorder columns, then replace values in only the columns you choose.
A Cognism list download mixes verified and unverified emails, role inboxes, personal webmail and addresses on a different domain from the company. How to download it, what to set aside, why a verified email still needs a check on send day, and the UK and EU rules to keep in mind.
Clay now splits its plans into actions and data credits. If you only fill work email, headcount and tech stack, a smaller Clay tier, your own API keys, a lookup tool or a simple n8n flow may cost less. Clay's published numbers, the options, and how to price them for your row count.
Brevo suspends email campaigns when a send to new contacts, or any campaign in the last 24 hours, shows a hard bounce rate above 2%, unsubscribes above 1% or complaints above 0.2%. How to read the reason in the Deliverability Center, clean the flagged segment and reactivate, knowing a second suspension may not be reversible.
Brevo deactivates any API key that hasn't made a successful call in 90 days, even one set to 'no expiration'. SMTP keys follow the same rule. How to reactivate, how to keep a quiet contact form's key alive, and what to check before switching providers.
Braze's email validator only checks syntax: it doesn't look up MX records or confirm a mailbox exists. A hard bounce marks the address invalid but leaves the subscription state alone. Braze's import guide says to leave suppression lists behind and import only users who opened in the last six months. How to prepare a list for Braze.
Should cold email domains be .com, .io, .co or something cheaper? What mailbox providers say, what recipients see, and which TLDs to avoid.
Every AWeber import is reviewed by its import specialists, and a list can be rejected for its origin, its age, bad addresses, bounces, complaints, a vague form, co-registration or formatting. What each reason means, what AWeber says to do, what a list cleaning service can and can't fix, and the order to prepare a resubmission.
When the Apollo or ZoomInfo Chrome extension stops loading on LinkedIn, try Apollo's own fixes first. If you're tired of depending on it, move prospect research into a Clay table, verify emails there, and push only checked contacts into HubSpot without creating duplicates.
AI Ark's API docs say emails are verified in real time by BounceBan (SMTP and catch-all) at the moment they're returned, and an export with email costs 0.5 credits per person plus 0.5 per valid email found. That check is a snapshot. When an AI Ark list is ready to send as-is, and when it's worth checking again before a sequence.
ActiveCampaign puts accounts under review for high spam complaints and for too many bounces caught during campaign approval, and sending stops until it's resolved. Its help centre names new and re-imported lists as a common cause and treats 0.1% complaints as the line. What to fix before the next import, and what to send support.
554 5.4.4 "unable to route" (Exchange's SMTPSEND.DNS.NonExistentDomain) and Gmail's 553 5.1.2 "We weren't able to find the recipient domain" mean the part after the @ has no usable mail route. What RFC 3463 and RFC 5321 say, the usual causes (typos, dead domains, null MX), when it's your DNS instead, and how to clear these from a list before sending.
Gmail's 553 5.1.3 says "The recipient address is not a valid RFC 5321 address." The address is malformed, so it never reached a mailbox check. The usual culprits in a CSV (two addresses in one cell, mailto:, angle brackets, spaces, smart quotes, non-ASCII), the RFC limits, and how to find every broken row before the send.
A 551 or 5.1.6 bounce means the address used to work and the receiving server no longer accepts mail for it. What the two RFCs say, why you should not quietly switch to a forwarding address, and how to keep the dead address out of future sends.
Zoho Mail's usage policy says it can't be used for bulk, mass, marketing or automated email, and its limits are reputation-based and rolling per hour. What that means for cold outreach, why bounces trigger blocks, and what to do if you're already on Zoho.
A verified list rarely bounces at zero, and small campaigns make a few bounces look worse than they are. Why some bounces survive verification, how to read a bounce rate on a small send, and the steps that get you as close to zero as the data allows.
Yahoo rejects or defers mail when the domain in your MAIL FROM or From header doesn't appear to exist. Yahoo checks this with an SOA query, so sending subdomains need SOA records as well as A or MX records. What triggers it, how to test with dig or a free DNS lookup, and how to fix it.
Yahoo's 421 4.7.0 [TSS04] deferral means Yahoo is slowing mail from your IP because of complaints, volume or reputation. What Yahoo's Sender Hub says about it, why it is not a bounce yet, and the steps that make it clear.
Secondary domains are meant to absorb damage, but swapping them too early or too late both cost you. The signals that say rest, the ones that say retire, how to hand live leads to a replacement, and why the domain should stay registered after you stop sending.
The price per credit is only half the cost. Vendors differ on whether unknown, catch-all and duplicate rows use credits, and whether credits expire. Here is what we found on each vendor's own pages.
Warmup builds a sending history, not a reputation with your real prospects. Why domains that warmed perfectly land in spam on the first campaign, the five usual causes, and a launch plan that protects the warmup you paid for.
Export customer emails from WooCommerce, check them, and import only the good ones into Mailchimp, Klaviyo or another email tool. WooCommerce's checkout only checks the format.
Typeform's Email question only checks the format. Here is how to export responses, verify the email column and send only the real addresses to Mailchimp, a CRM or a sequence.
Mailshake's CSV rules (1MB, one email per row, per-campaign caps), its built-in list cleaning, how to export prospects campaign by campaign and how to re-import only verified rows.
Mail merges from Gmail send from your own account, so bounces hit your own reputation. Here is how to verify the sheet before you run GMass, YAMM or Mailmeteor.
Email verification and phone validation answer different questions. What a mailbox check, a phone format check and a live carrier lookup each tell you, which outreach needs which, how to clean a lead list with both columns, and what it costs on one plan.
Verifying 1,000 emails costs from nothing (free tiers) to about $40, depending mostly on each vendor's minimum purchase. A sourced table of the smallest packs and plans, the free allowances that cover part of a small list, and which option makes sense for a one-off versus a monthly 1,000.
What each result in an email verification report means, which reasons sit under risky, how catch-all rows are graded, and how to turn the report into send, test and suppress lists.
Double verification means checking a list with two tools and sending only where they agree, or running a second tool on the first one's risky rows. When it lowers bounces, when it just throws leads away, what it costs, and a workflow that keeps both numbers in check.
Public shorteners like bit.ly share one domain with every sender, spammers included, and hide where a link goes. What Spamhaus and Google say, when a branded short link is fine, and how to check your links before you send.
Truelist's Unlimited plan is $799-$999 a month paid upfront for 3, 6 or 12 months; credits start at $1.40 per 1,000 and catch-all resolution costs 3 credits. Alternatives compared on flat pricing, one-off packs and catch-all handling, from each vendor's own pages.
Before you move a whole campaign to a new data vendor, scraper or enrichment tool, run a pilot. How many leads to test, why 100 is too few to judge a bounce rate, the pass marks to set in advance, and a scorecard for comparing sources side by side.
SURBL lists domains that appear in spam, phishing, malware and hacked-site links. What each SURBL list means, why a listed domain can hurt email and even link previews elsewhere, and the cleanup SURBL asks for before you request removal.
A deferral is a 4xx 'try again later' and the message is still in your provider's queue. A bounce is the final failure. How long Gmail, Microsoft 365 and other servers retry, what the delay notices mean, and what cold senders should do with each.
A list-prep checklist for a US A2P 10DLC SMS campaign: consent records, E.164 formatting, deduping, line-type checks and opt-out handling, and what validation cannot tell you.
Amazon SES places accounts under review when trap operators report hits. AWS won't name the trap addresses or the threshold, and says proving a fix can take three weeks or more. Which parts of the list to cut, and why a reconfirmation email can backfire.
Amazon SES can put an account under review for complaints that never show in your complaint rate metric. What direct and email-provider complaints are, why SES can't tell you who complained, and what to send AWS within the three-week window.
At 30 to 40 hand-written cold emails a day, a separate domain isn't required, but it's cheap insurance. When sending from your main domain is reasonable, the numbers that would hurt it, and the setup if you do split.
Scrubby's Deep Verification sends real emails and watches for bounces over 72 hours at 3 credits each, on plans from $47 a month. The alternatives for catch-all leads, from resolvers to grading to testing the slice from your own inbox, with published prices.
You verified an address yesterday and it came back valid; today it says risky or unknown. Greylisting, rate limits, catch-all flips, provider blocks and real mailbox changes explain almost every flip. How to tell which answer to trust, and what to do with the address.
Split a cold email list by the prospect's mail provider before you send: Google Workspace, Microsoft 365, security gateways, Microsoft consumer and other hosts. What each route needs, how to cap volume per route, and what provider matching can and cannot do.
Suppress every hard bounce, but not every hard bounce is forever. A rule set by bounce code: keep 5.1.1 suppressed, re-check domain-level failures after a wait, and release an address only on new evidence, such as a new signup or a fresh mailbox check.
Someone uploaded a bought list to your main email platform and hit send. What happens next with your ESP, Gmail and your real subscribers, a day-by-day recovery plan, and how to stop it happening again.
Leads who finished a sequence without replying are not dead, but mailing them again months later has its own risks: addresses that died, people who moved, and complaints from people who already ignored you. How long to wait, who to exclude, how to re-verify the old list, and how to change the second attempt.
Some addresses only accept mail from inside their own organisation. Microsoft 365 returns 550 5.7.133 for groups, 5.7.134 for mailboxes and 5.7.12 for the organisation; Google Workspace returns a 550 5.7.1 policy rejection. What each means, why shared addresses like sales@ hit it, why a verifier can't always see it, and what to do.
What to ask a B2B contact data vendor before you buy: what verified means, when the record was last checked, what you're charged for bad results, sample terms, CRM dedupe and the legal basis. With the published answers from Apollo, Lusha, Snov.io and UpLead.
When a prospect's company uses Proofpoint, your mail can be blocked with '554 Blocked - see proofpoint.com/postmaster', deferred with 421, or filtered silently. What each means, what Proofpoint checks, and how to request removal.
Pre-warmed and done-for-you inboxes save weeks, but you may not own the domain, get admin access or be able to leave the platform. Seven questions to ask, how to test a new batch, and why warmup doesn't fix a bad list.
Enrichment tools and scraped lists often return personal addresses for business leads. When a freemail address is the right one to send to, when to swap it for a work address, when to drop it, and how to split a list by free and company domains before you verify.
The 550 5.7.1 S3150 bounce from Outlook.com and Hotmail means Microsoft has blocked the network your mail comes from, not your address or your copy. Who owns the blocked IP, which Microsoft form to use (and which not to), what to send, and what to do with Outlook.com leads while you wait.
Consumer Microsoft addresses (outlook.com, hotmail.com, live.com, msn.com) often come back risky from email verifiers. Here is why, including our own current limit, how Microsoft 365 business addresses differ, and a routing plan that keeps these leads without wrecking your bounce rate.
check-if-email-exists (Reacher, Rust) and AfterShip's email-verifier (Go) are MIT-licensed and do real SMTP mailbox checks. What they need to run: open port 25, a clean IP with reverse DNS, and proxies at volume. Where self-hosting is the right call and where a hosted verifier is cheaper.
Mimecast rejections such as '550 Administrative prohibition envelope blocked', 'Anti-Spoofing policy', 'Local CT IP Reputation' and '451 Internal resources are temporarily unavailable' each mean something different. What each one means, who can fix it, and what a cold sender should do.
550 5.7.708, 5.7.705 and 5.7.750 are Microsoft 365 errors about your own tenant, not the recipient. 5.7.708 means Microsoft is not accepting outbound traffic from the IP, usually for new or trial tenants; 5.7.705 means the tenant is blocked for spam; 5.7.750 means mail from an unregistered domain. What each means and how an admin gets the block lifted.
Microsoft's 550 5.7.606-649 bounce means your sending IP is on the Microsoft 365 blocked senders list. What it means, how the sender.office.com delist portal works step by step, when it does not apply (5.7.511, Outlook.com), and how to avoid being listed again.
Microsoft 365's 550 5.7.509 bounce means your From domain failed DMARC and publishes p=reject. Why cold email setups trip it (a sending tool without aligned DKIM, a borrowed bounce domain, strict alignment), how to read the headers, and the fix in order.
Microsoft's 451 4.7.650 is a temporary deferral on Outlook.com, Hotmail and Live mail because of your sending IP's reputation. What it means, why retrying harder makes it worse, and a step-by-step way to recover.
Blank merge fields come from empty cells, tags that don't match a column name, placeholder values like n/a, and unclosed braces. How each sending tool handles them, the fallback syntax for Instantly, lemlist, Smartlead, Mailchimp and HubSpot, and a pre-send check.
How to export, verify and re-import contacts in Loops: its CSV matching rules, how it suppresses hard bounces, its bounce-rate guidance and what its terms say about imported lists.
When cold email bounces climb, the cause is either bad addresses or a sender problem: reputation, authentication or a block. The bounce codes, the pattern across providers and three quick tests tell you which, and the fix for each is completely different.
Enrichment waterfalls, merged lists and CRMs often give one person several addresses. How to pick one send address per lead: verification status first, then work over personal, then the company's current domain and pattern. Plus how to stop the others leaking into campaigns.
Apollo refunds bounced verified emails within 30 days (its help pages differ on whether mail sent outside Apollo counts); Findymail refunds credits above a 5% bounce rate; Hunter charges nothing for no-result searches. What each policy covers, and what none of them do.
Kajabi's import limits, its 5% hard bounce and 0.2% complaint limits, and how to export, verify and re-import a contact list so imports go through and sends are not suspended.
ZeroBounce is a well-known email verifier with a wider deliverability suite, a $39 minimum pack and a $99-a-month subscription. What you actually pay per 1,000 at each size, what the guarantee and credit terms say, and when a cheaper verifier makes more sense. Sourced from ZeroBounce's own pages, with read dates.
MillionVerifier is a real, long-running email verifier with some of the lowest published bulk prices and credits that never expire. What it costs per 1,000, who runs it, what its money-back guarantee actually requires, and the cases where results look inconsistent. Sourced from its own pages, with read dates.
Apple's iCloud Mail rejects mail with 554 5.7.1 [CS01] or [HM08] 'Message rejected due to local policy'. Apple doesn't publish what each code means, but it does publish its sender requirements. How to read the bounce, the checklist to work through, and when to contact Apple.
Work out how many cold email domains you need from daily sends, sequence length and inboxes per domain, with a worked table and the limits behind it.
Emailing ten people at the same company on the same day looks like a campaign to their security filters and their colleagues. A practical per-company cap, how to stagger contacts, how catch-all and gateway domains change the answer, and how to enforce it in a lead list.
Choosing the mailbox provider behind your cold email inboxes: the sending limits each one publishes, the trial and new-tenant traps, how each treats bulk mail in its own terms, and why many teams run both. A planning table and a setup order.
Gmail's 550 5.7.26 rejects mail that fails authentication. It comes in three versions: unauthenticated sender (no SPF or DKIM pass), SPF hard fail (-all), and a DMARC policy rejection. What each one means, how to find which service is failing, and how to fix it without breaking other mail.
Gmail uses 550 5.7.1 for spam judgements, low reputation, sending from the wrong IP, broken headers, rate limits and recipient policies. A table of every variant on Google's list, who has to fix each one, and what to do about 'likely unsolicited email' and 'policy that prohibits'.
Gmail rejects messages with duplicate headers, more than one From header, no Message-ID, several addresses in From or malformed header values. What each 550 5.7.1 format error means, the RFC 5322 rule behind it, why scripts and mail merges trigger it, and how to find the broken header.
Gmail's 'The IP you're using to send email is not authorized to send email directly to our servers' means mail is leaving from an IP that should hand it to a relay. Why home, office and some cloud IPs get it, how the Spamhaus PBL fits in, the IPv6 variant, and the fixes that work.
Gmail rate-limits (421 4.7.29) or blocks (550 5.7.29) mail that arrives over a connection without TLS. Who still sends unencrypted mail, how to turn on STARTTLS in Postfix, Exim, scripts and devices, how to test the connection, and how it differs from 530 5.7.0 and MTA-STS.
Gmail's 421 4.7.28 deferral says it has seen an unusual rate of email, or of unsolicited email, from your IP, netblock, DKIM domain, SPF domain or a URL in your message. What each variant points at, why cold senders hit it, how 4.7.28 differs from 550 5.7.28, and a fix plan that works.
Gmail rate-limits mail that fails SPF (4.7.27), fails DKIM (4.7.30), has a From domain that isn't aligned (4.7.32) or comes from a domain with no DMARC record (4.7.40). What each code checks, the permanent 5.7.x versions, the cold email setups that trigger them and how to fix each one.
Gmail's 421 4.7.0 and 550 5.7.1 'suspicious due to the very low reputation of the sending IP address' or 'sending domain' errors mean Gmail no longer trusts that sender. What the IP and domain versions mean, why they happen to cold senders, how to rebuild, and what not to do while you wait.
How to export Ghost members, verify the email addresses, and import or update members by CSV, plus what Ghost does when newsletters to a member keep failing.
Freshsales warns at a 5% bounce rate and can suspend email at 10%. How to export contacts, verify them, and update only the good records with an update-only import.
Step 1 bounces under 2%, then follow-ups climb to 5% or more. The causes are a shrinking denominator, delayed bounces, addresses that die mid-sequence, and blocks that build up as you keep mailing. How to tell which one you have and the fixes for each.
Flodesk reviews imported lists and needs opt-in records. How to export subscribers, verify them, and upload a CSV that passes review and does not bounce.
é and ’ in a contact list mean a UTF-8 file was read as Windows-1252, and the text can be recovered. � means a Windows-1252 file was read as UTF-8, and that copy has lost the letter. How to tell which, fix it, and import the list cleanly.
Remove Duplicates only catches the same address twice. The same person at a work address, a Gmail and an old job's address needs matching by name and company. How to do it in Excel, what HubSpot's duplicate tool compares, and which address to keep.
A CSV of leads has a job title column but no seniority level. How to sort titles into owner, C-level, VP, director, manager and IC with rules that handle Sr., SVP and assistants, pick the levels that buy, and cap contacts per company before you send.
Export Wix contacts as a Regular CSV so the email subscription status comes with them, sort Subscribed from Unsubscribed and Never subscribed, merge repeats and check the addresses before importing them elsewhere.
Download the registration or attendance report from Teams, Google Meet, GoTo Webinar or Zoom, split attendees from no-shows, drop your own panelists, respect the opt-in answer and check the addresses before the replay email.
Export a Squarespace mailing list as subscribed, unsubscribed and cleaned files, or export contacts and customers. Which file to import, what Accepts Marketing means, and how to check the addresses first.
Export the Square customer directory, keep only customers whose Email Subscription Status allows marketing, merge repeats and check the addresses before you import them into Mailchimp, Klaviyo or another email tool.
PayPal has no customer export, but its activity download lists the payer's email on every payment. How to download it, strip out fees, transfers and your own address, merge repeat buyers, handle consent and check the addresses.
Download your Mighty Networks member list, find the commercial email opt-out column, keep members with an address, merge members on several plans and check the addresses before mailing them from another tool.
Export the customer list from the Clover web dashboard, split cells that hold several addresses, keep customers who allow marketing, merge repeats and check the addresses before your first campaign from another email tool.
Export your Circle community's members as CSV, use the email marketing preference column to keep only subscribed members, drop invites who never joined, merge repeats and check the addresses before mailing them from another tool.
Google Calendar exports guest responses to Sheets on large events, and any calendar exports an .ics file. Outlook copies or downloads the tracking list. How to get attendees out with their RSVP, drop rooms and declines, and check the addresses before the follow-up.
Export BigCommerce customers with the Bulk Edit template, find the column that says who wants email, add newsletter subscribers and guest buyers, merge repeats and check the addresses before a campaign.
Export AWeber subscribers from the Subscribers page or with Backup Data, keep Currently Subscribed, carry unsubscribes into your next tool's suppression list, drop pending contacts, merge lists and check the addresses.
EmailOctopus' Acceptable Use Policy sets a hard bounce line below 5% and complaints below 0.10%. How to export, verify and re-import contacts so the account stays within them.
Enterprise prospect lists are full of catch-all domains and security gateways, and each lead is worth far more than a check. What matters when you choose a verifier for enterprise sales: honest catch-all handling, gateway transparency, re-check cost, CRM and API fit, and the security paperwork procurement will ask for. A checklist and a scoring table.
Some email verification credits never expire, some expire after 12 months, and some reset every 30 days. A sourced, dated table for 15 verifiers and our own plans, read from each vendor's own pages, plus how expiry changes the real price you pay.
MillionVerifier, NeverBounce, ZeroBounce and Emailable all publish bounce or accuracy guarantees. The fine print decides whether a cold-email list qualifies: opt-in only, freemail excluded, 24-72 hour send windows, full bounce logs. A side-by-side table and what to do instead.
AI SDR agents find, guess and write to addresses without a human checking each one. Here is how to put a verification step in the loop, what fields an agent should read, and how to catch addresses an LLM made up.
Email verification checks whether a mailbox accepts mail, not whether the person still works there. How Microsoft 365 and Google Workspace admins handle a leaver's mailbox (shared mailbox, forwarding, alias, deletion), what a verifier sees in each case, the signals that someone has left, and a process that keeps your list current.
No mailbox provider publishes an image-to-text ratio. What is published: SpamAssassin rules that fire on HTML email with images and very little text. What they test, where 60/40 and 80/20 come from, and how to check your email.
A feedback loop tells you when recipients mark your mail as spam. Yahoo's CFL works per DKIM domain, Microsoft's JMRP works per IP through SNDS, and Gmail's FBL gives aggregate data by Feedback-ID in Postmaster Tools. What each one needs, what you get back, which ones a cold sender on Google Workspace or Microsoft 365 can use, and what to do with the reports.
Customer Insights - Journeys sets an 8% hard bounce limit and a 0.3% complaint limit. How to export contacts and leads from Dynamics 365, verify them and update records with an alternate-key import.
Cold senders on Google Workspace or Microsoft 365 send from shared IPs they do not own. What that leaves you in charge of: domain reputation and the standing of each sending account. How to tell which one is hurt from the symptoms, and what to do about each.
Verifying a list with a hosted email verifier does not send any email and does not use your domain or IP, so it cannot hurt your sender reputation. What a verification check actually does, the cases where it can cause problems (running checks from your own sending server, mailing the risky results), and the questions to ask a vendor.
Inbox placement fell after a commerce replatform or ESP move, even with DKIM, SPF and DMARC redone and a warmed IP pool. The usual causes (new IPs, a changed From or DKIM domain, mixed mail streams, dormant contacts re-imported) and the order to fix them in.
At 10,000 emails a day you're a Gmail bulk sender with DMARC and one-click unsubscribe required. Published prices for Amazon SES and Mailgun at that volume, what changes with a dedicated IP, and the list-cleaning cost that's easy to leave out.
Adding a contractor to email leads? Don't share a founder's password or put cold outreach in a shared sales@ inbox on your main domain. Give them their own mailbox, preferably on a separate domain, control the list they send to, and know how to cut access the day they leave.
Clean on Spamhaus, listed on UCEPROTECT Level 3, perfect score on a content tester, and still in spam. Each test measures a different thing. What each one can and can't tell you, and how to isolate the real cause one variable at a time.
Large companies put security gateways and strict Microsoft 365 settings in front of their inboxes, so cold email that lands fine at small businesses gets blocked, deferred or quarantined at enterprises. How to see which filter a target uses, what each one's rejections mean, and a sending plan built for enterprise lists.
Setting up MX, SPF, DKIM and DMARC on 10, 30 or 50 sending domains by hand is where typos happen. How to use one record template, bulk tools at Cloudflare and Namecheap (and their traps), keep a domain inventory, and check every domain in one pass.
Turn a bounce-rate limit into a number of bad addresses per inbox per day and per campaign. Why small daily volumes make one bounce look huge, how sequencer auto-pause minimums work, and how to spend the budget on catch-all and unverified leads.
When a company moves from Google Workspace to Microsoft 365, or the other way, addresses that verified last month can start bouncing. How migrations change addresses, why a domain can look catch-all mid-migration, how to spot a move before you send, and what to re-verify.
Keap calls a hard bounce rate above 5% per provider excessive. How to export contacts from Keap Pro/Max or Max Classic, verify them, and bring results back without breaking email statuses.
Talos scores sending IPs as Good, Neutral or Poor, and Cisco email gateways use that score to filter mail. What each level means, why cold-email IPs land on Neutral or Poor, and the fix-then-wait-then-ticket route to recovery.
Resellers offering ZoomInfo exports or shared logins at a fraction of the price are selling data the licence says can't be passed on. What ZoomInfo's licence terms say, the $2-per-record liquidated damages clause, why resold exports bounce, and safer ways to get the same contacts.
A catch-all address that did not bounce on step 1 is not proven to exist. How to structure catch-all leads inside a multi-step sequence: their own campaign, the gap before step 2, which signals let a lead continue, and when to stop.
Every 'catch-all verifier' uses one of four methods: label it risky, grade it, resolve it with private data, or send real mail and watch for bounces. How each works, what it costs per address, the trade-offs, and how to test one on your own list.
A CAN-SPAM footer needs two things the law spells out: a valid physical postal address and a clear way to opt out. Here is what counts, what Gmail and Yahoo add for bulk senders, what Canada adds, and a footer you can copy.
Campaign Monitor's import rules, its 0.2% complaint warning and 0.5% suspension line, how bounces are handled, and how to export, verify and re-import a list cleanly.
A company hiring for a role your product supports is one of the clearest buying signals in B2B. How to turn job posts into a lead list: which roles to watch, how to find the hiring manager rather than the recruiter, how to get and verify their address, and how fast to act.
If verified addresses bounce from your sequencer inboxes but accept the same email from your own mailbox, the receiving server is rejecting the sender, not the address. How to read the codes, run the test properly and fix the sending side.
When a burst of bounces comes from a single recipient domain, the cause is rarely your whole list. It is usually a mail migration, a directory or catch-all setting that changed, a guessed email pattern, or that company blocking you. How to diagnose it in ten minutes and what to do with the leads.
A 90% open rate and 15% click rate with no replies usually means security scanners and privacy features, not people. How Microsoft Safe Links and other filters click links, how to spot machine clicks, and what to measure instead.
A 554 bounce that says your client host was blocked using Barracuda Reputation means the sending IP is on the Barracuda Reputation Block List. What it means, how to confirm which IP is listed, Barracuda's removal form and its rules, and how to stop it happening again.
Welcome or waitlist emails sent by Apps Script from a Gmail inbox often land in spam: identical machine-sent messages, links, no history and a CC on every send. The Apps Script quotas, what to change if you stay on Gmail, and when a sending service is cheaper than the damage.
Scaling a running campaign by plugging in fresh inboxes is where many teams undo their warm-up. How to bring new inboxes in at a low daily cap, which leads to give them, what to watch in the first two weeks, and the account limits that apply to brand-new Workspace and Microsoft 365 accounts.
550 5.4.1 'Recipient address rejected: Access denied' is Microsoft 365 refusing an address that is not in the recipient's directory. It is not a block on your domain. How to read it, when it is the recipient's fault, and what to suppress.
Phone validation ranges from free format checks to paid carrier lookups billed per number. Here is what each level tells you and what it costs, using published prices.
How sender reputation is scored, domain vs IP, how to check it in Postmaster Tools, SNDS and Sender Score, and the habits that improve and protect it.
How to avoid spam filters in the order filters weigh things: authentication, a verified list, steady volume, low complaints, then content.
EmailListVerify publishes some of the lowest prices for small and mid-size lists. Here is when to stay with it, and when volume, features or phone checks make an alternative better.
Get a SimpleVerifier API key, test it, verify an address with curl, then call it from Node.js or Python. Links to the open-source SDKs on GitHub and the full API docs.
One table of email marketing benchmarks from Brevo, Mailchimp, MailerLite, Klaviyo, GetResponse and more, with what to do if you're below each one.
Cold email deliverability step by step: verified list, secondary domains, authentication, tracking, warm-up, per-inbox volume, rotation and monitoring.
Eight breakup email templates for the final follow-up, when to send one, which versions to avoid, and how to suppress and re-verify non-responders afterwards.
Check the six causes of spam placement in order: authentication, blocklists, bounces, sending patterns, content, then engagement. A free tool for each step.
Add SimpleVerifier's MCP server to Claude Code, Claude Desktop or Cursor and ask the assistant to check addresses: the config for each client, the tools it gets, and what the results mean.
Microsoft disables Basic auth for SMTP AUTH by default at the end of December 2026. Here is what stops sending, how to tell if your sequencer is affected, and the order to fix things in.
Omnivore is Mailchimp's abuse-prevention system. If it flags your import or campaign, here is what usually triggered it, how to respond, and what verification can and cannot fix.
Hunter.io alternatives for email finding, compared on October 2026 prices, cost per 1,000 found emails, and whether you pay for unverified results.
Nine public cold email studies compared on sample, period, reply definition and headline number, plus the stats on bounces, follow-ups, length and tracking.
Six complete cold email sequences for SaaS, agencies, local services, recruiting, partnerships and re-engagement, with day spacing, full copy and the reasoning.
Clearout's lowest headline prices need annual billing; month-to-month and one-time credits cost more. Here is how its published prices compare with other email verifiers.
Cold email studies point to Tuesday to Thursday mornings in the recipient's time zone, but the gaps are small. Why not to send it all at once.
A practical list hygiene checklist for Instantly and Smartlead: what each platform's API lets you do with bad leads, the rate limits that set your timing, and the order to clean a campaign before launch.
Hard bounces are permanent, soft bounces temporary. How to tell them apart by SMTP code, and how many soft bounces Mailchimp, Klaviyo and Brevo allow.
Published open rate averages run from 21.5% to 43.46%. Each source with its date and sample, why they differ, and what Apple Mail Privacy Protection does.
The four levers of email deliverability (authentication, list quality, volume and engagement), what Gmail, Yahoo and Microsoft require, and how to fix problems.
Published email bounce rate benchmarks run from 2.33% to 10.09%. Every figure linked to its source and date, why they differ, and the number to aim for.
Cold email in launch order: the law, the list, verification, domains, warm-up, volume, copy, follow-ups and measurement, each linked to a deeper guide.
Contact data from Lusha, Seamless.AI and similar tools still needs checking before it goes into a sequence. A step-by-step clean: dedupe, verify, handle catch-all, and re-import.
Bouncer sells non-expiring credit packs and the same volumes monthly at 20% off. Here is how alternatives compare on published prices, and which pricing model suits your volume.
A plain breakdown of ZeroBounce's published pricing: the free plan, pay-as-you-go packs, the ZeroBounce ONE subscription, and how the cost per 1,000 changes with volume.
What SPF, DKIM and DMARC each check, how alignment ties them to your From address, example records, and what Gmail, Yahoo and Microsoft now require.
How to clean and verify a lead CSV before importing it into Reply.io, Woodpecker or Saleshandy: columns, dedupe, verification, catch-all handling and a safe first send.
How to write a cold email step by step: pick the reason, check the address, write the subject, opener and one ask, then cut. With a bad draft rewritten.
Copy-paste DMARC records for monitoring, quarantine, reject, subdomains, parked domains and third-party reports, each explained tag by tag against the RFCs.
24 cold email templates for sales, partnerships, recruiting, PR, agencies and investors, each with when to use it and why it works. No invented reply rates.
Instantly, Smartlead, Saleshandy, lemlist, Woodpecker, Mailshake, Apollo and Reply.io compared on price, metering, warm-up and verification, from vendor pages.
Turn on daily auto-verify for a campaign, list or audience: once a day only addresses not seen before are checked and tagged, up to 10,000 a day, using your plan allowance and never pack credits.
How to format a professional email: subject line, greeting, a one-line purpose, short body, clear ask, sign-off and signature. With six ready examples.
What daily sending-domain monitoring checks (MX, SPF and its 10-lookup limit, DKIM, DMARC, free blocklists), how change alerts show the exact fix, and how to set it up for cold email domains.
If Microsoft 365 returns 550 5.1.8 or puts a user on the restricted entities list during cold outreach, here is how to unblock them and stop it happening again.
Instantly, Smartlead, Woodpecker, Mailshake, Apollo and Reply.io compared with lemlist on what each meters and costs, from vendor pricing pages on 8 Oct 2026.
Lead enrichment adds missing fields to a contact or company record. Which fields matter, where the data comes from, how fast it decays, and the GDPR duties.
Email list management is a lifecycle: collect, confirm, segment, verify, suppress, sunset. What to do at each stage, who owns it, and the rules that apply.
DeBounce has some of the lowest published per-credit prices for email verification. Here is when it is the right choice, and when a flat plan, phone checks or other features make an alternative worth it.
A six-step process for cleaning phone numbers in any CRM: export, normalise to E.164, remove invalid numbers, merge duplicates, split mobiles from landlines and re-import.
Six B2B lead generation strategies compared on the real cost: hours per week, time to first lead, and what breaks. Plus how to pick two and run them well.
Google Maps scraper exports are full of role addresses, dead websites, duplicates and messy phone numbers. Here is how to turn one into a list you can safely email or call.
Validate, format and classify phone numbers in Python with the phonenumbers library: parsing, E.164, line type, finding numbers in text, and cleaning a CSV with pandas.
Kickbox bills per email through credit packs, from $10 for 1,000 to $500 for 100,000. Here is how other verifiers compare on published prices, expiry and pricing model.
Write international numbers as + country code + national number, without the trunk 0. Examples for 12 countries, the Italy exception, and how to convert a mixed list.
Read receipts, tracking pixels and Apple Mail Privacy Protection explained from the providers' own docs, and why a reply is the only reliable sign of reading.
Google's published daily sending limits for personal Gmail and Google Workspace, what happens when you hit one, and why Gmail is the wrong tool for bulk mail.
Twelve follow-up email templates by scenario: after no reply, after a meeting, after a proposal, after a referral and more, with notes on when each one fits.
Authentication checkers, blocklist monitors, Postmaster Tools, SNDS, seed testers, warmup and verification: what each tool type can and can't tell you.
How to write cold email subject lines that read like a real message, with 50 examples sorted by situation and no made-up open-rate statistics.
Many business domains accept any address, so their mailboxes cannot be confirmed. How to split catch-all rows by higher, medium and lower likelihood, and which ones to send, test or drop.
ZeroBounce and NeverBounce compared on published pricing, free allowance, credit expiry and fit for one-off cleans versus regular verification, plus when a third option costs less.
Connect Instantly to SimpleVerifier once, pick a campaign or lead list, and check every lead in place. Results are tagged back as sv_status; deleting or blocking invalid leads is opt-in.
Connect HubSpot with a service key, verify a list or segment in place, and write valid, risky or invalid into an sv_status contact property you can filter, report and build workflows on.
is_email() only checks the shape and checkdnsrr() misses null MX. A small tested plugin adds a real domain check to registration, WooCommerce and form plugins.
We tested Commons Validator, Hibernate's @Email and Jakarta Mail on 17 cases: what each accepts, the empty-string trap, and an MX check with JNDI timeouts.
Texts fail because of invalid numbers, landlines, wrong country codes, opt-outs, unregistered 10DLC traffic and carrier filtering. What each failure means and how to stop it before you send.
Why bots create fake Shopify customers, the settings that stop them (hCaptcha, new customer accounts, double opt-in), and how to find and delete the fakes.
Verify a Mailchimp audience or segment in place, tag each subscribed contact with an SVSTATUS merge field, and optionally unsubscribe or archive invalid contacts before the next campaign.
How to hide a honeypot so bots fill it and people never do: off-screen vs display:none, keyboard and screen reader tests with axe, autofill, and server code.
Connect Smartlead to SimpleVerifier, verify a campaign's leads without exporting, tag risky and invalid ones, and optionally pause, delete or block invalid leads. With Smartlead's API limits explained.
A tested Python script that verifies a CSV through any email verification API: dedupes, paces requests, honours Retry-After and resumes after a crash.
Amazon SES puts accounts under review when the bounce rate reaches 5% and may pause sending at 10%. Here is how to respond to a review, fix the list and get the rate down.
555-0100 to 555-0199 is reserved for films and examples, yet phone validators mark (212) 555-0100 as valid. What 555 numbers are, and how to catch them in a lead list.
A tested Next.js 16 server action that checks email syntax and MX records on signup, keeps the user's input on error, and defers slow checks with after().
Validate, format and type-check phone numbers in JavaScript and TypeScript with libphonenumber-js: parsing, E.164, line type, as-you-type formatting, and a React form example.
A tested React 19 email field: native constraint validation, errors on blur, typo fixes that won't mangle real domains, and a server check that fails open.
Every character RFC 5321 and 5322 allow before and after the @, the dot and hyphen rules, quoted local parts, and how five validators handled 33 symbols.
US calling rules treat mobiles and residential landlines differently, and you can't tell them apart from the number. What the TCPA distinguishes and how to find each number's line type.
What RFC 6530-6532 allow, which libraries accept user@münchen.de vs 用户@例子.广告, and which big mail servers advertised SMTPUTF8 when we checked.
Cold email puts different demands on a verifier than newsletters do. Here is what to check: catch-all labelling, provider detection, export format, re-check pricing and more.
Pace verification API calls under the vendor's limit, honour Retry-After, back off with jitter. Tested against a mock API: going over the limit was slower.
A step-by-step way to clean a ZoomInfo contact export before it goes into a sequencer: dedupe, filter, verify, handle catch-all domains and re-import.
A bounce spike needs triage before recovery: pause every send on the list, sort bounces by SMTP code, find the source, clean what is left, then resume small.
Scraped email lists carry parsing junk, stale pages, role addresses and traps verifiers cannot see. Clean the artefacts, verify, then decide what to send.
The Reassigned Numbers Database tells US callers whether a number was disconnected after they got consent. How it works, the safe harbor, and how it differs from phone validation.
PECR lets you cold email UK limited companies without consent but not sole traders. The regulation text, ICO guidance, 2026 fine limits and a sending checklist.
NeverBounce charges $8 per 1,000 pay as you go and its credits expire after 12 months. Here are alternatives with non-expiring credits or flat pricing, compared on published prices.
An email list that has not been mailed for months carries dead addresses, recycled traps and lapsed consent. Check permission, verify, then restart in stages.
If Google Workspace stops a user from sending or suspends an account during cold outreach, here is how to tell which limit you hit, how to recover, and how to stop it happening again.
Founder-led cold email is for learning who buys, not for volume. How to pick accounts, protect your product's sending domain and judge results by conversations.
A domain can receive email if its DNS says where to deliver it. How to run an MX lookup on Mac, Windows or the web, read the answer, and what it does and doesn't prove.
ZeroBounce's smallest pay-as-you-go pack is 2,000 credits for $39. Here is what the same small lists cost at other verifiers, from their published pricing pages.
Verifying 100,000 email addresses costs anywhere from about $39 to over $800 depending on the vendor and pricing model. Here are the published numbers and how to cut the bill.
Australia's Spam Act needs consent before a commercial email, but a conspicuously published work address can imply it. The Act's text, ACMA rules and fines.
Salesforce Phone fields accept almost any text, so formats drift. Store numbers in E.164, add a validation rule, and clean existing records with an export and update.
Copy-paste regex patterns for E.164 and US numbers, what each one accepts that it shouldn't, and why numbering-plan libraries beat regex for real phone validation.
Open tracking adds a remote image and often a shared tracking domain to every cold email, and Apple Mail makes the data unreliable. When to turn it off.
We read the public DNS of 51 mailbox providers. All 51 publish SPF and DMARC, 39% still use DMARC p=none, 35% have MTA-STS and 22% DNSSEC. Plus where disposable email is hosted.
Inbox rotation splits cold volume across mailboxes, but domain reputation, list quality and complaint rates are still shared. How it works and how to set it up.
We asked 51 mailbox providers twice if a made-up address exists. 27 said no, 10 accepted everything, 7 refused us, and Microsoft and Apple were not asked.
74 figures on email deliverability in one CSV: bounce and spam-rate limits from Gmail, Yahoo, Microsoft and 10 platforms, plus our own 2026 studies of 51 mailbox providers.
Personalizing cold email at scale is a data problem: segment-level relevance, clean merge fields and checked AI lines. The fields, fallbacks and QA steps.
Build a B2B email list by choosing accounts first, then roles, people and addresses, then verifying. Seven steps, the columns to keep and the traps.
Unlimited email verification plans charge one monthly price instead of per address. Here is the break-even point against credit packs, and when credits are still the better buy.
UK numbers are written 07911 123456 at home and +44 7911 123456 abroad. What each prefix means (01, 02, 03, 07, 08, 09), how to convert to E.164, and the quirks validators hit.
"Toxic" is a vendor umbrella term for traps, complainers, breached and bot addresses. What each tool means by it, and what a mailbox check can actually catch.
Turn on DKIM for a custom domain in Microsoft 365: get the selector1 and selector2 CNAMEs from Defender or PowerShell, publish both, enable signing, verify.
Store HubSpot phone numbers with a + and country code (E.164). How to fix a mixed-format property, clean numbers before import, and validate them in bulk.
Set up DKIM in Google Workspace from the Admin console: generate the key, publish the google._domainkey TXT record, start authentication and confirm it passes.
Validation usually means checking an address is well-formed; verification means asking the mail server if the mailbox exists. How vendors blur the two words.
Split your list by who hosts each mailbox, not by domain name: Gmail vs Workspace, Outlook.com vs 365, Yahoo and gateways. Each has its own rules and tools.
Bulk email verification checks a whole CSV of addresses in one job. Here is what each check does, what a list costs to verify at different sizes, and a step-by-step run.
A migration is when old list problems surface. What to export, verify and segment before your first send on a new ESP, using each platform's own rules.
Who to include, what to send, how to measure it without trusting opens, and what to do with people who never answer. A practical re-engagement campaign plan.
A bad calling list burns rep hours on dead numbers, switchboards and wrong countries. What to check before a cold-calling session, in what order, and what each check costs.
Bulk verification time depends less on list size than on the servers you check: greylisting, rate limits, timeouts and domain mix. How to estimate yours.
Seven phone validation tools compared on price at 5,000 numbers a month, live carrier data, bulk upload and email checks. Which to pick for forms, SMS lists and lead files.
Business and consumer lists fail in different ways. Catch-all and job changes dominate B2B; typos, fake signups and Yahoo dominate B2C. What to do for each.
Accept-all means the server answered yes to everything. Unknown means it never answered. How to tell them apart, and why one is worth a retry.
Yahoo Mail serves far more than yahoo.com: ymail.com, rocketmail.com, country domains, AOL, and ISP addresses like att.net and verizon.net. Checked MX records and what that means for your list.
Twilio Lookup charges $0.008 per line type request, about $40 for 5,000. Alternatives compared on price, bulk upload and email verification, as of October 2026.
What each Spamhaus dataset lists, how ZEN combines them, what every return code means, and the usage rules for the free mirrors versus DQS.
We probed Gmail, Outlook, Yahoo, iCloud and six company domains to show where SMTP verification misfires, in both directions, and how to catch each error.
Sender Score rates a sending IP from 0 to 100 against other IPs over roughly 30 days. What feeds it, what the bands mean, and what it can't tell you.
What a null MX record is, the exact DNS syntax, why a domain with no MX still receives mail attempts, and the full no-mail setup for parked domains.
Gmail's Promotions tab is inbox, not spam. What Google says decides the tab, why annotations don't move mail, and what changed in Promotions in 2025.
Copy-paste Google Sheets formulas to strip formatting, convert US numbers to E.164, flag invalid ones and find duplicates, plus where formulas stop and what to do then.
What a PTR record is, why Gmail and Yahoo reject mail without forward-confirmed reverse DNS, how to check yours with dig, and who can actually change it.
Numverify costs $14.99 a month for 5,000 requests. Alternatives compared on price, request caps, live carrier data and whether email checks come with it, as of October 2026.
How a seed test works, how to run one so the result means something, how to read inbox, tab, spam and missing results, and what a seed list cannot tell you.
What a custom tracking domain does, the exact CNAME records Instantly, lemlist and Smartlead use, the HTTPS catch, and whether to track opens at all.
The bounce rate formula, the denominator choices that change it, how to split hard, soft and policy bounces by code, and spreadsheet formulas you can copy.
What ARC (RFC 8617) is, how its three headers and cv= chain work, why forwarding breaks DMARC, and how Gmail and Microsoft 365 actually use ARC results.
Build a Make scenario that verifies emails through an API: HTTP module settings, routing statuses, Retry and Resume handlers, a cache, and the credit math.
Airtable can clean, dedupe and syntax-check emails but not confirm mailboxes. Formulas, a verification script within Airtable's limits, and a CSV round trip.
Tested PHP email validation: what filter_var accepts and rejects, why checkdnsrr passes null-MX domains, egulias/email-validator, Laravel rules and SMTP.
Server-side email validation in Node.js: what zod's z.email() rejects, why normalizeEmail should not be stored, cached MX lookups and checking a whole list.
A US phone number is +1, a 3-digit area code and a 7-digit number. The rules that make one valid, the formats to use where, and the numbers that look real but aren't.
What each Constant Contact bounce type means, how to remove the ones it recommends, why to unsubscribe rather than delete, and where verification fits.
You can check one number by saving it as a contact or opening a wa.me link. There's no official way to bulk-check a list. What works, what's risky, and how to narrow a list down to likely WhatsApp numbers.
Salesforce only flags an address after it bounces. How to export leads and contacts by Id, verify them, and write the results back with Data Loader.
Pipedrive marks a contact Bounced only after Campaigns fails to deliver. How to export people with their ID, verify the emails, and update Pipedrive in bulk.
Bad numbers cost money on every SMS send and drag down delivery rates. What to check before a campaign: format, country, mobile vs landline, consent and reassigned numbers.
US and Canadian toll-free numbers start 800, 833, 844, 855, 866, 877 or 888. UK freephone is 0800 and 0808. The full list by country, and how to find toll-free numbers in a contact list.
What Klaviyo suppresses on its own, what it misses, and a cleanup that uses its export, bulk suppression and sunset segment to cut bounces and billing.
Brevo can suspend campaigns above a 2% hard bounce rate. What it blocklists for you, what it cannot see, and a cleanup that uses its own tools.
ActiveCampaign's bounce rules, which statuses count toward your contact limit, and a cleanup using export, verification, import options and unengaged cleanup.
Single words rarely send email to spam. We read SpamAssassin's rule scores and Google and Microsoft's docs to show what filters weigh instead.
Choosing a phone number validation API: when a free library is enough, when you need a paid carrier lookup API, what they cost, and when a bulk CSV upload beats both.
Twelve questions to put to any email verifier before you pay, what a good answer sounds like, and a one-hour test protocol to check the answers yourself.
hotmail.com, outlook.com, live.com and msn.com all run on Microsoft's Outlook.com service. What's still issued, how their mail is routed, and how to handle them in a list.
A break-even formula for email verification with every assumption stated, worked across list sizes and invalid rates, including when it is not worth paying for.
Google Workspace allows 2,000 messages a day and Microsoft 365 10,000 recipients, but those are ceilings, not targets. Here is how to size a safe cold volume.
Published data says follow-ups add a large share of replies, but each extra step adds spam complaint risk. How to size a sequence against Gmail's 0.3% line.
Check every new HighLevel contact's email and phone inside a workflow with the Custom Webhook action: the request, saving the response, writing status into custom fields, tags, If/Else branches, costs, and how it compares with HighLevel's built-in email verification.
Verify the email on every Google Forms response with a short Apps Script: an installable form-submit trigger, an API call with the key in Script Properties, status and reason columns, a backfill for old rows, and the quotas that limit it.
Verify Zoho CRM lead and contact emails automatically: a Deluge function on a workflow rule calls an email verification API with invokeUrl, writes Email Status and reason back, and handles timeouts, rate limits and edition limits.
What Webflow's native forms and reCAPTCHA can and can't catch, then two working patterns: verify each submission through a signed form_submission webhook, or check the address before submit through your own endpoint. Copy-ready Cloudflare Worker code included.
Use Supabase's Before User Created hook and an Edge Function to reject invalid and disposable email signups before the user exists, with a short timeout that fails open so real signups never break.
Check every new lead and contact email in real time with a record-triggered Flow: the external credential and custom header, the HTTP Callout action, the asynchronous path, writing status and reason to custom fields, fault handling and loop prevention.
Build a Power Automate cloud flow that verifies email addresses from Microsoft Forms, SharePoint lists or an Excel table with the HTTP action: licensing, the request, Parse JSON schema, Switch on status, concurrency and retry settings, and writing results back.
Set up an email verification call in Bubble's API Connector with the key kept private, check addresses before Sign the user up, and verify existing users with a backend workflow that respects the API's rate limit.
Apple's Mail Privacy Protection made opens useless for spotting inactive subscribers. A worked sunset policy built on clicks, replies and purchases instead.
Duplicate phone numbers hide behind different formats: (415) 555-2671 and +1 415-555-2671 are the same line. How to normalise to E.164 and then remove duplicates in Excel, Google Sheets, code or a bulk tool.
GDPR allows B2B cold email on legitimate interest, but only after the ePrivacy or PECR rules allow the send. The two-layer test, with regulator quotes.
Published cold email reply rates range from 0.45% to 8.5%. Most of that gap is the denominator, not performance. How to read benchmarks and measure your own.
A step-by-step way to clean a phone column: back up, set the default country, convert to E.164, remove invalid and duplicate numbers, and import without Excel mangling them.
CASL needs consent before a commercial email to Canada, but a published business address can imply it. The Act's text and the CRTC's tests, applied.
CAN-SPAM does not ban cold email, B2B included. It sets seven rules on headers, subject lines, ad disclosure, address and opt-outs. Here is the text, applied.
No. Platforms forbid purchased lists, their spam traps can't be verified away, and UK rules need consent naming you. What the sources say, and what to do.
Outside North America the prefix usually tells you if a number is a mobile. In the US and Canada it can't, and porting makes it worse. How line-type lookups work and when you need one.
Format phone numbers in Excel as (415) 555-2671, 415-555-2671 or +14155552671. Custom formats, TEXT formulas, Flash Fill and converting a whole column to E.164.
Badge scans, hand-typed leads and business card scans fail in different ways. How to clean an event lead export in the 48 hours before your follow-up goes out.
Who verifies, when, and where the result lives: a verification workflow for SDR teams using Salesforce or HubSpot with Outreach, Salesloft or Apollo sequences.
Where ecommerce email addresses go wrong (checkout typos, popup discount abuse, Apple relay addresses) and how to verify them without blocking real orders.
The famous 22.5% a year figure has no traceable study behind it. What BLS job tenure data supports, a simple model by role, and how to measure yours.
Step by step: what the receiving server does with a dead address, the bounce you get back, how your sending platform and mailbox providers react, and the numbers that trigger trouble.
Build an n8n workflow that verifies each lead's email with an HTTP Request node: credentials, the request, batching under a rate limit, retries, routing valid, risky and invalid results, and when to use a CSV upload instead.
Add an HTTP API enrichment column in Clay that verifies every found email before it reaches your sequencer: setup, column references, rate limits, run conditions, routing risky results and verifying phone numbers too.
Verify every new HubSpot contact's email inside a workflow, using a Send a webhook action or a Custom code action: properties to create, setup, the 20-second limit, retries, branching on the result, and options without Data Hub.
Why addresses at gateway-protected companies come back risky, how to spot the gateway from the MX record, and how to send to them without wrecking your bounce rate.
Every free way to check an email list: what each one catches, where it stops, and how to tell when a list is clean enough to send. With a no-signup check you can run now.
Why addresses that passed verification still bounce, how to sort your bounces by SMTP code in ten minutes, and which causes are list problems, sending problems or real verifier errors.
Copy-paste Excel formulas to strip formatting, check US and UK numbers, flag invalid rows and find duplicates, plus how to stop Excel mangling phone numbers in the first place.
Twilio's SMS delivery errors sorted into list problems, compliance problems and temporary failures: 21211, 21614, 21610, 30003, 30004, 30005, 30006, 30007, 30008 and 30034, with what to do about each.
A step-by-step method for scrubbing a US calling list against the National Do Not Call Registry: who must do it, what access costs, the 31-day rule, exemptions, your internal list and the records that support the safe harbor.
A field-by-field method to validate leads: what each check on email, phone, name and company can prove, what it cannot, and a simple scoring rule to route every record.
An acceptance test for commissioned B2B lead lists: verify every email, sample the other fields, set pass marks in the contract, and read the result with a confidence interval.
Where to find the reason Gmail bounced your email, how to read the code, and a grouped table of Gmail's SMTP errors (recipient, authentication, reputation, format, limits) with the fix for each.
Candidate emails and client emails decay for different reasons. How to verify both in an ATS like Bullhorn, and why a hiring manager's address dies faster.
Real estate lists fail three ways: junk portal and IDX sign-ups, decade-old sphere addresses, and ISP mailboxes now run by Yahoo. How to clean each one.
How agencies should verify client email lists: intake checks, per-client reports, passing on the cost, and the processing terms needed before uploading.
Verifying an email list is processing personal data under GDPR. The lawful basis, the accuracy principle, processor contracts and the due-diligence questions to ask any verifier.
How email verification credits are metered: fractional credits, monthly resets, packs that never expire, duplicates and re-checks. With a break-even worked example.
Clean a donor email list in order: verify, reach lapsed donors by post or phone, then suppress. With steps for Bloomerang and Raiser's Edge NXT.
One master do-not-contact list for cold email: what goes on it, the deadlines Google, Yahoo, the FTC and the ICO set, how to sync it across tools, and where it fits before verification.
How to find and verify owner emails for roofers, HVAC and other trades: licence data, Google Places, the website, then verification. With Texas data.
Syntax and MX checks are a day's work. Mailbox-level SMTP verification needs port 25, clean IPs, catch-all detection, greylisting retries and constant upkeep. A component-by-component build-vs-buy guide.
A step-by-step protocol to compare email verifiers on your own data: seeded known-good and known-bad addresses, catch-all handling, unknown rates, timing and how to settle disagreements.
How to verify each new lead's email the moment it arrives, using Zapier, Make or your own webhook receiver, with the plan limits and timeouts that break it.
Tested Python email validation with email-validator and dnspython, plus three gotchas: untrimmed input, 65-character local parts and silent DNS timeouts.
Tested code for the three layers of email validation in JavaScript: syntax with validator.js, MX lookups with node:dns including null MX, and an SMTP probe.
Which providers ignore dots and +tags, sourced from their own docs, plus tested JS and Python that builds an identity key to stop repeat free trials.
How to check if a phone number is a cell phone: read the prefix outside North America, run a free check, use a carrier lookup for US numbers, and check a whole list at once.
We checked DNS for 37 common webmail typo domains. 20 can receive mail, so the typo never bounces. Here is tested code for a 'did you mean' prompt.
E.164 is the international phone format: a plus sign, the country code and the national number, no spaces, at most 15 digits. Examples for 12 countries and the conversion mistakes to avoid.
Stack cheap invisible checks first, challenges second and email confirmation last. Tested Node code for a honeypot, signed time-trap, rate limit and Turnstile.
Find which carrier a phone number belongs to today, including numbers that were ported. How carrier lookups work, why the area code lies, and how to look up a whole list at once.
googlemail.com is Gmail. Both domains reach the same inbox and share mail servers. Why the domain exists, why it breaks deduplication, and how to handle it in a list.
A free phone check confirms a number can exist, finds its country and puts it in E.164 format. What it can't do is tell you the line is connected. Here's where the line sits.
Nine email verification APIs compared from their own docs: endpoints, auth, timeout units, rate limits and status values, plus tested code to normalise them.
We tested five common email regexes against 23 real and broken addresses. None scored above 15. One took 4.8 seconds on a 33-character input. Here is the fix.
Verification proves a mailbox exists; double opt-in proves the person who owns it wants your mail. Here is what each one misses, and the order to run them in.
Checking a phone number happens at four levels: shape, numbering plan, carrier, and a real person. What each one proves, what it costs, and which you actually need.
A carrier lookup is the only reliable way to tell a VoIP number from a mobile or landline. How the check works, what free tools miss, and how to flag VoIP numbers across a whole list.
Gmail is personal and acme.com is business. But what about att.net, googlemail.com, or a company on Google Workspace? A practical test for any domain, plus the edge cases.
How to validate thousands of phone numbers at once: format every number to E.164, tag country and number type, split out the bad rows, and add carrier lookups where you need them.
Blocklists miss new throwaway domains; an MX check caught 420 of 445 that our list missed. Tested Node code and false-positive rules for signup forms.
How SendGrid, Mailgun, SES, Mailchimp and Postmark retry soft bounces, what RFC 5321 says, and a code-by-code rule for when to stop mailing an address.
Shared IPs suit most senders under about 50,000 emails a month. What SendGrid, Mailgun, Postmark and Amazon SES each publish as the cut-off, and what it costs.
Spam traps arrive through specific doors: bought or scraped lists, unconfirmed typos, old addresses and bot sign-ups. Here is each route and how to close it.
Read a raw email header the right way: Received lines bottom-up, Authentication-Results from your own provider only, then DKIM, Return-Path and alignment.
25 pre-send checks grouped by authentication, infrastructure, list, content, compliance and monitoring, each with the command to run and whose rule it is.
A step-by-step diagnosis for mail landing in Gmail spam: read the headers, check authentication and alignment, then reputation and spam rate, in that order.
A week-by-week plan to repair a damaged sender reputation: find the cause, stop the damage, restart with engaged recipients, and know what Gmail needs to see.
Delisting steps and published expiry times for Spamhaus, Barracuda, SpamCop, UCEPROTECT and Microsoft, plus our test showing public DNS can hide a listing.
What each Google Postmaster Tools dashboard measures, why a low spam rate can be bad news, and what to do about each reading, from Google's own docs.
Read the CAT, SFV and BCL values in Microsoft's headers to see why Outlook junked your email, then fix it with SNDS, JMRP and the May 2025 sender rules.
The exact List-Unsubscribe headers Gmail and Yahoo expect, a tested endpoint that handles both POST encodings, and the five mistakes that quietly break it.
Week-by-week warm-up tables for a new cold-email inbox and a new marketing domain, built on what Google says about volume, with clear stop rules.
We checked the DKIM keys big companies publish: many still use 1024-bit. What the RFCs and providers require, the defaults that cause it, and how to rotate.
How to set up secondary domains for cold email: DNS per domain, redirects, how many inboxes you need, and what a separate domain does not protect.
BIMI shows your logo in the inbox if DMARC is at enforcement and, for Gmail, you hold a VMC or CMC. Requirements, costs, a 40-domain check, and when to skip it.
SPF allows 10 DNS lookups. We measured what common includes cost, counted a real domain at 13, and show how to get back under without breaking mail.
Role addresses are not all equal. When info@ and sales@ are fine to email, why abuse@ and postmaster@ never are, and what Mailchimp and the RFCs say about them.
How to add email verification to a signup form without slowing it down or locking out real users: a layered latency budget, hard timeouts, and fail-open rules.
Outlook.com requires SPF, DKIM and DMARC from domains sending 5,000+ emails a day and rejects failures with 550 5.7.515. Who it covers and how to fix it.
A staged DMARC rollout with exit criteria for each step, how to read aggregate reports, and what changed when RFC 9989 retired the pct tag in May 2026.
Yahoo's documented missing-user error uses a code SMTP reserves for after a message is sent. Why that defeats verification, and how to handle Yahoo and AOL.
Outlook.com, Hotmail and Microsoft 365 behave differently when you check a mailbox. How to tell which one you are dealing with, and what each answer means.
A worked method for deciding how many catch-all addresses to email: score by source, measure with a test batch, then cap volume against your bounce limit.
Re-verify on triggers, not a calendar: at entry, before mailing anything not known-good in three months, and after a bounce spike. Cadences by list type.
Verifier accuracy claims rarely say what was measured. Why there is no ground truth, the three numbers that matter, and how to test a vendor yourself.
Syntax catches malformed input, MX catches dead domains, SMTP catches dead mailboxes. Real DNS lookups show where each layer stops and the next must take over.
How Smartlead calculates bounce rate, why its auto-pause fires late on big campaigns, and the list prep and settings that protect your inboxes.
Remove duplicate and malformed emails from a CSV in Excel, Google Sheets or a tested 20-line Python script, plus an MX check that handles null MX.
lemlist alerts at 10% bounces and auto-pauses at 50%, far above its own 5% advice. How to set your own stop rule, use its statuses, and prep lists.
How Instantly's 5% auto-pause, 200-email minimum, 7-day grace period and BounceShield actually work, and the list prep that keeps you below them.
Google Sheets can clean, dedupe and syntax-check emails, but it cannot confirm a mailbox exists. Tested formulas, the gaps, and the round trip to fix it.
Clean, dedupe and syntax-check an email list in Excel with tested formulas for Microsoft 365 and older versions, then verify the mailboxes properly.
What Apollo's email statuses, its 91% accuracy claim and its 6-month caveat mean in practice, and which rows of an Apollo export to re-check first.
What Mailchimp already cleans for you, what it leaves behind, and a step-by-step cleanup using its own bounce, Omnivore and archiving rules.
HubSpot's six hard bounce reasons need different fixes. A decision table, the segments to build, unbounce limits, and how to stop paying for dead contacts.
Collecting business emails is generally lawful, but the rules on collecting and using them differ sharply between the US, UK and EU. The regulators' own text.
At small firms the CEO often reads info@. At large ones the address follows a pattern but cannot be confirmed. We probed 60 big-company mail servers.
We ran 337 local trades businesses through the list-building funnel: source, website, email, mail server, verification. What survives each step, and why.
LinkedIn shows a member's email only where they allow it, and its User Agreement bans scraping. The methods that stay inside the rules, by reliability.
first.last, flast and first@ cover most business addresses. How to find a company's format, confirm a guess with an SMTP check, and when you cannot.
Voila Norbert's appeal is pay-on-success billing and rollover credits. These alternatives are compared on the same terms, at October 2026 prices.
Gmail rejects unknown mailboxes during the SMTP conversation, so you can check an address without sending. How, plus the dots, plus-sign and Workspace traps.
Verifalia sells verification depth by the credit. We priced its quality levels against alternatives and compared how long each API waits, October 2026.
We evaluated SPF records for 200 SaaS firms and 496 S&P 500 companies, counting every DNS lookup. 16 exceed the limit of 10, and ~all beats -all.
Hunter, Voila Norbert, Findymail and a split stack compared with Snov.io on what a found, sendable address really costs, on October 2026 pricing.
Reoon had the lowest published price under 100,000 emails in October 2026. When an alternative fits better, and the Quick-mode caveat in its own docs.
We checked MTA-STS and TLS-RPT on the S&P 500, 200 SaaS firms and the Tranco top 1,000. Only 58 domains publish MTA-STS, and just 28 enforce it.
MillionVerifier is hard to beat on price above 500,000 emails. Here is where alternatives win instead, with prices from each vendor's own page in October 2026.
Mailgun's validation API compared with five verifier APIs on price, auth, rate limits, timeouts and results, plus a status mapping for migration.
The exact bounce text Gmail, Microsoft and Yahoo publish for a non-existent mailbox, side by side with the SMTP and enhanced codes, and what to do with each.
Seven ways to find a work email address, ranked by how far you can trust the result, plus the verification step that turns a guess into a sendable address.
The ten steps to clean an email list, in the order that saves money and avoids mistakes, from suppression lists and MX checks to bounce handling.
What Gmail and Yahoo require from bulk senders, read from their own docs: authentication, the 0.3% spam line, one-click unsubscribe, and where the two differ.
A copyable list of 79 consumer email domains, from gmail.com to naver.com, each checked for live MX records in October 2026, with who actually hosts the mail.
Findymail starts at $99 a month with a 10-credit trial. Alternatives compared on entry price, trial size, phone costs and billing, as of October 2026.
Emailable sits mid-market on price with a clean API. Where Reoon, DeBounce, MillionVerifier, Bouncer and others beat it, on October 2026 prices.
An audit of accuracy percentages, guarantees, 'unlimited' and compliance claims on 19 email verifier sites, read in October 2026, and which can be checked.
What each email verification status means, how eight vendors name the same results differently, and which ones to send to, hold back or delete.
What 10,000, 100,000 and 1 million verifications cost at 19 vendors, read from their pricing pages in October 2026. The spread at 1M is more than 9x.
We looked up MX records for 496 S&P 500 firms and 200 SaaS companies. SaaS runs on Google (93.5%). Big companies hide Microsoft behind Proofpoint.
We looked up the DMARC record of 200 SaaS companies and 496 S&P 500 firms. 97% of the SaaS firms publish one, but only 63.5% fully enforce it.
We analysed all 8,740 domains on our disposable list and looked up each MX record. 47% of live ones share ten mail servers; a fifth no longer exist.
Cost per 1,000 checks at 5,000, 50,000 and 500,000 addresses from ten vendors' October 2026 pricing pages, and when a subscription beats credits.
The published bounce and complaint thresholds for Amazon SES, HubSpot, Brevo, Postmark, Instantly, lemlist and others, read from each vendor's own docs.
We checked BIMI records, logos and certificates on the S&P 500, 200 SaaS firms and the Tranco top 1,000. 16.9% of S&P 500 brands publish BIMI.
Free verification allowances from 14 vendors, read in October 2026, and a live test of what a free checker misses when it skips the SMTP step.
File caps, speed and the price of verifying 1,000,000 addresses at eight vendors, from their own docs in October 2026, and how big a million-row CSV is.
Nine email verifiers compared on prices read from their own pages on 1 October 2026: cost for 10,000 and 100,000 addresses, credit rules, and who each suits.
Eleven email finders compared on published October 2026 prices, cost per 1,000 credits, and the rule that matters most: what you are actually charged for.
Apollo bundles a contact database, email finder and sequencer. The right alternative depends on which job you are replacing. Prices checked October 2026.
We measured outbound port 25 across the hosts we actually ran our verifier on. Two blocked it silently. Here is how to test your own host in thirty seconds, and why a blocked port makes a verifier unable to tell a real mailbox from a fake one.
The four checks that establish whether an address is real, what each one can and cannot prove, and how to do them by hand before you trust a tool to do them for you.
The six causes of a high bounce rate, in the order they actually matter, and how to check each one for your own domain in a few minutes.
Catch-all domains accept mail for every address, real or not. That is why a good verifier returns risky instead of valid, and what to do with those addresses.
A 60-second test that catches a verifier marking made-up addresses as valid. We ran it on our own tool first, and it failed.