About this bot
naver-blueno is a legacy crawler associated with NAVER and used for legacy identification.
The primary identifying User-Agent token is naver-blueno. Representative HTTP identity or detection model: naver-blueno (historical/observed).
Directory status: Legacy. Identity classification: Unverified with Low confidence. Identity type: legacy-observed.
This is a historical identity retained for log compatibility; no current crawler behavior is implied.
Risk classification: Neutral. Recommended handling is to evaluate the request context before allowing, rate-limiting, or blocking.
How to identify this bot
- User-agent and crawler identifiers
-
naver-blueno
Details
- Kind
- Legacy crawler
- Family
- NAVER
- Purpose
- Legacy identification
- Common Use
- Historical NAVER-related preview/crawler identification.
- Respects robots.txt
- Unknown
Verification
- Identity Type
- legacy-observed
- Evidence Method
- Current NAVER documentation identifies `Blueno` for preview retrieval, not `naver-blueno`; the older token remains historical and unauthenticated.
- Detection Notes
- Treat `naver-blueno` as a legacy observation. Current NAVER preview traffic should be classified under the separate Blueno record.
Website controls
- Robots.txt Snippet
# Legacy identity retained for log compatibility; no current crawler control is implied.- Apache Rule
RewriteCond %{HTTP_USER_AGENT} naver\-blueno [NC] RewriteRule .* - [F,L]- Nginx Rule
if ($http_user_agent ~* "naver\-blueno") { return 403; }