Automattic WordPress Domain Bid: The Extension It Wants and the Trademark It Doesn’t Own

ICANN’s 2026 top-level domain application round went public on Reveal Day (October 7), releasing all 1,615 applications — and Automattic is making a big play. The parent company of WordPress.com, WooCommerce, and Tumblr has bid for 16 new web extensions through Knock Knock WHOIS There LLC, the registry arm that won .blog in the 2012 round. The list includes .wordpress, .woo, .tumblr, and .matt — a nod to founder Matt Mullenweg’s first name. But as one former Automattic domains executive pointed out in a widely read analysis, there is a wrinkle: Automattic does not own the WordPress trademark. The Automattic WordPress domain application has opened a conversation about who gets to control the most valuable name in the WordPress ecosystem — and under what rules.

What Happened with the Automattic WordPress Domain Bid

The Automattic WordPress domain application is one of 16 strings the company filed in ICANN’s first application round since 2012. The full list: craft, hire, human, jazz, make, matt, mesh, pod, pop, robot, soul, story, tumblr, vibe, woo, and wordpress. Applications were submitted through Knock Knock WHOIS There (KKWT), the Automattic subsidiary that already operates .blog — an extension that has since climbed to around 375,000 registrations, according to Domain Name Wire.

Demand differs sharply from one string to the next. On five of the 16, Automattic faces no challengers: .jazz, .matt, .tumblr, .woo, and .wordpress each drew a single applicant. The other 11 are contested, with between two and nine rivals each. Interest peaks at .pop and .robot, where nine applicants each are competing, followed by .pod with eight and .vibe with seven. Several contests put Automattic up against hosting and website-builder companies: in .human it goes head-to-head with Hostinger and Aruba among six total applicants; in .pop it crosses paths with Aruba; in .pod it runs into Squarespace. Aruba, Hostinger, and Squarespace also collide on .lab, while Hostinger and Aruba both chase .gen.

Automattic has also named 11 replacement strings, and applicants can switch until October 21. Four remain available: .freelance for .hire, .php for .vibe, .task for .soul, and .rap for .jazz. The other seven are deactivated because each matches a string another applicant filed, which the replacement rules do not allow. Notably, Automattic is the only applicant for .php — and its application defines the string as “an acronym for Personal Home Page,” with a mission statement tying it directly to WordPress: “WordPress is the largest open-source PHP project and .php would offer a home to WordPress developers.”

The trademark wrinkle arrived via Kellie Peterson, who was Head of Domains at Automattic from 2016 to 2023. In a Medium post titled “Automattic Wants .wordpress. It Doesn’t Own WordPress,” published the week of Reveal Day, she checked the application against ICANN’s Applicant Guidebook and registry contract, and urged WordPress developers, hosts, and contributors to comment on the Automattic WordPress domain once ICANN’s input period opens. The core facts are not disputed: the WordPress Foundation owns the WordPress trademarks, and under a 2010 agreement, Automattic holds what the agreement calls an exclusive, perpetual commercial license to use and sub-license them. Automattic CEO Matt Mullenweg is also a director of the Foundation. Paolo Belcastro, Automattic’s Head of Domains, confirmed to The Repository that the Foundation owns the trademarks and that this has not changed: “Automattic holds a limited commercial license from the Foundation, as it has since 2010, and its use of the WordPress name remains subject to that agreement and the Foundation’s oversight.”

The Automattic WordPress domain application itself describes WordPress as a brand without saying who owns it: “KKWT affirms that the applied-for string, WordPress, corresponds to a brand with multiple registered trademarks and thus is not a ‘Generic String'” — the classification ICANN uses to block closed TLDs for generic words. The WordPress Foundation is not named in the application. Automattic is also seeking an exemption from ICANN’s Registry Operator Code of Conduct for .wordpress — the provision that would otherwise require the registry to treat all registrars equally — signaling an intent to operate the Automattic WordPress domain as a closed, brand-controlled namespace.

Who Is Affected by the Automattic WordPress Domain Application

The Automattic WordPress domain bid touches several constituencies:

• The WordPress community at large. If granted as a closed TLD, .wordpress would put the Automattic WordPress domain entirely under Automattic’s control — who can register, at what price, under what policies. Belcastro said policies governing the use of .wordpress would be published before any launch, but the community has not yet seen them. Peterson’s call for public comment is aimed squarely at developers, hosts, and contributors.
• The WordPress Foundation. The Foundation owns the trademarks that the application leans on. Its oversight role under the 2010 license agreement is now entangled with a registry application it is not named in. How the Foundation responds during ICANN’s comment and objection periods will shape the outcome.
• WordPress businesses and hosts. Companies building on the WordPress name — hosts, agencies, plugin shops — have a direct interest in whether .wordpress becomes a gated brand asset or remains unavailable. The contested strings (.human, .pop, .pod, .lab, .gen) already pit Automattic against Hostinger, Aruba, and Squarespace in head-to-head fights.
• Domain investors and developers. The .php backup application is the sleeper story: Automattic is the sole applicant, and an open .php registry aimed at WordPress developers could become a genuinely useful namespace — project sites, package homes, documentation, developer portfolios — if the .vibe contest pushes Automattic to switch.

