Naver Yeti — how we verified all 618 crawler IPs via FCrDNS
by shop owners for shop owners.
How the PARC feed for Naver Yeti was built: Naver publishes no official IP list and points to reverse DNS against *.web.naver.com instead — we swept four crawler blocks in full and confirmed every one of the 618 IPs bidirectionally.
Yeti is the web crawler of Naver, South Korea's largest search engine. Naver publishes no official IP list — its own documentation points instead to reverse-DNS verification against *.web.naver.com (the same principle as Google's "verify Googlebot"). We therefore swept the four active crawler blocks in full and confirmed each one of the 618 IPs found, bidirectionally. Part of our PARC Security feed.
naver.json — view feed Naver — Yeti robot docs →
The feed
38 CIDR prefixes = 618 verified IPs, spread across four KR blocks:
110.93.150.0/24
114.111.32.0/24
125.209.235.0/24
211.249.46.0/24
Only the FCrDNS-confirmed portions of each — not the full /24 (see below). Aggregated losslessly, the 618 addresses collapse into 38 prefixes from /26 to /32.
No official list — Naver’s reverse-DNS policy
Naver publishes no CIDR list. Its official documentation (naver.me/spd → Naver search help) describes bot identification via user-agent and a reverse-DNS check against *.web.naver.com. Naver does run an autonomous system of its own (AS23576), but that covers the entire Naver network (search, cloud, blog, mail …) — the crawler must not be drawn from the whole ASN, only from the blocks actually used for crawling. Those are isolated via DNS.
Full FCrDNS sweep
Step 1 — reverse across all four /24 (1,024 addresses):
IPs with a PTR total : 618 / 1,024
of which crawl.*.web.naver.com : 618 (= 100%)
foreign PTRs in the blocks : 0
no PTR : 406 (not verifiable → not in the feed)
Not a single foreign PTR in the four blocks — every IP with a reverse record is Yeti (crawl.{ip}.web.naver.com). The 406 IPs without a PTR stay deliberately out: not verifiable.
Step 2 — forward-confirm for all 618 (not a sample):
OK : 618
FAIL : 0
For each of the 618 IPs the PTR hostname was resolved forward and compared against the original IP. Result: 100% bidirectionally confirmed, not a single mismatch.
Current vs. historical
Today’s active Yeti (Yeti/1.1) crawls from the four blocks above. Older Naver crawler addresses — Korean legacy space (61.247.x) plus Japanese blocks (119.235.237.x via naver.jp, 182.22.30.x via yahoo-net.jp, 147.92.153.x via line-apps.jp) — have been inactive since around 2020 and are not in the feed.
User-agent
Mozilla/5.0 (compatible; Yeti/1.1; +https://naver.me/spd)
Robots token: Yeti.