What Is the .page Domain? Meaning, Uses & Real Sites
.page is Google Registry's HSTS-secured gTLD for personal sites, portfolios, and landing pages, launched in 2018. Learn its history, real adopters, and fit.
- tld
The .page domain is Google's generic top-level domain for exactly what it sounds like: a page. Personal portfolios, publisher pieces, documentation, and landing sites all fit the word naturally, and every .page site runs on enforced HTTPS by default. Operated by Charleston Road Registry, .page predates the 2023 wave of Google gTLDs by five years — it launched in 2018 as one of Google's earliest open extensions. This page covers its history, real adopters, and honest trade-offs.
.page at a glance
| Fact | Detail |
|---|---|
| TLD type | Generic top-level domain (new gTLD) |
| Registry operator | Charleston Road Registry Inc. (Google Inc.), Mountain View, CA |
| Year launched | Delegated to the root zone March 2015; general availability October 9, 2018 |
| IDN support | — |
| DNSSEC | Supported |
| Registration restrictions | Open to all — no credential, community, or local-presence requirement |
| Best for | Personal sites, portfolios, publishers, documentation and landing pages |
What is .page?
.page is a generic top-level domain (gTLD), not a country-code TLD, so it carries no geographic association. The string is deliberately plain-spoken: Google Registry describes it as fitting anyone building "a simple, more secure online presence," from a business launching a site to "an author telling your story." You can confirm the delegation record and operator in the IANA root-zone database entry for .page.
Google also states that keywords in a TLD do not give any advantage or disadvantage in search, so the extension itself receives no inherent ranking boost or penalty.
Because .page is a generic extension, Google Search Central confirms gTLDs "aren't associated with specific locations," so .page carries no automatic geo-targeting signal, and no inherent ranking boost or penalty from the extension itself.
History of .page
- 2014–2015 — contracted and delegated. Charleston Road Registry signed the ICANN Registry Agreement for .page on December 4, 2014, and the string was delegated to the root zone on March 12, 2015, during the 2012 New gTLD Program round.
- 2018 — an early, deliberate launch. Unlike .ing, .meme, and .zip (all launched together in 2023 despite similar 2014 delegation dates), .page opened years earlier: a trademark sunrise period ran August 27–October 2, 2018, an early access period followed October 2–9, and general availability began October 9, 2018 — making .page Google Registry's fifth open top-level domain.
- Positioned around HTTPS from day one. Google's own launch messaging emphasized that .page was "secure by default," requiring HTTPS to connect to any .page site — a security-first design choice years before Chrome made HTTPS the web-wide default expectation.
How people use .page
Real, specific niches where .page shows up:
- Personal portfolios and creative writing tools — collaborative and individual storytelling projects.
- Drag-and-drop personal site builders — link-in-bio pages, moodboards, and simple landing pages.
- Mobile-first publishing platforms — niche content and information services built for phones first.
- Daily or serialized content — comics, newsletters, and other page-a-day style formats.
- Documentation and single-purpose landing pages — a natural fit anywhere the word "page" describes the actual content.
Who it's not ideal for: sprawling e-commerce platforms, multi-department enterprises, or any brand whose site is explicitly not a single page or simple presence — the name works against that framing.
Notable sites using .page
Google Registry's own get.page showcase lists real, currently active adopters:
- mmm.page — a drag-and-drop personal-site builder for link-in-bio pages, portfolios, and moodboards (also referenced as an .ing domain-hack adopter via
mak.ing). - byline.page — Byline, a multiplayer creative-writing experience where each contributor sees only one line before their own.
- Front.Page — a mobile-first publishing tool for niche content and information-service creators.
- Funnies.Page — a daily comics newsletter delivered by email.
.page vs other domains
| Factor | .page | .com | .site | .blog |
|---|---|---|---|---|
| Recognition & trust | Established since 2018, moderate familiarity | Highest, universal | Moderate, generic | Moderate, content-specific |
| Semantic fit | Personal/simple sites, landing pages | Universal | Universal | Blogs and articles specifically |
| Availability of short names | Wide | Very scarce | Wide | Wide |
| Security | HSTS-preloaded (HTTPS enforced) | Varies by registrar | Varies by registrar | Varies by registrar |
| Geo bias in SEO | None (generic) | None (generic) | None (generic) | None (generic) |
Pick .com for a project that needs maximum universal trust; pick .blog when the content is specifically a blog rather than a static page; pick .site for a fully generic web presence; pick .page when the project genuinely is a page — a portfolio, landing page, or simple personal presence — and you want enforced HTTPS out of the box.
Why choose .page?
- Mature for a "new" gTLD. Having launched in 2018, .page has years more track record than most Google Registry extensions.
- Security built in. As a Google Registry TLD, .page is included on the HSTS preload list, so browsers enforce HTTPS on every connection with no per-site setup.
- Precise semantic fit. For anything that genuinely is a single page — portfolio, landing page, documentation — the name reads as literal, not clever.
- Availability. Short, clean names remain findable in a namespace far less exhausted than .com.
Things to consider
- Narrower framing than .site or .com. "Page" implies something simple; a growing multi-section business site can outgrow the name's connotation.
- Moderate mainstream recognition. Users may still default to trusting .com first on sight, even eight years into .page's existence.
- Confusable with generic "page" language. Because the word is so common in everyday web vocabulary, a .page URL can sometimes read ambiguously in plain text (is "myportfolio.page" a URL or a description?).
- No fresh-launch novelty. Unlike the 2023 wave, .page's "new gTLD" appeal has faded with age — it now competes on merit rather than launch buzz.
Who can register a .page domain?
Registration restrictions: open to all. .page is an unrestricted generic TLD with no credential, professional-membership, community, or local-presence requirement. Any individual or organization worldwide can register through an accredited registrar.
The trademark sunrise period ran August 27–October 2, 2018, so today registrations are first-come, first-served, alongside an ongoing trademark claims-notice period for registered marks. DNSSEC is supported, and WHOIS privacy is available through most registrars. Standard ICANN lifecycle protections apply, including auto-renew grace and redemption-grace periods, so a lapsed name is not instantly re-available. The binding rules are set out in the ICANN Registry Agreement for .page and Google Registry's Domain Registration Policy.
.page pricing and value
.page pricing dynamics follow the pattern common to Google gTLDs: first-year promotional pricing typically differs from the standing renewal rate, so budget for the renewal rather than any introductory offer. The registry also designates certain premium names (short, dictionary, or high-demand strings) at elevated registration and renewal pricing. Cost is primarily driven by string length, dictionary-word status, premium classification, and registrar margin. We list no figures here — check current rates at the point of purchase.
Reputation and email deliverability
.page carries none of the controversy attached to .zip and no documented abuse pattern comparable to some ultra-cheap new gTLDs. Its 2018 launch and eight-plus years of history give it a longer, quieter track record than most Google Registry extensions. As a Google Registry TLD, .page is included on the HSTS preload list, meaning every .page connection is HTTPS-enforced at the browser level by default — a genuine security advantage for anything handling forms, logins, or personal data. For email sent from a .page domain, standard hygiene (SPF, DKIM, DMARC) applies the same as for any other extension; there is no documented deliverability penalty specific to .page.
Branding and naming tips
- Let "page" do descriptive work, not just decorative work. Names like
about.pageorresume.pageread cleanly because the word genuinely describes the content. - Keep it short. The TLD's strength is simplicity — a long second-level name undercuts that.
- Consider it for single-purpose sites first. Link-in-bio pages, one-page portfolios, and landing pages are the most natural fits.
- Don't force it onto a multi-section business. If your site has many distinct pages and sections, .site or .com communicates that scope more accurately.
How to register a .page domain at Namefi
- Search for your desired
.pagename to check availability. - Choose the exact name and review the term.
- Register and configure DNS to point your site or email.
Namefi is an ICANN-accredited registrar that bridges Web2 and Web3. Beyond standard registration, you can optionally tokenize your domain — turning it into a blockchain asset you own outright, with easier transfers and added security — all with transparent pricing and fast DNS.
Frequently asked questions
Can anyone register a .page domain?
Yes. .page is an open, unrestricted generic top-level domain operated by Charleston Road Registry, a Google subsidiary. There are no credential, membership, or local-presence requirements, so anyone worldwide can register a .page name through an accredited registrar.
Does a .page domain affect SEO?
No. Google treats .page as a generic top-level domain with no built-in ranking boost or penalty and no geographic association, the same as .com or .site. Ranking depends entirely on the content and authority of the site itself.
Is .page secure by default?
Yes. .page is included on the HSTS preload list, so web browsers require an encrypted HTTPS connection for every .page site automatically, without the site owner needing to configure HSTS individually.
Who should register a .page domain?
It suits personal portfolios, writers and publishers, landing pages, documentation sites, and student or research pages where the word "page" fits naturally. It is a weaker fit for full e-commerce platforms or multi-service businesses that outgrow a single-page framing.
Related resources
- What is a TLD?
- What is a domain?
- How to name your project
- Glossary: domain landing page, gTLD, registrar
- Compare TLDs: .com, .site, .blog, .ing, .meme
Sources and further reading
- registry.google — Charleston Road Registry
- IANA — IANA root-zone database entry for .page
- Google Search Central — keywords in a TLD do not give any advantage or disadvantage in search
- Google Search Central — Google Search Central
- ICANN — ICANN Registry Agreement for .page
- registry.google — general availability began October 9, 2018
- get.page — get.page showcase
- mmm.page — mmm.page
- registry.google — Domain Registration Policy
Related keywords
- .page domain
- Charleston Road Registry .page
- personal landing page domain
- HTTPS-only domain
- what is .page
- .page TLD
Contributors
Aileen Wright is a student in her twenties living in New York City, where the distance between a museum wall and a library reading room is a short walk and a long afternoon. She came to name writing through art and history — the way a single portrait, coin, or manuscript margin can carry a name across centuries and change its meaning on the way.
Most weeks you can find her in Central Park with a paperback, or in the quiet of a public reading room chasing down where a name actually comes from rather than what a name-list says it means. She is also teaching herself to code, which has made her oddly precise about spelling, sorting, and the small details that decide whether a name ages well.
For Namefi she writes about the history and culture behind domain names, the stories brands carry as they rename, and the difference between a good story and a verified source.
Victor Zhou is a technology founder and standards editor focused on digital identity and trust. He founded Namefi, edits Ethereum Improvement Proposals, and previously led smart-contract architecture work at Google Labs.
His work sits at the intersection of naming, ownership, and the systems people use to establish identity online. That perspective makes him especially interested in the way names move between personal meaning, public recognition, and digital infrastructure.
For Namefi, Victor edits and writes about domains as durable digital identity: how names become ownable onchain assets, how tokenization changes custody and trust, and what naming can learn from the systems people use to establish identity online.