Point a subdomain
Create a CNAME record from a subdomain such as feedback.yourdomain.com to the target shown on the Custom domain page, plus a TXT record that proves the domain is yours. Once the domain is verified, Looph issues the certificate automatically; there is nothing to upload or renew.
- 1Open Settings, then Custom domain.
- 2Enter the hostname you want to use, without https:// or a path, and save.
- 3Add both records shown on the page at your DNS provider: the CNAME and the TXT ownership record. If you use Cloudflare, set both to DNS only.
- 4Choose Verify, and check that the status shows Verified and the Certificate card shows Serving with a valid certificate.
The two DNS records
The Custom domain page lists two records, each with a copy button. The CNAME has your hostname as its name and cname.looph.ing as its value; it serves your board and sign-in. The TXT record goes at _looph-verify followed by your hostname, such as _looph-verify.feedback.yourdomain.com, and holds a token issued to your workspace alone. The token appears once you save the hostname, and a different hostname gets a new token.
Verify needs both records the first time. A CNAME that points at Looph without the right TXT value leaves the domain at Pending DNS, because until ownership is proved the domain belongs to no workspace: several can hold it pending, and the first to prove ownership gets it. After that, a save or a Verify from any other workspace answers: Another workspace has already verified this domain.
Use a subdomain. A bare domain such as yourdomain.com cannot carry a CNAME record, and the Hostname field refuses it.
Reading the status and fixing problems
The Domain card shows one of four statuses. Pending DNS means Looph is still waiting for your records, or the CNAME is right and the TXT record is not. DNS not found means no CNAME was found; new records can take up to an hour to appear, so wait and choose Verify again. Misconfigured means the CNAME points somewhere other than cname.looph.ing, and the Status card names the host it found. Verified means the domain is yours and your board is served on it.
Next to each record, a live check shows DNS verified, DNS not found or DNS points elsewhere for the CNAME, and TXT found, TXT not found or TXT value is wrong for the ownership record. If the TXT value is wrong, replace it with the token on the page rather than adding a second record.
HTTPS is checked separately, because a verified domain still needs a certificate before browsers trust it. Looph requests the certificate only once the domain is verified, and it usually arrives within a minute or a few minutes. While it is pending, the page re-checks every 30 seconds until it shows HTTPS live. If the Certificate card stays on Certificate not issued yet, the record is probably proxied: in Cloudflare, click the orange cloud next to each record so it turns grey.
What moves to your domain
The whole public site moves together: boards, posts, the roadmap and the changelog, along with the changelog's RSS feed and the canonical links search engines see. Sign-in carries over too, so customers who are signed in to Looph are signed in on your domain. The admin area stays on Looph.
Once the domain is verified, your old looph.ing address sends visitors to your domain, so older links keep working. You can switch this off under Redirect the Looph subdomain. The redirect is permanent, so browsers remember it, and switching it off can take days to reach people who already followed it. The app.looph.ing/w/ address for your workspace keeps working either way.
After launch: checks, downgrades and disconnecting
Looph re-checks the CNAME of every verified domain every six hours. If the record stops pointing at Looph, workspace admins get an email titled Action needed, followed by the domain and will stop working soon. The domain keeps serving for 72 hours so a DNS mistake can be fixed, but the Looph subdomain stops redirecting to it in the meantime. If the record is still wrong after 72 hours, the domain stops serving your board and admins get a second email. Fix the record and choose Verify to bring it back.
If the workspace moves below Growth, the domain is kept but not served: visitors to it get a not found page, and links use your Looph address. It comes back when you upgrade. Disconnect removes the domain on any plan; visitors to it lose access until the DNS points elsewhere, and your Looph address keeps working.
Why it matters for SEO
A public board on your own subdomain accrues links and rankings for your brand rather than ours. Long-tail queries about your product start landing on pages you control, and each board and post page carries its own title, description and structured data.
Branding
In Settings, then General, under Branding, upload a logo and favicon, add a social share image, set your primary colour, and choose whether public pages use a light theme, a dark theme or follow the visitor's system setting. Removing our badge entirely is available on Growth and Business.
Plans and who can set it up
A custom domain and removing the Looph badge come with Growth and Business; on Free and Starter your board stays on its Looph subdomain. The owner can set the domain, and so can admins unless the owner has turned off Workspace settings for them.
Notification emails keep coming from Looph's sending domain under your workspace's name; set a reply-to address in Settings, then General, so replies reach you.
Choosing the subdomain
Pick a name that says what customers will find there, such as feedback, roadmap or ideas, on the domain your customers already know. Keep it stable: the address will end up in help articles, emails and search results, and every change after launch breaks some of those links.
Use the same subdomain for the board, roadmap and changelog, since they move together, and link it from the product's help menu so customers find it without searching.