Does it point to a website?
See the public A, AAAA, or CNAME connection and whether the www version also works.
Custom domain checker
Check DNS, www, and the HTTPS padlock in plain English. Made for websites created with ChatGPT, Claude, Gemini, v0, Lovable, Replit, and other AI tools.
Quick answer
An AI website custom domain checker shows whether your domain points to a published website and whether HTTPS is working. It reads public DNS, identifies where DNS is managed, checks the root and www versions, and explains common connection problems without changing any records.
You do not need to understand DNS first. The report tells you what is working, where to make a change, and what to leave alone.
See the public A, AAAA, or CNAME connection and whether the www version also works.
Nameservers reveal the active DNS provider—even when the domain was bought somewhere else.
Check whether the secure certificate matches the domain and spot a CAA rule that may block it.
Simple workflow
The AI tool creates the page. A website host publishes it and gives you the DNS values. Your DNS provider is where you add those values.
Read the full setup guidePut the HTML, ZIP, or built website online so the host can give you the correct destination.
Enter the domain in your hosting dashboard. Copy the A, CNAME, or verification record the host supplies.
Use the provider named by the checker. Keep email MX records and unrelated TXT records unchanged.
Run the checker again until the website record and HTTPS both pass.
From diagnosis to done
Enter the domain above. The checker reads its public DNS records and tests HTTPS. A website record means the domain points to a host. A valid certificate means the secure padlock is ready.
Yes, after the generated website is published on a host that supports custom domains. Your AI tool creates the website; the host supplies the DNS records and HTTPS certificate.
DNS changes can take time to appear. A wrong record name, an old conflicting record, or editing DNS at the registrar instead of the active nameserver provider can also cause the problem.
No. It reads public DNS and TLS data only. It cannot log in, edit records, or change MX records used for email.
No. A public DNS result does not prove ownership and is not a complete security audit. It shows whether common website and HTTPS records are visible right now.
Publish the website, add the domain in GeminiLaunch, then copy the exact DNS records into the provider detected by the checker. GeminiLaunch checks the records and issues HTTPS after they are correct.
Need a different check? Check your website files or see all free tools.