3 ms·

0.0.0.0 qeys.io

• detaro 8y ago
  Or a CSP header server side. But still something the average client will miss, at least at first, and trip the alert.
  • frits1993 8y ago
    > But still something the average client will miss, at least at first, and trip the alert That's totally it, thanks for pointing that out!
• tzahola 8y ago
  Exactly my thoughts.
• bjpbakker 8y ago
  That won't really work for the scenario they try to "protect" against. When you copy some js files that include their license checking code to your server and them serve it to your clients, your clients need to block qeys.io, not you. You can instruct clients to do that of course, but it's rather easy for one of them to forget and the copyright holder is noticed. Still, blocking qeys.io by default on your system sounds like a good idea :)
  • ake1 8y ago
    if it's for internal use, you most likely have access to the DNS-server the clients are using, not an unlikely scenario when it comes to licensed code like this i would imagine.
• imtringued 8y ago
  You will still get caught because google will crawl your site which in turn will make a request to qeys.io and then I will get a notification with something along the lines of "Customer jlebrech is using an unlicensed version of your software on unlicensed-domain.com". The purpose of this software is to report the copyright infringement of the host, not the user.
  • jlebrech 8y ago
    I didn't think of this, you could still steal something that's designed for an intranet (those may cost thousands)