SPF and DMARC records for temp-mail.org
Live SPF and DMARC lookup for temp-mail.org: the raw TXT records and the policy they enforce.
try:
- mail hosts
- amir.mx.cloudflare.net, linda.mx.cloudflare.net, isaac.mx.cloudflare.net
- provider
- other
- spf record
- v=spf1 include:_spf.mx.cloudflare.net ~all
- dmarc policy
- reject
- dmarc record
- v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; pct=100; ri=604800; adkim=r; aspf=r; fo=1;
- disposable domain
- yes
- free consumer provider
- yes
SPF for temp-mail.org
temp-mail.org 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 temp-mail.org
The DMARC policy for temp-mail.org is p=reject: mail that fails SPF and DKIM alignment is refused outright. It is the strictest setting and the one Gmail and Yahoo now expect from bulk senders.
Why it matters
SPF says which servers may send as temp-mail.org; 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 temp-mail.org is trusted, and whether someone else can pretend to be temp-mail.org. 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 temp-mail.org
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.