Mailbox provider · EarthLink
How to verify an earthlink.net email address
Can you verify @earthlink.net addresses?
PartlyPartly. @earthlink.net often refuses checking servers before the mailbox question.
Check one address
Five checks a minute, no account needed. Nothing is sent to the address — we ask its mail server whether the mailbox exists, then disconnect.
Checking a whole list? The first 100 addresses are free, with results to download. No card.
By continuing you agree to our Terms and Privacy Policy.
The checker does probe @earthlink.net, but its server screens or defers unfamiliar checking connections. A refusal at that stage is about the connection, not the address, so it comes back risky ("Server refused our check" or "Mailbox check unavailable") and never invalid. It always checks the syntax, the domain's MX records, disposable domains and role addresses such as info@ first.
Server refused our checkMailbox check unavailableEarthLink addresses usually come back inconclusive from a mailbox check. On 13 October 2026 the earthlink.net mail server mx01.earthlink-vadesecure.net refused our checking server at the greeting stage, citing a Validity Sender Score blocklist listing for the connecting server's IP. A refusal like that says nothing about whether the address exists.
Price: this tool is free. Checking a whole email list is from $9/mo, and the first 100 checks are free with Google, no card. See pricing
Live DNS snapshot: earthlink.net
Checked 6 November 2026, 08:17 UTCRead from DNS at the time shown and refreshed at most once a day. MX says where mail for earthlink.net goes; SPF and DMARC describe mail sent from it, not whether any one address exists.
- 5
mx03.earthlink-vadesecure.net - 5
mx01.earthlink-vadesecure.net - 5
mx02.earthlink-vadesecure.net - 5
mx04.earthlink-vadesecure.net
v=spf1 mx a ip4:208.89.14.209/32 ip4:208.89.13.209/32 ip4:208.89.14.202/32 ip4:24.41.67.0/24 ip4:15.204.141.63/32 ip4:15.204.141.62/32 ip4:51.81.221.83/32 ip4:51.81.221.17/32 include:spf.earthlink-vadesecure.net -allp=none: meets the requirement, but blocks nothing. No rua= address, so you get no aggregate reports.
v=DMARC1; p=none; adkim=r; aspf=r; pct=100;Look up any other domain with the MX lookup or the email provider lookup.
EarthLink at a glance
| Operated by | EarthLink LLCSource: EarthLink help: email inactivity policy |
|---|---|
| MX hosts | mx01.earthlink-vadesecure.net, mx02.earthlink-vadesecure.net, mx03.earthlink-vadesecure.netObserved 13 October 2026 (dig MX) |
| Answer to a made-up address | Connection refused at the greeting: 550 5.7.1 Connection refused - blocked by Validity - ELNK001_102Observed 13 October 2026 (SMTP probe of a made-up recipient, no message sent) |
| Inactive accounts | If the owner does not sign in to EarthLink WebMail, MyEarthLink or EarthLink Portal for 90 days, EarthLink stops delivering new mail until the mailbox is accessed againSource: EarthLink help: email inactivity policy |
| Postmaster rules | Mail to a stale mailbox is refused with 550 ... Due to extended inactivity new mail is not currently being accepted for this mailbox, and it cannot be recoveredSource: EarthLink help: email inactivity policy |
| Postmaster rules | Refusal code ELNK_102 (550 5.7.1 Sender blocked error) means the sending IP is listed on a Validity BlocklistSource: EarthLink Postmaster by Vade: inbound SMTP error codes |
| Postmaster rules | EarthLink's postmaster asks senders to remove invalid users by watching RCPT TO responses and bounces, and to drop addresses that return 5xx errorsSource: EarthLink Postmaster by Vade |
What EarthLink's server says about a missing mailbox
EarthLink's server replied 550 5.7.1 Connection refused - blocked by Validity - ELNK001_102. That refusal happened at the greeting stage, before the checking server could name any recipient, so it is a verdict on the connecting server, not on the address. SimpleVerifier returns these as risky with "Mailbox check unavailable" and never as invalid, because treating a refusal as "mailbox not found" would delete real customers from your list.
Servers screen connections this way to keep spam out: missing reverse DNS, a low sending reputation or a blocklist listing are the usual triggers. The same screen applies to every checking service that connects from a shared or new IP, which is why earthlink.net results differ between verifiers. SMTP verification false positives explains how much to trust each answer.
EarthLink's inbound mail is filtered by Vade (the earthlink-vadesecure.net hosts), and the refusal code ELNK001_102 is documented on EarthLink's Vade postmaster page as a blocklist rejection of the connecting IP.
EarthLink stops delivery to mailboxes idle 90 days
EarthLink stops delivering new mail to a mailbox the owner has not opened for 90 days, and answers senders with a 550 saying new mail is not being accepted because of extended inactivity. The mailbox comes back as soon as the owner signs in.
EarthLink's inbound mail is filtered by Vade, and its postmaster pages explain each ELNK_ code; _102 means the sending IP is on a Validity Blocklist. That is a block on the connecting server, not a verdict on the address, so an EarthLink address that could not be checked is unknown. Treat a 550 inactivity reply from a real send as a reason to suppress the address.
Cleaning earthlink.net addresses you can't check
Treat inconclusive earthlink.net results as unknown, not bad. The checks that don't need the mailbox still work: format, typo domains, duplicates and whether the domain can receive mail. The free list health check runs those in the browser.
For the rest, use the address's history. An address that signed up, bought or replied recently is very likely live. For old or bought data at earthlink.net, send a small batch first and suppress anything that hard-bounces. If the earthlink.net share of your list is small, it's often simpler to keep those rows out of a high-risk campaign than to guess.
Common questions
- Can you verify @earthlink.net addresses?
- Partly. @earthlink.net often refuses checking servers before the mailbox question. The checker does probe @earthlink.net, but its server screens or defers unfamiliar checking connections. A refusal at that stage is about the connection, not the address, so it comes back risky ("Server refused our check" or "Mailbox check unavailable") and never invalid. It always checks the syntax, the domain's MX records, disposable domains and role addresses such as info@ first.
- Can I check if an earthlink.net address exists without emailing it?
- Usually not from a checking service. On 13 October 2026 EarthLink's server refused our checking connection at the greeting stage, before any mailbox question, so the result is inconclusive rather than valid or invalid.
- What mail servers does earthlink.net use?
- On 13 October 2026, earthlink.net published these MX hosts: mx01.earthlink-vadesecure.net, mx02.earthlink-vadesecure.net, mx03.earthlink-vadesecure.net. You can look them up yourself with the free MX lookup tool.
- Should I delete earthlink.net addresses that come back risky?
- No. For earthlink.net, risky reflects how the server treats checks, not the address. Remove the ones that fail format, typo-domain and duplicate checks, then send to the rest in a small batch and suppress whatever hard-bounces.
Related tools
Another provider? See every mailbox provider and what our checker does at each.
Got a list with EarthLink addresses?
Sign in with Google and the first 100 addresses are checked free: valid, risky and invalid, with the reason for each row and a file to download. No card. After that, plans start at $9/mo for 2,500 emails a month.
By continuing you agree to our Terms and Privacy Policy.