How to use Deep Target – SSL pinning bypass, HTTP intercept & traffic capture. Step-by-step setup for Unity, emulators, and Windows apps.
1. Quick start
Run DeepTarget.exe.
Open Settings (gear icon). In License Activation, enter your license key and click Activate. The key is saved securely (encrypted in the Windows registry). Free version allows Win Processes only; Pro (licensed) unlocks Unity, Emulators, and advanced options.
Under Interceptors, choose a mode: Unity, Win Processes, or Emulators.
Set Proxy port (e.g. 8080) and turn System proxy on if you want Windows apps (e.g. browsers) to use the proxy.
Click the checkmark to save settings, then click Start in the main window. Traffic will appear in the list.
Click a row to see Request and Response in the bottom panels. Use Plain / Web / XML under the Response panel to switch view. Use Copy Headers or Copy Full to copy the selected request.
2. License (Free vs Pro)
Deep Target validates your license online. After activation, the key is stored encrypted in the Windows registry (per-machine).
Free: Win Processes only – capture from any Windows app that uses the system proxy. System proxy and proxy port are available.
Pro (licensed): Unity, Emulators, Console logging, Exclude Google, Capture Unity Functions, Auto Save Captures, and the Filters / Ignore list.
Activate in Settings → License Activation. If the key is invalid, expired, or bound to another PC, you will see an error. One license is bound to one machine (HWID).
3. Modes (Interceptors)
In Settings → Interceptors you pick what to capture:
Mode
Use when
Unity
Unity / IL2CPP games (e.g. Avakin Life). Injects into the game and captures HTTPS via proxy. Pro only.
Win Processes
Any Windows app that uses the system proxy. Turn on System proxy and start capture. Available in free version.
Emulators / VM
Android emulators (LDPlayer, BlueStacks, Nox, MEmu, etc.). Emulator traffic goes through your PC proxy. Pro only.
You can use Unity alone, or Win Processes / Emulators (not both with Unity at once).
4. Emulator setup (step-by-step)
To capture HTTPS from an Android emulator (e.g. LDPlayer, BlueStacks):
Step 1: Install the root CA on the emulator
Deep Target creates a root certificate when the proxy runs. You must install it on the emulator so it trusts the proxy.
Start Deep Target and click Start (so the proxy is running).
In the app folder, open crts\ or the folder where the root CA is exported. Find the root certificate (e.g. rootCert.pfx is used internally; the app may export a .cer for installation). If the app shows a path or export option in Settings or status bar, use that.
Copy that file into the emulator (drag & drop or shared folder).
On the emulator: Settings → Security → Install from storage (or “Install certificates”) and select the .cer file. Name it e.g. “DeepTarget” and install.
Step 2: Set the proxy on the emulator
The emulator must use your PC as HTTP/HTTPS proxy.
On the emulator go to Settings → Network / Wi‑Fi → Proxy (or “Edit” the Wi‑Fi network → Advanced → Proxy).
Set Manual proxy.
Host: your PC’s IP (e.g. 192.168.1.100). Not 127.0.0.1 – use the IP the emulator uses to reach your PC.
Port: same as in Deep Target (e.g. 8080).
Save. Some emulators use “Wi‑Fi proxy” or “Proxy” in Developer options.
Step 3: Configure Deep Target
Open Settings. Enable Emulators / VM under Interceptors (Pro required).
Set Proxy port to the same port (e.g. 8080).
System proxy can be on or off for emulators; the emulator uses the manual proxy you set in Step 2.
Click the checkmark to save, then Start in the main window.
Tip: If you don’t see traffic, check that the proxy port in Deep Target matches the emulator, that the root CA is installed, and that the app in the emulator is using the network (e.g. open the app and refresh).
5. Settings explained
Interceptors
Unity – Capture from Unity/IL2CPP games (injection + proxy). Pro only.
Win Processes – Capture from any Windows app that uses the system proxy. Free.
Emulators / VM – Capture from Android emulators (LDPlayer, BlueStacks, Nox, MEmu, etc.) when they use your PC proxy. Pro only.
Options
System proxy – Set Windows system proxy to Deep Target so browsers and other apps send traffic through it.
Console logging – Extra debug output in console (if you run from a terminal). Pro only.
Exclude Google domains – Don’t MITM Google (e.g. login) so it keeps working. Pro only.
Optional features
Proxy port – Port the proxy listens on (e.g. 8080). Must match what you set in the emulator or system proxy.
Capture Unity Functions – Log Unity/IL2CPP function calls (Unity mode only). Pro only.
Auto Save Captures – Save request/response logs to the captures\ folder. Pro only.
Filters (Pro only)
In Settings you can add domains to an ignore list. Traffic to those domains won’t be shown in the main list. You can also right‑click a row in the main window and choose Add filter by domain (or URL) to add it to the list.
6. Main window
Start / Pause / Stop – Control capture. Use Start after configuring Settings.
Clear – Clear the traffic list.
Export CSV – Export the (filtered) list to a CSV file.
Search box – Filter the list by URL, domain, or process name.
Traffic list – Each row is one request (ID, offset, time, method, URL, status, type, size, process, domain). Click a row to see Request and Response below.
Request panel – Request line, headers, and body for the selected row.
Response panel – Response headers and body. Use Plain (text), Web (HTML in browser view), or XML to switch how the response is shown.
Copy Headers / Copy Full – Buttons under the response area: copy only the request headers of the selected entry, or the full request (headers + body).
Right‑click menu – Copy URL, copy as cURL, open in browser, add filter by URL/domain, remove filters, delete selected, clear selection.
7. Files and folders
Item
Description
settings.ini
Your settings (port, modes, filters, etc.). License key is stored in the Windows registry (encrypted), not in this file.
filter.txt
Process names to exclude from capture (one per line).
captures\
Request/response logs and exported root CA when Auto Save Captures is on.
crts\
Certificates used by the proxy (e.g. per-domain or root).
*.ssl-keys.log / ssl_keys.log
SSL key log (e.g. for Wireshark) when using Unity or proxy mode.
8. Troubleshooting
No traffic in the list
Confirm the correct mode (Unity / Win Processes / Emulators) is enabled and you clicked Start.
For emulators: check proxy host (PC IP) and port on the emulator; confirm root CA is installed.
For Windows apps: turn on System proxy and ensure the port matches.
Port already in use
Change Proxy port in Settings to another port (e.g. 8081) and update the emulator or system proxy to use that port.
Unity game not captured
Use Unity mode (not Emulators). Ensure you have an active Pro license and the game is running and using the network. Check filter.txt so the game’s process isn’t excluded.
License invalid or expired
Open Settings → License Activation and re-enter your key, then click Activate. If the key is expired or banned, contact support. The license is bound to one machine (HWID).