Trojan monitoring
TLS-mimicking bypass protocol, URI auto-detect — actively verified from ExitProbe's distributed edge probes.
About Trojan
Trojan disguises proxy traffic as ordinary HTTPS. It requires a valid TLS certificate and falls back to serving a normal-looking website to non-authenticated probes, which is what makes it effective — and also why shallow port checks say nothing about its health.
A Trojan node whose certificate has expired or whose fallback page is answering will look perfectly "up" to simple monitors while carrying zero proxy traffic.
How ExitProbe tests it
- 1ExitProbe parses trojan:// URIs including password, SNI, transport and query parameters.
- 2Completes the full TLS handshake and authenticates with your password from an edge probe.
- 3Pushes verification traffic through the tunnel and confirms the exit IP.
- 4Certificate problems are surfaced as explicit failure reasons instead of generic timeouts.
Your credentials are stored encrypted (AES-256-GCM) and only decrypted in memory at check time on the probe running the test. They never appear in logs, API responses, or incident payloads.
Common questions
Yes — by design. Trojan without TLS is not Trojan, so ExitProbe treats a failed TLS handshake as a hard failure rather than a warning.
Yes. type=ws with path/host parameters in the URI query string is parsed and used during the check.
An immediate authentication/TLS failure and an open incident — plus the exact error reason on the incident page.
Monitor your Trojan server today
Free plan included — real handshakes, exit IP verification, instant alerts.