X-Cacheable
HTTP response headerPrefix 'X' in X-Cache indicates that the header is not a standard HTTP Header Field. Also its meaning vary from one proxy implementation to another. ... Both HITs means that the client has made a cache-able request and the proxy had a cache-able response that matched and was forwarded back to the client
Header usage statistics
X-Cacheable response header information and usage statistics.| Websites using header X-Cacheable | 214,769 |
| Percentage of websites that use X-Cacheable header | 1.84% |
| Total discovered header values | 268 |
| Header uses directives | No |
| Header values are unique or random | No |
| Most popular in the country | 
United States of America
|
Distribution by websites popularity
X-Cacheable detection in the top websites by popularity| Top 10k sites | 350 websites |
| Top 100k sites | 2,710 websites |
| Top 1m sites | 26,937 websites |
Websites utilizing X-Cacheable
List of websites that use X-Cacheable header| Domain | Country | Rank | Contacts |
|---|---|---|---|
|
|
United States of America
|
181 | |
|
|
United States of America
|
249 | |
|
|
United States of America
|
336 | |
|
|
United States of America
|
468 | |
|
|
United States of America
|
536 | |
|
|
United States of America
|
688 |
Geographical Distribution
Header usage distribution by websites across the globe.Common header values
List of top common X-Cacheable header values| Header value | Value prevalence |
|---|---|
| SHORT | 39.93% |
| YES:Forced | 21.67% |
| YES | 16.41% |
| non200 | 6.28% |
| CACHEABLE | 3.52% |
| NO:Cache-Control=private | 3.08% |
| NO:HTTPS Redirect | 2.29% |
| NO:Not Cacheable | 2.19% |
| bot | 0.75% |
| YES:15552000.000 | 0.48% |
| YES:3600.000 | 0.38% |
| YES:2592000.000 | 0.34% |
| NO:Private | 0.31% |
| NO:Set Known Cookie | 0.30% |
| NO:Non-cacheable status | 0.20% |
| NO | 0.17% |
| YES:172800.000 | 0.14% |
| Matched cache | 0.12% |
| YES:briefly:500 | 0.11% |
| No, not cacheable. | 0.08% |