Technical Glossary
A hierarchical and distributed naming system that translates human-readable domain names into numeric IP addresses and other resource records required for locating internet services. DNS operates through a delegation chain from root servers through top-level domain servers to authoritative nameservers, with recursive resolvers caching responses to optimize query performance. It supports record types including A, AAAA, CNAME, MX, TXT, and SRV for diverse service addressing requirements. The core DNS protocol is defined in IETF RFCs 1034 and 1035 with numerous extensions for security, privacy, and modern applications.
A contractual arrangement granting a licensee the right to use, operate, or sublicense a registered domain name under specified terms, conditions, and duration without transferring ownership of the underlying registration. Domain licensing agreements define permitted uses, branding requirements, revenue sharing structures, content restrictions, and termination provisions between the domain holder and licensed operator. They are increasingly used in portfolio monetization, franchise digital presence management, and namespace-as-a-service business models. ICANN policies and applicable intellectual property law establish the regulatory framework governing domain licensing practices.
A query-response protocol used to retrieve registration information about domain names, IP address blocks, and autonomous system numbers from authoritative database servers maintained by registries and registrars. WHOIS returns structured data including registrant identity, registration and expiration dates, nameserver assignments, and registrar details. Privacy regulations including GDPR have led to significant changes in WHOIS data availability, prompting the development of RDAP as a modern successor. RFC 3912 defines the WHOIS protocol specification, while ICANN policies govern its implementation across gTLD registries.
A RESTful HTTP-based protocol designed to replace WHOIS by providing standardized, machine-readable access to domain registration data with built-in support for internationalization, structured responses, and differentiated access controls. RDAP returns JSON-formatted responses with typed data elements, enabling programmatic consumption and fine-grained privacy controls compliant with data protection regulations. It supports queries for domain names, IP networks, autonomous systems, nameservers, and entity information across registries. IETF RFCs 7480 through 7484 define the RDAP protocol architecture, query format, and response structure.
The systematic assessment of a domain name's monetary worth based on quantitative and qualitative factors including keyword relevance, search volume, extension type, brandability, length, comparable sales history, and existing traffic metrics. Domain valuation methodologies employ algorithmic scoring models, machine learning-based price prediction, and expert appraisal techniques used by registrars, brokerages, and portfolio managers. Accurate valuation is essential for domain acquisitions, licensing negotiations, insurance underwriting, and intellectual property portfolio management. Industry data from platforms like ICANN-accredited registrars and aftermarket exchanges informs valuation benchmarks.
A suite of IETF specifications that add origin authentication and data integrity verification to DNS responses through hierarchical chains of cryptographic signatures, protecting against cache poisoning and man-in-the-middle attacks. DNSSEC introduces new resource record types including RRSIG, DNSKEY, DS, and NSEC that enable resolvers to validate that DNS data has not been modified in transit. The trust chain extends from the signed root zone through each delegated zone's key signing ceremonies. DNSSEC deployment is specified in RFCs 4033, 4034, and 4035 with subsequent operational guidance in RFC 6781.
A standardized XML-based protocol for provisioning and managing domain name registrations, host objects, and contact information between registrars and registry operators through authenticated and encrypted sessions. EPP defines a client-server architecture with command-response semantics supporting create, read, update, delete, and transfer operations with built-in extension mechanisms for registry-specific requirements. It replaced earlier proprietary registration protocols to enable multi-registrar competition and interoperability within the domain name industry. The EPP framework is specified in IETF RFCs 5730 through 5734.
A centralized database established by ICANN that serves as an authoritative repository of verified trademark information used to protect intellectual property rights during domain name registration processes across new generic top-level domains. The TMCH enables trademark holders to register their marks and receive priority registration through Sunrise periods and ongoing notifications through the Trademark Claims service when matching domains are registered. It validates trademark data against national and international registration records before inclusion. The TMCH represents a critical rights protection mechanism in the expanded gTLD namespace environment.
An administrative dispute resolution procedure established by ICANN for resolving conflicts between trademark holders and domain name registrants without resorting to court litigation. UDRP proceedings evaluate whether a domain was registered and used in bad faith, whether the registrant has legitimate rights or interests, and whether the domain is identical or confusingly similar to a complainant's trademark. Disputes are adjudicated by WIPO and other approved dispute resolution providers through panel decisions that can order domain transfer or cancellation. The policy applies to all gTLD registrations and many ccTLD registries by adoption.
The strategic administration of multiple domain name assets encompassing acquisition planning, renewal management, categorization, monetization strategy, brand protection coverage, and disposition decisions across a coherent portfolio framework. Portfolio management employs automated monitoring for expiration alerts, trademark infringement, DNS health, and valuation fluctuations across hundreds or thousands of domain holdings. It integrates with registrar APIs, analytics platforms, and marketplace services to optimize return on investment and minimize defensive registration costs. Enterprise domain portfolio management aligns with broader digital asset governance and intellectual property strategy.
Domain names that contain characters from non-ASCII scripts such as Arabic, Chinese, Cyrillic, Devanagari, and other Unicode character sets, encoded using the Punycode compatible encoding scheme for backward compatibility with existing DNS infrastructure. IDN processing involves IDNA2008 validation rules that map, normalize, and verify internationalized labels before converting them to ACE-encoded labels prefixed with xn--. They enable native-language internet addressing for billions of non-English-speaking users worldwide. IETF RFCs 5890 through 5895 define the current IDNA framework, with ICANN coordinating IDN TLD deployment policies.
A monetization practice in which registered domain names that are not actively hosting content are pointed to placeholder pages displaying contextually targeted advertising, generating revenue through pay-per-click advertising models. Domain parking services automatically analyze domain keywords, type-in traffic patterns, and advertiser bid landscapes to optimize ad placement and revenue yield for portfolio holders. It serves as a holding strategy during development planning, licensing negotiation periods, or as a passive income stream for premium domain investments. Industry self-regulation and ICANN policies address parking abuse including deceptive practices and trademark-infringing traffic arbitrage.
The three-tier organizational structure governing domain name registration in which registries maintain authoritative zone databases for top-level domains, registrars serve as accredited intermediaries processing registration requests, and registrants are the end-user entities that register and control individual domain names. This model separates infrastructure operations from retail distribution, enabling competitive pricing and service differentiation at the registrar level while maintaining registry-level consistency. ICANN accreditation agreements and registry agreements define the contractual relationships between parties. The model extends to reseller and privacy/proxy service layers in practice.
The standardized procedures and technical mechanisms governing the migration of domain name registrations between registrars, including authorization verification through transfer authorization codes, gaining and losing registrar acknowledgment workflows, and mandatory waiting periods. Domain transfer protocols enforce identity verification, prevent unauthorized transfers, and maintain registration data integrity throughout the migration process. ICANN's Inter-Registrar Transfer Policy defines the mandatory timelines, notification requirements, and dispute resolution procedures applicable to gTLD transfers. EPP transfer commands specified in RFC 5731 provide the technical implementation layer for automated transfer processing.
A business model and technical architecture in which organizations offer managed namespace allocation, subdomain provisioning, and hierarchical naming services to third parties under licensing or subscription arrangements within their controlled domain infrastructure. NaaS platforms provide API-driven namespace creation, DNS management, SSL certificate provisioning, and usage analytics for tenants operating within the provider's domain hierarchy. This model enables franchise networks, platform ecosystems, and enterprise divisions to maintain branded digital presence without independent domain procurement. The architecture draws on DNS delegation standards, multi-tenant certificate management, and automated provisioning through EPP and DNS API integrations.