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

# Domains

The Didomi Web SDK, including its assets (Javascript files, images, etc...) and API requests, rely on the `privacy-center.org` domain to load a consent notice, preferences widget and/or privacy request widget by default.&#x20;

As an alternative to relying on the default Didomi domain to serve these assets your organization can configure a custom domain to load the SDK and its assets. Some benefits of configuring a custom domain to serve the Didomi SDK include:

* Share consent across domains
* Prevent adblockers from blocking the Didomi SDK&#x20;
* Ensures Didomi does not appear as a third-party on your websites

### Custom domain configurations

Didomi offers your organization two different solutions to configure your custom domains:

> [Domain delegation relying on Didomi infrastructure](https://developers.didomi.io/api-and-platform/domains/domain-delegation)
>
> [Reverse proxy relying on your organization's infrastructure](https://developers.didomi.io/api-and-platform/domains/reverse-proxy)

{% hint style="info" %}
Only custom domains configured using domain delegation is available directly via the Didomi console. The articles in this section cover how to create and manage custom domains from the Didomi console using domain delegation method.
{% endhint %}

Refer to the table below for additional information for all domain options available to your organization:

<table><thead><tr><th width="173"></th><th>Default (privacy-center.org)</th><th>NS delegation (subdomain)</th><th>Reverse proxy (subdomain)</th><th>Reverse proxy (main domain)</th></tr></thead><tbody><tr><td>Increased adblocker resilience</td><td><span data-gb-custom-inline data-tag="emoji" data-code="274c">❌</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td><td><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span></td></tr><tr><td>Safari ITP</td><td>Cookie maintained for 7 days</td><td>Cookie maintained for 7 days</td><td>Cookie maintained for 7 days</td><td>Cookie maintained for 7 days</td></tr><tr><td>Implementation complexity</td><td>Low</td><td>Low - NS record only</td><td>High - requires reverse proxy setup</td><td>High - requires reverse proxy setup and path transformation</td></tr><tr><td>Recommendation</td><td>Low budget, non-technical teams or non-critical setups</td><td>Low budget, non-technical teams or non-critical setups</td><td>Technical teams with strong infra  and allows for subdomain branding</td><td>Technical teams with strong infra and adblocker 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 by asking a question.

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

```
GET https://docs.didomi.io/organization-and-account-settings/domains.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.
