.link
covers similar shortcut and redirect use cases but without a mandatory 100-day action-flow requirement or registry-enforced usage policy
Domains / Generic top-level domain
.new domain names: registry rules and use policy
.new is a generic top-level domain delegated to Charleston Road Registry Inc., a Google entity, in 2014. Unlike most gTLDs it isn't meant as a general-purpose address: every .new domain must resolve directly into an action, such as creating a document, sending an invoice or opening a form, rather than serving as a normal website homepage.
Facts reviewed 2026-09-12Prices checked 2026-09-12
.new at a glance
For a buyer, that means .new only suits a specific job: a memorable shortcut that launches a tool or workflow, such as sheet.new or invoice.new. It is not a substitute for a standard business domain, and registrations that don't resolve into an action within 100 days can be suspended without refund.
- Registry / delegated manager
- Charleston Road Registry Inc. (a Google Inc. entity), the IANA-listed sponsoring organisation for .new
- Delegated (IANA record date)
- Registration date shown in the IANA root database: 12 June 2014 (this is the IANA record date, not a commercial launch date)
- Who can register
- Open to anyone, but every .new domain must be used for 'action generation or online content creation' under the .new Registration Policy, and must resolve into that action flow within 100 days of registration
- Minimum term
- Not verified in the dossier for .new specifically
- Maximum term
- Not verified in the dossier for .new specifically
- HTTPS requirement
- Mandatory. Google Registry states .new is 'a secure namespace that requires HTTPS to be used on all .new domains in order for the domains to work in web browsers,' and .new is on the HSTS preload list
- Premium names
- Not verified in the dossier for .new specifically
verified against the linked source not verified, not inferred from another extension sources disagree
Compare .new prices
| Provider | Registration | Renewal | Transfer |
|---|---|---|---|
| OpenproviderNon-member prices | Check providerNo current public quote | Check providerNo current public quote | Check providerNo current public quote |
| AI VikingsPublic price list | $462.30Listed price · confirm termChecked 2026-09-12 · source 2026-09-12 | $598.38Listed price · confirm termChecked 2026-09-12 · source 2026-09-12 | $462.30Transfer fee · confirm termChecked 2026-09-12 · source 2026-09-12 |
| OpusDNSBusiness customers | Check dashboard pricingBusiness customers only | Check dashboard pricingBusiness customers only | Check dashboard pricingBusiness customers only |
| PorkbunPublic API prices | Check providerNo current public quote | Check providerNo current public quote | Check providerNo current public quote |
Advertised prices for standard names, not an availability check. USD as published; taxes and final fees are confirmed at the provider. How we compare All 28 extensions
Who runs .new?
- Policy authorityICANNSets the rules the registry and registrars follow
- Registry for .newCharleston Road Registry Inc.Owned by Google Inc.
- RegistrarsOpenprovider, AI Vikings, OpusDNS, Porkbun and othersSell registrations and pass the wholesale fee to the registry
- RegistrantYouHold the individual name for the term you have paid for
Charleston Road Registry Inc. shows up as the sponsoring organisation for .new in the IANA root zone database, and it's the same outfit named as contracted registry operator on the ICANN Registry Agreement, signed 30 January 2014. Charleston Road Registry is Google's entity for this: Google fills in the administrative and technical contacts on the IANA record and pushes .new through Google Registry at get.new. There's no separate third-party technical backend named in the paperwork, the nameservers sit on Charleston Road Registry's own infrastructure. ICANN stays the policy authority here, holding the Registry Agreement that sets the terms Charleston Road Registry has to operate .new under.
Within .new's own rules, the registry (Charleston Road Registry, trading as Google Registry) writes and enforces the Registration Policy, including the HTTPS requirement and the action-flow rules. Registrars are accredited separately and are simply the businesses selling .new domains to the public, they have to pass on the registry's required notices about those rules before anyone can buy. The registrant is whoever ends up holding the name, Stripe for invoice.new, say, and stays bound by the registry's policy no matter which registrar sold them the domain.
- Delegated managerCharleston Road Registry Inc.Listed as the Sponsoring Organisation in the IANA root zone database for .new. source
- Registry operatorCharleston Road Registry Inc.Operator on the ICANN Registry Agreement for .new, agreement dated 30 January 2014, classified as a Base, Non-Sponsored agreement. source
- Corporate parentGoogle Inc.Google Inc. supplies the Administrative and Technical Contacts for Charleston Road Registry Inc. in the IANA record, and markets .new through Google Registry (get.new / registry.google) as 'How is Google using .new?' source
- Policy authorityICANNICANN holds the Registry Agreement with Charleston Road Registry Inc. governing .new as a new gTLD, signed 30 January 2014. source
What changed, and when
- ICANN Registry Agreement for .new signed with Charleston Road Registry Inc. (Base, Non-Sponsored agreement). source
- IANA root zone database registration date recorded for .new (record date, not a commercial launch date). source
- IANA published the delegation report for .new, delegating the domain to Charleston Road Registry Inc. source
Who can register .new, and what are the rules?
Anyone can register a .new domain. The .new Registration Policy says there is no restriction on who may register, and Google Registry's FAQ confirms individuals as well as companies are welcome. The restriction is entirely on use, not on the registrant's identity or location.
Every .new domain must be used for action generation or online content creation, and navigation to the domain must take the user directly into that action or creation flow, not to a homepage requiring further clicks. New registrations get a 100-day grace period during which the domain can sit unused without enforcement, provided it does not resolve. After that, Google Registry can suspend or delete non-compliant domains without refund. HTTPS is mandatory too: .new sits on the HSTS preload list, so browsers simply refuse an unencrypted connection. These are registry rules set out in the policy itself. Registrars have to display notice of them before checkout, but they cannot alter or waive a single one.
Renewing, transferring and expiring a .new name
A .new domain moves between registrars the same way as any other gTLD: through the standard ICANN inter-registrar transfer process, using an EPP authorisation code from the registrar of record. The usual ICANN mechanics apply too, a registrar-applied transfer lock has to come off before you can shift the domain elsewhere, because Charleston Road Registry's agreement with ICANN is a standard base agreement, not some bespoke arrangement built for this string.
What actually sets .new apart isn't the transfer process, it's the usage clock ticking alongside it. Under the .new Registration Policy, a domain has to resolve into an action or content-creation flow within 100 days of registration, or Google Registry can suspend or delete it without a refund, even if the registration itself is current and fully paid. This rule sits on top of normal expiry handling, not instead of it.
The dossier has no published figures for minimum or maximum registration terms, standard renewal periods, grace period length, redemption period, or restore fees specific to .new. Other gTLDs publish these as fixed registry parameters; nothing of the sort turns up for .new in the sources reviewed here. Treat any number you see quoted elsewhere as a registrar's own house practice, not a registry rule, until someone confirms it.
Is .new right for this project?
Whether .new is worth buying comes down to one thing: does the domain need to trigger an action, or does it just need to exist. The registry's own rule states that navigating to a .new domain must drop the visitor directly into an action or creation flow, not a landing page, within 100 days of registration.
Take three cases. A product team building a one-click shortcut, something like invoice.new or meeting.new that opens a form or generates a document immediately, is exactly the scenario the extension was built for. The policy requirement and the intended use line up, and the mandatory HTTPS setup is a minor technical task, not an obstacle.
A small business after a short, memorable domain for a general company website is a weaker fit. A brochure site or a blog doesn't obviously satisfy "action generation or online content creation" the way Google Registry defines it, and the registry has said plainly it will suspend or delete non-compliant domains without refund. That's not a risk worth carrying for a name that a .com, .co or .site would serve just as well, with no usage condition attached.
A domain investor, or anyone registering a name to sit on for future use, is the poorest fit of the three. The 100-day enforcement window, and the registry's stated preference for registrants who are "ready to use" the name, work directly against speculative or parked registrations. Compare that to extensions with no comparable usage policy at all.
This is editorial judgment based on the published policy. It isn't a claim that .new performs better or worse than any other extension in general.
.new alternatives
.app
also requires HTTPS by registry mandate, but has no action-generation content rule, so it suits a broader range of product and marketing pages
.io
an open, unrestricted namespace favoured for tech branding, with no usage policy but a different, typically higher renewal cost structure
.co
short and brandable with no eligibility or usage restriction at all, useful where a name needs to work as a static destination rather than an action flow
.xyz
a low-cost generic option with open eligibility, suited to testing a name or project without any compliance deadline attached
.new questions
What exactly must a .new domain do to comply with the registration policy?
It has to drop a visitor straight into an action, generating something, opening a document, starting a form, creating a new item. A homepage or landing page that forces extra clicks before anything happens fails the policy outright. And the domain has to hit this state within 100 days of registration, not a day later.
Sources: registry.google
Is HTTPS mandatory for every .new domain?
Yes, and this isn't optional. Google Registry describes .new as a secure namespace and states flatly that HTTPS is required for a .new domain to work in web browsers at all, because the extension sits on the HSTS preload list. There's no fallback mode, no plain HTTP version. Skip the certificate and the domain simply won't load.
Sources: registry.google, get.new
Can an individual register a .new domain, or is it restricted to companies?
Anyone can register a .new domain. Google Registry doesn't restrict who's eligible, only how the thing gets used once it's live. Companies, solo developers, whoever, all fair game, as long as the domain actually does something (kicks off an action or generates content) within that 100-day window.
Sources: get.new
What happens if a .new domain is not used the way the policy requires?
Google Registry keeps an eye on compliance and will get in touch with a registrant, giving them a window to sort out a non-compliant domain. Miss that window and the domain can be suspended or deleted. Google Registry has been clear this happens without a refund, since refund policies sit with individual registrars, not the registry itself.
Sources: get.new, registry.google
Who actually manages the .new registry and who sits above it?
Charleston Road Registry Inc. is the IANA-listed sponsor and the operator named on the ICANN Registry Agreement for .new, signed 30 January 2014. Google Inc. sits behind it, providing the administrative and technical contacts and pushing the extension under the Google Registry banner. ICANN holds the agreement that spells out the contractual terms Charleston Road Registry has to follow.
Sources and accountability
Facts on this page were checked against the sources below on 2026-09-12. Prices come from the public sources described in the methodology and carry their own check dates. Registry facts and retail prices are refreshed on different schedules.
HostList does not sell domains and earns nothing from the provider links on this page. Report a correction.