# 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. 

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 
* 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:

> [Delegated custom domain 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 delegated custom domain relying on Didomi infrastructure (NS delegation) is available from the Didomi console. The articles in this section cover how to create and manage custom domains from the Didomi console using the NS 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: 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:

```
GET https://docs.didomi.io/organization-and-account-settings/domains.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.