False negative for: Instagram

[NukeOfficial]

Additional info

Instagram is returning Not Found for known Instagram account names.
It worked ~ a month ago and I haven't updated sherlock on my end, so maybe something changed on Instagram's side.

Code of Conduct

• I agree to follow this project's Code of Conduct

[NukeOfficial]

As a note, this happens for multiple (presumably all) Instagram profiles. Looking up the url and urlProbe links from data.json manually returns the expected profiles.

[Giardias]

Yusuffakgl7

[Giardias]

yusuffakgl7

[kanagasabai-Hub]

same problem here

[srujanaelicherla]

Hi @NukeOfficial , I've investigated this and I'd like to try and fix it. Can you please assign it to me?

[NukeOfficial]

Hi @NukeOfficial , I've investigated this and I'd like to try and fix it. Can you please assign it to me?

Thank you, but it seems like I don't have the permissions to assign issues to people, so you'll have to wait for someone else to do so.

[ppfeister]

We typically only assign tickets for larger projects, rather than simple manifest changes --- and even then, it's pretty rare. If you want contribute, just follow the guidelines and push good, well thought-out code, and it'll be reviewed for possibly being merged.

[VivekGaddam]

Hey @NukeOfficial, is this issue still open? I’d love to help out if it hasn’t been fixed yet.

[Stanley-24]

Hey everyone 👋

I’ve fixed the Instagram detection issue by updating the site config and adjusting the detection logic.
All tests passed locally ✅

Submitting this as part of my Hacktoberfest 2025 contribution 🎉

PR: #2685

– Stanley (@Stanley-24)

[LordVader15]

Hello. I have just today encountered the same problem. I used it today the first time and it did not work on 2 different (currently) tested accounts.

[Stanley-24]

Yes, they haven't merged my pull request, so it won't work with the production code yet. It is working locally, and I did test before I opened the PR

Thank you @LordVader15