> For the complete documentation index, see [llms.txt](https://docs.ts.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ts.finance/security-and-risks/dns-security.md).

# DNS Security

TermMax implements robust DNS security measures to protect users from domain-based attacks and ensure secure access to our platform. Our DNS infrastructure is designed to prevent spoofing, cache poisoning, and man-in-the-middle attacks.<br>

### DNSSEC Implementation

#### DNS Security Extensions (DNSSEC)

TermMax domains are signed with DNSSEC, enabling cryptographic validation of DNS records by resolvers. This helps prevent DNS spoofing and cache-poisoning attacks that could redirect users to malicious sites.

#### Digital Signature Validation

All DNS records are DNSSEC-signed, enabling validating resolvers to cryptographically verify the authenticity and integrity of DNS responses. This helps ensure users are directed to the legitimate TermMax platform and reduces the risk of DNS spoofing and cache-poisoning.<br>

### Domain Protection Measures

#### Domain Monitoring&#x20;

We proactively monitor for suspicious or look-alike domain registrations (including typosquatting) and phishing sites targeting TermMax. When identifying the unknown registrations, the team will immediately survey and respond.

#### Secure DNS Resolvers

We are using DNS resolvers that perform DNSSEC validation. This helps protect against DNS spoofing and cache-poisoning attacks.


---

# 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.ts.finance/security-and-risks/dns-security.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.