Automattic Wants .Wordpress. It Doesn’t Own WordPress.  🔗 **Source:** [Automattic Wants .Wordpress. It Doesn’t Own WordPress.](https://medium.com/@kelliepeterson/automattic-wants-wordpress-it-doesnt-own-wordpress-d9e6be3f3a45) > [!note]+ Document Notes > --- > tags: ["wordpress-governance", "domain-names", "icann", "trademarks", "public-interest"] > author: "Kellie Peterson" > source: "Medium" > reference: "https://medium.com/@kelliepeterson/automattic-wants-wordpress-it-doesnt-own-wordpress-d9e6be3f3a45" > date created: 2026-10-08 > --- > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > # 🏷️ Automattic Wants .wordpress. It Doesn’t Own WordPress. > ## 🧭 Table of Contents > - [[#📝 Summary|📝 Summary]] > - [[#📖 Main Content|📖 Main Content]] > - [[#🗒️ Notes|🗒️ Notes]] > - [[#📚 References|📚 References]] > - [[#🗣️ Paraphrase|🗣️ Paraphrase]] > - [[#📰 Newsletter|📰 Newsletter]] > - [[#✅ Action Items|✅ Action Items]] > - [[#🧪 Hypotheses|🧪 Hypotheses]] > - [[#📊 Methodology|📊 Methodology]] > - [[#❓ Questions|❓ Questions]] > - [[#🔮 Future Research|🔮 Future Research]] > - [[#💡 Implications|💡 Implications]] > - [[#🧠 Learning Styles Assessment|🧠 Learning Styles Assessment]] > - [[#📊 Accessibility Assessment|📊 Accessibility Assessment]] > - [[#🌍 DEIB Assessment|🌍 DEIB Assessment]] > - [[#✅ Logical Validity|✅ Logical Validity]] > - [[#🛡️ DARVO Analysis|🛡️ DARVO Analysis]] > - [[#🎯 Conclusion|🎯 Conclusion]] > - [[#🔄 Refactor Appendix|🔄 Refactor Appendix]] > ## 📝 Summary > Peterson argues that Automattic’s reported application for a closed .wordpress namespace deserves community scrutiny because the WordPress name represents an open-source project with stakeholders outside Automattic. Her strongest distinction separates a registry Code of Conduct exemption from formal .Brand eligibility. Her conclusions about common control, license termination, and future marketplaces require more evidence than the filing excerpts alone provide. > ## 📖 Main Content > A top-level domain is a namespace such as .blog; an application requests control of that namespace, not merely one website address. Peterson identifies Knock Knock WHOIS There, LLC as the applicant and says its proposed registrations are restricted to the operator and affiliates. She then separates four questions: who owns the WordPress trademark; who licenses it commercially; who may operate the registry; and which ICANN evaluation track applies. Keeping those questions separate makes the governance concern testable. > Her argument moves from regulatory criteria to institutional legitimacy: a corporate registry might use the project’s name to signal authority even without owning the trademark. That is a proposed risk, not evidence that certification services or a plugin marketplace already exist. The published application was not independently retrieved in this run; the article’s excerpts remain attributed to Peterson. > ## 🗒️ Notes > Verified context: ICANN Module 7 §7.4.4 lists exclusive operator/affiliate use, no transfer to unaffiliated third parties, and public-interest protection as exemption criteria. §7.4.1 also requires non-generic eligibility. §7.3 treats .Brand eligibility separately. This supports the procedural distinction; it does not settle this application’s outcome. > WordPress.org’s security page attributes the WordPress trademark to the WordPress Foundation. The license terms, present board composition, application-specific affiliations, registry transition clauses, and article’s November 17, 2026–March 16, 2027 dates were not independently verified. Treat those dates as reported dates to recheck before action. > ## 📚 References > - [Captured source](https://medium.com/@kelliepeterson/automattic-wants-wordpress-it-doesnt-own-wordpress-d9e6be3f3a45) — read from Reader, 2026-10-08. > - [ICANN](https://www.icann.org/) — linked in source; not necessarily independently opened. > - [full list of 2026 top-level domain applications](https://newgtldprogram-aps.icann.org/applications) — linked in source; not necessarily independently opened. > - [ICANN Reveals 2026 Round Applications](https://www.icann.org/en/announcements/details/icann-reveals-2026-round-applications-for-new-generic-top-level-domains-07-10-2026-en) — linked in source; not necessarily independently opened. > - [2026 Applicant Guidebook, Module 7](https://newgtldprogram-2026-agb.icann.org/en/11-module-7-string-and-application-evaluation-procedures.html) — linked in source; not necessarily independently opened. > - [2026 Applicant Guidebook, full PDF](https://newgtldprogram.icann.org/sites/default/files/documents/new-gtld-program-2026-round-applicant-guidebook-current-en.pdf) — linked in source; not necessarily independently opened. > - [2026 Base Registry Agreement](https://itp.cdn.icann.org/en/files/registry-agreements/base-registry-agreement-12-03-2026-en.pdf) — linked in source; not necessarily independently opened. > - [LWN on the WordPress Foundation and trademark](https://lwn.net/Articles/991771/) — linked in source; not necessarily independently opened. > - [.blog on ICANNWiki](https://icannwiki.org/.blog) — linked in source; not necessarily independently opened. > - [ICANN Module 7](https://newgtldprogram-2026-agb.icann.org/en/11-module-7-string-and-application-evaluation-procedures.html) — independently consulted for evaluation criteria. > - [WordPress security](https://wordpress.org/about/security/) — independently consulted for disclosure and coordination context. > ## 🗣️ Paraphrase > - P1: The 2026 application publication prompts Peterson to inspect .wordpress. > - P2: She reports that Automattic applied for that string. > - P3: She discloses prior employment and domain-industry experience, including possible personal bias. > - P4: She identifies the subsidiary applicant and its proposed closed registration model. > - P5: She explains why a registry with only affiliated registrants might seek a conduct exemption. > - P6: She says classification as non-generic matters for an exclusive namespace. > - P7: She separates Foundation trademark ownership from Automattic’s commercial license. > - P8: She enumerates the three conduct-exemption tests. > - P9: She contrasts those tests with the trademark requirements of the brand track. > - P10: She predicts evaluators will not flag ownership under the exemption track; that prediction exceeds a quoted checklist. > - P11: She proposes affiliation as a possible route to brand eligibility. > - P12: She points to a contract definition and a historical board report as evidence of overlapping governance. > - P13: She frames nonprofit independence and common control as conflicting public claims. > - P14: She anticipates an objection that new brand domains attract little use. > - P15: She says regulatory acceptance itself would create an institutional record. > - P16: She describes ten-year contract and renewal terms. > - P17: She describes a conditional restriction on transferring a closed registry. > - P18: She predicts license changes would leave the registry in place; a complete legal analysis is still needed. > - P19: She lists possible future uses while acknowledging none exists today. > - P20: She supplies reported string-confirmation and community-input dates. > - P21: She identifies public interest and generic-string classification as grounds for scrutiny. > - P22: She recommends reading the filing, commenting, and examining community-objection requirements. > - P23: She prefers raising concerns before the reported input period closes. > ## 📰 Newsletter > Draft for review; not sent or published. > A domain application is a request, not a completed delegation. [Peterson’s analysis](https://medium.com/@kelliepeterson/automattic-wants-wordpress-it-doesnt-own-wordpress-d9e6be3f3a45) asks WordPress contributors to inspect the proposed .wordpress registry and distinguish trademark ownership from ICANN’s exemption and brand tests. Start with the filing, then compare its assertions against [Module 7](https://newgtldprogram-2026-agb.icann.org/en/11-module-7-string-and-application-evaluation-procedures.html). Keep any public-interest argument tied to a documented effect on hosts, contributors, or users. > ## ✅ Action Items > All entries below are analyst suggestions, not work assigned by the author. No external messages, production changes, or Things imports occur. > ### DevR 📄 **Full text:** [[Full Document Contents/Articles/Automattic Wants .Wordpress. It Doesn’t Own WordPress..md|Automattic Wants .Wordpress. It Doesn’t Own WordPress. by Kellie Peterson]] ## Highlights - Here’s what I didn’t expect when I opened ICANN’s 2026 Applicant Guidebook. The Code of Conduct exemption has exactly three tests, set out in Section 7.4.4. Every registration must belong to the registry operator or its affiliates, for their exclusive use. None can be sold or handed to anyone outside that group. And applying the Code must not be “necessary to protect the public interest.” ([View Highlight](https://read.readwise.io/read/01m4epm80wshebzdjh1tpkjdzf)) - Note: Public interest shapes exemption eligibility — generated analysis; source paragraph remains verbatim. - Tags: xref, atom/literature/h2 - Trademark ownership isn’t one of them. ICANN runs a separate track for brand TLDs, called Specification 13, which requires a registered trademark verified through the Trademark Clearinghouse. But the Guidebook says plainly that an applicant can get the Code of Conduct exemption without qualifying for brand status. ([View Highlight](https://read.readwise.io/read/01m4epmekw67yrdmkawfkgsjtq)) - Note: Code exemption differs from brand eligibility — generated analysis; source paragraph remains verbatim. - Tags: atom/literature/h1, xref - Closed registries get one more protection. Under Section 4.5, a registry that keeps every name for itself and its affiliates, and where no public-interest reason requires a handover, can’t have its TLD moved to a new operator when the contract ends unless it consents. Those are the same conditions the Code of Conduct exemption is built on. ([View Highlight](https://read.readwise.io/read/01m4epmb9s334gjs4ahbpgy60n)) - Note: Closed registries can resist operator transition — generated analysis; source paragraph remains verbatim. - Tags: atom/literature/h3, xref - If you build with WordPress, host it, sell plugins for it, or contribute to core, read the application yourself on [ICANN’s Application Publication System](https://newgtldprogram-aps.icann.org/applications). Comment when the window opens. If hosts and contributors want to go further, ICANN’s rules allow a community objection. It requires showing a clearly delineated community, substantial opposition within it, a string that targets it, and likely detriment. ([View Highlight](https://read.readwise.io/read/01m4epm9k9fd2e1aa6phgstywk)) - Note: Community objections require evidence — generated analysis; source paragraph remains verbatim. - Tags: xref, atom/literature/h3