There’s a few ways to detect use of CH: we can look for the opt-in via Accept-CH header or equivalent meta element; we can look at Chrome’s feature counters that log use of CH.
There are only 16 domains serving Accept-CH headers.
SELECT
DISTINCT NET.REG_DOMAIN(url)
FROM
`httparchive.requests.2018_07_15_desktop`
WHERE
JSON_EXTRACT(payload, '$._headers.response') LIKE '%Accept-CH: %'
And there are 4817 origins that have a feature counter with the CH prefix:
SELECT
url
FROM
`httparchive.pages.2018_07_15_desktop`
WHERE
JSON_EXTRACT(payload,
'$._blinkFeatureFirstUsed.Features') LIKE '%ClientHints%'
Many of these urls are from softonic.com (turns out we have 4532 origins from this domain, not including other TLDs), so that’s overwhelming the results.
There are 441 unique domains:
SELECT
Alexa_rank AS rank,
NET.REG_DOMAIN(url) AS domain
FROM
`httparchive.pages.2018_07_15_desktop`
LEFT JOIN
`httparchive.urls.20170315`
ON
NET.REG_DOMAIN(url) = Alexa_domain
WHERE
JSON_EXTRACT(payload,
'$._blinkFeatureFirstUsed.Features') LIKE '%ClientHints%'
GROUP BY
rank,
domain
ORDER BY
rank
Here’s a sheet with all of them in Alexa rank order: