.page domain guide: registry, rules and setup notes

Charleston Road Registry Inc. holds the contract to run .page, under a Registry Agreement with ICANN signed on 4 December 2014, and IANA lists it as the sponsoring body for the delegation. It's a Google entity through and through: IANA's administrative and technical contacts for .page sit under Google Inc., and the registry does business publicly as Google Registry. There's no third-party backend provider named in the sources we checked. Name servers run on charlestonroadregistry.com infrastructure, which tells you the technical side is kept in-house rather than farmed out to a specialist.

Three roles sit behind every .page domain, same as any gTLD. The registry, Charleston Road Registry trading as Google Registry, writes the rules for the whole extension, including the HTTPS requirement, and keeps the master database via the RDAP and registration services IANA has on record. Registrars are the accredited firms you actually buy the name from, and they're who you go to for support, renewals and DNS changes. Then there's you, the registrant, bound by ICANN's baseline rules and by Google's own .page registration policy, the document that sets out the HTTPS disclosure your registrar has to give you before you hand over any money.

.page carries no nationality clause, no industry test, no entity-type box to tick. It sits open to the public the same way .com or .io does. According to registrar-published rules on domain eligibility,.page falls under "open (technical)": anyone can buy one, but there's a technical hurdle rather than a background check on who you are.

That hurdle is HTTPS. Google's own .page registration policy forces every accredited registrar to spell out, separately from the rest of the terms, that .page is encrypted by default and that HTTPS has to be set up before a site will even load in a browser. It's baked into the sign-up flow rather than into some vetting process. The policy also drags in the usual new-gTLD boilerplate: two-letter ASCII labels can't be registered in a way that implies a government or country-code link that doesn't exist, and anything matching the IOC, Red Cross or IGO reserved list has to actually belong to one of those bodies. Outside of that, individuals, businesses and organisations anywhere can register a .page domain.

Transfers between registrars work the way they always do under ICANN's rules: unlock the domain, grab the authorisation code from your current registrar, confirm the move with the new one. Nothing in the .page documentation suggests this registry does it differently, so assume it follows the standard gTLD process.

Minimum and maximum registration terms for .page aren't published anywhere in the sources we have checked, and neither is a registry-specific grace period, redemption window, or restore fee. These details tend to live in the registrar's own terms rather than the registry agreement itself, so confirm the actual figures with your registrar before you plan around them.

One thing is nailed down, though: every .page domain sits on the HSTS preload list. Browsers simply won't load it over plain HTTP, full stop. It's not a lifecycle stage like renewal or expiry, but it's a fixed condition that travels with the domain for as long as you own it.

Google Registry's own showcase for .page lists a handful of live examples: mmm.page, a drag-and-drop builder for link-in-bio pages and moodboards; byline.page, a collaborative writing project; front.page, a mobile-first publishing tool; funnies.page, a daily comics newsletter; and volition.page, a goal-tracking site. Individual registrants named in the same material include afrohairmatters.page and wondershop.page, both personal or portfolio projects rather than large commercial operations.

Before going live, there's one setup step you cannot skip: HTTPS. Because .page sits on the HSTS preload list, a domain without a valid TLS certificate just won't render in a browser. No fallback to plain HTTP, no exceptions. Google Registry's own documentation and its registration policy both flag this as a registrar disclosure requirement, which tells you it catches people out often enough to warrant the warning.

The sources we checked say nothing about email deliverability or spam-filter reputation for .page specifically, so file that under unverified rather than assume it's fine. One naming tip worth following: since .page reads as a description of the content itself, use it for a single, well-defined thing, a portfolio, a launch page, a story, rather than as the umbrella domain for a sprawling multi-section site.