Back to home
Verification
Verification and compatibility notes for public links
This page explains what is verified from the control VM, which links are designed for auto-refresh, which links are snapshot downloads, and what still requires client-side import testing on real devices.
What is currently machine-validated
- Homepage, updates page, and status page return HTTP 200.
- Raw Clash, sing-box, V2Ray, and status endpoints return HTTP 200.
- Latest release download endpoints return HTTP 200.
- Clash YAML parses as a valid document with proxy entries.
- sing-box JSON parses as a valid document with outbound entries.
- V2Ray Base64 decodes into subscription lines.
- Status JSON parses into node records with protocol, region, port, and last-check metadata.
A GitHub Actions validation workflow now re-runs these checks on repository changes and on a scheduled cadence, so this page is no longer only backed by one-off manual checks.
What this page does not claim
- It does not claim every GUI client on every operating system has been manually imported and clicked through from this VM.
- It does not claim every public node is always reachable. Use the live status page for the current signal.
- It does not treat release snapshot assets as the same thing as real-time status. Snapshot files are historical checkpoints.
Share the right path
- Share the homepage, updates page, or this verification page first when the user still needs context.
- Share raw `output/*` links only when the client clearly supports long-lived remote subscriptions and auto-refresh.
- Share the current Release page when the user wants a downloadable snapshot file or a historical checkpoint.
- Share the live status page when the question is “is it fresh right now?”, and share client guides when the problem is import format.
Compatibility guidance
- Use Clash YAML for Clash Verge Rev, FlClash, and Mihomo-style clients.
- Use sing-box JSON for clients that support remote JSON profile flows.
- Use V2Ray Base64 for mobile-first import paths such as v2rayNG, NekoBox, Hiddify Next, and many Shadowrocket-style subscription flows.
- If you are unsure, start with the V2Ray path for broad mobile compatibility or open the format decision page.
Recommended validation flow before sharing
- Open the status page and confirm there is a recent check timestamp.
- Open the raw subscription link that matches the client format.
- If the user wants a file download instead of a refreshable URL, switch to the latest release asset.
- If the user still cannot import, send the client-specific guide instead of only repeating the same link.