FAQ
fTLD on Twitter

Top 10 QuestionsExpand Top 10

Why .BANK?

As a verified domain, exclusively for the banking community, .BANK is a more secure space for online banking and communication. A web or email address ending in .BANK quickly and easily confirms for customers and employees that they are communicating and transacting with your bank, and not a phisher or a spoofed site.  A .BANK domain is a visual cue anyone can look for and recognize, an online stamp of trust that will give your customers confidence in your online banking platform, and help protect your bank from bad actors collecting data for breaches, financial fraud and identity theft.

Can I redirect my current domain name to my .BANK domain name?

Yes, you can redirect traffic and emails from your .com (or other gTLDs) to your .BANK domain names, enabling you to retain traffic and communication while you educate your customers about your move to a more secure domain. While there are many ways to redirect visitors to a .BANK domain name, an effective method to do this while maintaining your search engine ranking is by using the http ‘301 Moved Permanently’ response status code. Your .BANK domain name must meet the HTTPS requirement by having a public key certificate installed to secure the domain name.

Is there a way I can check to see if my .BANK domain name is in compliance with the Security Requirements?

fTLD has compiled a list of publicly available, free resources that can be helpful in understanding whether the implementation of a .BANK domain name addresses the defined requirements and it’s available here. Although these resources are useful, they are not exact checks against the Requirements so you may still receive compliance notices even if these resources do not identify any issues. fTLD will work with you and your registrar to address compliance issues.

How do we implement the .BANK Security Requirements to move to our .BANK domain?

fTLD has developed an Implementation Hub to provide all of the necessary information, guides, resources and tools for implementing, testing, requesting assistance with and reporting on each of our Security Requirements. We also have guides for eligibility and planning & communications that many .BANK registrants have found helpful in making the move to .BANK.

What makes a .BANK domain name more secure?

fTLD requires compliance with a set of Registrant Security Requirements that are not mandated by the operators of other commercially available gTLDs. Additionally, the fTLD Operations Pledge outlines the policies and procedures we and our registrars must follow to ensure the secure, stable and reliable operations of the .BANK domain.

How does the .BANK verification process work?

fTLD has contracted with Symantec to ensure that registrations are made only to organizations that meet the eligibility requirements. Symantec performs verification upon the initial registration of a.BANK domain, and at each renewal or every two years, whichever comes first. An overview of the Symantec verification process is available here.

Where can I register my .BANK domain name?

Domain names must be registered with an fTLD Approved Registrar for .BANK. fTLD Approved Registrars for .BANK are listed here and are added on a rolling basis as they are approved.

How do I check on the availability of a domain name?

To determine if a domain name is available for registration, use the “Select My .BANK Domain” feature here.

What information is required to register a .BANK domain name?

Registrants must provide the following information:

  • Legal Name of the Eligible Registrant (the organization name)
  • Registrant Contact Name
  • Registrant Contact Address (Street, City, State/Province/Region, Postal Code)
  • Registrant Contact Email Address
  • Registrant Contact Telephone Number
  • Government Regulatory Authority (if applicable)
  • Regulatory ID Number (if applicable)

Note: The Registrant Contact must be a full-time employee of the Registrant Organization and cannot be a contract employee.

Registrars may request additional information such as a human resources contact name and telephone number who can verify the employment information of the Registrant Contact and a contact name and telephone number for another employee (e.g., manager of the Registrant Contact)  who can verify that the Registrant Contact is authorized to register the domain names requested. The additional contact information is required and must be provided to your registrar. It will expedite the verification process for your domain names as will providing the Government Regulatory Authority and Regulatory ID Number when applicable.

Who is eligible for a .BANK domain name?

Only verified members of the global banking community are eligible to register domain names. For banks and savings associations it includes charter and supervision verification with the organization’s regulator. Please see the .BANK Registrant Eligibility Policy for complete eligibility requirements.

Eligibility

Who is eligible for a .BANK domain name?

Only verified members of the global banking community are eligible to register domain names. For banks and savings associations it includes charter and supervision verification with the organization’s regulator. Please see the .BANK Registrant Eligibility Policy for complete eligibility requirements.

Are bank holding or parent companies eligible to register a .BANK domain name?

