SPF and DMARC records for 0hio.net
Live SPF and DMARC lookup for 0hio.net: the raw TXT records and the policy they enforce.
try:
- mail hosts
- aspmx1.migadu.com, aspmx2.migadu.com
- provider
- other
- spf record
- v=spf1 include:spf.migadu.com -all
- dmarc policy
- quarantine
- dmarc record
- v=DMARC1; p=quarantine;
- disposable domain
- yes
- free consumer provider
- no
SPF for 0hio.net
0hio.net publishes an SPF record; it authorises 1 included sender list, and the record ends in -all (hard fail): mail from a server that is not listed should be rejected.
DMARC for 0hio.net
0hio.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 0hio.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 0hio.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.