.chase

From ICANNWiki
Jump to: navigation, search
Status: Delegated
Registry Provider: Neustar
Registry: JPMorgan Chase & Co.
Registry Backend: Neustar
Type: Brand TLD
Priority #: 208 - JPMorgan Chase & Co.
nTLDStats
Registrations: 3
Parked Domains: 1
Parked Domain %: 33.33 %
Important Dates
Delegation: 28 February 2016
General Availability: N/A

More Information: NTLDStatsLogo.png

.chase is a Brand TLD delegated to the Root Zone in ICANN's New gTLD Program on 27 February 2016. The registry operator is JPMorgan Chase & Co.[1][2]

Application Details

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

"The Applicant is a leading global financial services firm operating in more than 60 countries. It is one of the oldest financial institutions in the United States. With a history dating back over 200 years, the Applicant is a leader in investment banking, financial services for consumers, small business and commercial banking, financial transaction processing, asset management, and private equity.

..

Following the delegation of the applied-for gTLD, the gTLD is likely going to be a so-called “single registrant TLD” as contemplated by ICANN in Article 4.5 of the template Registry Operator Agreement. For the avoidance of doubt, a “single registrant TLD” is a TLD where “(i) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for its own exclusive use, and (ii) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator.”

As a result, it is unlikely that there will be multiple applications for a particular domain name. There will also likely be no social costs for third parties, given the fact that they will be unable to register domain names in the applied-for gTLD.

If the Applicant determines, at its sole discretion, that it will allow certain categories of stakeholders to register domain names in the applied-for gTLD, the Applicant will devise policies to that effect. The Applicant reserves the right to subject the registration or use of a domain name to internal approval processes and procedures, at each and every step of the domain name life cycle.

If the Applicant allows certain categories of stakeholders to register domain names in the applied-for gTLD, it will release available domain names in a highly controlled manner. This also reduces the likelihood that two or more applicants qualify for the registration of the same domain name in the applied-for gTLD."[3]

References