1

Configure your device to use the proxy

required

Set your browser, device, or application's HTTP/HTTPS proxy to the address below. The IP is an Elastic IP — it does not change between redeploys.

Proxy 52.200.113.73:443
  • Browser (any): Launch a separate browser instance with its own proxy profile so you can run a proxied and a non-proxied browser at the same time. Example for Edge:
    & "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" ` --user-data-dir="$env:APPDATA\Code\tempDirEdge-proxy" ` --proxy-server="52.200.113.73:443" ` --proxy-bypass-list="<-loopback>;*.youbora.com;youbora.com;*.npaw.com;*.lcdn.claro.net.co"
  • Android phone / iPhone: Settings → Wi-Fi → tap your network → Proxy → Manual. Enter 52.200.113.73 as host and 443 as port.
  • Android TV / Fire TV: Use ADB — adb shell settings put global http_proxy 52.200.113.73:443. To remove later: adb shell settings put global http_proxy :0.
  • Tizen (Samsung TV) / WebOS (LG TV): These platforms cannot be routed through a proxy. Instead, open the browser's DevTools, go to the Network tab, and export a HAR file. Then upload it using the Upload HAR button on the HAR Imports page.
  • Custom app / script: Set HTTP_PROXY=http://52.200.113.73:443 and HTTPS_PROXY=http://52.200.113.73:443 in your environment.
2

Install the mitmproxy CA certificate

required for HTTPS

To capture HTTPS traffic the proxy needs to intercept TLS. Install its CA cert so your device trusts it.

  • With the proxy configured, open your browser and go to http://mitm.it — this page is served locally by mitmproxy, no internet access needed.
  • Download the certificate for your platform (Windows, macOS, iOS, Android, Firefox…).
  • Install and mark it as trusted in your OS certificate store or browser trust store.
  • Verify: visit any https:// site — if the connection succeeds without a warning, the cert is trusted.
Your dedicated port: Each tester has their own mitmdump process. Nobody else captures on your port, and your results are visible only to you.
Note: On Android 7+ and some apps, user-installed CAs are not trusted by default for app traffic. You may need a rooted device or a debug build with networkSecurityConfig set to trust user CAs.
Proxy-enabled app build required: Most Android and iOS apps ignore the system Wi-Fi proxy and send traffic directly. Use the proxy-enabled build of the app to ensure its traffic is routed through mitmproxy.