Whitelist IP's for Google Home/Assistant

Sem Craeghs 1 month ago in Devices / Other updated by Jürgen Jürgenson 1 month ago 3


I was exploring the Google Home functionality, by configuring port forwarding on my firewall.

I've noticed in the log files of the firewall a lot of residential IP's (coming from US, Russia, Bangladesh, ...) trying to connect to the port, probably considered "not legit addresses".

Do you have list of IP's that I can whitelist so I can mitigate this thread?


If you want to use Google Home / Alexa, you need to open / expose HTTPS port 443 (this port applies to access ComfortClick remotely, and therefore the Google and Alexa skills will communicate with that port).

Nonetheless, you don't need to use the standard port, but rather redirect a different external port to the internal 443 port.

For example, I'm using external port 52443 redirected to the internal 443 (you can go as high as 65535). Higher ports, can at least move away some pseudo-hackers from finding your server (it can obviously be found with a deeper scanning). But usually the standard ports are the most attacked ones, so if you move away from the standard ones at least you can "hide" the server a little bit.

Best regards 

Hello Ricardo,

I'm aware of that possibility, but to further reduce the possibility, it would be nice to have a list of IP's which would connect to my ComfortClick installation.

For example, Microsoft, Google, and Amazon are also publishing their IP ranges so you can limit the sources in your firewall..

Use resource monitor or netstat? Filter by bosservice.exe and whitelist remote addresses?