Bank holding or parent companies that are supervised by a relevant government authority are hereby considered service providers as they have been pre-approved by fTLD’s Board of Directors. Further details are provided in the Registrant Eligibility Policy’s Implementation Guidelines (page 4).

Are credit unions/associations eligible to register for a .BANK domain name?

Credit unions/associations in the United States do not meet the eligibility requirements for .BANK and may be interested in .CREDITUNION, which is operated by the Credit Union National Association (CUNA). As .BANK serves the global banking community and must respect the regulatory policy in all jurisdictions where it is authorized to operate, including those where credit unions are legally identified as banks, it is possible credit unions/associations located outside of the United States are eligible to register a .BANK domain name.

Are banks with “Trust” or “Thrift” or “Cooperative” in their name eligible for a .BANK domain name?

Having the word “Trust” or “Thrift” or “Cooperative” in the registrant organization name of a financial institution is not the deciding factor in determining eligibility. It is determined by whether the organization is a bank that is chartered and supervised by a government regulatory authority or other eligibility category as defined in the Registrant Eligibility Policy.

Registering A Domain Name

Where can I register my .BANK domain name?

Domain names must be registered with an fTLD Approved Registrar for .BANK. fTLD Approved Registrars for .BANK are listed here and are added on a rolling basis as they are approved.

Why isn’t my current registrar on the list of fTLD approved registrars?

All ICANN-accredited registrars have the option to offer .BANK domain names. fTLD requires its registrars to comply with specific operational and security requirements that contribute to .BANK being a trusted, verified and more secure environment for domain name owners and their customers. As such, some registrars may elect not to support the registration of .BANK domain names. It may also be that your registrar hasn’t yet determined whether or not they will support .BANK. As new registrars decide to support .BANK, fTLD will update the list at Approved Registrars. Check with your registrar to see if they are in the process of adding .BANK registrations.

Since we already have a .COM address, are we automatically entitled to register the same domain name in .BANK?

No, domain names are initially awarded on a first-come, first-served basis; there is no preference given to those that currently have a specific name in another TLD. Given .BANK is available to eligible members of the global banking community, there could be an organization with a domain name similar to yours that currently uses another TLD, such as .NET, .CO, .UK, .FR, or .JP and this is one example why there is no preference for a domain name registered in an existing gTLD.

Is having a registered trademark a requirement to register a .BANK domain name?

No, this is not necessary. Your organization may, for example, have a common law right arising from the actual use of a trademark and this is sufficient for registering a domain name. If Symantec is unable to verify your right to register a .BANK domain name they will contact you and request proof-of-use of the mark. fTLD makes the final decision on whether a domain name meets the .BANK Name Selection Policy.

Can my company have a third-party provider or core processor register domain names on our behalf?

Yes, this is permissible. However, the registrant contact information provided in the registration process must be for the entity qualified to make the registration for fTLD and/or its verification agent to conduct a successful verification. If the third-party provider or core processor includes its name and contact information for a registration it is making on behalf of an eligible registrant, the verification will fail.

Is there any limit on the number of domain names I can register?

No, you may register as many domain names as you like.

Can I register any domain name I want if I am an eligible registrant?

You can register any domain name that corresponds to your company’s trademarks, trade names or service marks, provided it is not an fTLD or ICANN reserved name. For guidance on selecting domain names, please see the .BANK Name Selection Policy and/or contact fTLD@fTLD.com.

What if I want to register a domain name in .BANK associated with the geographic community (e.g., city, county, region, state) or area (e.g., New England, southern, midwest) my organization serves?

The domain name must correspond to your trademark, trade name or service mark as described in the Name Selection Policy. If the legal name of your organization does not include the geographic identifying domain name being sought, fTLD may require documentation to verify your organization’s right(s) to the generic geographic domain name to protect the interests of the global banking community who may have one or more members with a legitimate right(s) to the domain name being sought.

What if I want to register a name fTLD has reserved in .BANK?

fTLD is permitted by ICANN to reserve names, which it may use for itself, allocate to another entity, allocate in the future per the mechanisms enumerated in its Name Allocation Policy (i.e., first-come, first-served, auction, request for proposal or self-allocation) or keep permanently unavailable for registration. fTLD has reserved names comprised of Common Community and Generic names, which are available on its Reserved Names list. General information about Reserved Names and associated lists are available here.

