> For the complete documentation index, see [llms.txt](https://doc.sk5data.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sk5data.com/faq/proxy/how-to-test-if-your-proxy-connection-is-working.md).

# How to Test if Your Proxy Connection Is Working

After configuring your proxy, you can use the test commands provided in the SK5Data dashboard to verify that your proxy connection is working properly.

**Steps:**

1. Log in to the SK5Data dashboard and go to the corresponding proxy product's usage page.
2. Obtain the proxy hostname, port, username, and password.
3. Copy the test command provided on the page, or use the following curl commands.

**HTTP Proxy Test:**

```bash
curl -L -x http://username:password@hostname:port ipinfo.io
```

**SOCKS5 Proxy Test:**

```bash
curl -L -x socks5://username:password@hostname:port ipinfo.io
```

Replace the connection parameters in the commands with your actual proxy information.

**How to Interpret the Test Results**

* **Exit IP returned successfully:** The proxy connection and IP lookup request were successful.
* **Authentication failed:** Check your username, password, or IP whitelist settings.
* **Connection timed out:** Check the proxy hostname, port, and network connection.

You can also visit `https://ipinfo.io` to check whether the exit IP's geolocation matches your expected location.

**Note:** Successfully retrieving a proxy exit IP does not guarantee access to all target websites. We recommend testing your target website or application before starting your tasks.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.sk5data.com/faq/proxy/how-to-test-if-your-proxy-connection-is-working.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.