> For the complete documentation index, see [llms.txt](https://leather.gitbook.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leather.gitbook.io/guides/bitcoin-name-system-bns/when-do-bns-names-expire.md).

# When do BNS-names expire?

This depends on the namespace they are in. The namespace is the toplevel of a BNS name. For example bns.btc is in the .btc namespace. These expire after about 5 years because this is measured in Stacks blocks the actual expiration can vary slightly. After every renewal they are valid for 262,800 Stacks blocks from that moment of renewal.

Some more examples names in the:

* .id namespace expires after approximately 1 year (52,560 Stacks blocks).
* .stx namespace never expire.

Check when a name expires and/or renew it by using <https://renewbns.com/>

144 Blocks per day = 52,560 blocks per year = 262,800 blocks per five years


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://leather.gitbook.io/guides/bitcoin-name-system-bns/when-do-bns-names-expire.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.