Dolphin Anty Proxy Setup: HTTP and SOCKS5 Guide

Dolphin Anty keeps browser profiles separate, while a proxy controls the network route used by a profile. Adding a proxy does not create permission to access a service, change ownership of an account, or reproduce every signal associated with a place. It changes the public network exit observed by a destination. That makes the pairing useful for legitimate jobs such as checking an owned site's regional presentation, administering authorized client workspaces, and testing whether a campaign landing page reaches the correct country version.

Dolphin's quick-start documentation places the proxy field inside profile creation and editing, and its dedicated Proxy screen documentation explains how reusable entries are managed. Databay supplies the authenticated route: the gateway host and port stay the same, while the account username selects the pool, requested geography, and optional session behavior. The practical operating model is therefore simple: save a validated route, assign it to the intended profile, and verify the observed exit before starting the approved task.

Have the following Databay values ready from your dashboard: gateway host gw.databay.co, port 8888, the complete proxy username, and the proxy password. Do not substitute the email and password used to sign in to Databay. Proxy authentication is a separate credential pair. Choose HTTP or SOCKS5 for the Dolphin entry; Databay serves both through the same gateway, so the selected Dolphin protocol must match the prefix you paste.

Keep production values in a password manager. Use redacted examples in screenshots and support tickets, because a pasted proxy line can contain everything another person needs to consume the account's traffic allowance.

Dolphin's official add-proxy guide documents three base forms: host:port, host:port:login:password, and login:password@host:port. It also allows a protocol prefix, with examples for HTTP, SOCKS5, and SOCKS4. Databay users should select HTTP or SOCKS5 and include authentication. A clear single-line template is:

http://DATABAY_USERNAME:DATABAY_PASSWORD@gw.databay.co:8888

For SOCKS5, change only the scheme:

socks5://DATABAY_USERNAME:DATABAY_PASSWORD@gw.databay.co:8888

Replace both placeholders locally; do not publish the completed line. If Dolphin does not parse a credential containing a delimiter such as @ or :, do not silently change the secret or guess at URL encoding; obtain a parser-compatible credential through the approved account-support path. Do not select SOCKS4: it is a Dolphin input option but not one of the Databay gateway protocols offered for this setup. A protocol prefix also prevents a saved entry from being mistaken for a different connection type later.

The Proxy screen is the best starting point when more than one profile may reuse the same configuration. Open Proxy in Dolphin Anty and select Add Proxy, either in the center of an empty list or beside the search field. Paste one supported Databay line, confirm the protocol, and give the entry a name that describes its purpose without revealing credentials. A label such as US product QA - sticky is more useful than a copy of the gateway hostname.

1. Paste the complete HTTP or SOCKS5 route.
2. Use the arrows at the right of the row to run Dolphin's check.
3. Review the reported connection, geolocation, and time-zone information.
4. Save the proxy only after those results match the planned route.
5. Select the saved entry from the target profile instead of pasting credentials repeatedly.

Dolphin also exposes a Link to change IP field for providers that issue a rotation URL. Do not invent a URL for Databay. Geography and session behavior are chosen in the Databay username, so leave that field unused unless the dashboard explicitly supplies a compatible control for the purchased product.

For a one-profile setup, open Browser Profiles, create a profile or edit an existing one, and choose New Proxy in the proxy field. Dolphin's quick-start path for an existing profile is the three-dot menu, Edit, the proxy field, and New proxies. Paste the Databay route, wait for the verification step, and save only after the check completes. If the saved Proxy list already contains the right route, choose that entry instead.

Dolphin documents a faster edit from the profiles table as well: make the Proxy column visible with Customize columns, then use the pencil beside the current value. The editor offers No proxy, New proxy, or a previously saved proxy. Treat No proxy as an explicit direct-route decision. Before using an authorized account, open the profile and confirm the route; an accidental direct connection can invalidate a regional QA result and expose the operator's network address to the destination.

Databay routing controls belong in the proxy username, not in Dolphin's profile name. Start with the base residential selector, prove that it authenticates, and then add one control at a time. The following values are patterns rather than usable credentials:

USER-zone-residential
USER-zone-residential-countryCode-us
USER-zone-residential-countryCode-us-sessionId-dolphin_qa_01

A country selector requests an exit from the chosen pool in that country, subject to current availability. It does not change the browser's language, cookies, account region, GPS, payment details, or legal eligibility. A session identifier requests temporary route continuity; it is not a dedicated IP or a permanent identity. Give separate authorized workspaces distinct session labels so an investigation can trace each route without sharing one label across unrelated profiles.

