Intercept thick-client traffic in minutes.
To intercept non-HTTP thick-client traffic, send the application through a proxy that handles raw TCP, TLS, UDP, DTLS and QUIC. InterceptSuite does this with a SOCKS5 listener and lets you hold, edit and replay every packet. For apps with no proxy setting, use a transparent redirector such as ProxyBridge.
Last updated October 6, 2026
1
Route traffic
Configure the target app to use InterceptSuite SOCKS5, or use a transparent redirector such as ProxyBridge (on GitHub) when the app has no proxy setting.
2
Trust the certificate authority
Install and trust the InterceptSuite CA once so encrypted traffic can be decrypted for inspection.
3
Intercept, edit, and replay
Inspect packets live, modify payloads, drop frames, and replay traffic to test edge-case behavior.
Guides for thick-client testing
- Thick client pentesting: methodology, checklist and tools
- Burp not intercepting thick-client traffic? Why, and the fix
- mitm_relay, NoPE, PETEP and Deluder alternatives compared
- Echo Mirage alternative for Windows 10/11, macOS and Linux
- Replay: Burp Repeater for raw TCP, UDP, TLS, DTLS and QUIC
- Testing OWASP DA7 insecure communication on non-HTTP protocols
- Intercepting PostgreSQL, LDAP and MQTT traffic
- IoT traffic interception hub
Need implementation details?
See our thick-client walkthrough and protocol docs for setup guides, examples, and troubleshooting. If you hit a protocol edge case, reach [email protected].
Related guides
- mitm_relay, NoPE, PETEP and Deluder alternatives compared
- Testing OWASP Desktop App DA7 on non-HTTP protocols
- Thick client pentesting: methodology, checklist and tools
- Intercept thick-client traffic: TCP, TLS, UDP and QUIC
- Replay: a repeater for raw TCP, UDP, TLS, DTLS and QUIC
- InterceptSuite vs mitmproxy, Burp, PETEP, PolarProxy and Echo Mirage