QuinStreetSee original GitHub issue
www.quinstreet.com map to
www.quinstreet.com.edgekey.net. Current DNS filters only block via
||quinstreet.com^ & so only catch 2nd domain, but this feels like a 2nd-iteration CNAME, & should catch 1st, as well. But that seems like it could false positive other domains of the pattern, as well. What’s best way to catch these kind of scenarios? Right now, I’m just using user DNS filter
||quinstreet., which catches all of the above.
- Created a year ago
- Comments:6 (3 by maintainers)
Top GitHub Comments
Tbh, it does not seem as an ad network. Moreover,
www.insure.com is just a website.
I suppose Akamai works just like Cloudflare, i.e. this
quinstreet.com.edgekey.net is just a proxy that proxies traffic depending on the request’s domain. For one domain it may proxy it to some tracker, for some other domain it may proxy it to a legit web server.
As I recall,
edgekey.net is a domain that belongs to Akamai, i.e. this is a CDN, not a tracker. It’s also rather normal for different domains to map to a CDN edge.