SPF and DMARC records for 10m.in
Live SPF and DMARC lookup for 10m.in: the raw TXT records and the policy they enforce.
try:
- mail hosts
- mx1.hostinger.com, mx2.hostinger.com
- provider
- other
- spf record
- v=spf1 include:_spf.mail.hostinger.com ~all
- dmarc policy
- none
- dmarc record
- v=DMARC1; p=none
- disposable domain
- yes
- free consumer provider
- no
SPF for 10m.in
10m.in 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 10m.in
10m.in 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 10m.in. 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 10m.in
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.