1. Trustname Support
  2. Solution home
  3. Domain Registration, Transfers & Pushes
  4. Domain Basics
Open navigation

ICANN Policies and Domain Name Registrations

.The article explains how ICANN policies and country-specific rules govern the registration and management of domain names. It covers key policies that ensure the stability and integrity of the Domain Name System, highlighting how accredited registrars, such as Trustname, enforce these rules.


Key Takeaways

[Component][List][Markers] Custom
  • ICANN's Role – ICANN establishes policies that all accredited registrars must follow, including rules on registration agreements, data accuracy, and domain transfers to ensure a stable and fair domain system.
  • WHOIS Accuracy – You must provide accurate and current contact information for your domain, as failure to do so may result in the domain being suspended or cancelled.
  • Domain Transfer Policy – ICANN regulates domain transfers with specific rules, such as a 60-day lock after any significant changes to registrant information, to protect domain owners.
  • Dispute Resolution (UDRP) – ICANN's Uniform Domain-Name Dispute-Resolution Policy (UDRP) offers a cost-effective means of resolving disputes, particularly those involving trademark infringement.
  • ccTLD Variations – Country-Code Top-Level Domains (ccTLDs) have their own unique policies and eligibility requirements, often influenced by local laws, which must be followed in addition to ICANN's general rules.

TABLE OF CONTENTS


ICANN Policies


The Internet Corporation for Assigned Names and Numbers (ICANN) establishes and enforces policies that govern the registration, management, and resolution of domain names across the Internet. These policies are crucial for maintaining the stability and integrity of the Domain Name System. 


ICANN-accredited registrars, such as Trustname, facilitate the registration and management of domain names in accordance with the body’s regulations. Here’s a detailed look at ICANN’s policies and their functionalities:


1. Registration Agreements

First, ICANN’s Registration Agreement policy

[Component][List][Markers] Custom
  • Overview of the policy

    The Registrar Accreditation Agreement (RAA) is a contract between ICANN and domain registrars. It outlines the responsibilities of registrars in managing domain registrations, including verifying and maintaining accurate WHOIS information, handling domain disputes, and ensuring compliance with ICANN’s rules.

  • How the policy functions

    Registrars must adhere to the ICANN registration agreements to ensure they provide fair and transparent services to domain registrants. Some of these registrant-focused responsibilities include safeguarding registrant personal information, conducting domain transfers to other registrars/registrants, and managing domain name renewals.

  • This policy is in action on Trustname

    When you register your domain name on Trustname, as an ICANN-accredited registrar, we must adhere to the ICANN RAA guidelines, ensuring your registration details are accurate and updated as needed.


    If you opt for Trustname’s Two-Tier domain privacy, you won’t need to verify your domain’s contact details, as the proxy details we’ll use are verified and accurate.


2. WHOIS Accuracy Program


Second on this list is ICANN’s WHOIS Accuracy Program

[Component][List][Markers] Custom
  • Overview of the policy

    When registering a new domain name, ICANN requires that the domain registrant provide accurate contact information and keep it up to date. This policy is part of the WHOIS Accuracy Program, which is designed to ensure that domain data available through WHOIS queries is accurate.

  • How the policy functions

    By ensuring accurate and up-to-date domain contact information, ICANN ensures that the registrant can’t be reached concerning any issues with the domain. Registrants must verify their contact information when registering a domain name and whenever changes are made to the domain’s information. 


    Failing to verify the domain’s contact information within the allotted timeframe (typically 15 days) can result in the suspension or cancellation of the domain.

  • This policy is in action on Trustname

    If your WHOIS contact information changes (e.g., you move to a new address or change your email address), you must update this information in your Trustname customer account to comply with ICANN’s requirements and avoid potential issues with your domain.


3. Domain Transfer Policy


Next is ICANN’s Domain Transfer Policy

