# Introduction **EVMNS (EVM Name Service) is a distributed, open and extensible multi-chain DID domain naming system built on EOS-EVM,** relying on the high performance, security and reliability of EOS to better and seamlessly connect people, information, assets, dApps, etc. in the WEB3 world.\ \ EVMNS domains use the ERC1155 protocol standard with .evm as the domain suffix, such as abc.evm, 123.evm, jack.evm, etc., to map human-readable and easy-to-remember names with all kinds of content at the same time, including but not limited to EVM addresses, EOS addresses, other cryptocurrency addresses, content hashes, URLs, and metadata. EVMNS has similar goals to DNS, the Internet’s Domain Name Service, but has significantly different architecture due to the capabilities and constraints provided by the EOS blockchain and build on EOS EVM. Like DNS, EVMNS operates on a system of dot-separated hierarchical names called domains, with the owner of a domain having full control over subdomains. As the subdomain feature is in development by now, this functionality will be activated later. Top-level domain, like ".evm", is owned by smart contracts calla registrars, which specify rules governing the allocation of their subdomains. Anyone may, by following the rules imposed by these registrar contracts, obtain ownership of a domain for their own use. The hierarchical nature of EVMNS allow anyone who owns a domain at any level may configure subdomains for themselves or others as desired. An example, if Harry owns "harry.evm", he can create 'eos.harry.evm' and configure it as he wants. EVMNS is deployed on the EOS EVM mainnet and on its test network. The multichain will be deployed as the project develops. You can have some practice on [our app](https://app.evmns.space/) or learn more about us on [official website](https://evmns.space/). --- # 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.evmns.space/introduction.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.