domaindetails.com
Technical Guides
9 min read

Deprecated and Retired TLDs

The history of domain extensions that have been retired from the internet

What Happens When a TLD is Retired?

Throughout internet history, several Top-Level Domains have been deprecated or retired from the DNS root zone. This typically occurs when countries cease to exist due to geopolitical changes, when territories change status, or when new gTLD applications are withdrawn or fail to launch.

The retirement of a TLD is a significant event that requires careful planning to minimize disruption to existing domain holders. IANA (Internet Assigned Numbers Authority) manages this process under established policies and procedures.

Deprecated ccTLDs: Country Codes That No Longer Exist

Why ccTLDs Get Retired

Country Code TLDs are based on the ISO 3166-1 alpha-2 standard. When the ISO updates this standard to remove a country code (typically due to country dissolution, merger, or territorial changes), IANA evaluates whether to retire the corresponding ccTLD.

Historical Retired ccTLDs

.su (Soviet Union)

Still Active*

Country: Union of Soviet Socialist Republics (USSR)
ISO Code Retired: 1992 (after Soviet Union dissolution)
TLD Status: Technically deprecated but remains in DNS root zone

After the Soviet Union dissolved in 1991, the ISO retired the SU code. However, .su was never fully removed from the DNS. It continues to operate with thousands of active registrations, particularly in Russia. This is an exceptional case where a deprecated TLD persists due to existing usage and lack of political will to force retirement.

.yu (Yugoslavia)

Deleted 2010

Country: Socialist Federal Republic of Yugoslavia
ISO Code Retired: 2003
TLD Removed: March 30, 2010

Yugoslavia dissolved in the 1990s into multiple countries (Serbia, Croatia, Bosnia and Herzegovina, Slovenia, North Macedonia, Montenegro). The .yu TLD continued operating for years after dissolution, primarily serving Serbia and Montenegro. When Montenegro became independent in 2006, a transition period began. IANA removed .yu from the root zone in 2010, making it one of the first ccTLDs to be fully retired.

.cs (Czechoslovakia)

Deleted 1995

Country: Czechoslovakia
ISO Code Retired: 1993
TLD Removed: 1995

When Czechoslovakia peacefully split into the Czech Republic and Slovakia in 1993, the .cs TLD was phased out. It was replaced by .cz (Czech Republic) and .sk (Slovakia). The .cs TLD was removed from the root zone in 1995 after a transition period allowing domain holders to migrate to the new ccTLDs.

.dd (East Germany)

Never Delegated

Country: German Democratic Republic (East Germany)
ISO Code Retired: 1990
TLD Status: Reserved but never delegated

The .dd code was reserved for East Germany but was never actually delegated to the DNS root zone before German reunification in 1990. After reunification, .de (representing unified Germany) continued as the single German ccTLD. The .dd code became historically obsolete without ever being used.

.zr (Zaire)

Deleted 2001

Country: Republic of Zaire
ISO Code Retired: 1997 (renamed to Democratic Republic of the Congo)
TLD Removed: 2001

When Zaire was renamed the Democratic Republic of the Congo in 1997, the country code changed from ZR to CD. The .zr TLD was consequently phased out and replaced by .cd. After a transition period, .zr was removed from the root zone in 2001.

.tp (East Timor)

Deleted 2015

Country: Portuguese Timor / East Timor
ISO Code Changed: 2002 (TP to TL)
TLD Removed: February 2015

East Timor (Timor-Leste) gained independence in 2002 and received the new country code TL. The .tp TLD was gradually phased out in favor of .tl. After a lengthy transition period of over 12 years, .tp was finally removed from the root zone in 2015, demonstrating IANA's cautious approach to TLD retirement.

.um (U.S. Minor Outlying Islands)

Retired 2007

Territory: U.S. Minor Outlying Islands
TLD Status: Existed but had no registrations
Revoked: 2007

