.mobi is a delegated gTLD implemented on October 17, 2005, with Identity Digital Limited as its registry.

.mobi was originally introduced as a Sponsored TLD for mobile-related Internet content and services. It was intended for websites and services optimized for access by mobile devices. The original registry operator and sponsoring organization was mTLD Top Level Domain Ltd., commonly known as dotMobi.^[1]

As of 2026, .mobi is no longer under a sponsored registry agreement: ICANN lists the current .mobi Registry Agreement as a Base, Non-Sponsored agreement dated March 30, 2017.^[2]

History[edit | edit source]

Application and Approval[edit | edit source]

.mobi was applied for during ICANN's 2003-2004 sponsored TLD application process. ICANN received ten applications for nine proposed sponsored TLD strings by the close of the application period on March 16, 2004, including .mobi. The .mobi application was submitted by Nokia Corporation, Vodafone Group Services Limited, and Microsoft. The applicant selected Afilias Limited to provide back-end registry services.

The application raised policy and technical concerns during evaluation. According to the IANA delegation report, the technical evaluation team expressed concerns about using a TLD to signal mobile-device content, including possible namespace fragmentation and the possibility that content providers would feel compelled to register defensive .mobi names. The sponsorship/community value evaluation also raised concerns about the definition of the sponsored community and the proposed policy-development structure. After additional submissions from the applicant, the ICANN Board authorized contractual negotiations with the .MOBI applicant on December 13, 2004.^[1]

On June 28, 2005, the ICANN Board approved the proposed agreement with DotMobi, Ltd. for the .mobi TLD. The Board resolution stated that the applicant had provided satisfactory details regarding the proposed community of content providers for mobile-phone users and had confirmed that the approach would not conflict with telephone numbering systems.^[3] ICANN and DotMobi signed the Registry Agreement on 11 July 2005.^[1] The IANA delegation record lists the registration date for .mobi as 17 October 2005.^[4]

Launch[edit | edit source]

The .mobi rollout began in 2006. Its launch schedule included a Limited Industry Launch from 22 May to May 29, 2006, a Sunrise Registration Period from June 12 to September 22, 2006, a Land Rush Registration period from September 26 to October 11, 2006, and General Registration beginning on October 11, 2006.^[5]

The World Intellectual Property Organization (WIPO) administered .mobi-specific Sunrise Challenge and Premium Name procedures during the launch period. Between September 2006 and March 2007, the WIPO Arbitration and Mediation Center processed 18 Sunrise challenges and 105 Premium Name applications related to .mobi.^[6]

dotMobi, Afilias, and Identity Digital[edit | edit source]

The company behind .mobi was originally associated with Mobi JV, the predecessor to dotMobi. Afilias stated in 2010 that it had worked with dotMobi since Mobi JV was started by Nokia, Vodafone, and Microsoft to apply for the .mobi TLD in 2004, and that Afilias provided registry services for the launch of .mobi in 2006.

dotMobi was described as having been founded by 14 mobile operators, network and device manufacturers, and Internet content providers: Ericsson, Google, GSM Association, Hutchison 3, Microsoft, Nokia, Orascom Telecom, Samsung Electronics, Syniverse, T-Mobile, Telefónica Móviles, Telecom Italia, Visa, and Vodafone.

In February 2010, Afilias acquired mTLD Top Level Domain Ltd., the sponsoring organization and registry operator for .mobi. Under the transaction, Afilias acquired all issued and outstanding capital stock of mTLD, and dotMobi continued as a wholly owned subsidiary of Afilias. .^[7]

In 2016, ICANN opened a public comment proceeding on the proposed renewal of the .MOBI Sponsored Registry Agreement. ICANN stated that the renewal proposal resulted from bilateral discussions between ICANN and Afilias Technologies Limited, the registry operator for .mobi at that time.^[8] The proposed renewal moved .mobi toward terms substantially similar to the Base New gTLD Registry Agreement. ICANN noted that Appendix S from the prior .mobi agreement would not be carried over as Specification 12 Community Registration Policies, and that .mobi would not be categorized as a Community TLD under the renewed agreement.^[8] The current .mobi Registry Agreement is dated 30 March 2017 and is listed by ICANN as a Base, Non-Sponsored agreement.^[2]

In June 2022, Donuts Inc. and Afilias Inc. rebranded under the single company name Identity Digital.^[9] IANA's current delegation record for .mobi lists Identity Digital Limited in the Sponsoring Organisation field.^[4]

Sponsorship and Policy Status[edit | edit source]

.mobi was originally approved as a sponsored TLD. The 2005 Registry Agreement designated mTLD Top Level Domain Ltd. as the sponsoring organization and sole registry operator, and delegated policy-development authority to the registry operator for the sponsored TLD, consistent with the agreement.^[10]

The original .mobi structure included advisory bodies associated with the sponsored-TLD model. Afilias' 2010 acquisition announcement referred to continued founder involvement in the .mobi Advisory Group (MAG) and the dotMobi Policy Advisory Board (PAB).^[7] However, ICANN's 2016 renewal materials stated that the renewed agreement would not carry over the prior Appendix S as community registration policies and that .mobi would not be categorized as a Community TLD.^[8]

Criticism[edit | edit source]

The creation of a TLD dedicated to mobile-oriented content was criticized by some web architecture advocates. Tim Berners-Lee opposed .mobi in a 2004 note titled "New Top Level Domains .mobi and .xxx Considered Harmful," arguing that .mobi would undermine the universality of the Web by partitioning web content according to access device.^[11]

The W3C Device Independence Working Group also opposed the proposal. It argued that device-specific domain names were inconsistent with device independence principles because they embedded access-context information in the identifier itself, rather than allowing the same resource identifier to support different device contexts through content negotiation, metadata, or adaptation technologies.^[12]

References[edit | edit source]

ICANNWiki resources: Special Pages | Content Guide | Documentation | Development || Maintenance: Articles needing attention | Candidates for deletion || Projects: Internet & Digital Governance Library