[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:

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.com

Steps to Reproduce

1. In the Claude Code desktop app, navigate the Browser pane to https://www.naver.com.
2. Observe: https://naver.com is not allowed due to safety restrictions.
3. Repeat with https://blog.naver.com/naver_diary and https://cafe.naver.com/tk — same error.
4. Control: navigate to https://www.daum.net and https://www.tistory.com in the same
   session — both load normally.
5. Also try WebFetch on https://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.

Start by reproducing the restriction in the Claude Code desktop Browser pane and with WebFetch for the listed naver.com URLs, then determine whether the server-side blocklist is represented in this repository. Done means confirming an actionable implementation path that permits the apex domain and appropriate subdomains without removing narrower safety protections.