ipapi.gr

Bot signals — AI crawler & agent

ChatGPT-User IP addresses

OpenAI ChatGPT-User

ChatGPT user-triggered retrieval egress.

risk.is_airisk.is_crawler Ranges Reviewed
Official documentation (opens in a new tab) All AI crawlers & agents

Check an IP

Is this IP really ChatGPT-User?

Checks the address against what OpenAI ChatGPT-User publishes, the same evidence behind risk.is_ai.

01 — Verification

How IPAPI.GR verifies ChatGPT-User.

Only from what OpenAI ChatGPT-User 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.

OpenAI ChatGPT-User

risk.is_airisk.is_crawler
Method
Ranges Published IP ranges
Official file
Format
JSON range file
Refresh
Every hour. If a refresh fails, entries expire after 24 hours instead of being trusted forever.

02 — In the response

What a match looks like.

A lookup of a ChatGPT-User address sets risk.is_ai and risk.is_crawler. The flags come with geolocation and network data in the same response, for Pro API keys.

This publication is AI crawling or retrieval traffic, so it counts as both an AI source and a crawler.

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 ChatGPT-User but doesn't match is unverified.

GET /api/lookup/{ip}?key=PRO_KEY
{
  // … location and network fields …
  "risk": {
    "is_ai": true,
    "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://openai.com/chatgpt-user.json \
  | jq -r '.prefixes[] | (.ipv4Prefix // .ipv6Prefix // empty) | "\(.) 1;"' \
  > /etc/nginx/chatgpt-user-ranges.conf.new && [ -s /etc/nginx/chatgpt-user-ranges.conf.new ] && mv /etc/nginx/chatgpt-user-ranges.conf.new /etc/nginx/chatgpt-user-ranges.conf \
  && nginx -t -q && nginx -s reload

# 2. In the http block: 1 when the client IP is in the published ranges.
geo $chatgpt_user_ip {
    default 0;
    include /etc/nginx/chatgpt-user-ranges.conf;
}

# 3. A request that claims to be ChatGPT-User from any other address is an impostor.
map "$http_user_agent:$chatgpt_user_ip" $fake_chatgpt_user {
    default 0;
    "~*(ChatGPT-User).*:0$" 1;
}

# In the server block:
if ($fake_chatgpt_user) { return 403; }
Built from openai.com/chatgpt-user.json, a JSON file with a prefixes array.

04 — Questions

About ChatGPT-User.

Where does ChatGPT-User publish its IP addresses?

OpenAI ChatGPT-User publishes its addresses at https://openai.com/chatgpt-user.json. IPAPI.GR reads that publication directly, not a third-party copy.

How often is the ChatGPT-User 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 ChatGPT-User set?

A matching address sets risk.is_ai and 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 ChatGPT-User 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