If you believe your organization is eligible to register a name on the list (i.e., you believe a name on fTLD’s Reserved Names list corresponds to your trademark, trade name or service mark), please see fTLD’s Reserved Names Challenge Policy here, and complete the Reserved Names Complaint Form and submit it by email to complaint@fTLD.com.

The outcome of a successful challenge to a name on fTLD’s Reserved Names list is the removal of the name from the respective Reserved Names list. A successful challenge does not result in the requestor being awarded the name, but rather gives them an opportunity to compete to receive it. fTLD will allocate the name via one or more of the allocation mechanisms listed in the Name Allocation Policy. A Reserved Name allocation will not take place until all fTLD Approved Registrars have been provided notification of the change in the respective Reserved Names list.

Are there any premium domain names in .BANK?

Yes, all single-character names (e.g. 1.BANK), certain two-letter names (e.g., AB.BANK), and names fTLD has reserved for its potential use, indicated in bold on the list of Generic names, are identified as premium and subject to premium pricing. To determine if a domain name is available for registration, use the “Select My .BANK Domain” feature here.

Verification

How does the .BANK verification process work?

fTLD has contracted with Symantec to ensure that registrations are made only to organizations that meet the eligibility requirements. Symantec performs verification upon the initial registration of a.BANK domain, and at each renewal or every two years, whichever comes first. An overview of the Symantec verification process is available here.

Who is Symantec and why are they involved in the verification process? I thought verification was being handled by fTLD?

Symantec is a global leader in security and verifying the authenticity of organizations. The use of a third-party in the verification process ensures an impartial and expert entity for the examination of eligibility for registration of each registrant and provides registrants with global support in this important process.

fTLD is responsible for approving requests for domain names in .BANK. fTLD has contracted with Symantec to serve as its Registry Verification Agent. Symantec is responsible for reviewing the information provided by the registrar/registrant and providing a recommendation to fTLD. fTLD makes the final decision to approve or deny a request.

Is the .BANK verification by Symantec the same as the annual Whois verification required by ICANN?

No, the verification process facilitated by Symantec is the process that fTLD has mandated for all .BANK registrations.

In contrast, the Whois verification process is required by ICANN to be conducted annually by registrars and the purpose is to confirm accurate contact information. Registrars are required to contact their registrants to conduct this verification and a positive confirmation of details is required. Registrants may risk having their domain name suspended or cancelled for failure to respond to this verification request.

Registrants should respond promptly to all requests related to verification from fTLD, Symantec and their registrar, and failing to respond could result in rejection of your registration or inactivation of your domain name. If you want to confirm whether the request is legitimate, contact the requesting verification entity.

How long does the domain name registration and verification take?

Verification is initiated after the request has been accepted by fTLD and approval is generally expected to conclude within five days or less of the request. However, because the verification process requires telephone contact with the registrant’s organization to verify certain information (i.e., the requestor is a full-time employee of the company and it authorized to make registrations on their behalf), the verification may take longer to complete. Registrants can expedite verification by ensuring that all individuals that may be contacted are aware of the need to respond to these requests as quickly as possible.

My country does not have a specific license or charter document that is provided to us as a separate document. If this is requested by Symantec, what should we send?

Symantec understands that different countries have different regulations regarding bank certification and will accept other materials applicable to your specific locale.

What information is checked during the verification process?
  1. Security Check – To support compliance with applicable local and international laws, every application will undergo a security check to ensure that Symantec does not approve any organizations or persons found on any government and/or Symantec-maintained restricted lists/black lists or lists provided by fTLD.
  2. Organization, Jurisdiction, and Banking Credentials Verification – Symantec will verify that the registrant is a registered and active organization in a jurisdiction appropriate to its business location and has valid credentials to meet the requirements of the .BANK Registrant Eligibility Policy.
  3. Verification of Domain Name Selection – Symantec will verify that the applied-for domain name meets the requirements of the .BANK Name Selection Policy.
  4. Verification of Physical Address – Symantec will verify the address listed in the application as a valid address for the registrant organization using Symantec approved databases.
  5. Verification of Telephone Number – Symantec will verify the registrant organization’s telephone number using Symantec approved databases.
  6. Registrant Contact Employment – Symantec will initiate telephony contact to verify with registrant organization’s human resources (or appropriate department) that the registrant organization’s contact person is a full-time/non-contracting employee of the organization.
  7. Registrant Contact Authority – Symantec will initiate telephony contact to identify the Registrant Contact’s manager within the registrant organization with Human Resources (or appropriate department) and contact this person to confirm that the registrant contact is authorized to request domain names on behalf of the organization.