Why the Automattic WordPress Domain Bid Matters

The Automattic WordPress domain application matters because it sits at the intersection of two long-running tensions. The first is governance: the WordPress trademark has been held by the independent Foundation since 2010 precisely to separate community ownership from corporate control. A closed .wordpress registry operated by Automattic’s subsidiary — with a Code of Conduct exemption — would concentrate a new form of control over the name in corporate hands, even while the trademark itself stays with the Foundation. Whether that concentration of the Automattic WordPress domain is appropriate is exactly what ICANN’s public comment process exists to adjudicate, which is why Peterson’s analysis urges community participation rather than assuming the outcome.

The second tension is commercial. Automattic already operates .blog with roughly 375,000 registrations — proof that it knows how to run a registry. The 16-string portfolio behind the Automattic WordPress domain bid, from .matt to .woo to .tumblr, reads as a brand-moat strategy: lock up the namespaces adjacent to your products before anyone else does. The uncontested five (.jazz, .matt, .tumblr, .woo, .wordpress) are the dot-brand plays; the contested eleven are optionality. And the .php application — mission-stated as a home for WordPress developers — suggests Automattic is thinking about developer mindshare as a registry asset, not just brand defense.

There is also a procedural clock running. Applicants can switch to replacement strings until October 21, ICANN’s comment and objection periods will follow, and contested strings may head to auction. This story is in its first inning.

What to Do Now About the Automattic WordPress Domain News

Most site owners do not need to act — but the interested should engage:

1. Read Peterson’s analysis. Kellie Peterson’s Medium post (“Automattic Wants .wordpress. It Doesn’t Own WordPress”) is the clearest independent check of the application against ICANN’s rules. If you build on WordPress professionally, it is worth your time.
2. Watch ICANN’s public comment period. When the input period opens, developers, hosts, and contributors can file comments on the .wordpress application — including on the closed-registry model and the Code of Conduct exemption. This is the formal channel for community voice.
3. Do not buy “pre-registration” offers. No Automattic WordPress domain registrations exist yet, and none can be sold. Any offer to pre-register or reserve one today is at best speculative and at worst a scam.
4. Track the .php backup. If you are a developer, the .php application is the one to watch: Automattic is the sole applicant, and a switch from .vibe would create a real new namespace for project sites and portfolios.
5. Note the October 21 switch deadline. Automattic’s replacement-string decisions — .freelance, .php, .task, .rap — will be locked after this date, clarifying which strings are truly in play.

Automattic WordPress Domain: Frequently Asked Questions

Did Automattic apply for the .wordpress domain?
Yes. The Automattic WordPress domain application was filed through its Knock Knock WHOIS There LLC subsidiary as one of 16 strings in ICANN’s 2026 new-gTLD round, revealed October 7. It is the sole applicant for .wordpress.

Does Automattic own the WordPress trademark?
No. The WordPress Foundation owns the WordPress trademarks. Under a 2010 agreement, Automattic holds an exclusive, perpetual commercial license to use and sub-license them, subject to the Foundation’s oversight. Automattic’s Head of Domains confirmed this has not changed.

What does “closed” registry mean for .wordpress?
Automattic is seeking an exemption from ICANN’s Registry Operator Code of Conduct, which would let it operate the Automattic WordPress domain as a brand-controlled namespace rather than selling domains neutrally through all registrars. Usage policies would be published before any launch.

When could .wordpress domains become available?
Not soon. ICANN’s evaluation, comment, and objection processes run for many months, and contested strings can go to auction. Watch the October 21 replacement-string deadline and the opening of ICANN’s public comment period for next milestones.

Conclusion

The Automattic WordPress domain bid is a story about names and who controls them. On paper, it is a routine dot-brand application: a company that runs .blog wants the Automattic WordPress domain plus .woo and .tumblr too. In context, it is a governance question — whether the most valuable name in the WordPress ecosystem should become a closed corporate registry when the trademark itself was deliberately placed with an independent Foundation sixteen years ago. The facts on the Automattic WordPress domain are public, the comment period is coming, and the community’s voice is explicitly invited. Whatever ICANN decides, the .php sleeper application may end up mattering more to working developers than the headline string. For site owners, the practical lesson is simpler: the domain system keeps evolving, and the businesses that thrive are the ones with a team watching it for them. Qamar Digital Ventures LLC‘s website care plans include exactly that kind of watchful maintenance — Want to follow the Automattic WordPress domain story as it develops? contact us — we track the changes that affect your site. Visit https://qamardigitalventuresllc.com/ to see what’s included.

Sources

• Automattic Applies for Closed .wordpress Domain — The Repository
• WordPress maker Automattic applies for 16 top level domains including .matt — Domain Name Wire
• Automattic stakes claim to 16 new domain extensions, 11 of them contested — HostingDiscussion
• Automattic Wants .wordpress. It Doesn’t Own WordPress — WPNews.io