# Domain Verification - The bedrock of trust in DeDi

### Why Verify a Domain?

Domain verification helps establish trust and provides several benefits:

* Makes your namespace identifiers human-readable
* Establishes clear provenance of data
* Associates your namespace with a verified domain name
* Improves the readability and trustworthiness of API interactions

### Example

#### Before Domain Verification

```http
GET dedi/76EU7hbHV3aEnjjMZKTrPqbudeYrymjYR761h6v6egEe6JMjnkU6HT/employees/Alice
```

#### After Domain Verification

```http
GET dedi/dhiway.com/employees/Alice
```

The verified domain makes the URL human-readable and helps establish clear provenance of the data.

### Verification Process

#### Prerequisites

* A registered domain name that you control
* Access to your domain's DNS settings
* A namespace ID of the namespace you created

#### Steps

1. **Domain Whitelisting**
   * Submit a request [here](https://docs.google.com/forms/d/e/1FAIpQLScAwEZh94DCIw70zrxWUJ1cud_wYfo_WEjqDpEmbxaw5ZF9aw/viewform?usp=dialog) to whitelist your domain
2. **Generate a Verification Record**

   * Use our API/UI to generate the verification value

   ```http
    GET dedi/generate-dns-txt/{{namespace_id}}/{{domain}}?verification_method=self_dns
   ```

   * Supported verification methods are `self_dns`, `self_http`, and `request_other_namespace`
3. **DNS Configuration**
   * Add the provided TXT record to your domain's DNS settings
   * Wait for DNS propagation (can take anywhere from 15 min to 48 hours)
4. **Verify Domain**

   * Use either the UI or API to complete verification

   API Endpoint:

   ```http
   POST /dedi/verify-domain
   ```

   Request Body:

   ```json
   {
     "namespace_id": "string"
   }
   ```

   Verification checks DNS TXT first and falls back to `https://<domain>/.well-known/dedi-verification.txt` for HTTP-based verification.
5. **Re-verification lifecycle**
   * Verified domains are re-checked on a scheduled basis
   * The current implementation re-verifies active sources after a configurable interval with a default of `1` year
   * Failed sources enter a configurable grace period with a default of `7` days before the source is removed
6. **Delegated verification decisions**
   * Target namespace delegates use the verification-request and notification APIs to accept or reject delegated verification requests

### What's Next?

After verification, you can:

* Use your domain name instead of namespace ID in all API calls
* Establish stronger trust with your data consumers
* Create a more professional and polished API experience


---

# 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://dedi-global.gitbook.io/docs/dedi.global-developers/quickstart/domain-verification-the-bedrock-of-trust-in-dedi.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.