SPF and DMARC records for naver.com
Live SPF and DMARC lookup for naver.com: the raw TXT records and the policy they enforce.
try:
- mail hosts
- mx1.mail.naver.com, mx5.mail.naver.com, mx4.mail.naver.com, mx6.mail.naver.com
- provider
- other
- spf record
- v=spf1 ip4:111.91.135.0/27 ip4:125.209.208.0/20 ip4:125.209.224.0/19 ip4:210.89.163.112 ip4:210.89.173.104/29 ip4:114.111.35.0/24 ip4:61.247.196.0/24 ip4:61.247.197.0/24 ~all
- dmarc policy
- none
- dmarc record
- v=DMARC1; p=none; rua=mailto:[email protected]
- disposable domain
- no
- free consumer provider
- yes
SPF for naver.com
naver.com publishes an SPF record; it names its senders directly rather than through include mechanisms, and the record ends in ~all (soft fail): mail from unlisted servers is marked suspicious but usually still delivered.
DMARC for naver.com
naver.com 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 naver.com. 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 naver.com
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.