# Why Own an NFD? ### **Simplify transactions** Simplify transactions with human-readable names like *staci.algo* instead of long, complex wallet addresses. Users are far less likely to make errors when sending crypto to an NFD than to a traditional 58-character address. Non-Fungible Domains (NFDs) are integrated across all major Algorand wallets, explorers, and dApps, making sending and receiving crypto easier, faster, and more transparent. `staci.algo` ➡️ `Algo Address: DC7K77...EK3Q` *** ### **Self-sovereign identity** Your entire digital identity—linked wallets, assets owned, assets created, social links, bio, DIDs—unified in one profile that follows you across the ecosystem. Say goodbye to creating a new profile for every site and hello to seamless, portable identity.

*** ### **On-chain and off-chain verifications** You can optionally verify your Discord, Twitter, Telegram, Bluesky, Github, email, and domain, enabling you to establish credibility and trust across various platforms. This allows you to carry your off-chain reputation on-chain & vice versa, building a strong and cohesive digital identity.

*** ### **Native DNS — your NFD is a real domain** Your NFD isn’t just a name — it’s a fully functional domain powered by native DNS. Through the `.algo.xyz` TLD, names like `app.algo` become `app.algo.xyz` and are accessible from any browser, email client, or DNS-aware application worldwide. **What you can do with NFD DNS:** * **Host a website** — Point your NFD to a web server, Vercel, Netlify, or any hosting provider with A, AAAA, and CNAME records. * **Receive email** — Configure MX records to use Gmail, ProtonMail, or any email provider at your NFD. * **Secure with SSL** — Use CAA records to control which Certificate Authorities can issue certificates for your domain. * **Verify ownership** — Add TXT records for Google, Bluesky, SPF, DMARC, and other verification systems. * **Custom redirects** — Each NFD gets its own `.algo.xyz` URL that defaults to your profile page and can be set to redirect anywhere. All DNS records are stored on-chain in your NFD’s smart contract, giving you self-custodial, cryptographically enforced control — no third-party registrar required. Record changes are signed transactions, and advanced setups like multisig or DAO-controlled domains are fully supported. The DNS resolver itself is [open-source](https://github.com/TxnLab/nfd-coredns), so anyone can run their own. Learn more in the [Native DNS for NFDs](/platform/manage/native-dns-for-nfds.md) documentation. *** ### **Empowering collectors and creators** Multiple wallets can be linked to a single NFD enabling creators to connect all of their works under a single profile. Collectors or creators can advertise their listings on their 'for sale' page, which aggregates listings across all major NFT marketplaces.

*** ### **Suite of integrations** NFDs are built into the Algorand ecosystem with 60+ unique [integrations](/resources/integrations.md), including [Pera](https://perawallet.app/), [Defly](https://defly.app/), [Allo](https://allo.info/), [Folks Finance](https://folks.finance/), and many more.

*** ### **Multi-chain compatible** NFDs are multi-chain! Any integrator wishing to add support for NFDs can read NFD data from an Algorand node or our public API. You could use your NFD on Solana or Ethereum if the platform supported it!

*** ### **Built on** [**Algorand**](https://www.algorand.foundation/) NFDs are built on Algorand, one of the fastest and most efficient blockchains. Whether you're updating your avatar or adding a new address, every on-chain interaction completes in seconds with ultra-low transaction fees, giving you a smooth and reliable experience.

*** --- # Agent Instructions: 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: ``` GET https://docs.nf.domains/why-own-an-nfd.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.