Home ▼ Bookkeeping
Online ▼ Security
Audits ▼
Managed
DNS ▼
About
Order
FAQ
Acceptable Use Policy
Dynamic DNS Clients
Configure Domains Dyanmic DNS Update Password Network
Monitor ▼
Enterprise Package
Advanced Package
Standard Package
Free Trial
FAQ
Price/Feature Summary
Order/Renew
Examples
Configure/Status Alert Profiles | |||
Survey Data Mining: Home | FAQ | Archive | Glossary |
|
Report Description |
Cookie Survey Results |
Set a cookie for all hosts in the domain | 4.1% |
Set a cookie for longer than a day | 32.8% |
Set a cookie for longer than a year | 19.1% |
Set a cookie for longer than a decade | 8.7% |
Set a cookie for all URLs on the site | 99.3% |
Popular Cookies |
Cookie Name | % of sites |
ASPSESSIONID* | 43.0% |
JSESSIONID | 10.2% |
PHPSESSID | 6.3% |
CFID | 3.7% |
CFTOKEN | 3.7% |
cookietest | 3.2% |
permcookietest | 3.2% |
CookieStatus | 2.7% |
SITESERVER | 2.6% |
WEBTRENDS_ID | 2.2% |
REFERRER | 1.9% |
What is a cookie? |
When a server sends a cookie, it can ask the browser to store the cookie for a period of time, so that the cookie is remembered between sessions, even if your web browser or computer has been shut down. This is the expiry time of the cookie, which by default is to the end of the current session.
A cookie can be set so that it only applies to a certain pattern of URLs on that server, but the default is for the cookie to be sent with all requests to that server. It is also possible for a cookie to be set so that the browser will send the cookie with requests to all servers in the same domain, not just the one web server.
Due to their use in tracking users and some security problems surrounding them, cookies have been a concern to many privacy and security advocates.
Methodology |
Our crawler is only used to crawl web pages and not any images, applets, or other objects that may be contained in those pages. This means that any cookies sent only with those objects and not with any HTML pages will not be discovered by our crawler, but they would be received by most web browsers.