I have been notified that my domain name is pending verification from Symantec. What should I do?

Symantec is the Registry Verification Agent for the .BANK domain name. Symantec uses information provided by you to your registrar during registration to confirm your eligibility for a domain name. Symantec will contact you via email or telephone if specific additional information is needed. It is important that you respond to their request(s) promptly as your domain name will not be registered until the verification process and approval by fTLD are complete. In cases where Symantec has been unable to complete the verification, fTLD may also request information from the registrar and/or registrant. Repeated failures to respond to Symantec and/or fTLD requests for additional information in a timely manner may result in a failed verification and rejection of the requested domain name. Information about how to contact Symantec is provided on emails that you receive from them or can be located at www.symantec.com/support. You can always contact fTLD at fTLD@fTLD.com or by using the information on the emails that we send. If you have questions about the status of your registration, please contact your registrar.

Is the Registrant Contact in WHOIS allowed to be a role-based designation instead of a natural person?

In line with ICANN policy, fTLD allows role-based designations for the Registrant Contact Name and role email accounts for the Registrant Email. However, a specific individual’s name must be provided to the registrar to be submitted to Symantec for the verification and re-verification processes. This individual must be a full-time employee and authorized to register domains for the registrant organization. Please check with your registrar if you need to use a role-based designation.

Will a re-verification be necessary when my original registration expires and I renew the domain name?

Yes, when you renew your domain name it will be re-verified. Part of the Security Requirements for .BANK is to periodically reconfirm that each registration continues to have accurate registration information. fTLD checks each time a domain name is renewed that registration information is still accurate and that the registrant is still eligible for its .BANK domain name. A complete re-verification will be done at least every two years, including contacting the registrant organization to confirm the contact’s eligibility as a contact and their authority to register domain names.

Note too that if you register your domain name for a period longer than two years, fTLD requires that all domain names be re-verified every two years. This periodic reconfirmation is to assure that each registration continues to have accurate registration information. It is possible that registration data and/or eligibility may change over time. In the case of registration terms beyond two years, it’s important that fTLD ensures the registration continues to comply with .BANK eligibility requirements. A complete re-verification will be done, including contacting the registrant organization to confirm the contact’s eligibility and their authority to register domain names for your organization.

Security

What makes a .BANK domain name more secure?

fTLD requires compliance with a set of Registrant Security Requirements that are not mandated by the operators of other commercially available gTLDs. Additionally, the fTLD Operations Pledge outlines the policies and procedures we and our registrars must follow to ensure the secure, stable and reliable operations of the .BANK domain.

What are the Security Requirements in .BANK?

fTLD requires compliance with a set of Security Requirements that are not currently mandated by the operators of other commercially available gTLDs. Registrars are required to implement security measures that are outlined in the fTLD Operations Pledge.

How do we implement the .BANK Security Requirements to move to our .BANK domain?

fTLD has developed an Implementation Hub to provide all of the necessary information, resources and tools for implementing, testing, requesting assistance with and reporting on each of the Security Requirements. We also have guides for eligibility and planning & communications that many .BANK registrants have found helpful in making the move to .BANK.

Can Security Requirements change? If so, how are these changes made and how will registrars and registrars know about them?

Yes, Security Requirements can change. The Security Requirements specify that fTLD will periodically review and amend the requirements to respond to changing needs in security or the community. The amendment process includes a review by fTLD’s Security Requirements Working Group (SRWG) and consideration and approval of its recommendations by fTLD’s Board of Directors. Any approved changes to the requirements will be communicated directly to registrars and broadly announced to stakeholders via information posted to fTLD’s websites as well as other means for sharing such details. Adequate notification to stakeholders and time for implementation is provided when changes are required to processes and technical infrastructure by new or modified requirements. Please contact fTLD at fTLD@fTLD.com if you would like to participate in future efforts of the Security Requirements Working Group.

