SPF and DMARC records for telus.net
Live SPF and DMARC lookup for telus.net: the raw TXT records and the policy they enforce.
try:
- mail hosts
- aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.com
- provider
- spf record
- v=spf1 ip4:199.185.220.0/24 ip4:198.161.157.0/24 ip4:198.161.156.0/24 ip4:204.209.205.0/26 ip4:209.171.16.0/24 ip4:100.64.0.0/24 ip4:34.95.53.42/32 ip4:34.118.147.0/32 mx include:_spf.google.com ~all
- dmarc policy
- none
- dmarc record
- v=DMARC1; p=none; rua=mailto:[email protected]
- disposable domain
- no
- free consumer provider
- yes
SPF for telus.net
telus.net 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 telus.net
telus.net 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 telus.net. 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 telus.net
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.