Dolphin Anty proxy format

Last checked 2026-09-10

  • dolphin anty proxy format

'dolphin anty proxy format' shows up as its own completion, separate from any wording about an error or a failed connection. That is worth taking at face value: some share of the people searching for it are not stuck on a broken proxy at all, they are trying to write the string correctly the first time.

Dolphin Anty documents three input shapes for the same underlying values - host and port on their own, host:port:login:password as one four-field colon-separated string with the host first, and login:password@host:port with the credential pair moved to the front instead. Any of the three can also take a protocol prefix in front of it, such as http://, socks4:// or socks5://, which is how the proxy type itself gets communicated.

The risk is not any one of those three shapes in isolation, it is mixing them: a string built for host:port:login:password pasted into a field that expects login:password@host:port reorders which piece gets read as the host, and nothing in a plain text field stops that from being accepted and simply pointing at the wrong thing.

Everything below runs outside Dolphin Anty. Replace USER, PASS, HOST and PORT with your own values, and keep the single quotes - an ampersand or a hash in a generated password will otherwise be eaten by your shell.

Five-minute checklist

1. Verify host and port alone, the simplest of the three formats

host:port with no credentials is the first format Dolphin Anty documents. If this fails, the host or the port is wrong on its own, before login and password enter the picture at all.

curl -sS -o /dev/null -w 'http_code=%{http_code}\n' --max-time 15 --proxy 'http://HOST:PORT' https://example.com

2. Add login and password as the second format, host:port:login:password, expects them

curl does not parse a raw four-colon string directly, so this command carries the same four values - host, port, login, password - through curl's own user:pass@host:port syntax instead. A failure here means one of the four values is wrong, independent of which order Dolphin Anty wants them written in.

curl -sS -o /dev/null -w 'http_code=%{http_code}\n' --max-time 15 --proxy 'http://USER:PASS@HOST:PORT' https://example.com

3. Confirm the third format, login:password@host:port, behaves the same with no protocol prefix

This is Dolphin Anty's third documented format, written exactly as curl's own scheme-less --proxy syntax. curl's manpage says a value with no protocol prefix is treated the same as an http:// proxy, so this command and the previous one should return the same code; a difference here points at the string itself, not the network.

curl -sS -o /dev/null -w 'http_code=%{http_code}\n' --max-time 15 --proxy 'USER:PASS@HOST:PORT' https://example.com

4. Check whether only HTTPS traffic is blocked once the string is confirmed correct

A correctly assembled string can still fail specifically on HTTPS if the upstream refuses the CONNECT method. Plain HTTP succeeding here while the earlier HTTPS checks failed narrows the fault to CONNECT, not to anything left in the proxy string.

curl -sS -o /dev/null -w 'http_code=%{http_code}\n' --max-time 15 --proxy 'http://USER:PASS@HOST:PORT' http://example.com

5. Confirm the exit IP matches the proxy you meant to reassemble

A string that parses correctly can still point at the wrong proxy if a field was swapped with a value from a different one. Compare this IP against the provider dashboard before assuming the format itself is still at fault.

curl -sS --max-time 15 --proxy 'http://USER:PASS@HOST:PORT' https://api.ipify.org

6. Read the handshake to see which layer stops

Past the format questions above, the verbose trace is what separates a network-level failure from a permission failure from a certificate failure once every field has already been checked.

curl -sS -v --max-time 15 --proxy 'http://USER:PASS@HOST:PORT' https://example.com 2>&1 | head -n 25

Which side owns the problem

OwnerCauseWhat it looks like
The browser The two four-field formats mixed together host:port:login:password and login:password@host:port carry the same four values in a different order. Pasting a string built for one shape into a field that expects the other reorders which piece is read as the host, and the field accepts it without complaint.
The browser Protocol prefix omitted, wrong, or contradicting the proxy that was issued A prefix such as http://, socks4:// or socks5:// changes how the rest of the string is read. Leaving it off defaults to an HTTP proxy, so a proxy actually issued as SOCKS5 typed without the matching prefix - or with the wrong one - fails before authentication is even attempted.
The browser Invisible characters carried over from copy-paste A full-width colon typed from a non-English input method, trailing whitespace, or a line break introduced by a chat client or spreadsheet cell. None of these look different enough to catch by eye, and curl and a browser input field do not necessarily tolerate the same characters.
The proxy CONNECT not permitted on the exit Plain HTTP works, every HTTPS target fails, even with a correctly formatted string. The fourth checklist step isolates this in one command.
The proxy Plan limit or concurrency cap reached The upstream still answers TCP and still authenticates, then declines to forward. Nothing in a correctly formatted string can make this look any different from a bad password.
Credential handling The same reassembled string active on more than one machine at once When one host:port:login:password string is active on more than one machine, the provider sees concurrent sessions from unrelated IPs and may throttle or block the account, which reads exactly like a formatting mistake.

The same failure in other browsers

Vendor documentation only covers its own product. These are the phrasings the same underlying faults get in the other antidetect browsers.

BrowserHow it readsWhat differs
octo-browser octo browser failed to get proxy data Worded as a data-retrieval failure rather than a format complaint, but the underlying question is the same one this page asks: Octo Browser also has to parse a single proxy string into its component fields, and a malformed one produces this wording before any network request happens.
morelogin morelogin proxy detection failed MoreLogin asks for protocol, host, port, account and password as separate typed fields instead of one combined string, so it cannot suffer the exact field-order swap this page describes - but choosing the wrong protocol in its own dropdown produces the same kind of failure before detection even runs.
gologin gologin proxy not working 'gologin proxy not working' is phrased as undifferentiated as a symptom string can be: one wording standing in for format, protocol and credential causes alike, with nothing in it to say the string itself is the problem.

What this page cannot fix

  • socks5 upstreams. Our first release only accepts http and https upstream proxies.
  • An upstream IP that the destination site has already banned. That needs a different exit, and we do not sell IPs.
  • Bandwidth caps, concurrency limits and throttling applied on the provider side of the upstream proxy.
  • A proxy string that is already malformed somewhere upstream of Dolphin Anty, such as in a spreadsheet or a script that generates profiles automatically. We can only help with the string once it reaches the profile field.

If you hand these credentials to other people

Most of the causes above are diagnosable in one command. One is not: when the same host:port:user:pass string is in several hands, you cannot tell who is using which credential, so the same failure keeps coming back and every diagnosis starts from zero.

Proxy Bastion gives each person a separate, revocable, metered link instead of your proxy credentials. They never see the upstream address or password, and you can revoke one without rotating anything.

How it works

Sources

  • Dolphin Anty documents three proxy string input formats - host:port, host:port:login:password and login:password@host:port - and accepts a protocol prefix in front of any of them, for example http://192.168.0.1:8000, socks5://login:password@192.168.0.1:8000 and socks4://192.168.0.1:8000:login:password. https://docs.dolphin-anty.com/en/working-with-proxies/how-to-add-a-proxy-in-dolphin-anty (checked 2026-09-10)
  • The --proxy option treats a value with no protocol prefix the same as an http:// proxy, and accepts credentials embedded in the URL as user:pass@host:port. https://curl.se/docs/manpage.html (checked 2026-09-10)