[Component][List][Markers] Custom
  • Overview of the policy

    ICANN’s Transfer Policy governs the process and requirements that must be met when transferring domain names from one registrar to another. This policy includes authorization requirements, transfer timelines, and protection features for domain owners.

  • How the policy functions

    To transfer a domain, the current registrar must provide an authorization code (EPP code), and the domain owner must approve the transfer request. Transfers typically take a few days to complete. 


    The ICANN also enforces a 60-day domain transfer lock that prevents you from transferring a domain name to a different registrar within 60 days of making changes to the registrant name, organization, or email address (or the Administrative Contact email address).

  • This policy is in action on Trustname

    If you wish to transfer your domain from Trustname to another registrar, you will need to obtain an EPP code from Trustname and ensure that the domain is valid (i.e., it has not undergone any changes within the last 60 days). You’ll also need to turn off Domain Lock and WHOIS privacy.


    However, you can transfer your domain name to a new owner who also has a Trustname account as many times as you want if you are both using our Two-Tier Domain Privacy.


4. ICANN’s UDRP (Uniform Domain-Name Dispute-Resolution Policy)


And up next, the ICANN UDRP that governs domain disputes

[Component][List][Markers] Custom
  • Overview of the policy

    The UDRP offers a streamlined process for resolving disputes over domain names, particularly in cases involving trademark infringement or disputes over domain ownership. It is designed to provide a cost-effective alternative to litigation.

  • How the policy functions

    Disputants can file a complaint with an approved UDRP provider, who will review the case and determine the appropriate course of action. The decisions from a UDRP provider can be to dismiss the disputant’s claims, transfer the domain, or take down the domain.

  • This policy is in action on Trustname

    Suppose someone registers a domain that closely resembles yours and you believe it infringes on your trademark. In that case, you can initiate a UDRP to file a dispute and reclaim the domain.


5. Domain Name Expiration and Redemption


The ICANN also has policies that govern domain expiry timelines and redemption

[Component][List][Markers] Custom
  • Overview of the policy

    ICANN’s expiry policies outline the lifecycle of domain names, including expiration, grace periods, redemption periods, and pending deletions. When a domain expires, a grace period is available during which the domain can still be renewed at the standard price. 


    After this period, the domain enters a redemption period during which its data is deleted, and it is then placed on the market for anyone to register on a first-come, first-served basis.

  • How the policy functions

    Registrars must follow specific timelines for grace and redemption periods to allow registrants the opportunity to renew their domains before they are deleted. This ensures that registrants have enough time to reclaim expired domains.

  • This policy is in action on Trustname

    If your domain expires, Trustname provides a 30-day grace period during which you can renew it without incurring additional fees. If you miss the grace period, the domain enters the redemption period, where you’d need to pay a higher cost to restore it and contact our support.


    During the redemption period, your domain name may be put up for auction. If it isn’t, it then proceeds to the pending delete phase, where all the domain’s information is deleted, effectively making the domain available for registration by anyone.


ccTLD Policies

Country Code Top-Level Domains (ccTLDs) are top-level domains reserved for specific countries, states, or regions. To obtain a ccTLD, you typically need to have a physical presence in the relevant area. ccTLDs have their own set of rules and policies, which are managed by national authorities. Here’s an overview of ICANN’s ccTLD policies.

1. Eligibility Requirements


This policy dictates the criteria for obtaining a ccTLD domain.

[Component][List][Markers] Custom
  • Overview of the policy

    Many ccTLDs have specific eligibility criteria based on geographic location, residency, or business presence within the country.

  • How the policy functions

    Registrants must meet specific requirements to register or renew a country-code top-level domain (ccTLD) domain, which vary depending on the particular region and the registry managing the ccTLD. These rules ensure that domain registrations align with local regulations and interests.

  • This policy is in action on Trustname

    For the .uk ccTLD, registrants must have a physical presence in the United Kingdom. If you want to register a .uk domain on Trustname, you need to provide verification documents for your UK-based business or residence.



2. Registration Rules

