Mailbox provider · AT&T Mail
How to check if an att.net email address exists
AT&T Mail addresses can't be confirmed with a mailbox check. On 12 October 2026 the att.net mail server mx-att.mail.am0.yahoodns.net accepted a made-up recipient at RCPT TO with 250 recipient <…@att.net> ok, so real and fake addresses get the same answer. Expect att.net results to come back risky (accept-all), not valid or invalid.
Mailbox checks: Not verifiable. The server accepts any recipient, real or not.
AT&T Mail at a glance
| Same mailbox system | sbcglobal.net uses the same MX host, mx-att.mail.am0.yahoodns.netObserved 12 October 2026 (dig MX) |
|---|---|
| MX hosts | mx-att.mail.am0.yahoodns.netObserved 12 October 2026 (dig MX) |
| Answer to a made-up address | 250 recipient <…@att.net> ok, returned at RCPT TOObserved 12 October 2026 (SMTP probe of a made-up recipient, no message sent) |
What AT&T Mail's server says about a missing mailbox
AT&T Mail answered our made-up att.net address with 250 recipient <…@att.net> ok at RCPT TO, the step where a verifier names the recipient. When a server says yes to an address that cannot exist, its yes for your real address carries no information. SimpleVerifier tests a random address first for exactly this reason and returns att.net results as risky with the reason "Accepts all addresses".
Accepting at RCPT TO doesn't mean every message is delivered. Providers that do this usually decide later, after the message is sent, and a missing mailbox then produces a bounce rather than an up-front rejection. That is why accept-all results belong in their own segment: accept-all vs unknown results covers how to treat them.
Mail for this domain is received by Yahoo's yahoodns.net servers, the same network that receives yahoo.com and aol.com mail, so it behaves the same way when checked.
Cleaning att.net addresses when the server says yes to everything
Don't delete att.net addresses just because they came back risky; most will be real. Remove what can be proven bad without the mailbox check: syntax errors, typo domains, duplicates and disposable addresses, which the free list health check finds in the browser.
Then send to the att.net segment in a small first batch and watch the bounces. Addresses that bounce as unknown users are gone and should be suppressed; the rest have proved themselves. Engagement history is the other strong signal: an address that opened or replied recently is live whatever the check says. Should you send to catch-all emails? walks through the same approach.
Live DNS check for att.net
These are att.net's own sending records, refreshed daily. They describe mail sent from the domain, not whether a given address at it exists.
4 of 5 checks passed
80%Blocklist status
Not listed on SURBL, SpamCop
DKIM — message signing
No DKIM found on common selectors — it may use a custom one
DMARC — spoofing policy
DMARC set to quarantine — reasonable protection
Mail servers (MX)
1 mail server(s), primary mx-att.mail.am0.yahoodns.net
SPF — authorised senders
SPF present, soft fail (~all)
Common questions
- Can I check if an att.net address exists without emailing it?
- Not reliably. On 12 October 2026 AT&T Mail's server accepted a made-up att.net address at the RCPT TO step, so a mailbox check gets the same yes for real and fake addresses. Verifiers return att.net addresses as risky (accept-all).
- What mail servers does att.net use?
- On 12 October 2026, att.net published these MX hosts: mx-att.mail.am0.yahoodns.net. You can look them up yourself with the free MX lookup tool.
- Should I delete att.net addresses that come back risky?
- No. For att.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.
Check a AT&T Mail address
The free checker runs the mailbox check on one address and shows the server's reason, so you can see which of the cases above applies.