A custom domain changes recipient-facing HummingDeck URLs from the standard host to a branded subdomain such as docs.yourcompany.com.
You connect the subdomain in Workspace settings and add one DNS record. HummingDeck checks the record, issues the certificate and switches your share links. Existing HummingDeck links keep working throughout.
Choose the subdomain
Use a subdomain that recipients will recognize, such as docs.yourcompany.com or deals.yourcompany.com. Root domains such as yourcompany.com cannot hold the required record, so they are not supported. Subdomains beginning with app., such as app.yourcompany.com, are not available yet; choose docs. or share. instead.
Before you start, confirm:
- you or a colleague can edit DNS for the parent domain;
- the subdomain is not already used by another service;
- your team knows whether any existing branded links need to keep working.
Connect the domain
Custom Domain
docs.acme.com
Waiting for the DNS record
- 1
Add this DNS record
Create a CNAME record at your DNS provider and leave the TTL on its default. DNS changes can take up to an hour to show up.
- Type
CNAME- Host / Name
docsCopyIf your provider requires the full hostname, enter docs.acme.com.
- Target / Value
hd-4f2a9c1e7b3d5a60.customers.hummingdeck.comCopy
- 2
Certificate
Certificate issuance can take an hour or longer. Setup continues automatically in the background.
- 3
Live
Status updates automatically. You can leave this page and come back.
Open Workspace, scroll to Custom Domain, enter the subdomain and select Connect domain. Only the workspace owner can do this. HummingDeck reserves the subdomain for your workspace and shows the record to add:
| Field | Value |
|---|---|
| Type | CNAME |
| Host / Name | Copy the name shown in settings, for example docs |
| Target / Value | The full target shown in settings, ending in customers.hummingdeck.com |
When your DNS zone is known, Host / Name shows only the part before it: docs for docs.yourcompany.com, or docs.eu for docs.eu.acme.com in the acme.com zone. If your provider requires the full hostname, use the value in the hint directly below this field. When the zone cannot be identified, the field shows the full hostname instead.
Add the record with your DNS provider and leave the TTL on its default. If the name already has A or AAAA records, remove them first.
Copy the value exactly as shown. It is unique to this connection, so a target from another workspace or an earlier setup will not work.
Follow the setup
Settings show three steps: the DNS record, the certificate, and the switch to live. Once the record is verified, the first step shows DNS record confirmed. The current step is marked Pending in amber until it completes. Status updates automatically, so you can leave the page and come back. Select Refresh status to load the latest progress.
DNS changes can take up to an hour to appear. Certificate issuance can take an hour or longer after DNS verification. Setup continues automatically in the background. When the domain shows Active, links you copy from HummingDeck use it, and links you sent earlier keep working.
If a step cannot complete, settings say why:
- No CNAME record found yet. The record is missing or has not propagated.
- The CNAME record points somewhere else. Set the value exactly as shown.
- This name already has A or AAAA records. Remove them so the CNAME record can take effect.
- The certificate could not be issued. A CAA record on your domain may block
pki.googorletsencrypt.org. Allow them, then wait for the next check.
If setup stops after a longer wait, fix the record and select Retry. If no record appears within 14 days, automatic removal begins. Once the Connect domain form returns, you can connect the domain again using the new CNAME value shown in settings.
HummingDeck keeps checking an active domain. If the record changes later, settings show Needs attention together with the record to restore.
Test the recipient experience
After the domain shows Active:
- Open a document link on the custom domain in a private browser window.
- Open a Room link on the custom domain.
- Test the access mode you normally use.
- Check downloads and any HTML content you plan to share.
- Confirm that the browser shows no certificate warning.
Choose a custom Room URL
Once your custom domain is active, you can choose a readable URL for a Restricted Room link, such as https://docs.yourcompany.com/client-a. Your workspace must have access to custom domains. Members who can manage the Room can set the name.
In Rooms, choose Restricted when creating a Room or generating another link, then fill in Custom URL. For an existing link, open its settings in the Room's Links tab. Enter 3–50 letters, numbers, or single hyphens between words. Names are saved in lowercase; application route names and previously claimed names may be unavailable.
The custom URL stays in the browser while the recipient opens the Room and verifies their email. The same approved-email rules and viewing history apply. Each link can have one custom URL, and Copy original link keeps the original random URL available.
To rename the URL, change the name and select Save. To remove it, clear the field and save. The previous custom URL stops working; the original link keeps working under its existing access restrictions. A name change does not revoke an already verified recipient's access.
Change or remove a domain
Remove in the Custom Domain section disconnects the domain, including a setup that has not finished. Links on that domain stop working right away, and the same links on the standard HummingDeck host keep working. Settings show Removal in progress until automatic removal finishes. This can take several minutes or longer. The page updates automatically, and Refresh status loads the latest progress.
When the Connect domain form returns, you can connect the same subdomain again or choose a different one. Every new connection has a new CNAME value. Add the value shown in settings, replacing the previous value if you reuse the subdomain. If you move to a different subdomain, send recipients links on the new domain.
Removing the domain does not delete DNS records. Delete the old CNAME record with your DNS provider if you will no longer use that subdomain with HummingDeck.
Domains that HummingDeck Support set up for you keep working as before. Contact Support before changing or removing one of them.