Is it possible to prevent the sending cook to the domain from the address bar?

I was thinking... That has a user account in Google, Yandex, FB, VK, and the like the companies need to emphasize. Of course, 95% of the time he is logged in permanently, because inconvenient to enter the password.

And here comes the user to a completely left the website where they can stand - Google Analytics, Yandex direct, licalsi, widgets, comments, and so on. That is, search engines and social networks not just to track visits to other sites, but watch out by name.

Question: are there any technologies, settings, or extensions that would block sending cook to the server, if the document is loaded Ajax or iframe? Well, that is if the user comes specifically and this url in the address bar - cookies should be sent. And if the site is completely different, but Google was there as a left-side loaded - it should not get any cookies for it, the browser should look like he just installed.

About AdBlock, uBlock, Ghostery, and other blockers of the scripts - it's all clear, it is also necessary, but it is another line of defense. It is about sending cook.
August 23rd 19 at 11:33
1 answer
August 23rd 19 at 11:35
For chrome

To allow only first-party cookies, select "Block third-party files and site data". Please note that this setting closes access to the third-party cookies even on pages that are added to the exceptions list.

On these settings I thought, but as I understand from descriptions (correct if wrong) is a little different. These settings block the RECEPTION cook from third-party sites. That is, for example, will be blocked cookies some ad network code included in the page. But about READING previously and legitimately installed cook there, it seems, there is no writing. At least FF is written quite clearly "accept". Chromium has formulirovka more vague. - Trey.Emard commented on August 23rd 19 at 11:38
: I do not understand what you want. No cookies are, if not from the same domain. I.e. coming on Habr, when there is a request counter from VC, then cookies are not sent. - annalise commented on August 23rd 19 at 11:41
Go cookies the same VC. Comparing the referrer (or the API-key in General) with its own cookies, VC can understand - "John DOE went on Habr". Not an abstract abrowser, namely Bob. Isn't it? - Trey.Emard commented on August 23rd 19 at 11:44
: apparently, you have some special browser, again sent. I have not sent the cookies. - annalise commented on August 23rd 19 at 11:47
Play with devchonkami - if we talk about single files (images, fonts, scripts, etc), then do not go.
But then the question is: how, then, for example, widgets, comments FB, VK, Disquss determine its user? I understand this is possible because they are loaded via iframe, in this case, the cookies still go, right? And iframe can access the parent document.
That is the question more narrow than I first thought. But still is the place to be.
In short, you just have the iframe zablocie :) - Trey.Emard commented on August 23rd 19 at 11:50

Find more questions by tags BrowsersInformation security