SPF and DMARC records for 39393.me
Live SPF and DMARC lookup for 39393.me: the raw TXT records and the policy they enforce.
try:
- mail hosts
- email.chatgpt.org.uk
- provider
- other
- spf record
- no
- dmarc policy
- none
- dmarc record
- v=DMARC1; p=none; rua=mailto:[email protected]
- disposable domain
- yes
- free consumer provider
- yes
SPF for 39393.me
There is no SPF record for 39393.me. Without it, any server can claim to send as 39393.me and receivers have nothing to check it against, which both invites spoofing and hurts deliverability. Spaw's risk model treats a missing SPF record as a minor negative signal.
DMARC for 39393.me
39393.me 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 39393.me. 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 39393.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.