[BUG] All naver.com domains blocked by default safety restrictions — false positive on Korea's primary portal (daum.net / tistory.com not blocked)
What's Wrong?
All naver.com domains are refused with is not allowed due to safety restrictions, which
appears to be the default safety-category blocklist (adult content / known pirated content),
not a per-site permission or org policy. Naver is South Korea's dominant web portal,
and Naver Blog / Naver Cafe are where a large share of Korean
user-generated content, product reviews, and community discussion actually lives. Blocking
the whole domain makes Claude unable to read any Korean-language primary source for a very
large share of the Korean web.
This looks like a category false positive on a mainstream portal, not an intentional block:
directly comparable Korean platforms are NOT blocked.
Tested in the Claude Code desktop app's Browser pane, same session, back to back:
| URL | Result |
|---|---|
| https://www.naver.com | BLOCKED — "https://naver.com is not allowed due to safety restrictions" |
| https://blog.naver.com/naver_diary | BLOCKED — "https://blog.naver.com is not allowed due to safety restrictions" |
| https://cafe.naver.com/tk | BLOCKED — "https://cafe.naver.com is not allowed due to safety restrictions" |
| https://www.daum.net (Korean portal, Naver's direct competitor) | OK — loaded, title "Daum" |
| https://www.tistory.com (Korean UGC blog platform, direct analogue to Naver Blog) | OK — loaded, title "티스토리" |
Daum and Tistory are the same kind of service — a major Korean portal and a major Korean
UGC blog host — and both load fine. So the block is specific to naver.com, not to the
portal or UGC-blog category.
WebFetch is also blocked on the same domain: Claude Code is unable to fetch from blog.naver.com.
What Should Happen?
naver.com and its subdomains (blog., cafe., news., search., m.) should be treated
like any other mainstream portal — allowed by default, with the normal per-site permission
prompt — the same way daum.net and tistory.com already are.
If some subset of Naver is genuinely being flagged (e.g. individual Cafe posts that host
infringing files), the block should be scoped to that, not applied to the apex domain and
every subdomain of the country's primary search engine.
If the classification is intentional, it would help to say so publicly and document which
domains are in the default blocklist, since the list is server-side and not visible or
editable from any local settings file or from the extension's own per-site permission UI.
Error Messages/Logs
https://naver.com is not allowed due to safety restrictions and cannot be opened in the Browser pane.
https://blog.naver.com is not allowed due to safety restrictions. Use `navigate` to try a different URL.
https://cafe.naver.com is not allowed due to safety restrictions and cannot be opened in the Browser pane.
Claude Code is unable to fetch from blog.naver.comSteps to Reproduce
- In the Claude Code desktop app, navigate the Browser pane to
https://www.naver.com. - Observe:
https://naver.com is not allowed due to safety restrictions. - Repeat with
https://blog.naver.com/naver_diaryandhttps://cafe.naver.com/tk— same error. - Control: navigate to
https://www.daum.netandhttps://www.tistory.comin the same
session — both load normally.
- Also try
WebFetchonhttps://blog.naver.com/naver_diary— `Claude Code is unable to
fetch from blog.naver.com`.
Additional Information
Workaround for data collection specifically: Naver's official Search Open API (blog, cafe,
news, kin, web, image, local + DataLab trends) is reachable via MCP and returns results
normally, so this is not a network-level or geo restriction — it is the domain blocklist.
But the API only returns titles and short snippets, so article bodies remain unreachable.
Platform: Claude Code desktop app (Code tab), Windows 11.
4 Comments
Reproduced on macOS with the Chrome extension via the CLI (not the desktop Browser pane), so this is neither Windows-specific nor specific to one surface.
Environment
claude --chrome) · Claude in Chrome extension 1.0.94 · personal Max plan, no org policyResults (same session, same tab, back to back)
| URL | Result |
|---|---|
|
https://search.naver.com/search.naver?query=test| BLOCKED — "This site is not allowed due to safety restrictions." ||
https://m.naver.com| BLOCKED — same message ||
https://news.naver.com| BLOCKED — same message ||
https://www.naver.com,https://blog.naver.com/...,https://cafe.naver.com/...| BLOCKED (tested earlier this month) ||
https://www.daum.net| OK — navigated, title "www.daum.net" |Why this looks like a stale or mis-scoped entry rather than intent
The blocklist does get revised:
partners.coupang.comandtoss.imwere blocked for me in July–early September and are open now, so a review of the apexnaver.comentry seems feasible. Naver is Korea's default search engine and the primary host of Korean product reviews and community posts; for Korean users this is closer to blockinggoogle.comthan to blocking a niche site.Ask
naver.comand its subdomains by default with the normal per-site permission prompt, the same asdaum.net/tistory.complatform:windowslabel — this reproduces on macOS via the CLI + extension pathReproduced on macOS via the Claude desktop app (Code tab) → Claude in Chrome, 2026-09-27. Two surfaces not yet in this thread refuse
naver.comas well, so this isn't specific to the extension.Environment
Results (same session, back to back)
| URL | Claude in Chrome | Desktop app Browser pane | Claude Code
WebFetch||---|---|---|---|
|
https://www.naver.com| BLOCKED — "This site is not allowed due to safety restrictions." | — | — ||
https://mail.naver.com| BLOCKED — same | — | — ||
https://blog.naver.com| BLOCKED — same | BLOCKED — "https://blog.naver.com is not allowed due to safety restrictions" | REFUSED — "Claude Code is unable to fetch from blog.naver.com" ||
https://www.daum.net,https://mail.daum.net,https://www.tistory.com,https://mail.google.com| OK | — | — |WebFetch) refuse the domain with the same reasoning, which is consistent with the server-sideurl_hash_checkclassification described in #95326 — nothing in local settings changes the outcome.mail.naver.comandblog.naver.comare daily-use sites for Korean users, while the direct competitors (daum.net,mail.daum.net,tistory.com) are allowed in the same session.+1 to scoping any genuinely flagged subdomain (e.g. a payments host) instead of the
naver.comapex, and to droppingplatform:windows— this reproduces on macOS. Also reported to usersafety@anthropic.com as the help center suggests.Still reproducing as of 2026-10-07, on a browser and an extension version not yet reported in this thread.
Environment
claude-in-chromeMCP tools (navigate), i.e. a fourth surface alongside the CLI--chromeflag, the desktop app Code tab, and the desktop Browser paneResult —
navigatereturnsThis site is not allowed due to safety restrictions.for every one of these:https://www.naver.comhttps://blog.naver.comhttps://search.naver.comControl, same tab, same session, seconds apart:
https://www.daum.netloads normally. Other non-naver.comdomains I use daily also load normally, so the extension connection itself is healthy — it is specifically this apex domain.All three pages open normally when I open them by hand in the same browser profile, so this is not a network, DNS, or sign-in problem on my side.
With
www,blog, andsearchall refused whiledaum.netpasses, the block looks keyed on thenaver.comapex rather than on any individual host. For anyone working with Korean web services,naver.comis the primary portal, so a false positive here removes a large share of the practical value of the extension.Happy to provide extension logs if that would help narrow it down.
Still reproducing on 2026-10-07 on Windows 11, both in the desktop app's built-in browser and via Claude in Chrome. Also blocked:
new.smartplace.naver.com(Naver SmartPlace, where small-business owners see their store statistics and bookings), in addition towww.naver.com. Same session, controls load fine: daum.net, kakaocorp.com, kbstar.com (a bank), gov.kr, coupang.com, toss.im, tistory.com. No local site-block settings exist on this machine (checked app config and registry policies). Please unblocknaver.comor explain the reason.