Add chatgpt.site to AI ruleset

[skyswordw]

Summary

• add chatgpt.site and all of its subdomains to the AI ruleset

Why

chatgpt.site is the domain used by ChatGPT Sites. The root domain redirects to OpenAI's Sites documentation, and the official documentation shows generated sites on subdomains such as goblin-tales.openai.chatgpt.site.

Using DOMAIN-SUFFIX covers both the root domain and generated site subdomains.

Reference: https://learn.chatgpt.com/docs/sites

Validation

• pnpm lint (0 errors; existing repository warnings only)
• pnpm run build
• confirmed the generated Surge, Mihomo, and sing-box AI outputs include chatgpt.site

[SukkaW]

Does chatgpt.site impose any known geolocation restriction? Do we have any proof?

[skyswordw]

I do not have an official document that explicitly states the chatgpt.site country policy, but I can provide reproducible operational evidence that the hostname is geofenced.

I tested the same real ChatGPT Sites deployment on 2026-08-05 between 02:30 and 02:33 UTC:

https://orbital-live.skytutu.chatgpt.site/

Immediately before each request, I checked the egress location with Cloudflare's https://www.cloudflare.com/cdn-cgi/trace endpoint (loc=), then requested the Sites URL with curl -L through the same path:

Path	Cloudflare loc	HTTP result	Response marker
Mainland China direct	CN	403	Attention Required! | Cloudflare / Sorry, you have been blocked
Hong Kong exit 1	HK	403	same Cloudflare block page
Hong Kong exit 2	HK	403	same Cloudflare block page
United States exit 1	US	200	site HTML, title Orbital / Live
United States exit 2	US	200	site HTML, title Orbital / Live
Singapore exit	SG	200	site HTML, title Orbital / Live

The two HK tests and two US tests used different egress IPs. I also cross-checked another real Sites hostname, gargantua-raytracer.skytutu.chatgpt.site: the CN/HK paths received the same Cloudflare 403 block, while US/SG passed that gate and reached the application's expected 401 authentication response.

The direct test bypassed the local proxy/TUN path (curl --noproxy '*' --interface en1). Proxy tests ran through an isolated Mihomo instance bound to the physical interface, with one explicit exit selected at a time. No live routing-group selection was changed.

So while I cannot point to an official policy statement, chatgpt.site does have a reproducible region-dependent reachability difference: CN/HK are blocked at Cloudflare, while US/SG reach the application. This is the actual failure that motivated adding the suffix to the AI ruleset.