Can a .new domain point to a normal homepage while you build? Check the direct-action rule, sign-in flow, HTTPS, and the condition on its 100-day waiver.
Can you point a .new domain at a normal homepage or a coming-soon page while you build for 100 days? No, not under the ordinary .new action requirements. Google Registry requires .new names to take visitors directly into an action-generation or online-creation flow. Its 100-day enforcement waiver applies only while the domain does not resolve. It is not a grace period for running a live placeholder.
That distinction belongs in the buying decision, not in a launch-day surprise. A memorable extension can still be the wrong tool if the first thing you need is an ordinary company homepage, a parked name, or a place to collect interest while the product is unfinished. Policy checked September 7, 2026.
This is practical launch guidance based on the linked registry material, not a new-policy announcement or a guarantee of compliance. What should a .new address actually do? Think of .new as the beginning of a task, not the front door to a brochure. Google Registry describes it as a namespace for action generation and online creation.
Its public directory includes shortcuts for creating documents, designs and other new work. The important test is the visitor's path. The registration policy says navigation or redirection to a homepage or landing page that requires additional steps or clicks to initiate creation does not comply. A general homepage with a prominent "Create" button is still a detour.
For your own proposed shortcut, write one sentence before choosing the name: "Opening this address starts a new ______." If the answer is only "visit our website," pause and compare other primary-domain options whose current registry rules fit that use. Sign-in is allowed, but the task must survive it The policy makes a specific exception for authentication.
A logged-out visitor may reach a sign-up or sign-in page. After sign-in and any other required authentication, that visitor must go directly into the action or creation flow. Someone already signed in must enter that flow immediately. Test both states. A shortcut can behave correctly for its developer's existing session while sending a new visitor to a dashboard where the task has to be found again.
The policy is about the journey, not just the first redirect. Signed in: open the .new address and confirm that the intended creation flow begins without a homepage or menu detour. Signed out: open it in a clean browser session, complete the required authentication with your own test account, and confirm that the intended task resumes directly. Session expired: repeat the test after signing out.
A stale session should not silently change the destination to a general dashboard. Record the destination reached in each test and whether the intended creation flow opened. Use your own test environment and account; avoid sending real messages or making purchases just to test navigation.