Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
QuinStreet
See original GitHub issueBoth www.moneyrates.com & 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.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Tbh, it does not seem as an ad network. Moreover,
www.insure.comis just a website.I suppose Akamai works just like Cloudflare, i.e. this
quinstreet.com.edgekey.netis 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.netis 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.