SSL/security risk problem, but only for one domain (.page.gd)

Website URL

These two don’t work: https://ru-imperialism.page.gd and https://ua-support.page.gd/
(also started automatically redirect to http instead of https for some reason)

This one (.html-5.me) works just fine, as it was from the very beginning: https://webdevin.html-5.me

Error Message (Error code: SSL_ERROR_BAD_CERT_DOMAIN)

Warning: Potential Security Risk Ahead

LibreWolf (same with Floorp browser) detected a potential security threat and did not continue to ru-imperialism.page.gd (same with ua-support.page.gd). If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details.

Other Information

I use joindns4.eu DNS for all of my browsers, but only .page.gd triggers it. Also both of my browsers are Firefox forks. Though, again, everything work for .html-5.me.

Right after creation of these pages (November, 2025), everything was fine. Even automatic https access without the need to force it. Should I try to force it on for page that don’t work?..

I know that SSL by Default for All Free Subdomains and I don’t need to setting this up.
As I saw in other similar topics, “Order new Free SSL Certificate” option shows the same message (that I all subdomains already have it).

Is this problem of domain, my DNS or something with… me?

P.S. apologies if I didn’t notice some obvious details U_U

UPD: my friend checked all of these websites, and they work just fine. But this friend uses the other DNS (ad-block something something, I didn’t ask). Which still doesn’t help with the question: why only one domain affected, and only for joindns4?

UPD2: DuckDuckGo mobile browser (same DNS) also blocks .page.gds:



both look to be working fine now.

probably just a temporary glitch

6 Likes

Just a thought: does that DNS provider apply any “malware filtering” or anything like that? If so, then they may have added page.gd to their blocklist, making you unable to access it.

And since that means that they are rerouting the traffic to a different server, that different server does not have a valid SSL certificate for your website, which is why you see that SSL error.

Your website seems to be working fine from here (with HTTPS!), and I see nothing to suggest that anything went wrong on our end recently.

8 Likes

Yep, turned out it’s my DNS after all!

Them blocking this domain is so random that I didn’t realize my websites are actually fine.

Thank you everyone for your help and suggestions ^w^

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.