Audit date: 2026-07-26
The goal is to send verified mainland China game websites, authentication, launchers, updates, and identifiable CDN traffic through DIRECT, while keeping international game services on the final US/proxy route.
The resulting model has three layers:
InternationalGaming → final proxy: protect known international services first.ChinaGaming → DIRECT: match mainland game services.GEOIP,CN → DIRECT: cover raw-IP and UDP endpoints located in mainland China.
One exact-host exception precedes these providers: fastcdn.hoyoverse.com is used by a mainland miHoYo page, so it is routed directly before the broader international hoyoverse.com suffix.
The upstream SteamCN provider mixes verified mainland download nodes with global suffixes such as steamcontent.com, steamserver.net, and steamusercontent.com. Routing the entire provider directly would also capture global Steam content. This repository extracts verified mainland nodes into ChinaGaming and leaves the broad upstream provider on the configured Steam policy.
ChinaMax currently includes:
- DOMAIN-SUFFIX,cnAny .cn candidate already reaches ChinaMax unless an earlier rule captures it. Listing those domains explicitly in ChinaGaming still matters because it:
- places them before GlobalMedia, Bilibili, Steam, and ChinaMax;
- documents the intent that mainland game traffic should be direct;
- preserves them if a future upstream update removes the broad
.cnsuffix.
These .cn entries are priority hardening, not previously unmatched ChinaMax coverage. The clearest non-.cn gap found during the audit was lilithcdn.com. fastcdn.hoyoverse.com is a separate exact-host mainland override inside an otherwise international root domain.
- Tencent, WeGame, and Delta Force
- NetEase Games
- Mainland miHoYo versus international HoYoverse
- Perfect World, Valve China, and Kingsoft/Seasun
- Nuverse and Lilith Games
- Kuro Games, Hypergryph, and PaperGames
- Bilibili Games, Yoozoo, 37 Interactive, and 4399
- Mainland game platforms, distribution, and CDN infrastructure
- Authentication, real-name verification, anti-addiction, anti-cheat, voice, and update SDKs
- Effective first-match review across ChinaMax, SteamCN, Bilibili, and GlobalMedia
- The Delta Force mainland website uses
df.qq.com,repo.df.qq.com, andgame.gtimg.cn. - The WeGame mainland client page and official agreement establish
wegame.com.cnas a platform for game downloads, login, and updates. - Tencent ACE for PC is a global service, so no new broad ACE root was added to the mainland-only layer.
- The NetEase corporate website identifies
game.163.comas the NetEase Games website. - The NARAKA mainland FAQ separates the mainland NetEase-account client from Steam/global accounts. Its download page uses NetEase
gdldistribution hosts. - NetEase Games AI Lab documents anti-cheat technology used across NetEase games.
easebar.comandnarakathegame.comare associated with international services and were not added to the mainland layer.
- The mainland sites for Genshin Impact, Honkai Impact 3, Honkai: Star Rail, and Zenless Zone Zero establish the mainland
mihoyo.comand game-specific roots. - An official Star Rail installation guide identifies
autopatchcn.bhsr.com. - An official Zenless Zone Zero notice uses
mhyurl.cn. hoyoverse.com,hoyolab.com,genshinimpact.com, and other international roots remain on the proxy route; only the exact mainland-referencedfastcdn.hoyoverse.comis direct.
- The Dota 2 mainland download page and CS mainland download page establish
dota2.com.cn,csgo.com.cn,pwesports.cn, and Steam China flows. - A Perfect World game download page uses
wanmei.comandarc.arcgames.cn. - The JX3 patch page and official editor documentation establish
xoyo.comandxoyocdn.com. - The Mecha BREAK mainland site uses
seasungames.cn;seasungames.comis treated as international.
- The Nuverse mainland site and its product API use
nvsgames.cn; the.comsite is global. - The Lilith website exposes mainland products, accounts, and PC downloads under
lilith.comandlilithgame.com, with official assets onlilithcdn.com. The international publishing rootfarlightgames.comis excluded. - The Wuthering Waves mainland entry and its resources use
kurogame.com,kurogames.com, andaki-game*;kurogames-global.comis international. - Hypergryph customer support directly publishes a
launcher.hycdn.cnupdater component. An Arknights PC notice confirms launcher-based downloads and updates. - The Infinity Nikki mainland privacy page and mainland pages use
nuanpaper.comandpapegames.com;infoldgames.comis treated as an international publishing root.
- TapTap China and its login documentation explicitly distinguish mainland
open.tapapis.cnfrom the overseas.comendpoint. - TapTap gift documentation uses mainland
poster-api.xd.cnand overseas.com. - The 9Game download page uses
9game.cn. - vivo App Store/Game Center documentation establishes the
vivo.com.cndownload and game-center flow. - 4399 Game Box documentation and its download page establish
4399.cn. - The NPPA anti-addiction API specification lists
api.wlc.nppa.gov.cnandapi2.wlc.nppa.gov.cn.
A root domain should not be forced direct merely because the operator is a Chinese company. The mainland layer deliberately avoids:
- international publishing roots used by HoYoverse, NetEase, Lilith, Kuro, Hypergryph, and PaperGames;
- shared Akamai, AWS, Cloudflare, Alibaba OSS, and Tencent COS roots;
- mixed-use services such as
steamstatic.com,qcloud.com,myqcloud.com, andgmertc.com; - third-party analytics and attribution services such as AppsFlyer, Adjust, Google, and Facebook.
InternationalGaming.yaml also corrects international domains that broad China lists may otherwise route directly, including international miHoYo domains, bilibili.tv, 37games.com, the overseas TapTap API, and explicit international GME hosts.
Live game sessions may use:
- raw IP addresses;
- dynamically assigned UDP endpoints;
- shared cloud-provider infrastructure;
- hostnames delivered only after the client starts.
The current rules cover verified websites, authentication, launchers, patching, and public CDN endpoints. GEOIP,CN,DIRECT,no-resolve catches targets recognized as mainland IPs, but runtime capture is still required for endpoints outside current GeoIP data, shared or overseas cloud regions, or hosts that must be separated by game region.
A second-stage audit should capture DNS, SNI, target IPs, and ASNs during a mainland client flow: cold start, login, update, and one live match.