[Component][List][Markers] Custom
  • Overview of the policy

    Each ccTLD registry (the company responsible for maintaining the records for a particular TLD) has different rules for domain registration, renewal, and transfer. These rules can vary widely and are typically deeply influenced by the local laws of the region associated with the ccTLD.

  • How the policy functions

    Domain registrars must comply with these established rules when processing domain registrations and transfers with the ccTLD. These rules will also include specific procedures for handling domain disputes and compliance with local laws.

  • This policy is in action on Trustname 

    For example, the .de ccTLD (Germany) has specific registration rules, such as requiring a local administrative contact within Germany for domain registration. To register a .de domain on Trustname, you only need the contact details of someone in Germany to be listed as the domain’s Admin, and you may not need to be in Germany yourself.



3. Dispute Resolution


There are also particular policies set for ccTLD disputes.

[Component][List][Markers] Custom
  • Overview of the policy

    Some ccTLDs have their unique dispute resolution policies similar to ICANN’s UDRP. These policies address conflicts over domain name ownership or misuse.

  • How these policies function

    Disputants can file complaints to the ccTLD registry or an approved dispute resolution provider to resolve issues related to domain names. Unlike ICANN’s generic UDRP, which outlines UDRP providers, the ccTLD registries are responsible for specifying verified dispute resolution providers.

  • This policy is in action on Trustname

    For the .au ccTLD (Australia), disputes are resolved through the .au Dispute Resolution Policy (auDRP), which provides a process for addressing domain name disputes in the Australia region.



4. Compliance and Enforcement

[Component][List][Markers] Custom
  • Overview of the policy

    ccTLD registries are responsible for enforcing the registration policies particular to a ccTLD and ensuring that these policies comply with national laws and regulations.

  • How these policies function

    Registries monitor domain registrations and maintain records of all domain registrations for their country-code top-level domains (ccTLDs) sent from registrars. They also handle cases of non-compliance, including disputes and violations of the ccTLD registration rules.

  • These policies are in action on Trustname

    If a domain registered under the .cn ccTLD (China) is found to violate local laws or regulations, the .cn registry will take appropriate actions and may suspend or cancel the domain registration.



[Component][Callout] Wrapper - Info
Insert title here [Component][Callout] Title/Title with Icon -> 

Understanding both ICANN’s policies and ccTLD regulations is essential to ensure that you manage your domains effectively and comply with global and local laws.





1. .uk (United Kingdom)

[Component][List][Markers] Custom
  • Registry – Nominet

  • Requirements – .uk domains can be registered by anyone; however, non-residents must demonstrate a strong presence among UK-based businesses and individuals. There are popular second-level TLDs under the main ccTLDs, such as .co.uk and .ac.uk. The ccTLD is available to both individuals and organizations. A UK address is required for the administrative contact.

  • Special Policies – Domain name registrations must comply with Nominet's registration policies and guidelines. Any domain disputes are handled through Nominet’s Dispute Resolution Service.


2. .de (Germany)

[Component][List][Markers] Custom
  • Registry – DENIC

  • Requirements – Anyone can register a .de domain, but registrants must provide a local administrative contact in Germany. For businesses or organizations, proof of registration in the commercial register or similar documentation is needed.

    The .de is the most widely used country code top-level domain (ccTLD) today.

  • Special Policies – DENIC also has specific rules for registering and transferring .de domains. Domain disputes are resolved through DENIC’s own dispute resolution process.



3. .jp (Japan)

[Component][List][Markers] Custom
  • Registry – Japan Registry Services (JPRS)

  • Requirements – Registrants must have a local presence in Japan or a designated agent/representative to register a .jp domain. For organizations, a registered office or business address in Japan is required.

  • Special Policies – JPRS has specific rules regarding domain registration and transfer. Disputes are resolved through JPRS’s dispute resolution policies.


4. .au (Australia)

[Component][List][Markers] Custom
  • Registry – auDA (Australian Domain Administration)

  • Requirements – Registrants must be Australian citizens, residents, or businesses with a registered office in Australia to secure a .au domain. Popular second-level options include .com.au and .net.au.

  • Special Policies – Domain registrations are subject to auDA’s policies, which include eligibility requirements and a dispute resolution process.


5. .ca (Canada)

