SPF and DMARC records for about.com
Live SPF and DMARC lookup for about.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
- provider
- spf record
- v=spf1 ip4 64.125.213.247 ip4 216.223.13.247 ip4 34.194.76.185 ip4 35.164.185.216 ip4 34.194.69.219 include _spf.salesforce.com include _spf.google.com include spf.protection.outlook.com include amazonses.com ~all
- dmarc policy
- none
- dmarc record
- v=dmarc1; p=none; fo=1; rua=mailto [email protected]; ruf=mailto [email protected]
- disposable domain
- no
- free consumer provider
- yes
SPF for about.com
about.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 about.com
about.com has DMARC in monitoring mode (p=none). Receivers report what they see but deliver failing mail anyway, so the record protects nothing yet.
Why it matters
Receivers use SPF, DKIM, and DMARC together to decide whether a message really came from about.com. 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 about.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.