Overview
adsnaver is retained as a historical or noncanonical identity pattern associated with Naver traffic.
Naver's current advertising crawler is documented as Ads-Naver, with a hyphen and versioned browser-style user agent.
Do not treat this user-agent string alone as proof of Naver ownership. Current Naver traffic should be verified with forward-confirmed reverse DNS under naver.com or Naver’s current published network list.
Identity
- User-Agent Pattern
-
adsnaver - HTTP Agent Examples
-
adsnaver - Robots Token
- adsnaver
- Identity Type
- Observed
- Evidence Method
- Treat this as a legacy pattern only. For current Naver identities, use operator documentation and verify source addresses with forward-confirmed reverse DNS ending in naver.com.
Classification
- Type
- Search
- Kind
- Crawler
- Family
- Naver
- Operator
- Naver
- Company
- Naver
- Purpose
- Legacy identification
Behavior and handling
- Common Use
- Historical Naver crawler identification.
- Detection Notes
- Match `adsnaver` only as a historical signal. It is not one of Naver's currently documented Yeti, Ads-Naver, or Blueno identities.
- Respects robots.txt
- Unknown
- Spoofing Risk
- High identity ambiguity: the token is not part of Naver's current documented crawler set and can be copied by unrelated clients.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
User-agent: adsnaver Disallow: / - Apache Rule
-
RewriteCond %{HTTP_USER_AGENT} adsnaver [NC] RewriteRule .* - [F,L] - Nginx Rule
-
if ($http_user_agent ~* "adsnaver") { return 403; }