DDG Browser displays Private IP on dnscheck.tools

Privacyplease

After last nights update I checked dnscheck.tools to see where I was connected only to discover under my isp lan and cellular ip's addtess was my personal lan ip and has a new line called Nonpublic Reserved IP Space and that ip address under it is my lan ip so this is new and I have radios turned off. why is my lan ip now being picked up by dnscheck.tools? all radios are off until i get an answer or a new phone. I removed my vpn and turned off my personal dns setting and problem persists on this 7Pro phone. Please fix. Go to dnscheck.tools to see what your phone reports. I use the tool every day to see my dns resolvers and now my personal local ip is being exposed.

Mod note: Multiple times in this thread, Privacyplease suggests that this is due to a GrapheneOS update. It is not. Some posts were removed or edited because they were incorrect.

angela

It would probably help to know the VPN app you are using to know if it's an App specific issue.

How can I test this? What is expected versus what you get?

Privacyplease

angela Hello Angela. I removed the vpn app and also turned off my personal dns resolver on the phone. [removed]. The problem persists on my lan and cellular networks. I did not understand what Nonpublic Reserved IP Space was then I seen my lan ip address below it so we have ~~graphene os~~ at least on my phone exposing my local lan and on the cellular it has it's own local lan ip being exposed under the actual isp address.

Privacyplease

angela OK so to test just open a browser and type in dnscheck.tools and this tool will give you your isp and dns resolvers. The tool has been around for a very long time. I use every time i connect and after this am's update this is new.

angela

Privacyplease A reserved IP space like 192.168.X.X means nothing because those are addresses used to map things locally. Is it showing something like that?

angela

Privacyplease

What exactly is de-anonymizing you?

There are things like ublock that block local lan intrusion scanning. I am not sure if saying correct.

Privacyplease

angela when you connect to your cellular network you are not supposed to see the local address on their system. It has their isp address then the Nonpublic Reserved IP Space and the ip local address on their system and that is not supposed to happen. This has never happened before...new problem started last night.

Vsecu

I tried and it is correctly showing my cellular fake vpn connection. Like Angela mentioned, this likely has something to do with your VPN. I also run on the latest update.

Privacyplease

Vsecu I removed the VPN. There is No vpn on my phone right now. the Private dns resolvers are set to off. and my local ip's are exposed. And it happened after an update in the middle of the night. Like I said I use dnscheck.tools every time time i connect and this is new.

Privacyplease

angela a web browser should not be picking up your lan address with dnscheck.tools

Privacyplease

angela No it has the complete address not.x.x. My lan address is showing on a public facing dns tester dnscheck.tools

angela

Privacyplease why wouldn't your local IP show if your VPN is off? That's expected .

angela

Privacyplease Ublock has a block lan intrusion setting you can enable. I believe lan intrusion is possible with javascript and that's a known vulnerability for all browsers with javascript.

Privacyplease

angela It is Not expected nor have I ever seen it before. I public facing tool should not be able to detect your private lan address

Vsecu

Try a different vpn solution, check if it persists. Also you mention that you have a separate app for vpn a personal dns resolver. These usually are within one app, as Android and GOS cannot have two different tunneling solutions in chain. Rethink offers such a solution within one app to work around it, as many vpn apps route trough their dns. Didn't you put on your dns resolver which disabled the vpn?

Privacyplease

Vsecu Vsecu I am telling you I removed the VPN. It has nothing to do with my previous VPN. This behaviour is with No VPN installed. Had I not checked dnscheck.tools every day I would of missed it.

Vsecu

Privacyplease Without VPN you would see your cellular IP. When connecting to Lan, it would expose the isp IP. If like Angela mentioned as well it shows the internal lan ip's like 192.xxx and other free ip ranges, nothing is exposed. Indeed a javascript or webrtc leak could exist, but is done by your browser. Try Brave and see if this works.

Anyhow, you're IP will be exposed when not using a VPN. GOS is not a vpn solution.

Privacyplease

Privacyplease Just to be clear yes you always see your isp's address every time that is expected and normal. what is new is I can see my lan address under the isp address. The dnscheck.tools testing page is a report of what is seen on the public side and your lan address should not be there also your cellular lan address should not be there. You will see Tmobile and their public connection ip but then there is another line under it called Nonpublic Reserved IP Space and it has the full local address on the tower as well. OK I reported it and that is all I can do.

Vsecu

Privacyplease Ok I understand it better now. So your local ip is being exposed. When going cellular, I do not have a local lan. I did not try to see when i connect my phone on my lan what happens. Try Brave to see if it Vanadium related, if using this browser?

Privacyplease

Vsecu Vsec it is not showing a range it is showing my actual lan address under the title of Nonpublic Reserved IP Space. yes it says reserved space but my actual full address is being exposed on the internet through Graphene. Your lan address is not supposed to be exposed to the web. Not a vpn issue, not a dns issue [removed] exposing my lan address on under my isp and also on cellular. OK I put it out there I will wait for a fix and start looking for a new phone.

Privacyplease

Vsecu if you are testing with dnscheck.tools you should not see your lan address and also you should not see your cell providers lan address your only supposed to see the public address that makes the connection. If dnscheck.tools can see tou lan then the web can see it. that is why we use dnscheck.tools as I want to see where I am connected and which dns resolvers I am connected to. when your lan address is exposed that's a problem.