Use a dedicated hostname
Choose a hostname such as go.example.com rather than a domain already serving a website or application. Add it in the URLMe console, then publish the exact DNS records shown for the workspace.
Wait for both ownership and certificate readiness
DNS verification proves control of the hostname. Certificate activation makes HTTPS delivery possible. Do not begin distributing branded links until the console reports the domain as active.
Choose an alias on your domain
The custom hostname serves short-link redirects, not API requests. Growth and Scale continue creating links through api.urlme.link, include the active hostname in domain, and may add a case-sensitive customCode. URLMe returns HTTP 409 if that alias is reserved or already in use on the hostname.
{
"url": "https://example.com/products/summer-release",
"domain": "go.example.com",
"customCode": "summer-release"
}Plan for DNS changes
Removing or replacing verification records can interrupt certificate renewal or delivery. Treat the displayed records as production infrastructure and include them in DNS change reviews.