Understanding TLD-Specific Information: Where to Find It and What It Means
Where Can I Find TLD-Specific Information and What Does It Mean?
Depending on the TLD (Top-Level Domain = Domain extension like .de) you want to register, transfer, or manage, different rules and requirements may apply. These requirements are defined by the registry operating the TLD and can vary significantly between domain extensions.
To help you understand these requirements, we provide a comprehensive TLD Knowledge Base within our developer documentation:
https://developers.opusdns.com/tld-knowledge-base/
This Knowledge Base contains all relevant information for domain extensions supported by OpusDNS, including registration requirements, lifecycle policies, transfer procedures, DNS capabilities, contact requirements, and registry-specific restrictions.
Understanding TLD Types
We generally distinguish between two categories of TLDs:
Country-Code Top-Level Domains (ccTLDs)
ccTLDs are associated with specific countries or territories and are typically operated by national registries or organizations appointed by them.
Examples:
.at(Austria).de(Germany).fr(France)
These domains often have country-specific policies, local presence requirements, or unique transfer and renewal procedures.
Generic Top-Level Domains (gTLDs)
gTLDs are not tied to a specific country and are generally available worldwide.
Examples:
.com.fashion.berlin.shop
Although many gTLDs follow ICANN standards, individual registries may still define additional rules and operational procedures.
Why Is This Information Important?
Different TLDs may require different information from domain owners and registrars. Common differences include:
- Required contact roles
- Transfer procedures
- DNSSEC support
- Domain lifecycle and redemption periods
- WHOIS and RDAP policies
- Privacy protection availability
- Local presence requirements
- Registry-specific dispute resolution processes
Reviewing the TLD Knowledge Base before registering or transferring a domain helps ensure that all requirements are met and avoids delays or failed operations.
How to Interpret a TLD Article
Let's use .at as an example.
General Information
This section provides basic information about the TLD.
Example:
| Property | Meaning |
|---|---|
| TLD Type: ccTLD | The domain is a country-code TLD associated with Austria. |
| Registry: nic.at GmbH | The organization responsible for operating the .at namespace. |
| Provisioning Protocol: EPP | Domain operations are performed using the Extensible Provisioning Protocol (EPP). |
| Second-Level Registration: Yes | Domains can be registered directly under .at (e.g. example.at). |
| Accreditation Required: Yes | Registrars must be accredited by the registry to manage domains directly. |
Domain Lifecycle
This section explains how long domains remain active and what happens during renewals or deletions.
Example:
| Property | Meaning |
|---|---|
| Registration Period: 1 year | Domains can initially be registered for one year. |
| Renewal Period: 1 year | Renewals extend the domain by one year. |
| Auto-Renew Enabled: Yes | Domains are automatically renewed if configured. |
| Auto-Renewal Before Expiry: 7 days | Renewal is triggered seven days before expiration. |
| Deletion Policy: Immediate, At expiration | Domains are deleted immediately once they expire if not renewed. |
This information helps you understand when action is required to prevent domain loss.
Grace Periods
Grace periods define what happens after registration, expiration, or deletion.
Example:
| Period | Meaning |
|---|---|
| Redemption Period: 60 days | A deleted domain can still be restored during this period. |
| Pending Restore: 7 days | Additional processing period during restoration. |
| Pending Delete: 59 days | Domain is scheduled for final deletion and cannot be restored. |
These values are important when recovering accidentally deleted domains.
Domain Characteristics
This section describes technical limitations and capabilities.
Example:
| Property | Meaning |
|---|---|
| Domain Length: 1–63 characters | Allowed domain name length. |
| IDN Support: Yes | International characters such as ä, ö, ü are supported. |
| Registry Lock: Yes | Additional registry-level protection against unauthorized changes is available. |
| Premium Domains: No | No special premium domain pricing exists. |
Contacts & Roles
This section defines which contacts must be provided.
Example:
| Property | Meaning |
|---|---|
| Required Contacts: Domain Owner, Technical Contact | These contact types must exist for every domain. |
| Privacy Proxy Allowed: Yes | Privacy services can be used. |
| Thick WHOIS: Yes | Contact information is stored directly at the registry. |
| AuthInfo Required: Yes | Authorization codes are required for certain operations. |
This section helps determine what information must be collected from your customers.
Nameservers & DNS
This section describes DNS-related capabilities.
Example:
| Property | Meaning |
|---|---|
| Nameserver Count: 2–8 | Minimum and maximum number of nameservers. |
| DNSSEC Allowed: Yes | DNSSEC can be enabled for additional security. |
| DNSSEC Required: No | DNSSEC is optional. |
| DNSSEC Mode: DS | The registry expects DS records for DNSSEC configuration. |
If you operate your own DNS infrastructure, this section is especially important.
Transfer Policy
This section explains how domain transfers work.
Example:
| Property | Meaning |
|---|---|
| Transfer Lock Enabled: No | Domains are not automatically transfer-locked. |
| Confirmation Required: Yes (Both parties) | Both current and future domain holders must approve the transfer. |
| Transfer Extends Domain: No | A transfer does not add additional registration time. |
Transfer policies differ significantly between TLDs and should always be reviewed before initiating a transfer.
WHOIS & RDAP
This section contains information about public domain lookup services.
Example:
| Property | Meaning |
|---|---|
| WHOIS Server: whois.nic.at | Official WHOIS service for .at domains. |
Dispute Resolution
This section explains how domain ownership disputes are handled.
Example:
| Property | Meaning |
|---|---|
| Dispute Resolution Available: Yes | Formal dispute procedures exist. |
| Procedure: Domain Dispute | Registry-specific dispute process. |
| UDRP Support: No | The standard ICANN UDRP process does not apply. |
This is particularly relevant for trademark holders and legal disputes.
Comparing Different TLDs
The value of the Knowledge Base becomes especially clear when comparing TLDs.
For example, .at and .berlin differ in several important ways:
.atsupports DNSSEC, while.berlindoes not..atuses a 60-day redemption period, while.berlinuses 30 days..atdoes not extend the registration period during transfers, while.berlinadds one additional year..atsupports privacy proxy services, while.berlindoes not..berlinfollows the ICANN UDRP dispute process, while.atuses its own registry-specific dispute procedure.
Understanding these differences before registering or transferring a domain helps ensure smooth operations and compliance with registry requirements.