Domain still not working? Check these five things first.

You do not need to master every DNS term. Follow this order to locate the part of the launch that is actually failing.

1. 01

   Confirm the site is published

   Open the public Framer URL in a private window. If the origin itself is unavailable, changing the custom domain will not fix it.

2. 02

   Find where DNS is actually managed

   The company that sold the domain may not be the current DNS authority. Check the nameservers, then make changes in the dashboard they point to.

3. 03

   Look for conflicting records

   Old A, AAAA, CNAME, CAA, forwarding, or proxy records can create inconsistent access or prevent an HTTPS certificate from being issued.

4. 04

   Choose one root/www policy

   Decide whether `example.com` or `www.example.com` is primary. The other should redirect consistently instead of behaving like a separate version.

5. 05

   Verify HTTPS and real devices

   After the certificate is ready, test mobile data, Wi-Fi, desktop, and a private browser window. Working in one cached browser is not a complete launch check.