Top 10 QuestionsExpand Top 10
See the information at BECOME AN fTLD REGISTRAR for details on the process.
All fTLD-Approved Registrars will be issued credentials to fTLD’s Registrar Web Portal, where this information can be accessed.
Registrants must be verified by fTLD to ensure that registrations are made only to organizations that meet and maintain the eligibility requirements (.BANK eligibility requirements; .INSURANCE eligibility requirements) per the Registrant Eligibility and Name Selection Policies accessible here before their Registrars are permitted to register domain names for them. To get verified by fTLD, Registrants for .BANK domain name must complete the Verification Application available here and for .INSURANCE here. fTLD’s Verification Process Overview is accessible here and in the Registrar Web Portal.
In addition to the standard Registrant information, the following details are required for fTLD to process the application:
- Government Regulatory Authority Name and ID Number – This information is required unless it is not applicable to the Registrant type (i.e., Association, Government Regulator, Service Provider).
- Verification Contact name, email, and phone number – Contact information to verify the employment and authority of the Registrant contact to register the domain name(s) requested.
- Supporting Information – This information may be requested to support how a domain name complies with fTLD’s Name Selection Policy available here. The information may include websites, documents (e.g., advertising or marketing materials; pictures demonstrating use; a copy of the trademark, trade name or service mark registration) or trademark registration number and jurisdiction information.
The data used is the current Whois information. No, fTLD will initiate the process with a verification email to the Registrant to review the registration data.
Once fTLD completes the verification process and approves the application, fTLD will issue the registration token to the Registrant and its Registrar of choice (if selected). The Registrant will then present the registration token to its Registrar of choice. The Registrar validates the token and extracts the Whois data, then submits the registration data via EPP to the Registry System and the domain name(s) is automatically put into a pendingCreate status.
The Token Validation System (the “Token System”) is how Registrars validate .BANK and .INSURANCE domain registration tokens issued by fTLD for verified domain applications. A key goal of the Token System is to ensure that Registrars use the validated token results when processing a domain name registration. The registration token encodes data identifying Registrant information and the associated domain name(s), and this ensures that domain registration information EXACTLY matches what was verified by fTLD. The Token Validation System Guide (available to approved Registrars on the fTLD Registrar Web Portal) covers the two mechanisms for token validation, API and Web-Based (“Manual”), and identifies other information available through the system.
There is no separate cost for the verification process. fTLD’s wholesale domain name fee to Registrars includes the charge for verification services. There are no additional costs for annual verifications that are performed during the term of the registration.
Yes, the fTLD Operations Pledge accessible here outlines the policies and procedures fTLD and our Registrars must follow to ensure the secure, stable and reliable operations of the .BANK and .INSURANCE domains.
fTLD has incorporated the lessons learned and implementation solutions from early adopters into guides, tools and resources that are designed to help Registrants transition to their .BANK or .INSURANCE domain name:
- Eligibility .BANK | .INSURANCE
- Registrant Security Requirements .BANK | .INSURANCE
- Third-Party Provider Program .BANK | .INSURANCE
- Planning and Communications Guide
- Implementation Hub
fTLD Registry System
Neustar is the Registry Service Provider and fTLD is the Registry Operator. fTLD performs domain registration verification for .BANK and .INSURANCE.
No, fTLD registration is not supported by a web interface to EPP.
Yes, Registrars will need to ensure they have configured their systems to submit the create / renew / transfer commands in the appropriate format, which includes a price acknowledgment on period-based-fee-incurring transactions. This acknowledgment is mandatory, and failure to do so, results in the domain create / renew / transfer operation being unsuccessful. This is done through an extension in the EPP. An example command follows:
The five-day (5) Add Grace Period starts when the domain name has been put in the pendingCreate status.
Yes, a domain name can be deleted after the Add Grace Period. However, the Registrar would not receive a refund of the registration fee.
Please contact Neustar at reg-support@support.neustar for more information. Registry Lock is encouraged for .BANK and .INSURANCE domains.
Registering A Domain Name
All Registrants and domains must be verified by fTLD before their Registrars submit a registration to the Registry System. More information about fTLD’s Verification process is provided below.
No, Registrars must not submit any registrations until they have received a verification token for the domain name and successfully processed it in the Token Validation System. See Registration Token & System below for more information. If this process is not followed, fTLD will reject the registration.
Any domain name(s) that corresponds to the Registrant’s legal name or branding (e.g., trademarks, trade names or service marks) can be registered, provided it is not an fTLD or ICANN reserved name. For guidance on selecting domains, please see fTLD’s Name Selection Policies accessible here.
Yes, all single-character names (e.g., 1.BANK, B.INSURANCE), most two-letter names (e.g., AB.BANK, GE.INSURANCE), and names fTLD has reserved for its potential use, indicated in bold on the list of Generic Names in .BANK and list of Registry Operator Reserved Names in .INSURANCE, are identified as premium and subject to premium pricing. These names are available on first-come, first-served basis subject to fTLD’s Registrant Eligibility and Name Selection Policies.
Yes, domain names can be sold/transferred. However, the new/gaining Registrant must meet fTLD’s Registrant Eligibility and Name Selection Policies for the domain name and must also successfully be verified by fTLD. If fTLD does not approve of the transfer, Registrars will need to work with fTLD to restore the domain name ownership to the original verified Registrant.
fTLD Verification
fTLD is responsible for verifying and approving requests for domain names.
fTLD verifies registration data on an annual basis based on the last time that a verification was successfully completed. At that time, all domain names held by the Registrant will also be verified.
Registrants must be verified by fTLD to ensure that registrations are made only to organizations that meet and maintain the eligibility requirements (.BANK eligibility requirements; .INSURANCE eligibility requirements) per the Registrant Eligibility and Name Selection Policies accessible here before their Registrars are permitted to register domain names for them. To get verified by fTLD, Registrants for .BANK domain name must complete the Verification Application available here and for .INSURANCE here. fTLD’s Verification Process Overview is accessible here and in the Registrar Web Portal.
In addition to the standard Registrant information, the following details are required for fTLD to process the application:
- Government Regulatory Authority Name and ID Number – This information is required unless it is not applicable to the Registrant type (i.e., Association, Government Regulator, Service Provider).
- Verification Contact name, email, and phone number – Contact information to verify the employment and authority of the Registrant contact to register the domain name(s) requested.
- Supporting Information – This information may be requested to support how a domain name complies with fTLD’s Name Selection Policy available here. The information may include websites, documents (e.g., advertising or marketing materials; pictures demonstrating use; a copy of the trademark, trade name or service mark registration) or trademark registration number and jurisdiction information.
No, Registrants may apply for as many domain names as they like in one Verification Application. All approved domain names will be included in the registration token.
If the applications are more than 10 business days apart, fTLD will complete a verification. Otherwise, if a Registrant applies for domain names within 10 business days, fTLD will confirm the Registrant information exactly matches the previously verified information and verify the new domain name(s) comply with the relevant Name Selection Policy to complete the verification. Upon completion of the verification, fTLD will issue a registration token to the Registrant contact and its Registrar of choice (if selected).
The Registrar should work with the Registrant to ensure that the data is updated in the Registrar system and submitted to the Registry System as quickly as possible. A change to the Registrant Organization, Registrant Name, and/or Registrant Email will prompt a new verification.
The data used is the current Whois information. No, fTLD will initiate the process with a verification email to the Registrant to review the registration data.
Upon receiving the annual verification email from fTLD, if the Registrant reports the registration data needs to be updated, fTLD will in most cases request the updated information from the Registrant and pass it to their Registrar. fTLD will complete the verification using the updated registration information.
The verification process is usually completed within a few business days. If there are items pending from the Registrant contact or the employment/authority verification is taking a while to confirm/respond to fTLD’s request(s), there may be delays in the verification process.
No, the verification process is mandated for all .BANK and .INSURANCE domain registrations.
In contrast, the Whois verification process is required by ICANN to be conducted annually by Registrars to confirm accurate contact information. Registrars are required to contact their Registrants to conduct this verification.
Registrants may risk having their domain name suspended or cancelled for failure to respond to either type of verification request. If you want to confirm whether the request is legitimate, please contact fTLD at verify@fTLD.com
Once fTLD learns of a consolidation or acquisition (e.g., from a relevant regulatory authority), we will communicate with the Registrant and Registrar about what are and are not permissible activities for the domain registration to ensure compliance with fTLD’s Policies and Requirements. In the event of questions about this, please write to compliance@fTLD.com.
Registration Token & System
A registration token is used to provide Registrants and their Registrar of choice (if selected) with the information fTLD has verified. The token will include Registrant contact information and the domain name(s) that have been approved for registration.
Once fTLD completes the verification process and approves the application, fTLD will issue the registration token to the Registrant and its Registrar of choice (if selected). The Registrant will then present the registration token to its Registrar of choice. The Registrar validates the token and extracts the Whois data, then submits the registration data via EPP to the Registry System and the domain name(s) is automatically put into a pendingCreate status.
The Token Validation System (the “Token System”) is how Registrars validate .BANK and .INSURANCE domain registration tokens issued by fTLD for verified domain applications. A key goal of the Token System is to ensure that Registrars use the validated token results when processing a domain name registration. The registration token encodes data identifying Registrant information and the associated domain name(s), and this ensures that domain registration information EXACTLY matches what was verified by fTLD. The Token Validation System Guide (available to approved Registrars on the fTLD Registrar Web Portal) covers the two mechanisms for token validation, API and Web-Based (“Manual”), and identifies other information available through the system.
No, and unlike other TLDs that may have Registrars pass tokens to the registry service provider, this does not happen in .BANK and .INSURANCE. The purpose of the registration token is for Registrars to submit registrations using the exact information fTLD has verified.
Registration tokens are valid for 15-calendar days. If the token is not used and expires, the Registrant will need to contact fTLD at verify@fTLD.com and request a new token be generated.
Costs
There is no separate cost for the verification process. fTLD’s wholesale domain name fee to Registrars includes the charge for verification services. There are no additional costs for annual verifications that are performed during the term of the registration.
fTLD’s Pricing Addendum will be provided to Registrars that have completed step one of the onboarding process available here.
Yes, there is a difference in the cost. fTLD’s Registration Fees Schedule is available to Registrars that have completed step one of the fTLD Registrar application process here.
For new registrations, Neustar charges for a domain name once fTLD approves the registration. The Add Grace Period will start from the date of fTLD’s approval and not from the create date. The registration period of the domain will start from the create date. For renewals, Neustar charges after the 45-day Auto-Renew Grace Period or after the five-day (5) Explicit Renew Grace Period following an explicit renew of a domain name registration period.
Monthly statements/invoices are posted by Neustar to their billing extranet no later than 10 days after the end of the month. This is true for both pre-payment debit accounts and payment in arrears accounts.
Refunds for a domain name registration or renewal will be provided to Registrars by Neustar under these circumstances:
- When the domain name is deleted by the Registrar before the end of the five-day (5) Add Grace Period.
- When the domain name is deleted by the Registrar before the end of the five-day (5) Explicit Renew Grace Period.
There are no fees charged by fTLD for changing any registration information. fTLD requires Registrants to maintain accurate information to ensure a trusted, verified and more secure environment. Although a verification is performed when certain Whois data changes (e.g., Registrant Organization, Registrant Name, Registrant Email) there is no additional fee for this.
Although there is a charge for a mandatory one-year renewal, there are no additional fees for transfers in the Registry System.
Security & Implementation
fTLD requires compliance with a set of requirements that are not currently mandated by operators of other commercially available gTLDs. Please review the Security Requirements information for specific requirements for fTLD, Registrars and Registrants.
Yes, the fTLD Operations Pledge accessible here outlines the policies and procedures fTLD and our Registrars must follow to ensure the secure, stable and reliable operations of the .BANK and .INSURANCE domains.
fTLD is ultimately responsible for enforcing the Security Requirements and Policies in .BANK and .INSURANCE. Registrars will play a role in enforcement of Registrant Security Requirements, as they have a direct relationship with the Registrant and fTLD will communicate with the appropriate Registrar on any enforcement actions. fTLD retains the right to take action if the Registrar or Registrant fails to do so.
fTLD will work with the Registrant and Registrar to address the violation. Repeated violations of any requirements may lead to suspension or termination of the registration. 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 or .INSURANCE zone or more significant actions.
No, these services are prohibited for fTLD registrations. This is specifically noted in the RRA and is part of the fTLD Operations Pledge.
fTLD has incorporated the lessons learned and implementation solutions from early adopters into guides, tools and resources that are designed to help Registrants transition to their .BANK or .INSURANCE domain name:
- Eligibility .BANK | .INSURANCE
- Registrant Security Requirements .BANK | .INSURANCE
- Third-Party Provider Program .BANK | .INSURANCE
- Planning and Communications Guide
- Implementation Hub