FAQ
Answers to common questions about packet capture with NetPeek on iPhone, covering requirements, HTTPS decryption, data handling, and capability boundaries.
No. NetPeek records HTTP/HTTPS traffic through the standard iOS on-device tunnel API—no jailbreak required.
HTTPS inspection relies only on the standard iOS profile-install and certificate-trust flow; no system-level modification is involved.
No. Capture, HTTPS inspection, rewriting, scripts, and replay all run on the iPhone itself.
A computer is only involved if you enable MCP so a desktop AI client on the same Wi-Fi LAN or USB link can help analyze captures.
The steps for capturing HTTPS this way are in Capture HTTPS Traffic on iPhone Without a Mac.
Download the locally generated CA profile in the app, install it under Settings → General → VPN & Device Management, manually enable full trust under Certificate Trust Settings, then add the target host to the MITM list and send a new request.
iOS requires explicit user consent at every step; only hosts on the MITM list are decrypted.
Capture bodies are not uploaded. Capture, storage, and inspection stay on the device. An export, or MCP after you enable it and hand over the token, is how a capture reaches someone else.
Crash reports and anonymous statistics stay off until you turn on the matching switch under Settings → General Settings → Analytics & Improvements.
You can filter the request list by host and path inside the app to focus on the API under debug—this is not an OS-level “capture only one app” mode.
NetPeek captures at the device level through its on-device tunnel, and narrowing happens inside NetPeek. A swipe shortcut turns any request into a filter.
Yes. A request can be copied as a cURL command, exported as a HAR file, or turned into a replay you can edit and resend.
No. Rewrite rules act purely at the traffic layer — editing headers, replacing bodies, mocking responses, blocking, redirecting, or serving local files — while the target app itself is untouched.
Yes. Enable the local MCP service under Settings → NetPeek MCP; compatible clients such as Claude or Codex then use a Bearer token to call 15 capture-analysis tools: searching requests, decoding JWTs, timing waterfalls, security scans, diffing capture runs, and more. The service is off by default; NetPeek itself does not upload capture data.
No. NetPeek is not a consumer VPN and is not for bypassing blocks: its VPN tunnel loops back on the device solely to record traffic for debugging. It provides no proxy servers, does not change your public IP, and cannot unblock content.