FAQ

What is the current list of collected attributes?

# Name Description URL
1 Audio context fingerprinting WebAudio allows writing data to AudioBuffers and performs analysis on them.
2 Math routine Values for specific math routines
3 BuildID A string indicating the build identifier of the browser(not present in all browsers). This attribute is collected through JavaScript via the 'navigator' object.
4 Plugins An array containing information on plugins installed by the browser. This attribute is collected through JavaScript via the 'navigator' object.
5 Do Not Track A boolean indicating the status of the Do Not Track header. This attribute is collected through JavaScript via the 'navigator' object.
6 Screen Information regarding the screen. This attribute is collected through JavaScript via the 'screen' object.
7 Storage Information on the support of local and session storage . This attribute is collected through JavaScript.
8 Timezone A string representing the time-zone offset from UTC, in minutes, for the current locale. This attribute is collected through JavaScript via the Date API.
9 Cookies A boolean indicating if cookies are enabled or not. This attribute is collected through JavaScript via the 'navigator' object.
10 Platform A string representing the platform on which the browser is running. This attribute is collected through JavaScript via the 'navigator' object.
11 Accept-Language A string representing the list of acceptable human languages for response. This attribute is a HTTP header collected by the server.
12 List of headers An array with all the HTTP headers sent to the server. This attribute is collected by the server.
13 User-Agent A string giving details on the browser and its underlying operating system. This attribute is a HTTP header collected by the server.
14 Accept-Encoding A string representing the list of acceptable encodings. This attribute is a HTTP header collected by the server.

I'm interested in studying X but it is not present in the test suite. What can I do?

You can open an issue on GitHub HERE telling us you want that attribute to be added and why. You can also directly send us a Pull Request with the right code by following the imposed file format described HERE . In both cases, the relevance of the attribute will be discussed before it is accepted. This step is needed to make sure that the test suite does not become too heavy by having dozens of uninteresting attributes.