Finding and verifying business emails without burning your domain
A cold email list is only as good as its worst address. One wrong send is noise; a pattern of them is a bounce rate that tells Google and Microsoft your mail is unwanted — and that verdict attaches to your domain, not to the list.
Here is how to find real business addresses and how verification actually works, without the folklore.
Where local business emails actually live
- Contact pages — the obvious place, and still the most common source of a working address (info@, hello@, enquiries@).
- The homepage footer — smaller businesses often skip a contact page and put the address in the footer only.
- About and services pages — “email us to book” lines hide addresses there.
- Obfuscated on purpose — mailto: links, “name [at] company [dot] com”, or addresses rendered as images. A real reader can decode these; naive scrapers miss them entirely.
Reading multiple pages of a small-business site (contact, about, services, reviews) finds dramatically more working addresses than scraping the homepage alone.
Why guessed addresses are a trap
“First name @ domain” guessing works at large companies with predictable directories. At a 6-person plumbing company it happily invents addresses that look plausible and bounce hard. Pattern-guessing is fine as a last resort — but only behind a verifier that can say no.
What “verification” actually means
- Syntax: is it even an address shape? The one check that catches almost nothing.
- MX records: does the domain accept email at all? Catches dead domains cheaply.
- SMTP probe: ask the receiving server whether the mailbox exists. The strongest signal — and the one most tools skip because it is slow and needs reputation.
- Catch-all detection: the server accepts everything, so nobody can confirm the mailbox. Treat catch-alls as “unverified”, never as “verified”.
The bounce math nobody enjoys
Email providers watch your bounce rate closely. Below ~2% you are invisible; above ~5% you start getting filtered; sustained double digits gets your domain throttled or blocked. On a list of 200 that means the difference between 4 bounces and 20 — the second number can end a young mailbox.
A practical pre-send checklist
- Every address was either found on the business’s own site or pattern-guessed and then probed — never guessed and sent blind.
- Catch-alls are separated out and either skipped or sent tiny volumes first.
- The first batch to any new list is 10–20 emails; you watch for bounces before scaling.
- Bounces, unsubscribe requests and “not interested” replies all stop that business from being emailed again — automatically.
Questions we get asked about this
Is it safe to email info@ addresses?
Yes — for local businesses those shared inboxes are the norm and often the owner reads them. The risk is not the address shape; it is sending to addresses that bounce. Verified info@ beats unverified “personal” every time.
What is a catch-all domain?
A mail server configured to accept every address at the domain, real or not. You cannot confirm a mailbox there via SMTP, so the honest status is “unverified” — send small, watch bounces, or skip.
How does ProspectBeam verify addresses?
The same engine as the free checker on this site: syntax, MX, live SMTP probe and catch-all detection, run automatically for every prospect before it can ever be approved for sending.
Keep reading