.philips

Status:	Delegated
Registry Provider:	ARI Registry Services
Date Implemented:	09 May 2015
Type:	Brand TLD
Priority #:	1013 - Koninklijke Philips Electronics N.V.
More information:

.philips is a Brand TLD delegated in ICANN's New gTLD Program. Koninklijke Philips Electronics N.V. manages the TLD and is its Registry. The proposed application succeeded and was delegated to the Root Zone on 09 May, 2015.

Application Details

The following is excerpted from the applicant's response to question #18:

"i. PHILIPS is the Applicant’s most recognized brand, having international exposure. The Applicant is one of the world’s largest diversified companies. The Group has one of the largest international networks with a presence in more than 100 countries, and counts with more than 115,000 employees. The Applicant has key positions in its three core businesses: Healthcare, Lighting and Consumer Lifestyle. The Applicant’s Group is present in geographically diverse markets, and its operations are spread all over the world. The proposed gTLD aims at consolidating the reputation of the Applicant’s brand; ii. From the Applicant’s perspective, .PHILIPS will bring a high degree of recognition and specialization to the currently existing name space. Where in most cases the specific connotation that has been initially given to the gTLDs (or even ccTLDs) has disappeared, the .PHILIPS top-level domain will be unambiguous as regards the identity of the Registry Operator, the source of the content and services offered under the .PHILIPS and⁄or the affiliation between the Registry Operator and the TLD;"

Name Collision Issues

In October 2013 ICANN released their final assessment and mitigation plan for the Name Collision issue that was facing the New gTLD program. On 18 November 2013, ICANN announced the applied-for strings that were eligible for an alternative path towards delegation that would allow applicants to proceed without waiting for further mitigation research and plans to be published. 25 strings, including .philips, were not eligible for the alternative path, and will have to wait for more plans to be published before continuing towards delegation.

Top-Level Domain