The .um TLD was delegated for U.S. Minor Outlying Islands but never had any actual domain registrations. Since the territories are uninhabited or have minimal populations, there was no practical use for the TLD. IANA revoked the delegation in 2007. These territories now fall under .us jurisdiction for domain purposes.

The TLD Retirement Process

IANA Procedures for ccTLD Retirement

When a country code is removed from ISO 3166-1, IANA follows established procedures:

1. ISO Update Notification

IANA monitors ISO 3166-1 updates and identifies affected ccTLDs

2. Evaluation Period

Assessment of existing TLD usage, number of registrations, and local community input

3. Transition Plan Development

Working with registry operators to create migration path for domain holders

4. Public Notice and Grace Period

Announcement of retirement timeline (typically 3-5 years notice) and registration freeze

5. Domain Holder Migration

Domain holders transition to alternative TLDs (successor ccTLDs or gTLDs)

6. Root Zone Removal

After transition period, TLD is removed from the DNS root zone, making all domains unresolvable

Sunset Policies for Domain Holders

When a TLD is scheduled for retirement, domain holders typically receive:

  • Multiple Years Notice: Usually 3-5 years advance warning before removal
  • Registration Freeze: No new registrations accepted, only renewals for existing domains
  • Free or Discounted Migration: Offers to transfer to successor TLDs at reduced cost
  • Technical Support: Assistance with DNS updates and email forwarding
  • Data Preservation: Export of registration data before shutdown
  • Refund Policies: Partial refunds for prepaid registrations extending past retirement date

Impact on Domain Holders

When a TLD is retired, domain holders face several challenges:

  • Website Downtime: Domains become unresolvable after retirement
  • Email Disruption: Email addresses using the TLD stop working
  • SEO Loss: Search rankings and backlinks become invalid
  • Brand Confusion: Customers may be unable to find the business
  • Migration Costs: Time and expense of moving to new domain
  • Lost Marketing Materials: Printed materials with old domain become obsolete

Withdrawn New gTLD Applications

Failed Applications from 2012 Round

During the 2012 New gTLD Program, not all applications resulted in delegated TLDs. Many were withdrawn or failed for various reasons:

Reasons for Application Withdrawal

Financial Issues

Applicants unable to secure funding or sustain costs through lengthy evaluation process. Some applications cost over $500,000 when including consulting, legal fees, and potential auction costs.

GAC Objections

Governmental Advisory Committee advice against certain strings, particularly geographic names or sensitive terms. Some applicants withdrew rather than fight governmental opposition.

Community Opposition

Strong community objections from established groups. Examples include applications for religious terms (.islam, .catholic) that faced community concerns about appropriate operation.

Contention Resolution Failure

Multiple applicants for same string unable to reach private resolution, and unwilling or unable to participate in ICANN auctions. Some contested strings remain unresolved years later.

Strategic Abandonment

Companies reassessing business case during multi-year evaluation. Market conditions changed, leadership changed, or strategic priorities shifted.

Technical or Operational Deficiencies

Applications that failed Initial Evaluation and applicant unable or unwilling to address deficiencies during Extended Evaluation.

Notable Withdrawn Applications

  • .africa: Multiple competing applications led to years of contention, with some withdrawn
  • .islam: Faced community objections and concerns about appropriate governance
  • .wine and .vin: Initial objections from geographic indication interests, some applications withdrawn
  • Various brand TLDs: Some companies withdrew after deciding the investment wasn't justified

Failed New gTLDs That Never Launched

Delegated but Never Operational

Some TLDs were technically delegated to the DNS root zone but never actually launched for public registration:

Delayed Launches

Several delegated TLDs experienced years-long delays before launching registration services. Technical issues, business reorganizations, or strategic reconsiderations caused indefinite postponements. Some remain delegated but inactive.

Registry Operator Terminations

In rare cases, ICANN has terminated registry agreements for failure to meet contractual obligations. This can happen if a registry fails to launch within required timeframes, fails to maintain technical stability, or violates other agreement terms.

