SPF and DMARC records for 167mail.com
Live SPF and DMARC lookup for 167mail.com: the raw TXT records and the policy they enforce.
try:
- mail hosts
- 167mail.com
- provider
- other
- spf record
- v=spf1 ip4:212.18.237.194 ip4:212.18.237.199 ip4:109.73.168.194 +a +mx +ip4:109.73.172.66 ~all
- dmarc policy
- none published
- disposable domain
- yes
- free consumer provider
- no
SPF for 167mail.com
167mail.com publishes an SPF record; it names its senders directly rather than through include mechanisms, and the record ends in ~all (soft fail): mail from unlisted servers is marked suspicious but usually still delivered.
DMARC for 167mail.com
167mail.com publishes no DMARC record. Receivers have no policy to apply when SPF or DKIM fails, and the domain owner receives no aggregate reports about who is sending as 167mail.com.
Why it matters
SPF says which servers may send as 167mail.com; DKIM signs the messages; DMARC tells receivers what to do when neither checks out and reports back to the owner. Together they decide whether mail from 167mail.com is trusted, and whether someone else can pretend to be 167mail.com. For verification they are a domain-quality signal: Spaw folds a missing SPF record into the risk score and reports has_spf and dmarc_policy on every email and domain lookup.
More checks for 167mail.com
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.