ipapi.gr

Bot signals — Search & SEO crawler

Yahoo Slurp IP addresses

Yahoo Slurp crawler infrastructure

risk.is_crawler RangesrDNS Reviewed
Official documentation (opens in a new tab) All search & SEO crawlers

Check an IP

Is this IP really Yahoo Slurp?

Checks the address against what Yahoo Slurp publishes, the same evidence behind risk.is_crawler.

01 — Verification

How IPAPI.GR verifies Yahoo Slurp.

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

Yahoo Slurp (DNS)

risk.is_crawler

Yahoo documents hostnames ending in .crawl.yahoo.net that resolve back to the same IP. Complements the published Yahoo range list.

Method
rDNS Forward-confirmed reverse DNS
Reverse DNS
PTR hostname must end in .crawl.yahoo.net. The hostname must then resolve forward to the same address.
Refresh
Checked when the address is looked up; a confirmed result is reused for up to an hour.
Documentation
help.yahoo.com/kb/SLN22600.html (opens in a new tab)
Reviewed
2026-11-12

02 — In the response

What a match looks like.

A lookup of a Yahoo Slurp 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 Yahoo Slurp 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://s.yimg.com/bo/crawling/ipranges/common-crawlers.json \
  | jq -r '.prefixes[] | (.ipv4Prefix // .ipv6Prefix // empty) | "\(.) 1;"' \
  > /etc/nginx/yahoo-slurp-ranges.conf.new && [ -s /etc/nginx/yahoo-slurp-ranges.conf.new ] && mv /etc/nginx/yahoo-slurp-ranges.conf.new /etc/nginx/yahoo-slurp-ranges.conf \
  && nginx -t -q && nginx -s reload

# 2. In the http block: 1 when the client IP is in the published ranges.
geo $yahoo_slurp_ip {
    default 0;
    include /etc/nginx/yahoo-slurp-ranges.conf;
}
Built from s.yimg.com/bo/crawling/ipranges/common-crawlers.json, a JSON file with a prefixes array. It covers that file only.

04 — Questions

About Yahoo Slurp.

Where does Yahoo Slurp publish its IP addresses?

Yahoo Slurp publishes its addresses at https://s.yimg.com/bo/crawling/ipranges/common-crawlers.json. IPAPI.GR reads that publication directly, not a third-party copy.

How do I verify Yahoo Slurp with reverse DNS?

Look up the PTR record for the IP address. The hostname must end in .crawl.yahoo.net, and a forward lookup of that hostname must return the same IP address. A PTR record alone can be set by anyone who controls the address, so the forward confirmation is the part that matters.

How often is the Yahoo Slurp 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 Yahoo Slurp set?

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

From the blog

Go deeper.

Related operators

Every operator on the coverage page →

Verify Yahoo Slurp on every request.

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

See Pro Start free