As a courtesy, we will pre-screen your request to confirm you meet the eligibility and naming requirements for .BANK. Placing an order for a .BANK domain name does not guarantee it will be successfully registered to you. You will be required to complete the verification process (described below) directly with the registry.
.BANK DOMAIN ELIGIBILITY AND NAMING REQUIREMENTS
To become a .BANK Registrant, your organization must be one of the following government regulated entities:
- Retail bank
- Savings association
- National bank
- Bank holding or parent companies
Other eligible organizations include:
- Associations or groups of associations whose membership is primarily comprised of the above regulated entities
- Government regulators of retail banks, savings associations, national banks or organizations whose members are primarily comprised of such government regulators (if approved by the fTLD Board)
Domain Name Eligibility (Naming Requirements)
Domain names must correspond to the organization's legal name or branding (e.g., trademark, trade name, service mark). A registered trademark is not required to register a domain name.
Your domain submission will go through a detailed verification process to ensure that registrations are made only with organizations that meet the eligibility requirements. fTLD Registry performs verification upon the initial registration, annually thereafter, and if certain registration information changes (e.g., Registrant Organization, Registrant Name, Registrant Email). You may be required to submit certain information to fTLD Registry during the Verification process.
In accordance with our agreement with fTLD Registry Services, the Registry Operator, .BANK Registered Name Holder consents to the collection and use of Personal Data by the Registry Operator. In addition, the Registry Operator reserves the right to deny, cancel or transfer any Registered Name registration at their sole discretion. Registered Name Holder also agrees that in the event of any dispute concerning the time of the entry of a Registered Name registration into the Registry System, the timestamp shown in the Registry System records shall control. All applicable national, state or local law, regulation or court order in relation to its operations and registrations of the .BANK shall apply. In addition, the use of privacy or proxy registration services by the Registered Name Holder in registering or maintaining domain name registrations are not permitted. You will however be able to designate a role name such as "Domain Administrator" for use on public whois.
Additional information on eligibility, Registrant Obligations, naming requirements and verification process can be found on Registry Operator's website at www.ftld.com/policies.
In addition to the .BANK Policies, which are the foundation of a protected, trusted and more secure environment for .BANK domains, other documents are included to identify a variety of security and operational requirements, including: www.ftld.com/security/ and www.ftld.com/faq-dotbank.
Public Interest Commitments (PICs)
These commitments are mandated by ICANN and included as Specification 11 in fTLD's Registry Agreement. Public Interest Commitments (PICs) are reflected in 101domain Legal Agreements, the .BANK Policies or .BANK Security Requirements. Some PICs are included in .BANK Policies and in the Security Requirements.
fTLD Security Requirements
These Requirements are essential for fTLD to fulfill its mission for the .BANK domain. Some of the Requirements are drawn from the PICs and others from the Community Registration Policies included as Specification 12 to fTLD's Registry Agreement. The Requirements address issues such registrant verification and DNSSEC and identify the responsible party (i.e., Registry Operator, Registrar or Registrant) to ensure compliance. More information is available at Security Requirements which may be amended from time-to-time to meet the security and other needs of the global financial services community.
Registrant shall take all necessary action(s) as directed by Registrar or Registry Operator in relation to compliance actions, directives, or instructions from ICANN, and/or as otherwise directed by Registry Operator in its sole discretion as being reasonably necessary for the provision of Registry Services, and enforcing compliance with Registry Operator's Operational and Security Requirements and Operations Pledge, including monitoring for compliance regarding the Registered Name.
Verification
Verification, conducted by the registry operator, of registrants and their domains names will occur 1) annually, and 2) if certain registration information changes (e.g., Registrant Organization, Registrant Name, Registrant Email).
