.chase
Generic top-level domain
Nobody outside the registry can register here. .chase is a brand TLD run by JPMorgan Chase Bank, National Association, which under ICANN's Specification 13 means its operator is the only permitted registrant. ds reports names here as PRIVATE rather than AVAILABLE, and leaves the zone out of --tld all unless you pass --private include. See Brand and reserved TLDs.
- Registration
- Closedno public names
- Operator
- JPMorgan Chase Bank, National Association
- Lookup
- RDAPanswers for it
- DNSSEC
- Signed1 DS record in the root
- Level
- Secondmybrand.chase
Check a name
Names under .chase cannot be registered, but ds will still tell you what the registry says.
ds mybrand --tld chaseAdd --where for the registrars and the registry's rules, --registry for the server that answered, or --all-info for everything at once.
What it costs
No registrar in the price table bundled with ds quotes .chase, so the CLI prints no figure beside it — one of 927 such TLDs. That is a gap in the table as often as it is a TLD nobody sells, though here it is neither: the zone is closed. See Prices for supplying your own table with --pricing-file.
Who can register
Nobody outside JPMorgan Chase Bank, National Association — see the note at the top of this page.
How ds answers for it
RDAP first, WHOIS second — the same order for every TLD. .chase has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.
- RDAP
https://rdap.nic.chaseFrom IANA's bootstrap, refreshed when this page was built. The lookup ishttps://rdap.nic.chase/domain/mybrand.chase— a 404 means the name is free.
ds mybrand --tld chase --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .chase today. See Accuracy notes.
The registry
From IANA's delegation record for .chase. .chase is a generic TLD.
- Run by
- JPMorgan Chase Bank, National AssociationBased in United States of America. Delegated 2016-01-14, record last updated 2024-05-11.
- Registry site
- www.jpmorganchase.comWhere the registry documents .chase — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
- Published services
rdap.nic.chaseWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
a.nic.chaseb.nic.chasec.nic.chasens4.dns.nic.chasens5.dns.nic.chasens6.dns.nic.chaseThe 6 authoritative servers for the .chase zone — what the root delegates to. Nothingdsqueries directly; they are what makes a registered name resolve.
What it is
Derived from the root zone and ICANN's registry list — each one is a fact with a source.
genericIANA Root Zone Database types it "generic"brandICANN records Specification 13 — a brand TLD, closed to the publicnew-gtldICANN delegated it on or after 2013-10-23, when the 2013 round opened — seedelegated
In the root zone
The delegation itself, read out of the root zone — serial 2026090900, on 2026-09-09. The registry section above is IANA's record of what .chase was delegated to; this is what the root actually answers with when a resolver asks it where .chase lives.
- Delegated to
a.nic.chase37.209.192.92001:dcd:1::9b.nic.chase37.209.194.92001:dcd:2::9c.nic.chase37.209.196.92001:dcd:3::9ns4.dns.nic.chase156.154.156.392610:a1:1074::27ns5.dns.nic.chase156.154.157.392610:a1:1075::27ns6.dns.nic.chase156.154.158.392610:a1:1076::27
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 38962RSA/SHA-256 · SHA-256
7E231DFE930CAA42C760D3298C2F9B4B4F22AADC5A0FE6C7784E4E2177A0E317
- key 38962RSA/SHA-256 · SHA-256
Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net chase. NS and dig +norec @a.root-servers.net chase. DS.