A curated list of useful .new domain names with an explanation of what they are.
|Service||Domain||What do you get?|
|WordPress||Blog.new||New WP.com blog post|
|Doc.new||New Google Doc|
|Microsoft||Excel.new||New Excel document|
|Forms.new||New Google Form|
|GitHub||Gist.new||New GitHub gist|
|Meeting.new||New Google Calendar meeting|
|Note.new||New Google Keep note|
|eBay||Sell.new||New item to sell|
|Microsoft||Word.new||New Word doc|
You can view the full list of .New domains here.
What are .new domains?
Introduced by Google in 2018, and opened up to additional companies in 2019, .new domains are designed to be shortcuts to common new actions on the web.
The idea is that loading the domain name should take you straight to the new service.
For example if you want to launch a new spreadsheet, you would go straight to the new sheet – instead of having to go to a dashboard and then click ‘new spreadsheet’ or similar.
“Posting, linking, designing, recording — it’s all possible with action-based .new links. Replace menus and long URLs with easy-to-remember shortcuts.”
You can find out more about dot new domains on the Whats.new website.
Can I get a .new domain for my website/business?
You can apply for a .new domain on Get.new if you think you have a suitable web action.
Google may reject your application if they think it is unsuitable.
Google .new domains are unlikely to be suitable for a large number of different types of websites.
For example if you have an e-commerce website, blog, portfolio site, or similar – a .new domain would almost certainly not be appropriate.
Security, HTTPS & HSTS
Google like to focus on security with their domains, and like other Google domain extensions (such as .dev), .new domains have HSTS built-in and turned on by default.
This means that users visiting a .new domain will always be automatically forwarded (using a 307 redirect) to the secure version of the website if they attempt to visit a non-secure URL.
For example when a user visits
http://docs.new it will yield a 307 redirect to
https://docs.new, then a 302 redirect to the new document.