> ## Documentation Index
> Fetch the complete documentation index at: https://geonode.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Proxy Endpoint Formats

> Understanding Different Proxy Endpoint Formats and Their Uses

***

This guide will help you understand what a Proxy Endpoint is, the different types available in Geonode, and how to choose the best format for your needs.

***

## **What is a Proxy Endpoint?**

A **proxy endpoint** is the address used to connect to a proxy server. It defines how requests are routed through the proxy, ensuring secure and efficient data transmission.

## **Choosing Between DNS and IP-Based Endpoints**

Geonode allows users to select whether they want their proxy endpoint in DNS (hostname) or IP address format.

1. **DNS-Based Endpoints (Recommended)**

* Uses a domain name (proxy.geonode.io).
* Easier to manage and update dynamically.
* Reduces the risk of connection failures due to IP changes.
* IP-Based Endpoints

2. **Uses a direct IP address**

* May provide slightly faster resolution since it skips DNS lookup.
* Recommended for applications that do not support DNS endpoints.

***

## **Different Endpoint formats**

Geonode provides multiple endpoint formats to support different applications, authentication methods, and network setups.

<img src="https://mintcdn.com/geonode/Z2mY70PWUVAJ3gLv/images/knowledge-base/proxy-service-guide/endpoint-formats.png?fit=max&auto=format&n=Z2mY70PWUVAJ3gLv&q=85&s=531c1a693acee8fd3c4eb1c3eb176e24" alt="Choosing an Endpoint Format" width="1566" height="795" data-path="images/knowledge-base/proxy-service-guide/endpoint-formats.png" />

1. **hostname:port**

* Uses the hostname instead of an IP address.
* Example: `proxy.geonode.io:port`
* Best for: Standard proxy connections without authentication.

2. **hostname:port:username:password**

* Includes authentication credentials for secure access.
* Example: `proxy.geonode.io:port:user:pass`
* Best for: APIs and applications requiring login authentication.

3. **hostname:port\@username:password**

* Alternative authentication format.
* Example: `proxy.geonode.io:port@user:pass`
* Best for: Custom proxy configurations that support this format.

4. **username:password:hostname:port**

* Rearranged authentication format for compatibility with specific applications.
* Example: `user:pass@proxy.geonode.io:port`
* Best for: Applications that require username-password authentication before connecting.

5. **[http://username:password@server:port](http://username:password@server:port)**

* Used for HTTP/HTTPS proxies with authentication.
* `Example: http://user:pass@proxy.geonode.io:port`
* Best for: Secure browsing, authenticated API requests, and accessing restricted content.

***

## **How to Choose the Right Proxy Endpoint Format**

| Format                                                                           | Best For                                      |
| -------------------------------------------------------------------------------- | --------------------------------------------- |
| **Hostname:Port**                                                                | Standard connections without authentication   |
| **Hostname:Port:Username:Password**                                              | Secure authentication for APIs & applications |
| **Hostname:Port\@Username:Password**                                             | Custom proxy configurations, legacy systems   |
| **Username:Password:Hostname:Port**                                              | Applications needing authentication first     |
| **[HTTP://Username:Password@Server:Port](HTTP://Username:Password@Server:Port)** | Secure browsing, authenticated API access     |

***

## **Final Tips**

* Use Hostname:Port for simple connections without authentication.
* Choose IP:Port if you want faster resolution without relying on DNS.
* For authentication, use formats including Username & Password based on application compatibility.
* Ensure security by using encrypted HTTPS connections when handling sensitive data.