Project and domains
Project name, branded subdomains and the destructive delete zone.
Project settings
“Settings” tab: on the left “Home”, “Subdomains”, “Custom domains”, “API keys” and team access.
- Open “Settings”.
- On “Home” change the project name and description.
- Save changes in the header/form UI.
Project settings: name, description, delete.
Subdomains
A subdomain gives an address like https://name.<service-domain>/…. Subdomains belong to the account and can be used across projects.
- “Settings” → “Subdomains” → “+ Subdomain”.
- Set a name → “Create”.
- In the link builder select this subdomain.
- Badges: “here” — used by links in the current project; “elsewhere” — in other projects; “deleted · can restore” — soft delete.
- After deleting a subdomain, links on it stop working; the card shows “Subdomain deleted”.
- “Restore” brings the subdomain back; links work again except those turned off manually.
Subdomain list and create.
WARNING: “Delete subdomain” immediately breaks public URLs on that name until you restore it. Check which links depend on it first.
Custom domains
Your own FQDN (for example go.company.eu) instead of a service-zone subdomain. After TXT ownership proof and a wildcard CNAME, links open on your domain.
- “Settings” → “Custom domains” → “+ Domain” → enter the FQDN without https://.
- In DNS add the ownership TXT record (step 1 in the guide).
- Add a CNAME for the `*.your-zone` pattern → the service redirect edge (step 2).
- Click “Verify DNS”. When status is “Active”, pick the domain in the link builder.
“Custom domains” section: list, statuses, “+ Domain”.
Step 1 — ownership (TXT). One TXT record is required. Host is usually `_urlshortener.{your-domain}` (some registrars want only `_urlshortener` in Name, without the zone). Value: `urlshortener-verify=<token>` from the guide. TTL: 300–3600.
| Field | Value (example for go.company.eu) |
|---|---|
| Type | TXT |
| Host / Name | _urlshortener.go.company.eu |
| Value | urlshortener-verify=a1b2c3d4-… |
| TTL | 300 (recommended) |
DNS panel: adding TXT `_urlshortener…` with the token from the guide.
Step 2 — routing (CNAME). A CNAME on the apex (`@`) is not allowed at most registrars. Use a pattern: Host `*.company.eu` → Value `edge.kkoroch.ru` (exact host is in the guide). The pattern covers go.company.eu and other zone subdomains. If you register the apex (company.eu), you may also need A/ALIAS on `@` — see the in-app hint.
| Domain type | Type | Host | Value |
|---|---|---|---|
| Subdomain go.company.eu | CNAME | *.company.eu | edge.kkoroch.ru |
| Apex company.eu | CNAME | *.company.eu | edge.kkoroch.ru |
| Apex without www (@), optional | A / ALIAS | @ | IP / alias edge |
DNS panel: wildcard CNAME `*.zone` to the redirect edge.
- Service subdomain and custom domain are mutually exclusive for one link.
- Statuses: “Awaiting TXT” → “CNAME needed” → “Active”. Only Active can be selected in the builder.
- Deleting a domain deactivates links on it (status “Domain deleted”).
- Custom-domain limit is set by the plan (often 0 on Free+).
- Between DNS checks — ~15 s pause.
Domain in “Active” status after a successful DNS check.
WARNING: DNS records often take effect with delay (minutes, sometimes hours due to TTL and resolver cache). If after “Verify DNS” status is not yet “Active” — wait and retry; re-saving records is usually unnecessary.
WARNING: You cannot register the `*.company.eu` pattern as the custom domain itself — only a concrete FQDN. The routing record is a separate wildcard CNAME at your registrar.
After activation, pick the domain under “Custom domains” in the link builder. The public URL looks like https://go.company.eu/promo.
API keys
“API keys” lets you issue scoped keys for integrations (CRM, scripts, CI), limit permissions and revoke access.
- “Settings” → “API keys” → “Create key”.
- Set an integration name and permissions: “Full access” or pick specific scopes.
- Save the secret key immediately after creation — it is not shown again.
- To change name or permissions use “Edit”; to disable — “Revoke key”.
- The key is bound to the current project (scope) and does not work outside it.
- Rotate by revoking the old key and creating a new one: the secret cannot be changed via edit.
- If the project key limit is reached, the UI shows the plan restriction.
Choosing permissions when creating an API key.
WARNING: the secret key is shown once. Do not put it in client-side JavaScript or public repos; store it in env vars or a secrets manager.
Delete project
At the bottom of settings — “Delete project” with a long confirmation.
- “Settings” → delete zone → “Delete project”.
- Wait for the confirmation timer (~10 s) → “Delete forever”.
WARNING: deleting a project permanently destroys its folders and links. Account subdomains are kept. Do not confuse with deleting a single link or folder.