SPF and DMARC records for att.net
Live SPF and DMARC lookup for att.net: the raw TXT records and the policy they enforce.
try:
- mail hosts
- mx-att.mail.am0.yahoodns.net
- provider
- yahoo
- spf record
- v=spf1 include:_ipspf.yahoo.com ~all
- dmarc policy
- quarantine
- dmarc record
- v=DMARC1; p=quarantine; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected]
- disposable domain
- no
- free consumer provider
- yes
SPF for att.net
att.net publishes an SPF record; it authorises 1 included sender list, and the record ends in ~all (soft fail): mail from unlisted servers is marked suspicious but usually still delivered.
DMARC for att.net
att.net publishes DMARC with p=quarantine, which tells receivers to sideline mail that fails alignment instead of blocking it. Many domains stay here while they tidy up legitimate senders.
Why it matters
Receivers use SPF, DKIM, and DMARC together to decide whether a message really came from att.net. A domain with a strict SPF record and an enforcing DMARC policy is hard to spoof and easier to deliver for; one without either is neither. Spaw reports has_spf and dmarc_policy on every lookup and adds a small risk weight when SPF is missing.
More checks for att.net
checked 2026-09-03 · sources: live-dns 2026-09-03 · disposable-domains 2026-09-02 · free-provider-domains 2026-09-02 · mx-provider-patterns 2026-09-03
Need this at scale?
The Spaw API runs the same checks plus mailbox-level SMTP verification, batch and bulk endpoints, and list monitoring — 10 free lookups a month, no card required.