> 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

The domain determines from where the Didomi SDK and assets are served. In this section we cover the options available to your organization for determining which domain is utilized to serve the SDK and assets.

* [Default domain](#default-domain)
* [Custom domain](#custom-domain)

***

### Default domain

By default, Didomi relies on the `privacy-center.org` domain when serving assets- whether that is to load a consent notice, a preference center, or a privacy request widget, Didomi's SDKs and integrations, including their assets (JavaScript files, images, etc.) and API requests.

Utilizing the default domain is a fast and easy way to launch a consent notice on your organization's property.

### Custom domain

As an alternative to the custom domain that Didomi provides, your organization can also configure a custom domain. While using a custom domain your organization can:

<table data-header-hidden><thead><tr><th width="256"></th><th></th></tr></thead><tbody><tr><td>Serve SDK and API requests</td><td><p>All requests are redirected to your organization's custom domain instead of the default domain used by Didomi (<code>privacy-center.org</code>). This ensures that Didomi does not appear as a third-party on your websites. See the links below for more information:</p><ul><li><a href="/api-and-platform/domains/serve-didomi-assets-from-your-domain.md">Serve Didomi assets from your domain (web)</a></li><li><a href="/api-and-platform/domains/serve-didomi-assets-from-your-domain-mobile.md">Serve Didomi assets from your domain (mobile)</a></li></ul></td></tr><tr><td>Share consents between domains</td><td><a href="/cmp/web-sdk/share-consents-between-domains.md">Click here</a> for more information.</td></tr><tr><td>Reduce reliance on browsers</td><td>This ensures an end-user's consent is captured and ads served comply with the end-user choices.</td></tr></tbody></table>

{% hint style="info" %}
Once a custom domain is configured it can be used for one or more of the purposes listed above.
{% endhint %}

Didomi supports the following methods when configuring your custom domain. Please visit our dedicated resources for more information.

* [Domain delegation](/api-and-platform/domains/domain-delegation.md)
* [Reverse proxy](/api-and-platform/domains/reverse-proxy.md)

For your convenience, Didomi has compiled some benefits and considerations in the matrix below:

<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 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://developers.didomi.io/api-and-platform/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.