Configuring an HTTP proxy server - Port Swigger
Summary: PortSwigger's documentation explains that organizations blocking direct public internet access can configure a network proxy for the Burp Suite DAST server to reach external domains such as portswigger.net. The server needs access to portswigger.net on port 443 to activate its license and perform automatic software updates, and specific hosts can be excluded from the proxy through a 'No proxy for' list matched exactly against the hostname or IP address in the URL, without DNS resolution.
Why it matters: The DAST server's license activation and automatic updates depend on reaching portswigger.net on port 443, so a proxy configuration that blocks or intermittently drops that path leaves the scanner unlicensed or out of date. Because proxy bypass entries are matched literally with no DNS resolution, excluding a host by IP address will not bypass the proxy for requests made to that host by its hostname.
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