Live checked Trojan servers

Recently verified Trojan endpoints

Only checks newer than 72 hours are eligible. A row requires a real protocol tunnel, successful HTTPS traffic and a public exit IP different from the checker’s direct IP. Reachable ports and source-reported status are excluded.

Search indexing paused: insufficient qualified history. The gate requires at least 10 unique endpoints, 3 independent sources and 7 qualifying days in the last 14. The page remains available with noindex,follow while evidence accumulates.

Trojan JSON API

Use /api/v1/servers?protocol=trojan&status=online to retrieve the same fresh, downloadable and full-tunnel-verified rows without scraping this table. The response includes stable public IDs, transport metadata, the observed exit IP, checker timings and the current config download URL.

Open the Trojan API guide or read the complete API v1 documentation.

About Trojan

A Trojan client opens a TLS connection to the server and authenticates inside that protected session. The protocol is commonly used as a proxy transport; whether all device traffic follows it depends on the client routing mode. A valid certificate and the correct server name are important parts of the connection.

What a working configuration needs

Use a current client that supports Trojan over TLS and verify the SNI before importing any public configuration.

Connection material is quarantined and never printed in tables or logs. A download is returned only for a fresh full-tunnel result whose exact URI is still present in an allowlisted public source permitted by the publication policy.

Unknown public infrastructure may observe or manipulate traffic. Do not use community endpoints for banking, work accounts, private source code or other sensitive activity. Read the public endpoint risk guide.

Read the complete Trojan protocol, configuration and troubleshooting guide.