RIP Webby

Computer Discussion => Computer & Network Security => Topic started by: Admin on January 22, 2022, 04:47:06 pm

Title: Admin login site is not secure?
Post by: Admin on January 22, 2022, 04:47:06 pm
I noticed my Admin Login page was not secure to both of my WAP and main Router. Is this normal? The reply said it was, but is this accurate? Thanks in advance.
https://community.netgear.com/t5/Nighthawk-WiFi-Routers/Admin-login-site-is-not-secure/m-p/1923688/highlight/true#M159604 (https://community.netgear.com/t5/Nighthawk-WiFi-Routers/Admin-login-site-is-not-secure/m-p/1923688/highlight/true#M159604)
(https://images.weserv.nl/?url=th.bing.com%2Fth%2Fid%2FRe7fe5aa4954a54d1ae97df1776f26777%3Frik%3DkP74K%252fUYSLmj5A%26amp%3Bpid%3DImgRaw)
                  
Title: Re: Admin login site is not secure?
Post by: Admin on January 22, 2022, 04:47:18 pm
Is it connecting to a domain name or is it like http://192.168.1.1? (http://192.168.1.1?)

Does the url have http or https?

Sometimes a page that is https can load 1 stupid item like an image from an insecure (http) source and it will say the whole page is insecure.
                  
Title: Re: Admin login site is not secure?
Post by: Admin on January 22, 2022, 04:47:30 pm
It’s for the device’s actual IP.
192.168.0.1
Thank you for your response. I’ve been worried and paranoid especially since a family member of mine fell for a scam and let the scammer onto our network. I’ve been trying to check everything and secure it all. The “not secure” logo made me even more paranoid but you’ve alleviated some of that worry, as it’s just for the router login page and not every site I visit.

                  
Title: Re: Admin login site is not secure?
Post by: Admin on January 22, 2022, 04:47:42 pm
Most IPs aren't going to use a valid SSL certificate because they are typically issued to just domains. So I'm not surprised at all that 192.168.0.1 is saying insecure. It either doesn't have an SSL certificate at all or its using a self-signed one and not one issued by a verified source like LetsEncrypt. So no I don't think this is anything for you to worry about. This is normal and expected behavior, especially if the router is older.