Attry creates this for every workspace. You can create deep links immediately without touching DNS.
Use this when you want links to live on your own domain instead of the Attry-managed subdomain.
Only custom domains point here. Your default Attry Link subdomain is managed by Attry automatically.
Quick setup
The shortest path from a clean domain to verified mobile deep links.
Use the default domain
Open Settings to see the Attry-managed subdomain assigned to your workspace, such as luma.attry.link.
Decide if you need branding
If the default subdomain is enough, keep using it. If you want branded links, choose a subdomain you own.
Add the CNAME
Create a CNAME for the branded subdomain and point it to links.attry.link.
Verify and create links
Return to Settings, click Check, then select the verified domain when creating deep links.
DNS record reference
What Attry creates automatically
When a workspace is created, Attry reserves one managed subdomain under attry.link. It looks like luma.attry.link or another short generated name. This domain is ready for deep links immediately: Attry manages routing, TLS, redirects, deferred matching, and analytics for it.
When to connect a custom domain
A custom domain is optional. Add one when your team wants branded links such as go.yourapp.com, link.yourapp.com, or app.yourbrand.com. The user sees your domain, while Attry still handles deep link routing, store fallback, deferred deep links, and event attribution behind the scenes.
How to connect a custom domain
Add the custom domain in Attry Settings first, then create a CNAME record at your DNS provider. The custom domain should point to links.attry.link. Do not point customer-owned domains to attry.io, app.attry.io, api.attry.io, or to your default workspace host.
Cloudflare setup
In Cloudflare, add a CNAME record for the subdomain only. For example, if you want go.yourapp.com, create a record named go and set the target to links.attry.link. Keep the proxy status as DNS only so Attry can verify the record and serve TLS correctly.
Verification and TLS
After the CNAME exists, click Check in Attry Settings. Attry verifies that the domain resolves to links.attry.link and prepares it for HTTPS. Pending domains are checked in the background about every 5 minutes, but DNS propagation can still take longer depending on the provider.
Use a subdomain, not your root domain
Use a dedicated subdomain such as go.example.com instead of the root domain example.com. This keeps your marketing site, email records, and app link routing separate, and avoids DNS providers that do not support normal CNAME records at the root.
Troubleshooting
Domain stays pending
DNS may not have propagated yet, or the CNAME was added on the wrong host. Check that the exact subdomain points to links.attry.link.
Wrong CNAME target
Replace the current target with links.attry.link. Do not point a custom domain to attry.io, app.attry.io, api.attry.io, or to your default workspace host.
SSL or browser protocol errors
Keep the DNS record as DNS only, then run Check in Attry. TLS is issued after the domain is allowed and verified.
Apex domain does not accept CNAME
Use a subdomain such as go.example.com, link.example.com, or app.example.com instead of example.com.
Recommended DNS lookup
Use this to confirm what the public DNS resolver sees.
dig CNAME go.example.com +shortlinks.attry.link.What domain do free Attry links use?
Every workspace gets a managed subdomain under attry.link, such as luma.attry.link. The exact name is generated automatically by Attry and appears in Settings.
What is links.attry.link?
links.attry.link is the CNAME target used only when you connect a customer-owned custom domain. It is not the domain you share with users.
How often does Attry check DNS?
Attry checks a custom domain immediately after it is saved, when you click Check in Settings, and in the background roughly every 5 minutes while the domain is pending.