# HTTP Debugger Pro > A Windows tool that captures and decrypts HTTP and HTTPS traffic machine-wide, from any process, with no proxy configuration and no browser extension. Capture happens low in the Windows network stack, not through a proxy and not through pcap. It sees browsers, desktop applications, Windows services, console utilities, and AI agents running on the same machine, and it reads HTTP/2, WebSocket, Server-Sent Events, and gRPC. It runs on Windows 10 and Windows 11 only; there are no macOS or Linux builds. Current release: version 10.10, 2026-09-17. HTTP Debugger Pro is a commercial product from MadeForNet, in development since 2007. The trial runs 7 days with no feature limits and no registration. A single license costs $129, paid once; it does not expire and covers the first year of updates and technical support. After that year, renewing maintenance costs $89 per license per year and extends updates and support. Renewal is optional: the product keeps working without it. Volume discounts apply to larger orders: 10% off for 5–9 licenses, 15% for 10–24, 20% for 25–49, 25% for 50–99, and 30% for 100+. Every purchase carries a 30-day money-back guarantee. Pricing and checkout: https://www.httpdebugger.com/purchase ## Product - [HTTP Debugger Pro](https://www.httpdebugger.com/): What the tool captures on Windows and how machine-wide capture works without a proxy. - [Features](https://www.httpdebugger.com/features): Protocol coverage, viewers, filtering, traffic modification, and export formats. - [Download](https://www.httpdebugger.com/download): Get the Windows installer and start the trial. - [Purchase](https://www.httpdebugger.com/purchase): Price, what a license includes, and the volume discount tiers. - [Renew maintenance](https://www.httpdebugger.com/renew): Extend updates and technical support on a license whose first year has ended. - [Release notes](https://www.httpdebugger.com/changes): What changed in each version, newest first. - [Version history](https://www.httpdebugger.com/history): Screenshots of the application from the first 2007 release to the current build. ## Debugging tasks - [Debug WebSocket connections](https://www.httpdebugger.com/debug/websocket-connections): Read the upgrade handshake and the frames that follow, including opcodes, masking, compression, and close codes. - [Debug SSE and EventSource streams](https://www.httpdebugger.com/debug/sse-eventsource-streams): Check stream headers, event fields, reconnection behavior, buffering, and truncated streams. - [Debug gRPC calls](https://www.httpdebugger.com/debug/grpc-calls): Read gRPC on the wire: HTTP/2 streams, length-prefixed Protobuf framing, metadata, and grpc-status trailers. - [Debug HTTP traffic with AI agents over MCP](https://www.httpdebugger.com/debug/http-traffic-mcp-agents): Connect Claude Code, Codex, or another MCP client to the live capture session and read it through eight MCP tools. - [Debug HTTP/2 traffic](https://www.httpdebugger.com/debug/http2-traffic): Inspect multiplexed streams, HPACK-compressed headers, pseudo-headers, and per-connection stream IDs. - [Debug OAuth 2.0 and OIDC login flows](https://www.httpdebugger.com/debug/oauth-oidc-login-flows): Capture the authorize, callback, and token requests behind redirect_uri and invalid_grant failures. - [Debug CORS errors](https://www.httpdebugger.com/debug/cors-errors): Tell a failed preflight from a failed actual response, inspect the headers involved, and verify the server-side fix. - [Debug localhost and 127.0.0.1 traffic](https://www.httpdebugger.com/debug/localhost-127-0-0-1-traffic): Capture loopback traffic from browsers, CLI tools, services, and desktop apps without hosts-file tricks. ## Setup and troubleshooting - [Getting started](https://www.httpdebugger.com/gettingstarted/gettingstarted.html): First capture session, from starting capture to reading the panes, filtering, searching, and exporting. - [HTTPS traffic is missing or unreadable](https://www.httpdebugger.com/debug/https-traffic-not-captured): Trust the local root certificate in Windows, Firefox, and Java so HTTPS requests show up decrypted. - [Windows requires a digitally signed driver](https://www.httpdebugger.com/help/windows_requires_digitally_signed_driver): Fix the driver signature error that stops the installer. - [Capture HTTPS from Android emulators](https://www.httpdebugger.com/help/android.html): Intercept traffic from Android Studio virtual devices and other Android emulators. - [Capture HTTPS from Java applications](https://www.httpdebugger.com/help/java.html): Import the root certificate into the Java keystore with keytool so Java traffic decrypts. - [HTTP 503 Service Unavailable](https://www.httpdebugger.com/http/503-service-unavailable): What a 503 means, how it differs from 502 and 504, and how to find the cause. ## Rules and traffic modification - [HTTP Modifier](https://www.httpdebugger.com/manual/httpmodifier.html): Rewrite request and response headers and body on the fly with match rules and regex. - [Auto-Reply](https://www.httpdebugger.com/manual/autoresponder.html): Return a custom status, headers, and body without touching server code, to mock an API or simulate errors. - [TCP/IP Redirector](https://www.httpdebugger.com/manual/tcpredirector.html): Redirect TCP connections between endpoints and map ports without changing client code. - [Filtering captured traffic](https://www.httpdebugger.com/manual/filters): Narrow the grid by application, domain, method, and content type. ## Background - [HTTP debugging guide](https://www.httpdebugger.com/http/debugging-guide): Common HTTP debugging scenarios with request and response examples. - [No-proxy vs proxy debugging](https://www.httpdebugger.com/http/no-proxy-capture): How the two capture models compare on fidelity, apps that ignore proxies, loopback traffic, and setup risk.