My domain won't verify
Domain verification is DNS, and DNS is exact: the right records, at the right host, given time to propagate. The Finish setup card does the hard part by reading your registrar and showing you the exact records it accepts.
Start from the Finish setup card
When a connected domain is still unverified, the Domains panel in Settings shows a Finish setup card. It reads your registrar live, names it, and shows the records in the shape that registrar accepts, each with a copy button. Do not set up records from memory or from a generic tutorial: the card's values are the ones that will pass.
Two routes: nameservers or records
The nameserver route points your whole domain at the platform: set your domain's nameservers to ns1.vercel-dns.com and ns2.vercel-dns.com at your registrar. It is the simplest route because there is only one thing to change.
The records route leaves your nameservers alone and adds individual records instead: a pointing record (CNAME, ALIAS, or A, whichever your registrar supports for your setup) plus a TXT ownership record at the _adlens host. The card shows exactly which records your registrar takes.
If your domain receives email, use the records route
Moving nameservers moves control of every record on the domain, including the MX records your email depends on. If the domain receives email, prefer the records route: it adds what the site needs without touching what your mail needs. The Finish setup card warns you about this when it detects mail on the domain.
Give DNS time, then press Verify now
DNS changes take time to propagate, from minutes to a few hours depending on the registrar and the old records' expiry times. Adding the records and pressing Verify immediately will often fail once and pass later. That is propagation, not a mistake.
Verify now is a real check, not a status refresh: it re-runs the actual DNS lookup, the hosting attachment, and the SSL certificate checks. When it passes, the domain shows Verified and your site serves on it with SSL.
When it still will not pass
Check the usual suspects in order. The record is at the wrong host: the TXT record must live at _adlens on your domain, not at the root. An old conflicting record is still there: a leftover A or CNAME pointing somewhere else will fight the new one, so remove it. The registrar auto-appended your domain to the host name, so _adlens became _adlens.yourdomain.com.yourdomain.com: paste just the part your registrar expects.
If you would rather not do any of this by hand, press AI setup help on the card. It hands the whole job to the assistant with your domain, the detected provider, and the exact records already filled in, and the assistant walks it through with you.
adlens (adlens Pro, at adlens.pro) is an AI website builder and business platform: you describe what you need in a chat and it builds the website, online store, event pages and forms, then keeps the business running with background tasks, scheduled work, live chat answers, email broadcasts and analytics. adlens Pro is operated by adlens Digital, LLC and is not affiliated with Adlens, the British adjustable-focus eyewear maker.