Pimeyes.com and lenso.ai

[Peloxerat]

I've previously raised the topic of these two websites, and I'd like to do so again: pimeyes.com and lenso.ai

1. pimeyes.com

Pros:

• The paid version can be bypassed quite easily; you simply need to convert the hex from the obtained URL to ASCII, and we get the necessary data.
  
  

Cons:

• The number of requests from a single IP address is still limited, but this is bypassed by using personal and/or public proxies. At least I haven't found a way to bypass this without using proxies.
• Searching by URL is not possible. Or I haven't found such a way. Only by file.

2. lenso.ai

Pros:

• Now, for some reason, they don't encrypt the data (only visually), as they did before, that is obtained during the request, therefore, we can parse them.
  

• Even if it says "you have used free searches," it still searches and still gives results. Although I'm not entirely sure about this, as I haven't conducted in-depth tests.

• It was previously discussed that there was no search by URL, but the method I mentioned in the previous issue still works. That is, it can search by both URL and file.

Cons:

• MAYBE the same as with pimeyes.com. The number of requests from a single IP address is still limited, but this is bypassed by using personal and/or public proxies. But this is highly doubtful, as it seems to return results even if the limit is exhausted.
• The site is young and might frequently change its internal API, consequently, the method might stop working altogether or become very limited.

I'll leave it up to you to decide whether or not to proceed with adding these engines.

P.S If you're interested, when converting from hex to ASCII in lenso.ai, we get a link to lenso.ai's server IP address. I haven't figured out how to use this to our advantage, but it's amusing

[robot00f]

Pimeyes has already encrypted it...

[Peloxerat]

Pimeyes has already encrypted it...

Yes, you are right. Honestly, I'm very surprised. Because I saw this method in another project, and it worked for quite a while. Although I highly doubt it's due to the issue I created. But it is what it is

I think they are still returning data in hex, just with an offset or something similar. It seems to me this can still be exploited, but I'm not sure this fix will last long

Anyway, it's a pity, just yesterday everything was working...

[Bucky2001]

Yes, they encrypted it, but after researching and analyzing it, I believe it's just another encoding in hexadecimal. For example, d8ab19d5c7a0f27c10fa57540506ac68 is equivalent to 7b2275726c223a2268747470733a2f2f, which decodes to {"url": "https://

[NekoAria]

I support adding lenso.ai to the library, as it currently has fewer access restrictions.

Regarding pimeyes.com, since they have started encrypting data and may have implemented offsets or other anti-bypass measures, I believe it is better to continue monitoring the situation and assess whether new methods emerge to bypass the current restrictions.