SPF and DMARC records for spam4.me
Live SPF and DMARC lookup for spam4.me: the raw TXT records and the policy they enforce.
try:
- mail hosts
- smtp.spam4.me
- provider
- other
- spf record
- no
- dmarc policy
- reject
- dmarc record
- v=DMARC1; p=reject; sp=reject; rf=afrf; pct=100; ri=86400
- disposable domain
- yes
- free consumer provider
- yes
SPF for spam4.me
spam4.me publishes no SPF record. Receiving servers cannot tell which servers are allowed to send as spam4.me, so mail from the domain is easier to spoof and more likely to land in spam. A basic record (v=spf1 include:… -all) fixes that, and Spaw's risk score adds a small weight to addresses at domains without one.
DMARC for spam4.me
The DMARC policy for spam4.me 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 spam4.me; 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 spam4.me is trusted, and whether someone else can pretend to be spam4.me. 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 spam4.me
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.