SPF and DMARC records for twitter.com
Live SPF and DMARC lookup for twitter.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, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com
- provider
- spf record
- v=spf1 ip4:199.16.156.0/22 ip4:199.59.148.0/22 ip4:8.25.194.0/23 ip4:8.25.196.0/23 ip4:204.92.114.203 ip4:204.92.114.204/31 include:_spf.google.com include:_thirdparty.twitter.com -all
- dmarc policy
- reject
- dmarc record
- v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1
- disposable domain
- no
- free consumer provider
- no
SPF for twitter.com
twitter.com publishes an SPF record; it authorises 2 included sender lists, and the record ends in -all (hard fail): mail from a server that is not listed should be rejected.
DMARC for twitter.com
The DMARC policy for twitter.com 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 twitter.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 twitter.com is trusted, and whether someone else can pretend to be twitter.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 twitter.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 · rdap-registration 2026-09-03 · Top-domain list: Majestic Million, CC BY 3.0
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.