| Verizon Mail | |
|---|---|
| Domains | verizon.net, aol.com |
| Mail routing | Yahoo's AOL infrastructure. A verizon.net MX lookup resolves into the yahoodns.net family, which is the end of a long outsourcing chain. |
| What we can resolve | We resolve few mailboxes here |
How Verizon Mail answers a probe
What the server does when we open a connection and ask about one address.
- RCPT TO returns positive for every local part, following Yahoo's policy through the AOL migration.
- Some verizon.net customers were moved to AOL addresses during the transition and kept both, so duplicate reach into one person is common.
- Bounces are asynchronous, as they are everywhere on this infrastructure.
- The catch-all probe returns 250, and the domain classifies as accept-all.
The part that catches people out
What we do about it
We report verizon.net as catch_all, which costs a credit like any other result, and the mx_host on the row shows the chain, because the reason matters. A sender looking at a wall of unresolved US consumer addresses should know they are all the same infrastructure decision rather than a dozen separate problems.
Sending to Verizon Mail mailboxes
Verification is one step. These are the things that decide whether the message lands.
- Yahoo's sender requirements apply, since Yahoo receives the mail.
- The audience skews older and complaint-prone, in line with the rest of the AOL user base.
- If a list carries both a verizon.net and an aol.com address for the same person, deduplicate on the human rather than the string.
The 2017 deadline you can't see
In 2017 Verizon told its mail customers to choose: move the verizon.net mailbox to AOL and keep the address, or take their mail elsewhere. People who did nothing by the deadline lost the mailbox. Say your list was built in 2015 and has 800 verizon.net rows. Some of those owners migrated and still read that inbox. Others walked away, and their addresses were deleted eight or nine years ago.
Both groups look identical to a probe today. The MX for verizon.net is mx-aol.mail.gm0.yahoodns.net, the very same host aol.com uses (checked September 19, 2026), and it accepts the recipient in either case. Your only sorting tool is the late bounce after a real send. Mail that segment in small slices so the dead share shows up as a trickle in your bounce log instead of a spike.
A pool that only drains
Verizon stopped handing out verizon.net addresses when it left the email business, so nobody has joined this domain in years. Every row you hold is old, and no new signups will arrive to freshen the segment. That changes the math on keeping it. With a growing provider, a quiet segment gets diluted by new, active addresses. Here it just gets quieter.
Set a rule and stick to it. If a verizon.net row hasn't opened or clicked in twelve months, stop mailing it, whatever the verification column says. And if any of your own staff or clients still send business mail from a verizon.net address through a marketing tool, change that now. The domain publishes DMARC p=reject, which tells receiving servers to refuse mail that claims to be from verizon.net but wasn't sent by the mailbox provider itself.
Questions people ask
Does Verizon still run its own email?
No. Customers were migrated to AOL, which itself runs on Yahoo infrastructure. The verizon.net domain survives as a routing artifact.
Can these addresses be verified?
Not at mailbox level. The answering server accepts every recipient by policy, so no verifier gets a real verdict.
Why do I see the same person twice?
The migration gave many customers an AOL address alongside their existing verizon.net one. Both work, both reach the same inbox, and a string-matching deduplication pass will keep both.