Troubleshooting AI connectivity - Port Swigger
Summary: PortSwigger's Burp AI and Burp AT require outbound HTTPS traffic to ai.portswigger.net on port 443, and organizations using firewalls or content filtering must allowlist that host. The guide lists three causes of failed AI connectivity: being offline, a network that requires an upstream proxy, and an intercepting proxy such as ZScaler that re-signs traffic with its own certificate, which Burp does not trust by default.
Bottom line: The same TLS interception that security teams deploy to inspect traffic is what blocks Burp's AI features, so the fix is adding the proxy's certificate authority to Burp's trusted certificates rather than loosening network controls.
Read the original at PortSwigger Research ↗
- Topics
- Vulnerabilities & Patching
- Related
- Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026