> For the complete documentation index, see [llms.txt](https://developers.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.didomi.io/api-and-platform/domains.md).

# Domains

By default, whether used to load a consent notice, a preference center, or a privacy request widget, the Didomi Web SDK, including its assets (JavaScript files, images, etc.) and API requests, relies on the **privacy-center.org** domain.

You can use one of your own domains for:

* Serving the Web SDK and API requests from your own domain by redirecting all requests to your domain instead of the domain used by Didomi (`privacy-center.org`). This ensures that Didomi does not appear as a third-party on your websites.
* Sharing consents across domains.
* Reducing reliance on browsers. This ensure visitor's consent is captured and ads served comply with user choices.

Once configured, a custom domain can be used for some or all those purposes listed above.

We offer two solutions for setting up your domain:

* [A delegated custom domain relying on Didomi's infrastructure](/api-and-platform/domains/domain-delegation.md)
* [A reverse proxy relying on your own infrastructure](/api-and-platform/domains/reverse-proxy.md)

### Setup options available

<table><thead><tr><th width="142.2265625"></th><th>NS Delegation (subdomain)</th><th>Reverse proxy (subdomain)</th><th>Reverse proxy (main domain)</th></tr></thead><tbody><tr><td>Resilience</td><td>Robust against Adblockers until subdomain is blocked</td><td>Robust against Adblocker until subdomain is blocked</td><td>Robust against Adblocker.</td></tr><tr><td>Increase Adblocker resilience</td><td>✅</td><td>✅</td><td>✅</td></tr><tr><td>Safari ITP</td><td>🟡 Cookie maintained only 7 days</td><td>🟡 Cookie maintained only 7 days</td><td>🟡 Cookie maintained only 7 days</td></tr><tr><td>Implementation complexity</td><td>🟢 Low – NS record only</td><td>🔴 High – Requires reverse-proxy setup</td><td>🔴 High – Requires reverse-proxy setup + Path transformation</td></tr><tr><td>Recommendation</td><td>Best for low-budget, non-technical clients, or non-critical setups</td><td>Best for technical teams with strong infra and allows subdomain branding</td><td>Best for technical teams with strong infra and Adblockers concerns.</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developers.didomi.io/api-and-platform/domains.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.