How to read an xyz.sh report
Where the report comes from
Running curl -fsSL xyz.sh/all | bash -s -- -y on a VPS runs system info, a light disk / CPU check, overseas speed tests, three-network back-routes and unlock checks, then draws a terminal summary. The masked report is stored for 30 days at a URL like https://xyz.sh/r/<id> only if you add --share (or confirm upload on a terminal). -y never implies sharing.
IP addresses and the hostname are masked before upload. A delete command is printed after a successful upload; only someone with that token can delete it. Sharing is an explicit choice to make the result public, which is what the leaderboard at /en/rank is built from.
How the overall score is calculated
The total is 100 points, weighted route 40, speed 30, unlock 20 and system 10. It is a convenience for comparing similar machines, not an absolute “higher is always better” grade. A full disk drags the system score down; the route score reflects how many premium back-routes were seen; the speed score comes from overseas nodes (nearest, plus Hong Kong, Tokyo, Singapore, US West and similar), not mainland China speed tests; the unlock score reflects common streaming and AI sites.
Older reports that still contain China speed rows are scored and rendered with the historical rule so past totals do not jump. New reports show overseas speed rows only.
What each block is for
Overseas speed: download / upload / latency to the nearest node and a few regional ones. These figures are from this machine to the test nodes, not “how fast a visitor in China loads your site”.
Back-route matrix: read Telecom / Unicom / Mobile tags across the three cities as in “How to read return routes”.
Unlock: for example Netflix, Disney+, YouTube Premium, ChatGPT, Claude, Gemini and TikTok. An unknown or failed cell is not the same as a poor route, and it is not always a hard block — DNS, the egress IP type and the service’s own policy all matter.
System: OS, CPU, memory, disk and a light read / write. If the disk is 100% full, clean it before installing software; xyz.sh/clean can help.
Compare and the leaderboard
On a report page you can enter another share id under “Compare with another report” and open /en/compare?a=<id>&b=<id> to see score, speed, back-route, unlock and system differences side by side. Older reports work too.
The leaderboard at /en/rank only includes voluntarily shared reports, filterable by provider (ASN), region and route type, and never shows IPs or hostnames. It stays noindex for search engines until there are enough entries; an empty state is shown as-is, and we do not insert fake scores.