Your server. Your address.

Pro subscribers can serve a deployed drop on their own domain, with HTTPS set up automatically. It works for public and private drops alike: a private drop keeps its code private while its server answers on your domain.

Connect a domain

• Deploy the drop first: a domain serves the running drop.
• Open Share, then the Domains tab, and enter the domain (for example api.example.com or example.com).
• jsdrop shows two DNS records to add at your DNS provider: a TXT record that proves you own the domain, and a record that points the domain at jsdrop.
• Once both records are found, jsdrop requests a certificate and the domain goes live, usually within a few minutes. The Domains tab shows progress and re-checks on its own.

The records

TXT    _jsdrop.api.example.com   jsdrop-verify=<token>
CNAME  api.example.com           <id>.domains.jsdrop.com

Pointing the domain

Every domain gets its own target hostname, like a1b2c3d4.domains.jsdrop.com, never an IP address, so jsdrop can move servers without you touching DNS. For a subdomain such as api or www, add a CNAME to that target. For a root domain, use ALIAS or ANAME, or a CNAME if your DNS provider flattens it at the root (Cloudflare does). If your provider supports none of these, connect a subdomain instead.

When a domain stops serving

A domain stops serving if the drop is stopped or deleted, or if the Pro subscription ends. A domain can be connected to jsdrop or HTMLDrop, not both. Domains that are never verified are removed after 14 days.