[Component][List][Markers] Custom
  • Registry – CIRA (Canadian Internet Registration Authority)

  • Requirements – Registrants must be Canadian citizens, residents, or entities. There are Canadian Presence Requirements (CPR) for individual registrants and organizations.

  • Special Policies – The CIRA has policies for domain registration and transfer, and provides a dispute resolution process for domain disputes.


6. .br (Brazil)

[Component][List][Markers] Custom
  • Registry – Registro.br

  • Requirements – Registrant must be a legal resident or have a business in Brazil to secure a .br domain. Brazilian individuals or companies are eligible, and foreign entities must provide a Brazilian administrative contact.

  • Special Policies – Registro.br has specific rules for domain registration and transfer. Disputes are handled through Registro.br’s dispute resolution process.


7. .in (India)

[Component][List][Markers] Custom
  • Registry – NIXI (National Internet Exchange of India)

  • Requirements – There are no specific geographic requirements to register a .in domain, and anyone can register one. For organizations, a local business address in India is required.

  • Special Policies – NIXI has rules governing domain registration and transfer, including a dispute resolution process.


8. .cn (China)

[Component][List][Markers] Custom
  • Registry – NIXI (National Internet Exchange of India)

  • Requirements – There are no specific geographic requirements to register a .in domain, and anyone can register one. For organizations, a local business address in India is required.

  • Special Policies – NIXI has rules governing domain registration and transfer, including a dispute resolution process.


9. .ru (Russia)

[Component][List][Markers] Custom
  • Registry – RU-CENTER

  • Requirements – Registrants must have a local presence in Russia to grab a .ru domain. Russian citizens or entities are eligible, and foreign entities must provide a local administrative contact.

  • Special Policies – RU-CENTER enforces policies for domain registration and transfer, and disputes are resolved through RU-CENTER’s dispute resolution services.


10. .za (South Africa)

[Component][List][Markers] Custom
  • Registry – ZA Central Registry (ZACR)

  • Requirements – The .za TLD is open to anyone worldwide, regardless of local presence. Second-level domains, such as .co.za, .org.za, or .net.za, are more popular.

  • Special Policies – ZACR has policies for domain registration and transfer. Dispute resolution is handled through ZACR’s procedures.


11. .nz (New Zealand)

[Component][List][Markers] Custom
  • Registry – Domain Name Commission

  • Requirements – Anyone in the world can register a .nz domain name, and you don’t need a New Zealand Admin contact. Popular second-level domains include .co.nz, .net.nz, and .org.nz.

  • Special Policies – Domain registrations and transfers are subject to the Domain Name Commission’s policies, which include a dispute resolution process.


12. .ch (Switzerland)

[Component][List][Markers] Custom
  • Registry – SWITCH

  • Requirements – The .ch TLD can be registered by anyone without requiring a local presence in Switzerland, and it’s popular among non-residents.

  • Special Policies – SWITCH has specific policies for domain registration and transfer, including a dispute resolution process.


13. .tv (Tuvalu)

[Component][List][Markers] Custom
  • Registry – Verisign (operated by a third party)

  • Requirements – Anyone can register a .tv domain name, regardless of their location or the type of business they operate. A popular user of the .tv TLD is video streaming platform Twitch.

  • Special Policies – .tv domains adhere to general policies similar to those of other gTLDs, with specific rules governing domain management and dispute resolution.


14. .ae (United Arab Emirates)

[Component][List][Markers] Custom
  • Registry –.ae Domain Administration (AEDA) - TDRA

  • Requirements – There are restricted and unrestricted second-level TLDs under the .ae TLD, each with its own requirements. The .ae domain name is available globally; however, the registrant must verify that they have a legitimate presence in the United Arab Emirates (UAE).

  • Special Policies – AEDA has specific registration and transfer policies, as well as a dispute resolution process. The registrar oversees the registration process and verifies the registrant’s presence in the UAE.

Summary


Each generic top-level domain (gTLD) and country-code top-level domain (ccTLD) has its own registration requirements and policies. For ccTLDs, these requirements reflect the local regulations and operational needs of the respective countries or territories. Understanding these policies is crucial for effectively managing domain names and ensuring compliance with local rules and regulations.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article