Has anyone experienced getting their domains flagged as deceptive/phishing from Google after using NPM?
I moved from using NGINX Proxy SSL to NPM a few weeks ago due to needing to redirect more than 1 domain to different services, and wanted secure access. Not sure how long after, my the subdomain (from DuckDNS) that I was using to access HA was flagged as dangerous.
Shortly after, the other subdomain I was using to access this other addon was also flagged.
I have seen reports of people using DuckDNS subdomains of these issues. So I went and decided to use a domain of my own.
It was instaflagged too, and not only my own subdomain, but the main domain too (which was pointing to our business website). It caused quite a big deal of trouble tbh. Since it’s Google’s flagging system, it doesn’t allow you to use OAuth services with Google’s either.
After that I went ahead and did further testing today. I retraced my steps, went back to DuckDNS (same subdomain I was using) + NGINX Proxy SSL (NPM deactivated). So far it’s not being flagged, which is making me strongly suspicious NPM was indeed the culprit, and I’m not sure why.
I actually need to use NPM, as I said, since I need more than just HA to be accessible remotely. And NPM was easy enough for me (non-dev) to use, including the SSL certs.