Authentication
Duckip supports two practical access patterns: username/password and IP whitelist.
Username and Password
Use this when:
- Your machine IP changes.
- You run tools from laptops, cloud workers, or multiple environments.
- You need one credential format that works across cURL, Python, Node.js, browsers, and proxy tools.
http://your-username:your-password@Host:PortIP Whitelist
Use this when:
- Requests come from fixed servers.
- You want to avoid storing passwords in client-side tool configuration.
- Your deployment runs in a controlled network.
Add the server public IP in the Duckip dashboard before testing. If the server IP changes, update the whitelist first.
Session Notes
For high concurrency, give each worker its own session value instead of forcing all workers through one session. This keeps rotation and troubleshooting cleaner.