Site Shows Not Secure

💡 In this guide, you will identify whether the warning comes from SSL still issuing, the wrong URL, browser cache, or DNS. Estimated time: 5 minutes.

When the browser says "not secure," your site content is usually fine. Most cases mean SSL is not active yet, or the page was opened without https://.

Check in the order below. Do not start by deleting DNS records.

First Check

1Browser says not secure

2Just connected domain?

3Wait for SSLYes

4Check browser cacheNo

5Check SSL in AllinCMS admin

6Check DNS

What you see	Check first	Common fix
Domain was just connected	Whether SSL is still issuing	Wait 10 to 30 minutes
Address does not use https	Browser address bar	Enter https:// manually
Only your computer shows it	Browser cache	Test in incognito
Domain does not open	Whether DNS passed	Check DNS records

---

1. Wait SSL

If you just connected the domain, do not change the setup immediately.

AllinCMS admin first checks whether DNS points correctly, then issues the SSL certificate. This usually takes 10 to 30 minutes.

① Check Status

Open the AllinCMS admin site dashboard, then go to Settings -> Domains. Check the status on the right side of the domain row.

Focus on these two:

Status	Meaning	What you need
DNS	The domain points to the CNAME target provided by AllinCMS admin	Passed
SSL	HTTPS certificate was issued	Passed

② How Long

• Just added DNS: wait 10 minutes first.
• DNS passed but SSL has not: wait a little longer.
• Still not passed after 30 minutes: go to step 4 and check DNS.

DNS and SSL

DNS passing does not mean SSL passes at the same second. DNS checks whether the domain points correctly. SSL checks whether the HTTPS certificate has been issued.

If SSL has passed, go to step 4 and test access. If it has not, continue with the URL check.

---

2. Use https

Some browsers open http:// first, which shows a "not secure" warning.

Enter the full address in the browser:

https://www.example.com

Check:

• The address starts with https://.
• The domain matches the one added in AllinCMS admin Domains.
• If you only connected www.example.com, do not test only example.com.

If the site opens after adding https://, the site itself is fine. The issue was the access URL.

💡 If you want example.com to redirect to www.example.com, Cloudflare users can read Cloudflare DNS.

---

3. Clear Cache

If only your computer shows "not secure" while others can open the site normally, the browser may have cached an old state.

Try in order:

1. Open the site in an incognito window.
2. Test in another browser.
3. Test on mobile data.
4. Clear browser cache and open it again.

Use this to judge:

Result	Meaning	Next step
Incognito works	Browser cache issue	Clear cache
Another browser works	Browser cache issue	Clear cache or wait
Mobile data works	Local network cache issue	Wait for network cache to refresh
All devices still fail	Not cache	Check DNS

If only some devices fail, do not reconfigure the domain. Wait for cache to refresh.

---

4. Check DNS

If it is still not secure after 30 minutes, or the domain does not open at all, check DNS.

Start from the AllinCMS admin Domains page:

• DNS has not passed: check domain records first.
• DNS passed but SSL has not: wait a little longer, then refresh.
• Both DNS and SSL passed: check browser cache or the URL you entered.

① Check CNAME

Go back to the DNS provider and check:

Item	Correct setup
Record type	CNAME
Host	www or @, depending on which domain you connected
Value	The AllinCMS admin CNAME target
Old records	Do not keep a conflicting A or old CNAME on the same host

② Check Cloudflare

If your domain uses Cloudflare, turn off proxy for the www CNAME first. The cloud icon should be gray and show DNS only.

For Cloudflare root-domain redirects, proxy status, and www setup, read Cloudflare DNS.

③ Check Binding

If you are not sure how to fill @, www, or CNAME, go back to DNS Setup and review the main flow.

---

Pitfalls

Mistake	Result	How to avoid it
🔴 Waiting for SSL before DNS passes	SSL will not activate	Make DNS pass first
🟡 Reconfiguring right after DNS passes	Certificate issuing may be interrupted	Wait 10 to 30 minutes
🟡 Not entering https://	Browser shows not secure	Enter the full HTTPS address
🟡 Testing root while only www is connected	False failure	Test the domain added in AllinCMS admin
🔴 Deleting DNS records casually	Email or verification may break	Do not delete MX or TXT blindly

Completed

• ✅ You know that "not secure" is usually an HTTPS/SSL status issue, not broken site content.
• ✅ You know to check DNS and SSL in AllinCMS admin first.
• ✅ You know how to rule out cache with https://, incognito, and another device.
• ✅ You know when to check DNS again.

Next

• 📌 DNS Setup: read this if you are not sure how to fill CNAME.
• 📚 Cloudflare DNS: read this if your domain uses Cloudflare.
• 📚 Migrate an Old Site: read this when moving an existing website to a new AllinCMS site.