A New Home: HTMLvault is now htmlvault.com

We've acquired the htmlvault.com domain. Thanks to early supporters and steady growth, the product now lives on its .com home. Existing links and analytics carry over unchanged; a few connection details need a one-time update. Check your inbox for the full announcement, and use this page as the reference for what changed and what to do.

What changed

The application, marketing site, API, and MCP endpoint have all moved from htmlvault.com to htmlvault.com. The old domain redirects for a transition period, but you should update anything that stores or calls the domain directly so nothing breaks when the redirect is retired.

What you need to do

Most of this is a one-time cleanup. Work through the list once and you're done.

• Re-register your passkey. Passkeys are bound to the domain they were created on, so a passkey enrolled on htmlvault.com won't work on htmlvault.com. Sign in and enroll a new passkey under the new domain. This is expected browser behavior, not a bug — passkeys are scoped to a site by design.
• Update your MCP connection. Point your MCP client (for example, Claude) from the htmlvault.com endpoint to the equivalent htmlvault.com endpoint. Your API key and tools (list_links, get_link, create_link, and the rest) stay the same — only the host changes.
• Update any hard-coded API base URLs. If you call the REST API directly, or through Zapier, Clay, ChatGPT, or Gemini, swap htmlvault.com for htmlvault.com in your stored base URL.

What stays the same

Nothing you've already shipped needs to be touched.

• Existing links keep working. Every link you've created still resolves, and its security settings — expiry, password, retention window — are unchanged.
• Analytics carry over. All historical views, unique visitors, geo, device, referrer, scroll depth, and channel attribution stay attached to their links.
• Your account, plan, and API keys are the same. No re-purchase, no re-provisioning.

Questions

If something looks off after the move — a passkey that won't enroll, an MCP client that can't connect — email support@htmlvault.com and we'll sort it out. For most teams, updating the MCP endpoint and re-enrolling a passkey is the whole job.