SPF and DMARC records for 33mail.com
Live SPF and DMARC lookup for 33mail.com: the raw TXT records and the policy they enforce.
try:
- mail hosts
- aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, aspmx5.googlemail.com
- provider
- spf record
- v=spf1 include:email.freshdesk.com include:_spf.google.com ~all
- dmarc policy
- none published
- disposable domain
- yes
- free consumer provider
- yes
SPF for 33mail.com
33mail.com publishes an SPF record; it authorises 2 included sender lists, and the record ends in ~all (soft fail): mail from unlisted servers is marked suspicious but usually still delivered.
DMARC for 33mail.com
33mail.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 33mail.com.
Why it matters
SPF says which servers may send as 33mail.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 33mail.com is trusted, and whether someone else can pretend to be 33mail.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 33mail.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.