namehawk

How to find available .com domains in software release notes

Updated · Edited and reviewed by the NameHawk editor before publishing. How we make these guides

Fast-moving platforms name every feature they ship, and developers adopt those names immediately in docs, posts and products of their own.

When several platforms ship the same kind of feature under similar names, a category is forming, and its vocabulary is up for grabs.

Where to look

Why this works

Changelogs are the closest thing to a live feed of product vocabulary. Because platforms compete, they also converge: when several ship similar features, the names settle into a shared category term within months.

Scanning two or three competitors' changelogs side by side shows that convergence directly, and the shared term is usually the one worth owning.

Step by step

  1. 1

    Follow the changelogs of the platforms that set the pace in your field; AI and developer tools move fastest.

  2. 2

    Scan each changelog page: one page covers months of releases.

  3. 3

    Compare across platforms: terms several of them share point to a category.

  4. 4

    Skip product and model names; keep the feature vocabulary.

  5. 5

    Check the .coms of the category terms.

What NameHawk found

A selection of the words NameHawk flagged as new on these pages when they were scanned on September 19, 2026. They are candidate words, not names confirmed available: that scan didn't check their .coms, and some are already registered. Scan the page yourself to see what's there today and which .coms are available now.

the OpenAI API changelog

  • allowlist
  • webhooks
  • sandboxes
  • tool calling
  • agentic workflows
  • prompt caching

the Anthropic API release notes

  • extended thinking
  • context editing
  • memory store
  • hosted sandboxes
  • fast mode

the GitHub changelog

  • agentic
  • public preview
  • usage metrics

What makes a good find here

  • Feature vocabulary shared across platforms ('tool calling', 'sandboxes').
  • Phrases that describe a way of working ('agentic workflows').
  • Developer terms on their way to general use.

What to watch out for

  • Product, model and plan names are trademarks.
  • Changelogs mention deprecated features too; favor what's new.
  • Very technical terms may never mean anything to non-developers.

Check trademarks before you register

  • Search the exact word in USPTO Trademark Search for US marks, and in the WIPO Global Brand Database for international and other national registers.
  • A trademark holder can challenge a domain it sees as an abusive registration under ICANN's Uniform Domain-Name Dispute-Resolution Policy (UDRP), a fast administrative process run by approved providers. See ICANN's UDRP page.
  • NameHawk can't tell you whether a word is protected. It only demotes words written like names. Ask a trademark lawyer before you build on a name that matters to you.

Common questions

Aren't these words too technical?
Some are. The ones worth registering describe a way of working rather than an implementation detail, and those tend to spread past developers.
How far back should I look?
A changelog page usually covers months. Compare the oldest and newest entries to see which vocabulary stuck.

The other nine methods

Scan a page for new words