Thu, Aug 21, 2025

.JPMORGAN New gTLD Application

Click to view Chinese translation articles.

-----------------------------------

New gTLD Application Submitted to ICANN by: JPMorgan Chase & Co.

String: JPMORGAN

Originally Posted: 13 June 2012

Application ID: 1-1190-27386

 

Applicant Information

 

  1. Full legal name

JPMorgan Chase & Co.

 

  1. Address of the principal place of business

270 Park Avenue

New York New York 10017

US

 

  1. Phone number

+1 212 270 6000

 

  1. Fax number

+1 302 282 1660

 

  1. If applicable, website or URL

http:⁄⁄www.jpmorganchase.com

 

Primary Contact

 

6(a). Name

Mr. Winston Troy Fuhriman

 

6(b). Title

Manager, Domain Services

 

6(c). Address

 

6(d). Phone Number

+1 208 389 5740

 

6(e). Fax Number

+1 208 389 5799

 

6(f). Email Address

This email address is being protected from spambots. You need JavaScript enabled to view it.

 

Secondary Contact

 

7(a). Name

Ms. Maryann M. Sharkey

 

7(b). Title

Vice President – Risk Management Manager

 

7(c). Address

 

7(d). Phone Number

+1 302 282 1773

 

7(e). Fax Number

+1 302 282 1660

 

7(f). Email Address

This email address is being protected from spambots. You need JavaScript enabled to view it.

 

Proof of Legal Establishment

 

8(a). Legal form of the Applicant

Corporation

 

8(b). State the specific national or other jursidiction that defines the type of entity identified in 8(a).

United States (incorporated in Delaware)

 

8(c). Attach evidence of the applicant's establishment.

Attachments are not displayed on this form.

 

9(a). If applying company is publicly traded, provide the exchange and symbol.

New_York_Stock_Exchange;JPMPRI

 

9(b). If the applying entity is a subsidiary, provide the parent company.

N⁄A

 

9(c). If the applying entity is a joint venture, list all joint venture partners.

N⁄A

 

Applicant Background

 

11(a). Name(s) and position(s) of all directors

Crandall C. Bowles Director

David C. Novak Director

David M. Cote Director

Ellen V. Futter Director

James A. Bell Director

James Dimon Chairman of the Board, Chief Executive Officer and President

James S. Crown Director

Laban P. Jackson, Jr. Director

Lee R. Raymond Director

Stephen B. Burke Director

William C. Weldon Director

William H. Gray, III Director

 

11(b). Name(s) and position(s) of all officers and partners

Barry L. Zubrow Head of Corporate and Regulatory Affairs

Douglas B. Petno Chief Executive Officer of Commercial Banking

Douglas L. Braunstein Chief Financial Officer

Frank J. Bisignano Chief Administrative Officer and Chief Executive Officer of Mortgage Banking

Gordon A. Smith Chief Executive Officer of Card Services

Ina R. Drew Chief Investment Officer

James Dimon Chairman of the Board, Chief Executive Officer and President

James E. Staley Chief Executive Officer of the Investment Bank

John J. Hogan Chief Risk Officer

John L. Donnelly Head of Human Resources

Mary Callahan  Erdoes Chief Executive Officer of Asset Management

Michael J. Cavanagh Chief Executive Officer of Treasury  & Securities Services

Samuel Todd Maclin Chief Executive Officer of Consumer and Business Banking

Stephen M. Cutler General Counsel

 

11(c). Name(s) and position(s) of all shareholders holding at least 15% of shares

 

11(d). For an applying entity that does not have directors, officers, partners, or shareholders: Name(s) and position(s) of all individuals having legal or executive responsibility

 

Applied-for gTLD string

 

  1. Provide the applied-for gTLD string. If an IDN, provide the U-label.

JPMORGAN

 

14(a). If an IDN, provide the A-label (beginning with "xn--").

 

14(b). If an IDN, provide the meaning or restatement of the string in English, that is, a description of the literal meaning of the string in the opinion of the applicant.

 

14(c). If an IDN, provide the language of the label (in English).

 

14(c). If an IDN, provide the language of the label (as referenced by ISO-639-1).

 

14(d). If an IDN, provide the script of the label (in English).

 

