.blog Puts the Genre in the Root Label

Tim Ferriss could have kept timferriss.com/blog. GitHub could have stayed on github.com/blog. Both chose root labels where publishing is the product: tim.blog and github.blog still return HTTP 200 in mid-2026 checks—one author’s billion-download podcast archive, one company’s engineering-and-security editorial machine. The suffix does not magically rank you. It finishes a sentence strangers already understand: this hostname is for writing.

That sentence is also why the thin stub this guide replaces failed an audit. It padded “notables” with Mad Libs (name.blog, engineering.company.blog, cooking.blog), claimed wordpress.blog was WordPress’s official blog (mid-2026 it 301s to wordpress.org/news/—honest redirect, not a standalone .blog editorial home), and invented “AI engines love blogs”—a claim with no primary source and no place in a TLD guide. What follows is receipt-first: a $19 million dictionary-word auction, who actually hosts on the root label, Automattic’s dual life as registry and subdomain landlord, zone math, backend migrations, pricing cliffs, and the one ownership question that separates a publishing roof from a /blog folder.

Nineteen million dollars for one English word

Nine applicants filed for .blog in ICANN’s 2012 round—including Google, Afilias, M+M, Radix, and Donuts. In February 2015, a private auction settled on Primer Nivel S.A., a Panamanian vehicle widely read as a bidding shell. Matt Mullenweg revealed in May 2016 that Automattic had bankrolled the bid through Knock Knock WHOIS There, LLC—deliberately stealthy, he wrote, “in order not to draw too much attention.” The disclosed price: about $19 million (Matt Mullenweg, Domain Incite via Wikipedia). ICANN’s registry agreement moved from Primer Nivel to Knock Knock WHOIS There effective 29 April 2016.

IANA delegated .blog on 12 May 2016. Launch followed the usual sunrise / landrush / GA ladder—TechCrunch’s August 2016 landrush piece noted $250 all-in for contested early applications ($220 bid fee plus ~$30/year)—with premium tiers for dictionary left-sides. Automattic’s original application promised no renewal above $15/year for the first five registry years; retail reality drifted with registrar markup and premium inventory, but the strategic bet was never margin on year-one carts. It was owning the English word for the medium WordPress already served.

Knock Knock WHOIS There remains the sponsoring organisation in IANA records. Automattic runs one open gTLD through that subsidiary—registry concentration unusual among new-gTLD portfolios dominated by Radix-, Identity Digital-, or Donuts-scale landlords.

Live publishing roofs—and the Mad Libs to delete

Ignore listicles. These mid-2026 HTTP checks still return on-mission editorial surfaces:

tim.blog — Tim Ferriss’s author hub: podcast, books, and long-form posts on a single root label that is the brand’s public writing home.

github.blog — GitHub’s official engineering, security, and product editorial site—corporate publishing where the blog is not a subdirectory afterthought.

seths.blog — Seth Godin’s daily publishing practice on a root .blog; the URL grammar matches the product.

firebase.blog — Google Firebase’s developer-relations blog (mid-2026 200, fresh last-modified timestamps on posts).

joost.blog — Joost de Valk (Yoast founder) publishing SEO and WordPress technical writing from a personal root label.

matt.blog — Matt Mullenweg’s personal site on the TLD his company operates—registry founder eating his own cooking.

wordpress.blog — 301 to wordpress.org/news/. WordPress’s news lives on .org, not as a marquee .blog showcase. Cite the redirect; do not pretend it is an independent editorial property.

my.blog — Knock Knock WHOIS There’s registry marketing site (200).

design.blog — 301 to automattic.design—Automattic using a premium string as a redirect into a design-brand surface, not as a daily magazine.

Trash the old stub’s fiction: name.blog, engineering.company.blog, cooking.blog (no useful resolution mid-2026), and travel.blog as a “photography journal” notable—it is a subdomain landlord (“Get your subdomain of travel.blog”), the same genre Automattic runs on tech.blog. That is infrastructure, not proof your personal firstname.blog inherits Ferriss traffic.

If you cannot open a living, on-mission homepage today, you do not have a notable. You have registrar brochure filler.

~555k names, one registry, two distribution channels

Zone trackers in mid-2026 put .blog near 554,906 registrations on nTLDStats—roughly #27 among new gTLDs, ~1.14% share of the tracked nTLD pool—while HostDir’s broader census snapshot cited 528,737 (~#73 globally, ~0.12% of ~425M names). Hurricane Electric’s June 2026 DNS scrape counted 358,955 delegated domains with 330,631 A records—zone files and crawl lag always disagree; treat any single integer as a photograph, not destiny.

