Proof of control
A generated DNS token proves ownership before a hostname can serve workspace routes.
Branded domains
Make every shared link recognizable before it is opened.
A dedicated short domain makes every campaign link look like it belongs to your brand. Gods.ly shows the exact DNS record to add and keeps verification, HTTPS, and link status visible.
Connect a domainOne verified owner
A domain can belong to only one workspace, preventing conflicting claims.
Clear setup status
See whether a domain is waiting, verified, failed, disabled, or removed.
A domain is more than a settings field
DNS propagation, ownership changes, certificates, and renewal can all affect links already in circulation. A managed status gives teams a place to see the current condition and the next safe action.
Gods.ly normalizes hostnames and blocks platform-reserved domains before a record is created.
Verification is specific and repeatable
The domain screen provides the exact record name and token value required for verification. Re-checking is explicit, so a user can retry after DNS propagation without creating another domain.
A failed verification returns an actionable state rather than pretending the domain is ready.
The domain stays with its workspace
Once verified, the domain is attached to one workspace. Gods.ly still checks the member’s role, the link status, and whether a short name is available before publishing.
Review the links attached to a domain before disabling it, and keep the domain registration current while those links remain in circulation.
Common questions
What teams ask before they start.
Why does DNS verification take time?
DNS providers cache records for a set amount of time. Gods.ly keeps the domain pending until the required ownership record can be seen publicly.
Can another workspace claim my domain?
No. A verified domain has one owner in Gods.ly and cannot be added to another workspace.
Start with a real workflow