14(d). If an IDN, provide the script of the label (as referenced by ISO 15924).

 

14(e). If an IDN, list all code points contained in the U-label according to Unicode form.

 

15(a). If an IDN, Attach IDN Tables for the proposed registry.

Attachments are not displayed on this form.

 

15(b). Describe the process used for development of the IDN tables submitted, including consultations and sources used.

 

15(c). List any variant strings to the applied-for gTLD string according to the relevant IDN tables.

 

  1. Describe the applicant's efforts to ensure that there are no known operational or rendering problems concerning the applied-for gTLD string. If such issues are known, describe steps that will be taken to mitigate these issues in software and other applications.

To the Applicant’s knowledge, there are no operational or rendering problems concerning the applied-for gTLD string.

 

  1. (OPTIONAL) Provide a representation of the label according to the International Phonetic Alphabet (http://www.langsci.ucl.ac.uk/ipa/).

 

Mission/Purpose

 

18(a). Describe the mission/purpose of your proposed gTLD.

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.

 

Over its history, the Applicant has invested significant resources to develop and protect its JPMORGAN brand and achieve brand recognition.  For example, the Applicant holds more than 80 trademark registrations in over 60 jurisdictions around the world for the mark JPMORGAN.  The Applicant also holds many trademark registrations for services that are offered by Applicant under the JPMORGAN brand, including JPMorgan Access, JPMorgan Treasury Online, and JPMorgan E-Tax.  Additionally, the Applicant holds various domain names that include the mark JPMORGAN or some variation thereof, including jpmorgan.com and jpmorganchase.com.  The Applicant actively uses many of these domain names such as jpmorgan.com to provide services and information to its clients.  The Applicant has registered domains for many of its trademarks and also has registered domains separate from its trademarks.  Indeed, the Applicant has made significant investments to develop and protect its brand and achieve brand recognition.  In late 2011

and in the first quarter of 2012, the Applicant promoted the JPMorgan brand through television, print and digital media.

 

Against this background, the mission and purpose of the applied-for gTLD are manifold:

 

  1. securing and protecting the Applicant’s brand as a gTLD;

 

  1. reflecting and operating the Applicant’s brand at the top level of the DNS’ hierarchy;

 

  1. providing stakeholders of the Applicant (e.g., millions of consumers; small businesses; corporate, institutional and government clients; more than 240,000 employees; wholly-owned direct and indirect subsidiaries; business groups) with a recognizable and trusted identifier on the Internet; and

 

  1. providing such stakeholders with a secure and safe Internet environment, mainly or even fully under the control of the Applicant, which increases brand awareness and stakeholder trust, both of which are important within the financial services industry.

 

18(b). How do you expect that your proposed gTLD will benefit registrants, Internet users, and others?

  1. The applied-for gTLD is a recognized brand of the Applicant.  The applied-for gTLD aims to protect, develop, and maintain the reputation of the Applicant’s brand in the financial services industry.

 

  1. From the Applicant’s perspective, the applied-for gTLD 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 applied-for top-level domain is currently intended to be unambiguous as regards: the identity of the Registry Operator; the source of the content and services offered under the applied-for gTLD; the affiliation between the Registry Operator and the gTLD; and the affiliation between the Registry Operator and any third party that is authorized by the Applicant at its discretion to register and⁄or use one or more domain names in the applied-for gTLD.

 

  1. As mentioned in 18(a), key reasons why Applicant seeks delegation of the applied-for gTLD include, but are not limited to:

 

  1. Securing and protecting the Applicant’s brand as a gTLD.  The Applicant seeks to protect its brand from third parties, who may wish to trade on the good name of the Applicant’s brand by securing the applied-for gTLD.  The Applicant also seeks to avoid any confusion that may result from another entity holding the applied-for gTLD.  This is particularly beneficial for users.  Securing the applied-for gTLD is a logical extension of the Applicant’s continued investment in protecting and promoting its brand both offline and online.

 

  1. Reflecting and operating the Applicant’s brand at the top-level of the DNS’ hierarchy.  The ease with which users will be able to locate the Applicant’s brand at the top-level of the DNS’ hierarchy is also beneficial to users.

 

  1. Trust, safety and security for users.  The gTLD and most if not all of the domain names registered therein will be completely or at least partially under the control of the Registry Operator.

 

  1. The Applicant intends to implement the following policies and procedures with respect to the registration of domain names in the applied-for top-level domain:

 

  1. Reservation and registration of domain names in the name of the Applicant.   It is likely that this will be the scenario that the Applicant will put in place during the first months or even years of operation of the applied-for gTLD.  The names may include, but are not limited to:

 

  1. a) descriptive names, referring to the actual day-to-day business activities of the Applicant and⁄or its subsidiaries;
  2. b) descriptive names, referring to the internal departments of the Applicant;
  3. c) descriptive names, referring to the subsidiaries of the Applicant; and
  4. d) product and service brands promoted by the Applicant and⁄or its subsidiaries now and in the future.

 

  1. Launch of the gTLD.  If and when implemented by the Registry Operator, this is likely going to be a gradual process, whereby selected third parties that meet certain criteria, which the Applicant will be entitled to set at its own discretion, may register domain names in the gTLD.  These processes may include the following.  

 

  1. a) Sunrise: allow physical persons, organizations and entities that meet the eligibility requirements in force at that point in time to choose the domain names that are identical to their trademarks.
  2. b) Land rush and general availability: other available domain names may be registered by physical persons, organizations and entities that meet the eligibility requirements in force at that point in time to choose the domain names in accordance with the applicable terms and conditions.
  3. c) Depending on the terms and conditions in force at the time of launch of the gTLD, these domain names may or may not be registered in the name of the applicant for the domain name or in the name of the Registry Operator of the gTLD (i.e., the Applicant). In any case, the Applicant reserves the right to impose additional and other restrictions from time to time at its sole discretion.

 

  1. Given the fact that the Applicant is a company that operates in more than 60 countries including the United States, it is subject to both federal and state, privacy and data protection laws and privacy and data protection laws, rules and⁄or practices in other jurisdictions.  The Applicant will at all times be obliged to carefully consider and, where applicable, implement privacy, data protection and confidentiality measures during operation of the applied-for gTLD.

 

  1. At this stage, the Applicant has not developed concrete and tangible plans in order to establish online activities on the applied-for gTLD or move online activities from one or more of its active domain names to the applied-for gTLD.  However, the Applicant could implement different initiatives to make stakeholders aware of the development of a new online environment under the applied-for gTLD, including but not limited to:

 

  1. advertisements in newspapers and magazines;
  2. Internet advertising campaigns;
  3. resolving Internet traffic to one or more of the Applicant’s active domain names into domain names registered in the applied-for gTLD; and
  4. email marketing campaigns.

 

