A .BANK domain is a restricted top-level domain for verified banking organizations and a limited group of related entities. It is not a general-purpose finance extension. Eligibility, the requested name, and the organization’s ability to meet security requirements all need review.
That restricted model can create a clearer trust signal for customers, but it also means registration should begin with policy and technical planning. If your organization appears eligible, review the current .BANK process at NiceNIC before selecting a launch date.
What Is a .BANK Domain?
.BANK is a generic top-level domain sponsored by fTLD Registry Services. The registry was created for the banking community and limits registrations to qualifying organizations.
The extension can be used for a primary bank website, a customer portal, a campaign, or another approved service. Its value is not merely the word after the dot. The registry verifies eligibility and requires security controls for domains that resolve on the internet.
Who Is Eligible for .BANK?
The official fTLD eligibility page lists government-regulated retail banks, savings associations, national retail banks, and qualifying parent or holding companies. It also identifies certain associations whose membership is primarily made up of those regulated entities, plus qualifying government regulators subject to the registry’s policy and approvals.
Eligibility is narrower than “works in financial services.” A fintech company, lender, payment provider, adviser, software vendor, or cryptocurrency project should not assume it qualifies simply because its customers or products are financial.
NiceNIC's current .BANK page likewise states that the extension is restricted and that eligibility is verified. Prospective registrants should review the official fTLD .BANK eligibility page and the current NiceNIC process before ordering.
Domain Name Eligibility
An eligible organization cannot necessarily register any available word. fTLD states that the requested name must correspond to the organization’s legal name or branding, such as a trademark, trade name, or service mark. The registry’s public eligibility page notes that a registered trademark is not always required, but the name still needs a valid connection to the organization.
Prepare evidence showing how the requested label relates to the legal entity or brand. An abbreviation that is obvious internally may still need explanation during review.
Who Should Consider .BANK?
A qualifying bank replacing or complementing an existing domain
.BANK can give customers a recognizable banking-specific address. A bank may use it as its main site or introduce it alongside an established domain during a carefully managed migration.
A bank launching a verified customer service
A dedicated portal or campaign may benefit from the extension when the naming policy permits it and the service can meet the registry’s technical requirements.
An eligible association or regulator
Qualifying industry bodies and regulators may use .BANK when their category and requested name meet the official policies. These applicants should confirm approval requirements directly with the registry or registrar.
When .BANK Is Not a Fit
.BANK is not appropriate for an organization that falls outside the eligibility policy. It is also a poor choice for an eligible organization that cannot commit resources to DNS, certificate, email-authentication, and ongoing compliance work.
For a broader financial brand that is not eligible, extensions such as .FINANCE, .MONEY, or .CASH may be alternatives, but they do not carry .BANK’s restricted eligibility model. A conventional .COM can also be the clearer choice for a general financial product.
Security Requirements to Plan For
fTLD says registrants using .BANK domains that resolve on the internet must implement technologies including DNSSEC, encryption using Transport Layer Security, and email authentication. NiceNIC’s .BANK page highlights DNSSEC, HTTPS with current TLS, SPF, and DMARC among the controls applicants should plan for.
These requirements affect more than the website team:
- DNSSEC needs coordination between the DNS operator and registrar;
- TLS certificates and HTTPS need reliable issuance, renewal, and monitoring;
- SPF and DMARC need accurate mail-sending inventories and controlled DNS records; and
- vendors hosting portals, landing pages, or email must support the required configuration.
Use the current fTLD security page and .BANK implementation guide as the policy references during deployment. A successful domain order is not the end of compliance; eligibility and security controls need to remain valid.
Operational Questions Before Registration
Identify the legal registrant, policy owner, DNS provider, certificate owner, mail owner, and incident contact before placing the order. Decide whether the domain will replace an existing address or launch in parallel.
For a migration, inventory web applications, customer bookmarks, email addresses, certificates, redirects, third-party integrations, printed material, and regulatory notices. A staged move is usually easier to verify than an abrupt switch.
Check the current registration term, renewal, verification, and transfer process directly with NiceNIC before committing to a schedule. This guide does not quote a price or promise a review time because commercial terms and case-specific verification can change.
How to Register a .BANK Domain at NiceNIC
Step 1: Confirm organization eligibility
Compare the legal entity with the current fTLD eligibility categories. If the category is not clear, resolve that question with the registry or NiceNIC before planning a launch.
Step 2: Validate the requested name
Choose a name connected to the organization’s legal name or approved branding. Gather the legal, regulatory, and brand information needed to support that connection.
Step 3: Review security readiness
Confirm that the DNS, web, certificate, and email teams can implement the current .BANK requirements. Include external service providers in the review.
Step 4: Start the registration and verification process
Use the NiceNIC .BANK registration page to check the name and current terms. Submit accurate organization information and respond to eligibility or naming verification requests.
Step 5: Configure, test, and maintain compliance
Complete the required DNSSEC, TLS, and email-authentication work before public use. Test the domain, monitor the controls, and keep organizational and contact information current.
If your organization and name meet the policy, start a .BANK domain search at NiceNIC.
