Reviews the reverse proxy, load balancer, or ingress configuration in front of an application before it ships: nginx, Caddy, Traefik, HAProxy, Envoy, Apache httpd, a Kubernetes Ingress, or a cloud load balancer. Paste the proxy configuration, the upstream application's proxy trust settings, and the TLS setup to find client IP headers the proxy forwards without overwriting, Host headers passed through to the application, location rules that expose internal admin or metrics routes, path and alias rules that let a request escape the intended directory, request body, header, and timeout limits left at defaults or unlimited, TLS and HSTS settings weaker than the product requires, and WebSocket, gRPC, or upload paths that bypass the rules everything else gets. Returns a verdict, a route map of every path and upstream, evidence-linked findings, the smallest fix in the supplied proxy, and requests that prove it. Written for backend developers and operators who own the edge configuration between the internet and their service.