> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/key-features/main-domain-cookie/how-to-verify-the-domain-where-the-jentis-cookie-is-set.md).

# How to verify the domain where the JENTIS Cookie is set

To check in which domain the JENTIS First-Party Cookie is set, follow these steps:

1. Open your browser's Developer Tools by pressing **F12**.
2. Navigate to the **Application** tab (or its equivalent, depending on your browser).
3. In the sidebar, go to **Storage > Cookies** and select the domain of your current website.
4. A list of cookies set on your domain will be displayed.\\

Look for the **jts-rw** cookie name, which stores the JENTIS First-Party User ID. In the **Domain** column, you can see the specific domain where the cookie is set:

<figure><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2Fgit-blob-3883dd37d310638d696516d971c26986984b8a87%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

If we use the previous example domain <https://ckion-dev.jtm-demo.com/>, this means:

* With the Main Domain Cookie enabled, the domain should appear as `.jtm-demo.com`.
* With the Main Domain Cookie disabled, the domain should appear as `ckion-dev.jtm-demo.com`.

<table><thead><tr><th>Disabled</th><th>Enabled</th></tr></thead><tbody><tr><td><pre><code>Domain: .ckion-dev.jtm-demo.com
</code></pre></td><td><pre><code>Domain: .ckion-dev.jtm-demo.com
</code></pre></td></tr><tr><td><div><figure><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2F3JhSkabJX61Ffm6jSX1c%2Fimage.png?alt=media&amp;token=d559e5cc-4fac-4719-a1a3-0bfae2a63b17" alt=""><figcaption></figcaption></figure></div></td><td><div><figure><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2FPpiqM4YTMJWILIno4Lol%2Fimage.png?alt=media&amp;token=6ec354f1-1781-464a-83ce-ff1659682e5e" alt=""><figcaption></figcaption></figure></div></td></tr></tbody></table>

***

If you have any questions or suggestions, contact us through our [Helpdesk](https://jentis.atlassian.net/servicedesk/customer/portal/1).


---

# 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.jentis.com/key-features/main-domain-cookie/how-to-verify-the-domain-where-the-jentis-cookie-is-set.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.