Regest

Open Infrastructure for the Independent Web

The phone book
the web forgot
to build.

A decentralised, agent-generated, privacy-preserving directory of every meaningful domain on the independent web — scoped sensibly, resistant to SEO by construction, and runnable by anyone.

DNS but semantic
The problem
is not the
search engine.

The dominant search engines are centralised, surveillance-dependent, and progressively poisoned by SEO optimisation. The independent web — the tools, blogs, niche references, and personal projects that make the web worth having — has become effectively invisible.

Alternatives exist, but they are architecturally identical: still centralised, still operated by a single entity, still dependent on observed queries as a data product.

The missing piece is a discovery layer — one that is decentralised, privacy-preserving by architecture rather than policy, and scoped to the problem it actually needs to solve.

§ 01 — Mechanism

How Regest Works

Seeding from Zone Files

TLD registry zone files provide the complete seed list. No crawl required for initial domain inventory — the namespace is already documented. New registrations appear in zone file diffs automatically.

Agent-Generated Metadata

An agent makes a minimal pass on each live domain: resolve, fetch root, extract title, description, and headings. The output is a structured card describing what the domain is. It cannot be gamed — the site owner didn't write it.

Local Index Query

With the index held locally or synced peer-to-peer, queries are entirely local computation. A query never leaves your device. No intermediary sees what you searched for. Surveillance disappears as an architectural consequence.

Ongoing Maintenance

Maintenance is event-driven, not a global re-crawl. Zone file diffs queue new registrations. Query-time 404s flag domains for recheck. Dead domains drop out naturally. The index stabilises over time.

§ 02 — Design

Core Properties

Domains, Not Pages

The combinatorial explosion of web content comes from recursion within domains. Meaningful distinct domains number in the tens of millions — a bounded, tractable problem. The discovery layer and retrieval layer are separate concerns.

Scope

Privacy by Architecture

Surveillance-based search depends on the query being observed by a centralised intermediary. Remove the intermediary and the query disappears as a data product entirely — not by policy, but by construction.

Privacy

No SEO Surface

The metadata being ranked against was generated by an agent reading the site, not written by the site owner to influence ranking. Keyword stuffing, backlink schemes, and SEO content are irrelevant — none of it is in the index.

Integrity

Uncapturable Infrastructure

Because the indexing methodology is a replicable process rather than a proprietary database, the index cannot be captured or killed. No foundation to defund, no repository to take down. Anyone can reproduce a functionally identical index.

Resilience
§ 03 — Boundaries

Explicit Scope

Regest's usefulness depends on knowing what it isn't for. Platforms already have their own discovery systems. Regest covers the long tail that falls outside them.

Regest Indexes

  • Independent websites, tools, services, and blogs
  • Domains outside platform distribution — the long tail of the web
  • Anything that would benefit from being findable but has no algorithmic amplification

Regest Does Not Index

  • Content behind authentication or login walls
  • Platforms with their own search systems — social media, video, marketplaces, forums
  • Dynamic or user-generated content at platform scale
  • Any URL depth beyond what a site voluntarily provides
§ 04 — State

Project Status

  • Protocol design and scope specification
    Complete
  • Zone-file seeding methodology defined
    Complete
  • Agent metadata extraction tooling
    In progress
  • Index schema and structured record format
    In progress
  • Peer-to-peer sync mechanism
    Planned
  • Local query interface (CLI + browser extension)
    Planned
  • Public tooling release at regest.org
    Planned

Pre-Implementation

Regest is currently a protocol specification, not yet a running system. The design phase is complete. Implementation tooling is underway.

The goal is that anyone should be able to run a full indexing pass independently, produce a compatible index, and share or sync it with others without coordination.

Human curation adds a quality tier on top of the automated baseline — but is not required. The automated agent alone is sufficient to produce a useful and trustworthy index.