Visitors see 'Not secure' next to your website name. Here is why it appears and the ten-minute fix, step by step.

Why the warning appears The site is being served over plain http (no SSL certificate active), OR https works but the page mixes secure and insecure content (the 'mixed content' case).

Fix 1: activate SSL (the usual case) On Kairalmas, SSL issues automatically when a domain is added to hosting — a few minutes to a few hours for issuance. Check: portal → your website → SSL status. If it says active and the warning persists, it is cache — hard-refresh (Ctrl+Shift+R) and retest in incognito.

Fix 2: force https (so nobody ever lands on http) Add a redirect so every http visit flips to https. The file manager's .htaccess editor has this as a preset, or support applies it on request. Without this, old links and bookmarks keep hitting the insecure version.

Fix 3: mixed content (the sneaky one) The padlock appears then breaks on some pages: an image, script or iframe still loads over http. Find them: browser console (F12) lists exactly which URLs. Fixes: update the URLs to https, or make references relative (/images/logo.png instead of http://...).

Fix 4: after migration (the cache gotcha) Just moved hosts or activated SSL? Your browser and CDN may remember old versions. Flush browser cache, purge any caching plugin, retest. The server is usually fine — the memory of it is not.

Why this matters beyond the warning Chrome shames http sites next to your business name, Google ranks https higher, and payment flows require it. Free SSL means the only cost is these ten minutes — spend them today.