Skip to content

0027: Primary domain: vaultfold.app

  • Status: accepted
  • Date: 2026-09-29
  • Supersedes: the domain choice in ADR 0015 (the three-origin split stands)

Context

ADR 0015 split the web presence into three origins by trust level and put them on vaultfold.io, chosen over .dev because .dev reads as developer-only. That reasoning cuts the same way against .io: outside developer circles it is unfamiliar, and vaultfold is meant to be sold to teams and businesses, including people who never open a terminal. For a password manager the domain is part of the security story: users are told to trust exactly one name, so it should look reputable to an everyday person and sit on a TLD with a clean abuse record.

Options considered on 2026-09-29 (prices are first-year, per year):

  • .com: the most recognised, but not available at a sensible price.
  • .app: about $15. Widely recognised from app stores and advertising, operated by Google with a low abuse rate, and HSTS-preloaded at the TLD so every name under it is HTTPS-only in browsers with no extra step.
  • .io: about $50. Developer-coded, and its long-term status is uncertain after the Chagos sovereignty transfer (ADR 0015 already flagged this).
  • .security, .protection: about $2,000. Priced for defensive brand registrations, not for a primary domain.
  • Cheap novelty TLDs (.click, .onl and similar): rejected because several appear on high-abuse TLD lists, which hurts both deliverability and the "only trust this name" message.

Decision

vaultfold.app is the primary domain. It was registered on 2026-09-29 through Cloudflare Registrar, and its DNS is on Cloudflare. vaultfold.io was never registered, and no other vaultfold domain is held.

ADR 0015's origins map across unchanged in purpose and policy:

  • vaultfold.app: marketing site and documentation.
  • cloud.vaultfold.app: the hosted service.
  • s.vaultfold.app: share reveal and share request pages.

Every origin still sends Strict-Transport-Security: max-age=63072000; includeSubDomains; preload. Submitting the name to hstspreload.org is unnecessary, since the whole .app TLD is preloaded.

Any other vaultfold domain that is held, now or later, redirects to vaultfold.app. The .com is still worth acquiring if it becomes available at a reasonable price, both for recognition and so that it cannot be used for phishing.

Consequences

  • Every vaultfold.io reference becomes vaultfold.app, and the reverse-DNS identifiers derived from it (io.vaultfold.*) become app.vaultfold.*. The in-flight OpenSpec changes were amended with this ADR; code, tests and the remaining docs follow in the rename-primary-domain change.
  • Because vaultfold.io is not held, anyone could register it. No release, share link, config default or extension ID may point at it, so the rename must land before anything built on those origins ships. Registering vaultfold.io defensively (about $50 a year) would remove that risk, but it is optional once the rename is complete.
  • Registrar renewal and DNS both live in the Cloudflare account, so domain expiry and DNS changes are managed there, not in this repository.
  • Cheap typo and lookalike registrations (for example vaultfolds.app, vault-fold.app) are a defensive option to consider before launch.