.bank domains list

What is .bank TLD

.bank is a restricted top-level domain dedicated to verified, regulated banking institutions. In practice, .bank domains are issued only after eligibility and security checks designed to protect consumers and counterparties. .bank websites operate under heightened technical controls relative to open namespaces, signaling that the holder is subject to financial supervision. In our cross‑registry observations, the string is used for primary corporate sites, secure customer portals, and high‑trust email. These controls—such as mandatory DNSSEC, strong TLS, and authenticated email—reduce spoofing risk and clarify brand provenance across markets. The tradeoff is tighter onboarding and ongoing compliance compared with generic alternatives, which some institutions view as a worthwhile trust premium. Explore .bank domain datasets from webatla.

History and key features of .bank TLD

Introduced in the mid‑2010s under ICANN’s new gTLD program, .bank is operated by an industry‑backed registry with policies tailored to financial services. Early rollouts prioritized phased eligibility, then ongoing verification at registration and renewal. Core features applied to .bank domains include DNSSEC signing, enforced HTTPS, and authenticated email (SPF, DKIM, DMARC) for transactional communications. For .bank websites, registrants typically adopt stricter change controls, role‑based access, and monitoring aligned with regulatory expectations. Compared with open TLDs, abuse reporting and takedown processes are more prescriptive, and reserved names are more tightly managed. We track adoption velocity, nameserver diversity, and certificate hygiene to benchmark security baselines globally. Access detailed .bank datasets from webatla.

Why and who choose the .bank domain

Organizations selecting .bank domains are generally banks chartered or supervised by national or regional regulators; in some cases, sector associations and approved service providers qualify. We see .bank websites used for flagship branding, migration from legacy ccTLDs, and hardened landing pages for payments, onboarding, and investor relations. Drivers include measurable phishing reduction, clearer customer signposting, and email deliverability gains under strict authentication. Constraints include higher validation overhead, narrower naming inventory, and potential migration complexity for large portfolios. From our datasets, uptake patterns vary by jurisdiction and institution size, reflecting differing risk appetites and regulatory signals. Teams evaluating the extension should weigh security posture, user trust, and portfolio governance holistically. Start with .bank datasets from webatla.