.top

.top

I updated the article to reflect that the .top domain had cured its Notice of Breach from 2024 and edited Notice Of Breach to Notice of Breach in the previous sentence to reflect ICANN usage.

← Previous revision Revision as of 19:08, 21 April 2026
Line 29: Line 29:
A [[Second-level domain|second level domain]] under the [[top-level domain]] (TLD) .top can consist of digits, letters, hyphens and specific special characters while it can have a length of one up to (a maximum of) 63 characters. Like most other TLDs, it can be registered for a period of at least one year up to (a maximum of) 10 years in advance. The private registration ([[Whois privacy|WHOIS privacy]]) of .top domains is supported, as is the ability to register [[Internationalized domain name|internationalized domain names]] (IDNs), which include the character sets Arabic, Chinese (simplified and traditional), French, German, Japanese, Russian, and Spanish.
A [[Second-level domain|second level domain]] under the [[top-level domain]] (TLD) .top can consist of digits, letters, hyphens and specific special characters while it can have a length of one up to (a maximum of) 63 characters. Like most other TLDs, it can be registered for a period of at least one year up to (a maximum of) 10 years in advance. The private registration ([[Whois privacy|WHOIS privacy]]) of .top domains is supported, as is the ability to register [[Internationalized domain name|internationalized domain names]] (IDNs), which include the character sets Arabic, Chinese (simplified and traditional), French, German, Japanese, Russian, and Spanish.


On 16 July 2024 ICANN issued a Notice Of Breach to the registry for failing to respond to DNS abuse reports and failing to pay fees.{{cite web |title=RE: NOTICE OF BREACH OF REGISTRY AGREEMENT |url=https://www.icann.org/uploads/compliance_notice/attachment/1225/hedlund-to-wenxia-16jul24.pdf |website=icann.org |publisher=ICANN |access-date=29 July 2025}}
On 16 July 2024 ICANN issued a Notice of Breach to the registry for failing to respond to DNS abuse reports and failing to pay fees.{{cite web |title=RE: NOTICE OF BREACH OF REGISTRY AGREEMENT |url=https://www.icann.org/uploads/compliance_notice/attachment/1225/hedlund-to-wenxia-16jul24.pdf |website=icann.org |publisher=ICANN |access-date=29 July 2025}} On 2 June 2025, ICANN announced that the registry had cured its Notice of Breach.{{cite web |title=.TOP Registry Has Cured the Notice of Breach of its Registry Agreement |url=https://www.icann.org/en/blogs/details/top-registry-has-cured-the-notice-of-breach-of-its-registry-agreement-02-06-2025-en |website=icann.org |publisher=ICANN |access-date=21 April 2026}}


== Development==
== Development==