Set up kookeey proxies

MaskPilot manages kookeey connections as standard proxies and does not require a provider-specific plugin or account authorization. Generate a usable connection in the provider dashboard, then enter its protocol, server, port, username, and password.

Extract a kookeey connection

A static product normally exposes fixed connection details in the purchased-node list. For rotating residential proxies, choose a location, route, and session type before generating or extracting a connection.

Host and port reference

Product or connection	Server	Port	Protocol	How to use it
Public kookeey rotating-route example	gate.kookeey.io	15959	HTTP / SOCKS5	This is an example from official developer documentation, not a fixed value for every account
Static residential or datacenter	IP or hostname shown for the purchased route	Port shown for the purchased route	HTTP or SOCKS5	Every purchased route has its own host and port
Actual rotating residential connection	Host generated by Extract dynamic IP	Port generated by the same extraction	Protocol selected during extraction	Use the host, port, account, and password from the same generated record

Use gate.kookeey.io:15959 only to understand the field mapping. Do not apply it when the dashboard did not generate that entry for the current account. Always copy the actual host and port shown by Purchased route details or the current Extract dynamic IP result.

Confirm:

• The HTTP, HTTPS, or SOCKS5 protocol.
• The entry host and port.
• The proxy account and connection password.
• Whether rotating-proxy location and session parameters are already included in the account value.

Entry and authentication formats can differ by product. Use the current kookeey dashboard and official kookeey help center instead of copying a public example account or port.

Add one kookeey proxy

1. Open Proxies in MaskPilot and select “Add proxy.”
2. Select “Standard proxy.”
3. Choose HTTP, HTTPS, or SOCKS5 according to the extracted kookeey connection.
4. Enter the server address, port, proxy account, and connection password separately.
5. Set Provider to kookeey and optionally record the region, expiry date, and purpose.
6. Save, select “Check connection,” and confirm the expected exit.

MaskPilot does not send its Region label to kookeey. To target a country, state, city, or sticky duration, generate the corresponding connection in the provider dashboard first and preserve the complete authentication value.

Bulk import extracted connections

When several proxies are generated, normalize them to one node per line:

host:port:username:password
http://username:password@host:port
socks5://username:password@host:port

A host:port:username:password line without a scheme is imported as HTTP; keep the socks5:// prefix for SOCKS5 endpoints. Paste the list into Bulk import and verify the recognized count before importing. If the provider export contains an index, region, expiry date, or header, keep only the connection fields. Record inventory details on the saved proxies afterward.

Assign it to a browser profile

1. Create or edit a browser profile.
2. Under Network connection, select “Use proxy.”
3. Choose a successfully checked kookeey node.
4. Save and launch the profile, then verify the actual exit.

The kookeey connection and session policy control rotation. Generate a sticky connection when one profile needs a stable exit. When several profiles require different exits, generate and import separate connections instead of assigning the same proxy more than once.

If the check fails

• Confirm that you used the proxy account and connection password, not website sign-in credentials.
• Verify that the protocol, host, and port belong to the same generated route.
• Check plan status, traffic, node expiry, and provider source-network requirements.
• Generate one new connection and compare each field with the failing node.
• Change a VPN or system-proxy route only after confirming that it conflicts with the entry. When kookeey requires an overseas network environment, keep an overseas route that can reach the provider entry.

See Why does a proxy check fail? and Manage and test proxies for more diagnosis steps.