Who is responsible for enforcing the Security Requirements and Policies in .BANK?

fTLD is ultimately responsible for enforcing all of the requirements and policies in .BANK. Registrars will also play a role in enforcement as they have the direct relationship with the registrant. fTLD always retains the right to take action if the registrar fails to do so.

Is there a way I can check to see if my .BANK domain name is in compliance with the Security Requirements?

fTLD has compiled a list of publicly available, free resources that can be helpful in understanding whether the implementation of a .BANK domain name addresses the defined requirements and it’s available here. Although these resources are useful, they are not exact checks against the Requirements so you may still receive compliance notices even if these resources do not identify any issues. Registrants may email fTLD at compliance@fTLD.com to check the compliance status of a particular domain. fTLD will work with you and your registrar to address compliance issues.

Can my organization host a .BANK website without encryption?

No, .BANK is an HTTPS-only community to support privacy and integrity of web and other services by default.  As .BANK is on the HSTS preload list, websites that are not HTTPS compliant will not be accessible via browsers (like Chrome). As a global HSTS security policy becomes increasingly common, additional browsers are expected to block sites that are not HTTPS compliant.

What is a Proxy/Privacy Registration Service and why is it prohibited?

Proxy/Privacy Registration Services are used to conceal the true identity of the domain name owner and their contact information. fTLD does not support this practice as it makes it difficult to identify and contact a registrant that is alleged to be using their domain name for practices that are in violation of fTLD’s Acceptable Use / Anti-Abuse Policy.

Is it a problem if I use another TLD email address in the “rua” and/or “ruf” tag in my Domain-based Message Authentication, Reporting & Conformance (DMARC) record?

If you use a non-.BANK email address for that information, you may not receive the DMARC reports associated with your .BANK DMARC record unless you have configured an external reporting authorization record in the target domain name.  See the following for more information:  https://dmarc.org/wiki/FAQ#I_published_a_DMARC_record_with_reports_going_to_….

What happens if my activated .BANK domain name is not in compliance with fTLD’s Policies or Requirements?

fTLD is monitoring all domain names for compliance with the Policies and Requirements. fTLD will notify registrars/registrants of domain names that are not in compliance and failure of the registrar/registrant to provide a timely response and a remediation plan to fTLD can result in the domain name being removed from the .BANK zone or more significant actions.

Implementation

How does my organization implement the Security Requirements to move to our .BANK domain?

fTLD has developed an Implementation Hub to provide all of the necessary information, resources and tools for implementing, testing, requesting assistance and reporting on each of the requirements. We also have guides for eligibility and planning & communications that many .BANK registrants have found helpful in making the move to .BANK.

Once I register our .BANK domain name, what do I do with my .com (or other gTLD) domain?

You can continue using your current domain name (e.g., .com), and once you have your .BANK domain in place you can redirect your traffic and emails to your new .BANK site and email address. Maintaining your original domain and redirecting to your .BANK domain will allow you to retain all customer traffic and communication while educating them about your move to a more secure domain.

Can I redirect my current domain name to my .BANK domain name?

Yes, domain name registrants may redirect visitors from other gTLDs to .BANK domain names. While there are many ways to redirect visitors to a .BANK domain name, an effective method to do this while maintaining your search engine ranking is by using the http ‘301 Moved Permanently’ response status code.

Can I redirect my .BANK domain name to my current domain name (e.g., .com)?

Yes, provided your .BANK domain name meets the HTTPS requirement you may redirect to your current domain. Organizations that redirect from .BANK to non-.BANK domain names are strongly encouraged to inform visitors of this action via an explicit message to avoid confusion and to assure that visitors understand they are leaving a .BANK domain name. Registrants are reminded that .BANK is an HTTPS-only community and therefore any redirection must be made from the HTTPS version of the .BANK website.

What is the reason there are use restrictions imposed on my .BANK domain name?

As noted in fTLD’s Acceptable Use / Anti-Abuse Policy and the Implementation Guidelines annexed to the .BANK Registrant Eligibility Policy, fTLD may impose additional use restrictions, at any time, on a registrant’s use of a domain name to protect the integrity of the .BANK gTLD and the community that it serves. fTLD will communicate any use restrictions on a .BANK domain name to the registrant before approving the initial registration request or at any time during the term of the registration of the .BANK domain name, which must be accepted and complied with in order to maintain the registration. For example, associations may receive a use restriction that they may only use their .BANK domain name to support members who are regulated entities (i.e., banks and savings associations) and email communications to any of its members.

