You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Sherlock to check for the existence of an Instagram profile by providing a valid username, the expected result should be that the tool returns whether the profile exists or not.
When performing this action, however, the actual result was that no output was displayed for Instagram profiles, even for valid usernames.
This is undesirable because it prevents users from accurately checking Instagram profiles, which is a key feature of the tool. Thank you for looking into this issue!
Steps to reproduce
Open the Sherlock tool.
Enter a valid Instagram username (e.g., instagram) and run the tool.
Observe that no result is displayed for Instagram, regardless of the username's validity.
Additional information
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Thanks for reporting this. What region are you testing this from? I've checked it with North American IP, and it worked for me. I also tried relaying Sherlock connections via Tor Socks, and that worked too. It might be that Picuki.com (the site Sherlock gets Instagram data from) is blocked in your country/network
Installation method
Other (indicate below)
Package version
Sherlock v0.15.0
Description
When using Sherlock to check for the existence of an Instagram profile by providing a valid username, the expected result should be that the tool returns whether the profile exists or not.
When performing this action, however, the actual result was that no output was displayed for Instagram profiles, even for valid usernames.
This is undesirable because it prevents users from accurately checking Instagram profiles, which is a key feature of the tool.
Thank you for looking into this issue!
Steps to reproduce
Additional information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: