namehawk

How to find available .com domains in technical white papers

When a new technology is designed, its white paper or specification has to name everything in it: the parts, the processes, the roles. Those names become the vocabulary everyone who builds on the technology uses.

Standards documents from bodies like the W3C and IETF work the same way, and they're published openly, long before the products that use them.

Scan the Ethereum white paper

Where to look

Why this works

Specifications are unusually good sources because they're written to be precise: every term is defined once and then used consistently, so the words that matter repeat throughout the document. That repetition is exactly what NameHawk's ranking rewards.

The catch is that specs also contain code. Property names, parameters and data types read like words to a scanner but mean nothing off the page, so expect to discard a good share of any spec's results.

Step by step

  1. 1

    Find the white paper or draft specification for a technology you expect to grow.

  2. 2

    Use the HTML version: NameHawk reads web pages, not PDFs.

  3. 3

    Scan it and look first at the definitions and terminology sections, where new nouns are introduced.

  4. 4

    Favor the generic concepts over the named protocol or product.

  5. 5

    Check the .coms of the terms that would still make sense to someone outside the field.

What NameHawk found

A selection of the words NameHawk flagged as new on these pages when they were scanned on 2026-09-19. Pages change, and so does availability: scan them yourself for what's there today.

the Ethereum white paper

  • hashpower
  • onchain
  • multisig
  • merkle tree
  • smart contracts
Scan this page

the W3C Web Authentication spec

  • credential record
  • backup eligibility
  • correlatable
  • authorization gesture
  • resident key
Scan this page

the W3C Decentralized Identifiers spec

  • verification method
  • key agreement
  • trustless
  • service endpoint
  • dereferencer
Scan this page

What makes a good find here

  • Concept words that will outlive the specific protocol ('onchain', 'hashpower').
  • Two-word phrases that name a role or property people will talk about ('verification method', 'key agreement').
  • Terms from specs that are headed for wide adoption, like authentication and identity standards.

What to watch out for

  • Specs are full of code identifiers written as words (camelCase names flattened by the scan). Skip anything that only makes sense as code.
  • Protocol, product and token names are usually trademarks.
  • Some standards never take off; favor ones with real implementations.

Common questions

What about white papers published as PDFs?
NameHawk reads web pages, not PDFs. Many projects publish an HTML version as well; use that, or paste the key section into a page you control.
Is it too late once a standard is final?
Often not. Standards can take years to reach products, and the vocabulary only spreads when implementations do.

The other nine methods

Scan a page for new words