I often open Incognito the way you'd open a door, assuming whatever happens inside remains private. But when I started to investigate deeper, the results didn't match my idea of the feature I've had for years. "Private" was doing a far narrower job than I had given it credit for. The moment this realization dawned on me, I stopped using Incognito the same way.
Try doing this right now. Open Incognito and browse like you would normally, then open a Command Prompt (Windows), close any Incognito windows, then run: ipconfig /displaydns.
Scrolling through the results, you may find domains that were resolved while you were browsing, including domains from an Incognito session. The output isn't a copy of your browsing history; it can include DNS records created by other activity.
This isn't a bug or evidence that Chrome is intentionally deceptive; it reflects a narrower scope for Incognito. Incognito clears history, cookies, form data, the local cache—these are elements stored inside the browser.
Incognito isn't designed to clear DNS information maintained outside Chrome. When Windows handles DNS resolution, the operating system keeps its own cache independent of Chrome, and Incognito can't clear that because it doesn't control the OS cache.
However, that's not the only way information can leak outside the browser. When an active browser crashes mid-session, certain crash-recovery temporary crash-recovery files remain briefly on disk before being deleted. You may also see the same DNS lookups in your router's DNS cache.
While these are not dramatic privacy failures , they show one important fact: the scope of privacy for Incognito is often narrower than you would have thought.
Source link







