> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership/verify-with-dns-txt.md).

# Verify with DNS TXT record

How to verify domain ownership for a Snyk API & Web target with a DNS TXT record

{% hint style="info" %}
**Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface.
{% endhint %}

## Verify with DNS TXT record

Verify domain ownership by adding a TXT record to your DNS configuration.

This verification method proves you have control over the DNS records for your domain without making changes to your website.

### Get verification details

1. In Snyk API & Web, navigate to the **Targets** page.
2. Click the **Domains** tab.
3. Locate your domain and click **Verify**.
4. Select **DNS (TXT)** as the verification method.
5. Note the **CONTENT** value provided.
6. Keep the verification dialog open.

### Create the DNS TXT record

1. Access your DNS management console (provided by your domain registrar or DNS hosting service).
2. Add a new TXT record with these details:
   * **Name/Host**: Your domain's FQDN (for example, `example.com`)
   * **Type**: TXT
   * **Value/Content**: The content value from Snyk API & Web

### Complete verification

1. Return to the verification dialog in Snyk API & Web.
2. Click **Verify**.

After successful verification, you can remove the TXT record.

### Troubleshooting

#### DNS propagation delay

DNS records can take time to propagate across all DNS servers. If verification fails immediately:

* Wait up to 48 hours for full propagation (typically much faster)
* Use a DNS lookup tool to check if the TXT record is visible
* Try verification again after waiting

#### CNAME limitations

If your domain FQDN is a CNAME record, this verification method does not work because of DNS limitations. CNAMEs cannot have TXT records.

Use one of these alternative methods instead:

* [TXT file verification](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership/verify-with-txt-file.md)
* [DNS CNAME verification](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership/verify-with-dns-cname.md)
* [Meta tag verification](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership/verify-with-meta-tag.md)


---

# 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.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/configure-targets/verify-domain-ownership/verify-with-dns-txt.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.