SPF and DMARC records for cox.net
Live SPF and DMARC lookup for cox.net: the raw TXT records and the policy they enforce.
try:
- mail hosts
- mta6.am0.yahoodns.net, mta7.am0.yahoodns.net, mta5.am0.yahoodns.net
- provider
- yahoo
- spf record
- v=spf1 include:_ipspf.yahoo.com include:cxr.spf.a.cloudfilter.net ip4:68.230.240.0/24 ip4:68.230.241.0/24 ?all
- dmarc policy
- none
- dmarc record
- v=DMARC1; p=none; fo=1; ri=3600; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected],mailto:[email protected]
- disposable domain
- no
- free consumer provider
- yes
SPF for cox.net
cox.net publishes an SPF record; it authorises 2 included sender lists, and the record ends in ?all (neutral): unlisted servers are neither authorised nor refused, which gives receivers little to act on.
DMARC for cox.net
cox.net has DMARC in monitoring mode (p=none). Receivers report what they see but deliver failing mail anyway, so the record protects nothing yet.
Why it matters
Receivers use SPF, DKIM, and DMARC together to decide whether a message really came from cox.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 cox.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.