[ AI answer fetcher · OpenAI ]
ChatGPT-User: OpenAI's AI answer fetcher.
The fetcher ChatGPT uses when a person's question needs a live page. It reads your page while the answer is being written. Its intent is answer fetch: fetches your page live to answer a user's question.
IP ranges last updated Oct 25, 2026
[ technical facts ]
- operator
- OpenAI
- intent
- answer fetch
- user agent contains
chatgpt-user- robots.txt token
ChatGPT-User- verification
- published IP rangesverified
- official IP list
- openai.com/chatgpt-user.json
- ranges in registry
- none loaded (source unreachable at last refresh)
- last updated
- Oct 25, 2026
- operator docs
- platform.openai.com/docs/bots
[ verify ]
How to verify a real ChatGPT-User request.
OpenAI publishes the IP ranges ChatGPT-User uses. A request is real when its IP is inside that list.
- 01Check the User-Agent header contains "chatgpt-user" (case-insensitive). That is only a claim: anyone can send it.
- 02Download OpenAI's published list (https://openai.com/chatgpt-user.json) and check the request IP falls inside one of its ranges.
- 03Inside the list: the real ChatGPT-User. Outside it: a request using ChatGPT-User's name from someone else's server.
Skip the lookups: the free bot verifier checks one IP against the same registry, and the log file analyzer checks every ChatGPT-User request in a week of access logs. Requests that fail are flagged as spoofed, not hidden.
[ robots.txt ]
Block or allow ChatGPT-User in robots.txt.
Add one of these groups to the robots.txt at your domain root. The token matches case-insensitively. OpenAI runs other crawlers with their own tokens, so a rule for ChatGPT-User leaves GPTBot (training) and OAI-SearchBot (search index) untouched.
User-agent: ChatGPT-User
Disallow: /
User-agent: ChatGPT-User
Allow: /
robots.txt only binds crawlers that choose to follow it. A scraper sending ChatGPT-User's user agent from its own servers won't, which is why HadoSEO checks the IP behind every request.
[ questions ]
ChatGPT-User, answered.
[ free scan ]