Choose residential proxies when the approved test requires a consumer-network sample. Choose datacenter proxies when stable infrastructure and throughput better match the job. Pool choice should follow the documented requirement, not a destination's refusal.

A successful result in one interface is useful but not sufficient evidence for every layer. First, use Dolphin's arrow control beside the proxy row. Its documented check reports connection status, geolocation, and time zone. This proves a point-in-time connection from Dolphin's checker, not future availability. Second, confirm the expected saved proxy is visibly assigned to the intended profile. A working entry attached to a different profile does not protect the active one.

Third, launch the profile and open the Databay IP checker. Compare the observed address and country with the routing plan. Do not expect the result to equal gw.databay.co; the gateway is the entry point and the displayed address is the exit used for that connection. If the direct address appears, or the country does not match, stop the workflow and correct the assignment. Record only the exit, timestamp, expected country, profile label, and pass/fail result. Never capture the password or complete authenticated proxy line in verification evidence.

On paid Dolphin plans, the bulk profile control panel can change proxies for selected profiles. The documented flow is to select the profiles, choose Change Proxy from the action bar, and then select no proxy, a new proxy, or a saved one. Dolphin also offers random selection and can restrict that choice to entries whose status is Working. Random assignment is appropriate only when the approved job calls for an interchangeable pool; it is a poor fit for a logged-in workspace that needs a known, auditable route.

For controlled fleets, build a small route ledger: Dolphin profile label, owner, purpose, saved proxy label, Databay session label, requested country, and review date. Store the secret values elsewhere. Use a deterministic mapping for account administration and regional QA, then recheck after editing a route. This creates a clear topology from saved proxy, through the Dolphin connection check, to one assigned profile and its observed exit. It also makes cleanup possible when a client engagement or test window ends.

To edit an existing entry, Dolphin says to click its name on the Proxy screen, change the required values, and select Save. Re-run the connection check after changing the protocol, credential, gateway value, or optional rotation link. Because several profiles can reference a saved entry, identify every dependent profile before editing it; a central change can affect more than the row currently on screen.

Dolphin's sharing documentation limits proxy sharing to users of the same account. Select the proxy on the Proxy screen, choose Share, grant or remove access for the intended user, and save. Use least-privilege access and review it when team membership changes. Removing a proxy from a profile is different from deleting the saved entry: No proxy leaves the saved route available, whereas deleting it from the Proxy screen removes the stored object. Confirm dependencies before deletion, and rotate Databay credentials if they were shared outside the approved team or exposed in a screenshot, export, or ticket.

Change one variable at a time and keep the proxy layer separate from the destination layer. If Dolphin cannot verify the entry, check the selected protocol, the spelling of gw.databay.co, port 8888, the complete proxy username, and the proxy password. Re-paste a redacted template if the parser split the values incorrectly. Confirm the Databay account has an active product and available traffic, then test the same credentials once through an approved client or the cURL proxy setup to determine whether the issue is specific to Dolphin.

1. Document the authorized purpose, profile owner, expected country, and duration.
2. Copy the gateway values from the Databay dashboard and keep secrets out of shared documents.
3. Select HTTP or SOCKS5 and use one of Dolphin's documented authenticated input formats.
4. Save the entry under a descriptive, non-secret name on the Proxy screen.
5. Run Dolphin's connection, geolocation, and time-zone check.
6. Assign the saved route to the intended profile and save the profile edit.
7. Launch the profile and verify the observed exit with a controlled IP endpoint.
8. Record the result without capturing the proxy credential.
9. Keep one session label per continuity-sensitive authorized workspace.
10. Review same-account proxy sharing and remove access that is no longer required.
11. Stop on destination permission, authentication, quota, or rate controls instead of changing routes.
12. Recheck after any Dolphin update, Databay credential rotation, route edit, or network change.

This guide is derived from the official Dolphin Anty help center and Databay's current gateway contract; it does not claim that Databay ran a live Dolphin session on the publication date. Interface labels can change, so use the linked official sources as the authority when a current application screen differs.

Use Dolphin Anty and Databay only for systems, data, and accounts you own or are expressly authorized to operate. Browser isolation and a regional exit do not grant permission to impersonate another person, create deceptive engagement, access a protected resource, ignore a service's account rules, or continue after a destination denies the operation. Prefer a platform's official API, regional preview, sandbox, export, or delegated access whenever it meets the requirement.

Apply multifactor authentication, named profile owners, short-lived team access, source-level request budgets, and credential rotation. For client work, document which operator can use which profile and which regional route. Review Databay's Acceptable Use Policy before scaling. The safest proxy configuration is one that is traceable, purpose-limited, and easy to disable when authorization ends.