SPF and DMARC records for 1337.care
Live SPF and DMARC lookup for 1337.care: the raw TXT records and the policy they enforce.
try:
- mail hosts
- mail.1337.care
- provider
- other
- spf record
- v=spf1 ip4:212.87.214.42 -all
- dmarc policy
- reject
- dmarc record
- v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected];; fo=0:1:d:s;
- disposable domain
- yes
- free consumer provider
- yes
SPF for 1337.care
1337.care publishes an SPF record; it names its senders directly rather than through include mechanisms, and the record ends in -all (hard fail): mail from a server that is not listed should be rejected.
DMARC for 1337.care
The DMARC policy for 1337.care 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 1337.care; 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 1337.care is trusted, and whether someone else can pretend to be 1337.care. 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 1337.care
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.