🌐 Proxy transport

Proxy transport routes OpenDoor traffic through a configured proxy.

Permanent proxy

opendoor --host https://example.com --proxy socks5://127.0.0.1:9050

Use socks5h:// when hostname resolution must happen through the SOCKS proxy:

opendoor --host https://example.com --proxy socks5h://127.0.0.1:9050

socks5:// keeps the existing SOCKS5 behavior. socks5h:// is useful for Tor and proxy environments where DNS resolution must not happen locally.

Explicit proxy transport:

opendoor \
  --host https://example.com \
  --transport proxy \
  --proxy socks5://127.0.0.1:9050

opendoor --host https://example.com --proxy-pool

opendoor --host https://example.com --proxy-list proxies.txt

Example proxies.txt:

socks5://127.0.0.1:9050
socks5h://127.0.0.1:9050
http://127.0.0.1:8080

Custom proxy lists rotate randomly by default, which preserves the existing behavior:

opendoor --host https://example.com --proxy-list proxies.txt --proxy-rotation random

Use sequential rotation when you want each request to follow the proxy file order. Runtime-dead proxies are skipped for the current scan:

opendoor --host https://example.com --proxy-list proxies.txt --proxy-rotation sequential

--proxy-rotation is valid only with --proxy-list. It does not apply to --proxy, --proxy-pool, VPN transports, or direct scans.

opendoor \
  --host https://example.com \
  --transport proxy \
  --proxy socks5://127.0.0.1:9050 \
  --reports json,html

Use proxy transport only where you have permission and where routing behavior is expected.

Proxy credentials and private infrastructure details should not be committed to a public repository.