Backend Provider Failures

Some registry operators using shared backend providers experienced delays when those providers faced financial or technical difficulties. Transition to new providers caused extended launch postponements.

Registry Terminations and Transfers

When Registries Change Hands

Sometimes TLD operations are transferred between registry operators due to business failures, acquisitions, or voluntary transfers:

Emergency Backend Registry Operator (EBERO)

ICANN's contingency plan for registry failures:

  • Purpose: Ensure continuity of critical registry functions if operator fails
  • Activation: Triggered by persistent registry failures (DNS resolution, RDAP/WHOIS, etc.)
  • Temporary Operation: EBERO operates registry on interim basis while permanent solution found
  • Domain Holder Protection: Existing domains continue to resolve and renew
  • Transition: Registry eventually transferred to new operator or existing operator restored

Voluntary Registry Transfers

Registry operators may transfer TLDs through:

  • Corporate Acquisitions: Parent company sells business unit including TLD operations
  • Portfolio Consolidation: Operators selling non-core TLDs to focus on key properties
  • Financial Distress: Struggling operators selling assets to avoid complete failure
  • Strategic Realignment: Companies exiting registry business entirely

Domain Holder Protections During Transitions

ICANN requires registries to maintain operations during transitions:

  • Continuous DNS resolution throughout transition
  • Honor existing registration terms and pricing (usually)
  • Maintain RDAP/WHOIS services without interruption
  • Allow transfers and updates during transition period
  • Provide adequate notice of any policy changes under new operator

Historical TLD Changes and Rebranding

Country Name Changes

When countries change names without changing ISO codes, ccTLDs may undergo rebranding:

.cz (Czech Republic / Czechia)

The country officially adopted "Czechia" as a shorter name in 2016, but the ISO code remained CZ and the TLD unchanged. The registry now markets to both names.

.mk (Macedonia / North Macedonia)

After the country changed its name to North Macedonia in 2019, the ISO code MK remained unchanged, as did the .mk ccTLD. No technical changes were required.

.mm (Burma / Myanmar)

The country has been known as both Burma and Myanmar. The ISO code MM (Myanmar) was assigned, and .mm serves as the ccTLD regardless of which name is used internationally.

Territory Status Changes

When territories change political status but retain their ISO codes:

  • .hk (Hong Kong): Maintained after Hong Kong's transfer to China in 1997
  • .mo (Macau): Continued after Macau's transfer to China in 1999
  • .ps (Palestine): Delegated despite complex political status

Lessons for Domain Holders

Minimizing Risk from TLD Changes

  • Monitor IANA Announcements: Stay informed about potential ccTLD changes
  • Diversify TLD Portfolio: Don't rely solely on obscure or politically unstable ccTLDs
  • Maintain Alternative Domains: Have backup domains in stable TLDs (.com, country-specific)
  • Use Domain Redirects: Implement redirects from alternative TLDs as contingency
  • Plan Migration Early: Don't wait for final retirement notice to begin transition
  • Update Marketing Materials: Use domain names that can be easily changed if needed

Warning Signs

Indicators that a ccTLD may be at risk:

  • Country experiencing political instability or territorial disputes
  • Discussions of country name changes or mergers
  • ISO considering changes to country codes
  • Registry operator financial difficulties or management changes
  • Declining registration numbers or loss of international recognition

Key Takeaways

  • ccTLDs can be retired when countries cease to exist or change ISO codes due to political changes
  • Historical retired ccTLDs include .yu (Yugoslavia), .cs (Czechoslovakia), .zr (Zaire), and .tp (East Timor)
  • IANA provides multi-year transition periods with sunset policies to minimize disruption to domain holders
  • Many 2012 gTLD applications were withdrawn due to financial issues, objections, or failed contention resolution
  • Domain holders should maintain backup domains in stable TLDs and monitor IANA announcements for potential changes