What the numbers agree on: .blog is established but not industrial. It sits closer to .buzz and .digital than to Radix-scale factories like .online or .site. InternetNews.me reported that over a third of .blog names were registered through Automattic’s own registrar channel at the time of writing—distribution leverage most registries cannot replicate.

There are no eligibility restrictions. Ghost, Hugo, Substack custom domains, Next.js, and WordPress.com all work. The TLD does not require WordPress—though Automattic will always prefer you buy hosting there.

Three registry backends and a fourth migration

.blog has changed plumbing more often than most single-string registries:

1. Nominet — launch-era backend (Post Status / WP Tavern reporting, 2016).
2. CentralNic (Team Internet) — Automattic announced a May 2019 switch seeking registry tooling (Knock Knock WHOIS There blog archive).
3. CIRA Fury — HostDir’s mid-2026 IANA-adjacent notes list CIRA Fury Registry Services as backend provider.
4. Hello Registry — CIRA and SIDN’s joint backend; InternetNews.me reported .blog moving from April 2026—the third backend landlord change in a decade.

Registrars must re-integrate; registrants should notice only if migrations stumble. The operational lesson is narrower: your renewal contract is with a registrar; the master database keeps changing vendors. Lock auth codes, keep WHOIS email alive, and do not treat “Automattic forever” as immunity from industry consolidation.

Pricing: cheap genre labels, steeper renewals, premium dictionary rent

Retail in mid-2026 still theaters year one. Independent aggregator snapshots (domainoffer.net, dot.bs) showed Porkbun-style registration near $1.57 with renewal near ~$21; Spaceship near $1.88 / ~$20.18 renewal; GoDaddy near $1.99 / ~$39.99 renewal. TLD-List spans registration quotes from ~$1.88 to six-figure premium tiers on dictionary inventory.

Model three years at your registrar’s renewal, not the intro banner. Landrush-era TechCrunch pricing already warned that dog.blog would not sell for pocket change—premium left-sides still behave like registry real estate, not standard carts.

Automattic also sells .blog through WordPress.com bundles—convenient if you already host there; compare out-of-bundle registrar shelves before you assume bundle pricing beats Porkbun or Spaceship renewals.

SEO without folklore—and without “AIO” theater

John Mueller’s 2015 Search Central guidance still governs: new gTLDs are treated like other gTLDs; keywords in the TLD do not confer ranking advantage or disadvantage. github.blog ranks because GitHub is GitHub—not because Google secretly boosts .blog. Your practical risks are trust, CTR, and deliverability, not a phantom TLD penalty or boost.

Structured data (BlogPosting, Article, Person) helps crawlers understand pages; pairing it with .blog is coherent marketing, not a magic ranking lever. And no—there is no credible evidence that “AI engines love .blog domains.” Models cite pages with links, freshness, and authority—the same ingredients tim.blog earned over years. Delete that sentence from your strategy deck.

For subdirectory architecture, see our Subdomain vs Subdirectory guide.

Is publishing the roof—or the spare room?

Skip who-should / who-shouldn’t twin columns. Ask one ownership question:

Would a stranger correctly guess that this hostname is mostly for publishing—and is that guess the whole business?

If yes—solo author, daily essayist, developer-relations editorial, open-source project whose public voice is the product—yourname.blog or product.blog is semantically honest. Budget renewals, not intro carts; keep email authentication tight on a fresh hostname; retain a memorable .com or ccTLD if banks, app stores, or offline customers must type you cold without context.

If the site is primarily commerce, SaaS, or corporate brochure with a news section, brand.com/blog (or /news) is usually clearer: the root should sell the product; the folder holds updates. Splitting to brand.blog can still work for editorial spin-outs—firebase.blog is Firebase’s DR blog, not its console login—but do not register bakery.blog when the homepage needs menus, hours, and ordering.

If you want Automattic’s subdomain landlord pattern (you.tech.blog), price it as tenant infrastructure, not as inheriting tim.blog prestige—you are renting a second-level genre label, not buying a root dictionary word.

Alternatives when .blog is wrong: .me for personal brand (.me guide), .dev for technical writing with HTTPS enforced, .page for single landing narratives (.page guide), or platform hostnames (*.substack.com) when you prefer rent over DNS ownership.

Automattic paid dictionary-word prices to put blog in the root zone. Ferriss, GitHub, Godin, and Firebase proved the grammar on live hosts. Your job is to decide whether publishing belongs on the roof—or belongs in the spare room off a .com hall.