How to Clean and Validate Bulk Domain Lists to Avoid Dead Links and Redirects
Claire combined 480 domains from three sources and ran them through a registration check. Everything came back clean—yet two weeks after launch, bounces spiked and one domain resolved to a $1,499 broker listing. Registration and live use are two different checks.
Claire had built her domain list from three sources: a conference attendee export from eight months earlier, two enrichment runs against company databases, and a partner referral list. She combined them, removed duplicates, and ran all 480 domains through a registration verification tool. Everything came back clean.
Two weeks after launch, Ben’s SDR team started seeing bounce notifications on domains the tool had marked as valid. One of the domains loaded a domain broker listing offering the name for sale at $1,499. The domain was registered and resolving, and it had passed every check Claire had run. The company it had belonged to had stopped using it five months earlier.
The lesson is that registration and live use are different checks. A domain can be registered and still not belong to the company on your list.
Step 1: Run an HTTP status check
Claire wrote a script that requested each domain and recorded the response. The check took under ten minutes.
The results split into three groups:
Claire checked five of the dead domains by hand. Three belonged to companies that had shut down, and their registrations had lapsed. Two were typos from the original attendee export that never resolved to a real domain. Ben’s team had already sent two sequence touches to all 22.
Step 2: Sort the redirects before acting on them
“Redirect” covers situations that need different fixes, so Claire sorted the 41 before changing anything:
Parked pages (18 domains)
Broker listings, hosting placeholders, or empty sites. The company’s registration had lapsed and the domain was resold. These were removed. The companies still existed under other domains.
Rebrand redirects (15 domains)
The company moved to a new primary domain and set a 301 redirect from the old one. These were recoverable. Claire traced each redirect to its destination and checked that domain’s email setup before updating the list.
Redirect chains (8 domains)
Two or more hops, often left over from staged rebrands or acquisitions. Claire checked the email setup at the final destination and flagged any she couldn’t confirm.
Step 3: Check the MX records
An MX record tells mail servers which host accepts email for a domain. The HTTP check doesn’t test this, because a website can be live while email goes somewhere else.
Claire ran an MX check on the 458 domains that had responded. Two results needed care.
No MX record (19 domains)
A missing MX record doesn’t automatically mean a domain can’t receive email. If there is no MX record, mail servers fall back to the domain’s A record, which points to the web server. So Claire didn’t remove these domains on the basis of the MX record alone. She sent a test message to a named contact at each one. All 19 bounced, because the web servers at those addresses don’t accept mail. The companies were real and active. Their email ran through a different domain, so these domains were removed from the outreach list and the correct email domain was looked up separately.
Catch-all configuration (14 domains)
These servers accept mail for any address at the domain, whether or not a real inbox exists. Two of the 14 were small companies that had set up a catch-all so that nothing sent to them was lost. Delivery to a catch-all gives no signal about whether anyone read the message. These domains were flagged for manual review.
Step 4: Decide what enters the sequence
Claire sent Ben the updated list before he relaunched:
For the 15 rebrands, Claire verified the destination for 11, and those were corrected. She held the other four because the destinations couldn’t be clearly linked to the same company. For the 14 catch-all domains, Ben chose to reach the contacts through LinkedIn first, to get a response before sending cold email to an inbox he couldn’t confirm was monitored. Of the eight redirect chains, five cleared once Claire confirmed mail at the final destination. The other three joined the LinkedIn queue.
Ben relaunched with 400 domains: the 384 confirmed clean plus the 16 that were corrected or cleared.
Step 5: Run the check close to launch
Two weeks after the relaunch, Ben asked whether the same process could run on the three lists planned for the next quarter. Claire formalised the two checks, HTTP status and MX, as a mandatory step before any list goes into a sequence, and added a rule: run the audit within two weeks of launch, not when the list is built. Lists change, and a list that passed in January may not pass in September.
The list had been carefully built, and each check had done what it was designed to do. The problem was that the checks were answering a narrower question than the one that mattered. Claire had been asking whether a domain was owned. She needed to ask whether the company still used it for email.
FindCompanyDomain resolves company names to the domain each company currently uses, checked against live registration records and active MX infrastructure, so the domains on your list reflect where teams work today.
Frequently Asked Questions
Why do domains pass registration verification and still bounce during outreach?
Should I delete all redirecting domains from my outbound list?
If a domain has no MX record, can it still receive email?
How close to campaign launch should bulk domain validation run?
Validate Live Company Domains Before You Send
Resolve company names against live registration records and active MX infrastructure so your outreach list reflects where teams actually work today.
Start Free at FindCompanyDomain →