18(c). What operating rules will you adopt to eliminate or minimize social costs?

  1. In line with the Applicant’s mission and purpose for the applied-for gTLD, it is important for the Applicant to safeguard and protect its brand at the top level of the DNS’ hierarchy. Such protection does not only extend to the actual registration, delegation and use of the gTLD, but also to the domain names that are registered therein, and how these domain names are used.

Considering the fact that the actual award and delegation of the applied-for gTLD to the Applicant is subject to the successful evaluation of the application, we have not yet defined in detail: the types of domain names that will be registered; who will be entitled to select which domain names will be registered; who will be entitled to register such domain names; who will be entitled to use such domain names; and which types of use will be allowed or recommended.  As the Applicant believes the development and implementation of one or more business cases could likely take months or even years, the Applicant has only focused on high-level plans in relation to the operation of the applied-for gTLD.

 

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.

 

As a method of last resort, and subject to the actual domain name registration policy adopted by the Registry Operator and in force at the time of registration, domain names will be allocated on a first-come, first-served basis.

 

In any event, the Applicant reserves the right to change or restrict any policies, procedures and practices at any point in time if it is of the opinion that there would be a risk of damage to the reputation of the Applicant’s brand.

 

  1. The Applicant ⁄ Registry Operator intends to make the applied-for gTLD available to qualifying domain name registrants at no cost to them. The Applicant ⁄ Registry Operator may, at its discretion charge a fee for the registration of domain names under the applied-for gTLD.

 

  1. The Applicant ⁄ Registry Operator may at its discretion make contractual commitments to increase or decrease the fees for the registration of domain names under the applied-for gTLD.