Can I provide access to third-party content on my .BANK domain name?

Yes, this activity is permitted.

Costs

What does a .BANK domain name cost to register and why is it more expensive than my current domain name?

fTLD charges the same base price to Registrars for all .BANK domains, which cover operating expenses such as the verification (and re-verification) process to ensure registrations are only made to qualified entities, and implementation and monitoring of Security Requirements for .BANK. In addition, Registrars may include services and/or have operational expenses included in the final retail price of your .BANK domain name.

Is there difference in the cost between standard and premium domain names?

Yes, there is a difference in cost and registrants should consult with their registrar for this information.

Are there other costs associated with using my .BANK domain name?

There will be other costs to your organization associated with the implementation of the Security Requirements. For example, complying with the DNSSEC, TLS, and name server requirements may require additional support and/or services from your registrar, core processor, hosting provider, DNS provider, etc. As you consider which registrar to use, you should ask about their ability to support the requirements and the cost. You should also consider consulting with existing service providers as they may be helpful to you.

General Information

Who is eligible for a .BANK domain name?

Only verified members of the global banking community are eligible to register domain names. For banks and savings associations it includes charter and supervision verification with the organization’s regulator. Please see the .BANK Registrant Eligibility Policy for complete eligibility requirements.

What information is required to register a .BANK domain name?

Registrants must provide the following information:

  • Legal Name of the Eligible Registrant (the organization name)
  • Registrant Contact Name
  • Registrant Contact Address (Street, City, State/Province/Region, Postal Code)
  • Registrant Contact Email Address
  • Registrant Contact Telephone Number
  • Government Regulatory Authority (if applicable)
  • Regulatory ID Number (if applicable)

Note: The Registrant Contact must be a full-time employee of the Registrant Organization and cannot be a contract employee.

Registrars may request additional information such as a human resources contact name and telephone number who can verify the employment information of the Registrant Contact and a contact name and telephone number for another employee (e.g., manager of the Registrant Contact)  who can verify that the Registrant Contact is authorized to register the domain names requested. The additional contact information is required and must be provided to your registrar. It will expedite the verification process for your domain names as will providing the Government Regulatory Authority and Regulatory ID Number when applicable.

How do I check on the availability of a domain name?

To determine if a domain name is available for registration, use the “Select My .BANK Domain” feature here.

Where can I register my .BANK domain name?

Domain names must be registered with an fTLD Approved Registrar for .BANK. fTLD Approved Registrars for .BANK are listed here and are added on a rolling basis as they are approved.

How does the .BANK verification process work?

fTLD has contracted with Symantec to ensure that registrations are made only to organizations that meet the eligibility requirements. Symantec performs verification upon the initial registration of a.BANK domain, and at each renewal or every two years, whichever comes first. An overview of the Symantec verification process is available here.

What makes a .BANK domain name more secure?

fTLD requires compliance with a set of Registrant Security Requirements that are not mandated by the operators of other commercially available gTLDs. Additionally, the fTLD Operations Pledge outlines the policies and procedures we and our registrars must follow to ensure the secure, stable and reliable operations of the .BANK domain.

How do we implement the .BANK Security Requirements to move to our .BANK domain?

fTLD has developed an Implementation Hub to provide all of the necessary information, guides, resources and tools for implementing, testing, requesting assistance with and reporting on each of our Security Requirements. We also have guides for eligibility and planning & communications that many .BANK registrants have found helpful in making the move to .BANK.

Is there a way I can check to see if my .BANK domain name is in compliance with the Security Requirements?

fTLD has compiled a list of publicly available, free resources that can be helpful in understanding whether the implementation of a .BANK domain name addresses the defined requirements and it’s available here. Although these resources are useful, they are not exact checks against the Requirements so you may still receive compliance notices even if these resources do not identify any issues. fTLD will work with you and your registrar to address compliance issues.

Can I redirect my current domain name to my .BANK domain name?

