SSL certificates are now a standard requirement across the web. Major browsers like Chrome, Safari, and Firefox actively warn users when a website does not load securely over HTTPS. These warnings are enforced at the browser level and apply universally, regardless of platform or provider.
This change does not indicate a security issue with your app. It affects how browsers label web-based experiences that use a custom domain without SSL. Mobile apps published through the App Store or Google Play are not impacted.
Understanding how SSL works (and when it matters) helps ensure a consistent, trusted experience for users accessing your app or web content through a browser.
Requirements
A custom domain connected to your account
Access to your domain provider (for example, GoDaddy, Namecheap, or Google Domains)
How do I add an SSL certificate to my account?
Confirm whether your domain currently has SSL enabled
URLs starting with https:// are secured
URLs starting with http:// are not secured
Purchase an SSL certificate from your domain provider if one is not already active
A wildcard SSL certificate is recommended if you use multiple subdomains
Log in to the Control Panel
Go to Settings, then Account
Upload your SSL certificate details as provided by your domain host
Save your change. It can take 5-60 mins to update
Verify your domain now loads securely over HTTPS without browser warnings
Pro tips
Browser warnings only affect web-based experiences, not native mobile apps
A “Not Secure” label does not mean your site is hacked or compromised
SSL improves user trust and can positively impact search engine ranking
Our platform cannot bypass browser security warnings. These are enforced by the browser itself