Fresh Trojan proxy endpoints verified through a complete TLS tunnel, HTTPS request and changed public exit IP.
Each source catalog applies its freshness and publication checks. 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.
| Endpoint | Connection | Exit IP / country | Performance | Checked / stability | Source | Config |
|---|---|---|---|---|---|---|
WEBSOCKETTLS |
51.158.170.123Netherlands |
Speed6 MbpsHandshake7639 msHTTPS7819 ms |
75% successful 6/8 checks · last 7d | Barry Trojan | Download | |
WEBSOCKETTLS |
51.158.169.153Netherlands |
Speed2 MbpsHandshake7714 msHTTPS7946 ms |
100% successful 1/1 checks · last 7d · small sample | Proxy node collector by ishalumi (Base64) | Download | |
WEBSOCKETTLS |
51.158.180.25Netherlands |
Speed1 MbpsHandshake5746 msHTTPS5976 ms |
100% successful 1/1 checks · last 7d · small sample | Proxy node collector by ishalumi (Base64) | Download | |
TCPTLS |
2.27.109.179Hong Kong SAR China |
Speed1 MbpsHandshake972 msHTTPS1491 ms |
100% successful 1/1 checks · last 7d · small sample | Proxy-Hunter tested candidates | Download | |
WEBSOCKETTLS |
51.158.170.123Netherlands |
Speed—Handshake2215 msHTTPS2854 ms |
100% successful 1/1 checks · last 7d · small sample | Proxy-Hunter tested candidates | Download | |
WEBSOCKETTLS |
78.17.171.62Netherlands |
Speed4 MbpsHandshake1193 msHTTPS1424 ms |
100% successful 1/1 checks · last 7d · small sample | Anonymous tested configs | Download | |
WEBSOCKETTLS |
51.158.238.250Netherlands |
Speed—Handshake5107 msHTTPS5977 ms |
100% successful 1/1 checks · last 7d · small sample | Proxy-Hunter tested candidates | Download | |
WEBSOCKETTLS |
51.158.170.123Netherlands |
Speed4 MbpsHandshake3399 msHTTPS3576 ms |
75% successful 6/8 checks · last 7d | Barry Trojan | Download | |
WEBSOCKETTLS |
51.159.148.230France |
Speed5 MbpsHandshake343 msHTTPS523 ms |
87.5% successful 7/8 checks · last 7d | Barry Trojan | Download | |
WEBSOCKETTLS |
51.158.239.186Netherlands |
Speed1 MbpsHandshake2563 msHTTPS2810 ms |
66.7% successful 2/3 checks · last 7d · small sample | Barry Trojan | Download | |
TCPTLS |
155.138.138.2Canada |
Speed—Handshake575 msHTTPS861 ms |
100% successful 1/1 checks · last 7d · small sample | Matin Trojan | Download | |
TCPNONE |
108.61.186.37Japan |
Speed1 MbpsHandshake1407 msHTTPS1931 ms |
100% successful 1/1 checks · last 7d · small sample | Matin Trojan | Download | |
WEBSOCKETTLS |
51.159.148.230France |
Speed—Handshake390 msHTTPS583 ms |
100% successful 1/1 checks · last 7d · small sample | Matin Trojan | Download | |
WEBSOCKETTLS |
51.158.239.186Netherlands |
Speed3 MbpsHandshake2964 msHTTPS3434 ms |
100% successful 1/1 checks · last 7d · small sample | Matin Trojan | Download | |
WEBSOCKETTLS |
51.158.239.186Netherlands |
Speed4 MbpsHandshake9296 msHTTPS9881 ms |
100% successful 1/1 checks · last 7d · small sample | Iran Intranet Access verified configs | Download | |
WEBSOCKETTLS |
51.158.239.154Netherlands |
Speed4 MbpsHandshake804 msHTTPS1043 ms |
50% successful 1/2 checks · last 7d · small sample | Iran Intranet Access verified configs | Download | |
WEBSOCKETTLS |
51.158.240.195Netherlands |
Speed1 MbpsHandshake4348 msHTTPS4804 ms |
50% successful 1/2 checks · last 7d · small sample | Iran Intranet Access verified configs | Download | |
WEBSOCKETTLS |
51.158.237.119Netherlands |
Speed1 MbpsHandshake721 msHTTPS1005 ms |
75% successful 3/4 checks · last 7d · small sample | Iran Intranet Access verified configs | Download | |
WEBSOCKETTLS |
51.158.171.210Netherlands |
Speed5 MbpsHandshake1065 msHTTPS1331 ms |
100% successful 3/3 checks · last 7d · small sample | Iran Intranet Access verified configs | Download | |
WEBSOCKETTLS |
51.158.238.250Netherlands |
Speed5 MbpsHandshake2715 msHTTPS2950 ms |
100% successful 1/1 checks · last 7d · small sample | Iran Intranet Access verified configs | Download |
Showing up to 20 matching endpoints per page. Use the next page for more results with the same filters, or retrieve the full list from the 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.
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.
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.