.here
Generic top-level domain
- Register
- $21.99first year
- Renew
- $27.99a year
- Transfer
- $21.99to move it
- Registrars
- 1quoting it
- Lookup
- RDAPanswers for it
- DNSSEC
- Signed1 DS record in the root
- Level
- Secondmybrand.here
Check a name
One command, straight against the registry — no account, no page to load.
ds mybrand --tld hereAdd --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
Every published quote in the bundled table, cheapest registration first. The figure ds prints beside .here is the mean of the registration column — $21.99, which undercuts 77% of the 881 priced TLDs.
| Registrar | Register | Renew | Transfer |
|---|---|---|---|
| 101domain.com | $21.99 | $27.99 | $21.99 |
Mean — what ds prints | $21.99 | $27.99 | $21.99 |
List prices in US dollars, bundled with the binary and last regenerated 2026-09-09. Promotions, ICANN fees, taxes and premium names all move the real number, and a registry may decline to sell you the name at all. See Prices.
Where to register
One registrar in the bundled table publishes a registration price for .here, which is evidence it sells it — nobody prices what they cannot sell. Cheapest first, exactly as ds mybrand --tld here --where prints them.
Put a name in the box above and each link becomes that registrar's search for mybrand.here, where it publishes one. This list is what the price table knows, not the whole market — see Where to register.
Who can register
No eligibility rule is on file for .here, which is not the same as a promise that it is open: the list is hand-maintained and covers the restricted TLDs a registrar is likely to offer you. Check the registry's own page before counting on a name. 81 TLDs do carry a rule — see Who can register.
How ds answers for it
RDAP first, WHOIS second — the same order for every TLD. .here has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.
- RDAP
https://pubapi.registry.google/rdapFrom IANA's bootstrap, refreshed when this page was built. The lookup ishttps://pubapi.registry.google/rdap/domain/mybrand.here— a 404 means the name is free.
ds mybrand --tld here --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .here today. See Accuracy notes.
The registry
From IANA's delegation record for .here. .here is a generic TLD.
- Run by
- Charleston Road Registry Inc.Based in United States of America. Delegated 2014-06-12, record last updated 2025-04-11.
- Registry site
- www.registry.googleWhere the registry documents .here — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
- Published services
pubapi.registry.googleWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
ns-tld1.charlestonroadregistry.comns-tld2.charlestonroadregistry.comns-tld3.charlestonroadregistry.comns-tld4.charlestonroadregistry.comns-tld5.charlestonroadregistry.comThe 5 authoritative servers for the .here 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"new-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 .here was delegated to; this is what the root actually answers with when a resolver asks it where .here lives.
- Delegated to
ns-tld1.charlestonroadregistry.com216.239.32.1052001:4860:4802:32::69ns-tld2.charlestonroadregistry.com216.239.34.1052001:4860:4802:34::69ns-tld3.charlestonroadregistry.com216.239.36.1052001:4860:4802:36::69ns-tld4.charlestonroadregistry.com216.239.38.1052001:4860:4802:38::69ns-tld5.charlestonroadregistry.com216.239.60.1052001:4860:4805::69
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 32584RSA/SHA-256 · SHA-256
DC704BA2007A9F1F254659A40FC55762434B742F3919B6F31FDC53B8301657BE
- key 32584RSA/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 here. NS and dig +norec @a.root-servers.net here. DS.