Overview
Yeti is operated by NAVER and is used for Crawling and indexing web pages for NAVER Search.
Its documented identity is Mozilla/5.0 (compatible; Yeti/1.1; +https://naver.me/spd). The robots.txt token is Yeti.
It follows robots.txt rules addressed to Yeti.
Verify Yeti with forward-confirmed reverse DNS: the reverse hostname must end in naver.com and resolving that hostname must return the original request IP. Naver also publishes a current CIDR list.
Identity
- User-Agent Pattern
-
Yeti - Aliases
- Yeti/; Mozilla/5.0 (compatible; Yeti/1.1; +https://naver.me/spd)
- HTTP Agent Examples
-
Mozilla/5.0 (compatible; Yeti/1.1; +https://naver.me/spd) - Robots Token
- Yeti
- Identity Type
- Officially documented
- Evidence Method
- Verify Yeti with forward-confirmed reverse DNS: the reverse hostname must end in naver.com and resolving that hostname must return the original request IP. Naver also publishes a current CIDR list.
Classification
- Type
- Search
- Kind
- Crawler
- Family
- Naver
- Purpose
- Search indexing
Behavior and handling
- Common Use
- Crawling and indexing web pages for NAVER Search.
- Detection Notes
- Match the case-sensitive Yeti token or the current documented Yeti/1.1 user agent, then require forward-confirmed reverse DNS under naver.com or a match to Naver's current network list.
- Respects robots.txt
- Yes
- Spoofing Risk
- The user-agent is easily copied; use Naver's DNS or current network evidence before trusting it.
- Risk
- Safe
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
User-agent: Yeti Disallow: / - Apache Rule
-
RewriteCond %{HTTP_USER_AGENT} Yeti [NC] RewriteRule .* - [F,L] - Nginx Rule
-
if ($http_user_agent ~* "Yeti") { return 403; }
Relationships
- Operator
- NAVER Checked 2026-08-06
- Owner / parent organization
- NAVER Corporation Checked 2026-08-06
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.