There are a few online advertisement opt-out services such as:

Each of those pages connect to several advertising hubs, presumably request a 3rd party cookie to determine if tracking is enabled or not. This process is repeated several times. Screenshot:

enter image description here

I'd like to understand this transaction, how it works for determining status at a given provider, and how the non-track attribute is maintained.


  • Does each vendor have a standard way of determining tracking? (e.g. a ./well-known/ RFC based URL?)
  • Is the query to that vendor a GET or POST
  • What is the return value, and header information?
  • Is the return value and header information standardized in any way?
  • If a cookie is set on the client, is it a unique identifier of sorts, or is it a generic "don't track me" request?

closed as off-topic by Steffen Ullrich, techraf, schroeder Oct 13 '16 at 7:13

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question does not appear to be about Information security within the scope defined in the help center." – Steffen Ullrich, schroeder
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 2
    Bulk advertisement opt-out is called ad blocking. What you are showing here is called snake oil. I don't see why you should trust advertisers not to track you just because you asked nicely. – André Borie Oct 13 '16 at 2:36
  • I'm not sure this is a security question at all. Seems more web and API programming. – schroeder Oct 13 '16 at 7:13