Yes, you can redirect traffic and emails from your .com (or other gTLDs) to your .BANK domain names, enabling you to retain traffic and communication while you educate your customers about your move to a more secure domain. While there are many ways to redirect visitors to a .BANK domain name, an effective method to do this while maintaining your search engine ranking is by using the http ‘301 Moved Permanently’ response status code. Your .BANK domain name must meet the HTTPS requirement by having a public key certificate installed to secure the domain name.

What is gTLD?

gTLD – or generic Top-Level Domain – refers to the letters to the right of the dot at the end of an internet web address. Examples of gTLDs are .BANK, .COM, .ORG and .NET.

What is fTLD?

fTLD Registry Services, LLC was formed in 2011 by a coalition of banks, insurance companies and financial services trade associations from around the world. In 2012, fTLD submitted community-based applications to the Internet Corporation for Assigned Names and Numbers (ICANN) for the .BANK and .INSURANCE gTLDs. fTLD launched .BANK in May 2015 and .INSURANCE in May 2016.

What is ICANN?

The Internet Corporation for Assigned Names and Numbers, or ICANN, is an oversight body responsible for the stability and unification of the internet. Its key responsibilities include policy development for existing and new generic Top-Level Domains (gTLDs). In June 2011, ICANN’s board of directors authorized the launch of the New gTLD Program. The program’s goals include enhancing competition and consumer choice, and enabling the benefits of innovation via the introduction of new gTLDs.

Where can I find all the .BANK Policies mentioned in this FAQ?

All fTLD Policies for .BANK are located here.

What information is required to register a .BANK domain name?

Registrants must provide the following information:

  • Legal Name of the Eligible Registrant (the organization name)
  • Registrant Contact Name
  • Registrant Contact Address (Street, City, State/Province/Region, Postal Code)
  • Registrant Contact Email Address
  • Registrant Contact Telephone Number
  • Government Regulatory Authority (if applicable)
  • Regulatory ID Number (if applicable)

Note: The Registrant Contact must be a full-time employee of the Registrant Organization and cannot be a contract employee.

Registrars may request additional information such as a human resources contact name and telephone number who can verify the employment information of the Registrant Contact and a contact name and telephone number for another employee (e.g., manager of the Registrant Contact)  who can verify that the Registrant Contact is authorized to register the domain names requested. The additional contact information is required and must be provided to your registrar. It will expedite the verification process for your domain names as will providing the Government Regulatory Authority and Regulatory ID Number when applicable.

How do I check on the availability of a domain name?

To determine if a domain name is available for registration, use the “Secure Your .BANK Web Address” feature here.

Why .BANK?

As a verified domain, exclusively for the banking community, .BANK is a more secure space for online banking and communication. A web or email address ending in .BANK quickly and easily confirms for customers and employees that they are communicating and transacting with your bank, and not a phisher or a spoofed site.  A .BANK domain is a visual cue anyone can look for and recognize, an online stamp of trust that will give your customers confidence in your online banking platform, and help protect your bank from bad actors collecting data for breaches, financial fraud and identity theft.

Trademarks

What is the Trademark Clearinghouse (TMCH)?

ICANN’s TMCH is a global repository for trademark data. Designed to meet global needs for the domain name system, the TMCH verifies trademark data worldwide and maintains a database with the verified trademark records. The TMCH is not a trademark office; it is a centralized database of verified trademarks.

There is a cost to use the TMCH. Learn more at the Trademark Clearinghouse website.

Why would I want to register our trademarks in the Trademark Clearinghouse (TMCH)?

The Trademark Claims period initially ran for the first 365 days of General Availability and has been extended several times. To check the date the period will close, search for .BANK here. During the Trademark Claims period, anyone attempting to register a domain name matching a mark that is recorded in the TMCH will receive a notification displaying the relevant mark information.

If the notified party registers the domain name, the TMCH will send a notice to those trademark holders with matching records in the TMCH, informing them that someone has registered the domain name.

What trademarks does the Trademark Clearinghouse (TMCH) accept?

The TMCH will accept and verify registered trademarks, marks protected by statute or treaty or court validated marks as well as any other marks that constitute Intellectual Property (IP) rights that meet the eligibility requirements of the TMCH. Learn more about accepted marks at the Trademark Clearinghouse website.

(rev. 2018.01.24)
TOP