Skip to main content
T TON Adoption
RU
← Glossary
NODE/03 · Term

TON domain

A name in the .ton zone bound to a TON wallet address or site. Registered through TON DNS as an NFT, traded on marketplaces. Used as a human-readable alternative to long EQ addresses and to address TON Sites.

Aliases: .ton, .ton name, ton dns name

TON domain is a name in the .ton zone, for example wallet.ton or tonkeeper.ton. Technically it is an NFT in the TON DNS collection; the owner can configure which TON address or TON Site the name points to.

Different from a Telegram username

@durov (Telegram username) and durov.ton (TON domain) are distinct:

  • A Telegram username lives inside Telegram, resolves to t.me/durov.
  • A TON domain lives in decentralised TON DNS and resolves to a wallet address or TON Site (tonkeeper.ton → a specific EQ address).

Both trade on Fragment, both are NFTs on TON, both are bought with TON. They occupy different contexts.

What you can set

A TON domain record can hold:

  • Wallet address — the TON wallet the domain points to. Sending TON to mywallet.ton is equivalent to sending to its EQ address.
  • Site — the ADNL address of a TON Site (hosting inside the TON network, not classical HTTP).
  • Storage — a TON Storage file hash.
  • NFT — a back-reference for integrations.

Registration

Registration goes through the TON DNS contract, usually via the Fragment UI or Tonkeeper:

  • Price depends on length. Short names (1-3 chars) are expensive, long names are cheap.
  • Paid in TON. Part of the proceeds flow to TON DNS holders — part of the on-chain economy.
  • Registration lasts a year, renewed annually.

Usage

The most common cases:

  1. Brand addresses for projects: stonfi.ton, dedust.ton, tonkeeper.ton. A human-readable address users can recognise.
  2. Personal wallets: instead of EQAB…48 chars, the user shares myname.ton on a business card.
  3. TON Sites: a decentralised site at mycompany.ton, reachable from Tonkeeper and other TON-aware browsers.

Resolution in wallets

Tonkeeper, MyTonWallet, and the in-Telegram Wallet support .ton domains in their send flow: type myname.ton, the wallet queries TON DNS, gets the real EQ address, displays it for confirmation.

This reduces address-poisoning risk (a short name is hard to spoof visually) but introduces a dependency on the resolver: a wallet hooked to a compromised lite server could receive a poisoned answer. For large transfers it is worth cross-checking the resolved EQ address on an explorer.

Related terms