Bot signals — Search & SEO crawler

Naver search crawlers IP addresses

Published Naver search crawler ranges / Yeti

risk.is_crawler Ranges Reviewed

Check an IP

Is this IP really Naver search crawlers?

Checks the address against what Naver search crawlers publishes, the same evidence behind risk.is_crawler.

01 — Verification

How IPAPI.GR verifies Naver search crawlers.

Only from what Naver search crawlers publishes about itself. No third-party blocklists, no behavioural guesses. Live address counts change with every publication, so check the official file for the current list.

02 — In the response

What a match looks like.

A lookup of a Naver search crawlers address sets risk.is_crawler. The flags come with geolocation and network data in the same response, for Pro API keys.

The response says which kind of bot an address belongs to, not which operator. Pair it with the user agent: a request that claims to be Naver search crawlers but doesn't match is unverified.

GET /api/lookup/{ip}?key=PRO_KEY
{
  // … location and network fields …
  "risk": {
    "is_ai": false,
    "is_crawler": true,
    "is_scanner": false
  }
}

03 — Configuration

Allow, block or verify it yourself.

nginx + jq
# 1. Build a geo include from the official file (cron, e.g. hourly).
#    Keep the old file if the download fails or comes back empty.
curl -fsS https://searchadvisor.naver.com/doc/naverbot.json \
  | jq -r '.prefixes[] | (.ipv4Prefix // .ipv6Prefix // empty) | "\(.) 1;"' \
  > /etc/nginx/naver-ranges.conf.new && [ -s /etc/nginx/naver-ranges.conf.new ] && mv /etc/nginx/naver-ranges.conf.new /etc/nginx/naver-ranges.conf \
  && nginx -t -q && nginx -s reload

# 2. In the http block: 1 when the client IP is in the published ranges.
geo $naver_ip {
    default 0;
    include /etc/nginx/naver-ranges.conf;
}
Built from searchadvisor.naver.com/doc/naverbot.json, a JSON file with a prefixes array.

04 — Questions

About Naver search crawlers.

Where does Naver search crawlers publish its IP addresses?

Naver search crawlers publishes its addresses at https://searchadvisor.naver.com/doc/naverbot.json. IPAPI.GR reads that publication directly, not a third-party copy.

How often is the Naver search crawlers list refreshed?

IPAPI.GR re-fetches it every hour. If a refresh fails, the previous entries expire after at most 24 hours instead of being trusted forever.

Which risk flag does Naver search crawlers set?

A matching address sets risk.is_crawler in the lookup response. The risk flags are returned for Pro API keys.

Verify Naver search crawlers on every request.

Pro: 40,000,000 requests a day with is_ai, is_crawler and is_scanner in every lookup.