Check if a Threads username exists

Digital Footprint checks Threads from an username as part of every lookup, alongside 885+ other platforms, breach history and public web mentions - one request, one shape of answer. A hit means a profile exists for that input; profile contents are never collected.

Accepts
username
Speed
Standard tier
Popularity
#409 by global traffic
Category
Social media

What we check on Threads

Standard tier - checked on every full lookup

Threads is checked from a username. The response says whether that handle exists on Threads - registered: true or registered: false - with the moment that was established in checkedAt. An email address on its own cannot reach Threads; if you only have an email, its local part is tried as a handle and any hit is labelled as derived, never counted as a confirmed match.

Threads is checked on every full lookup (?wait=true or streaming), alongside every other platform. It is not in the sub-second instant subset, which is reserved for the highest-value platforms for each input type.

If Threads blocks the check, times out, or answers ambiguously, it is omitted from results[] entirely rather than returned as registered: false. Absence from the response means "unconfirmed", never "no account".

Who checks Threads accounts

Social media accounts are checked when a signup, buyer or applicant needs to look like a real person. A social footprint that goes back years is hard to fake in bulk, so an email or phone number registered on established social platforms lowers the odds of a throwaway or synthetic identity. Fraud and trust-and-safety teams read it as one signal among several, never as proof on its own.

More on this: Fake account detection.

Inputs Threads accepts

  • Username: send the handle as query. Threads is checked for that exact handle - useful when a person reuses the same name across platforms.

One request

POST /v2/lookup?wait=true
curl -X POST "https://api.digifootprint.dev/v2/lookup?wait=true" \
  -H "Authorization: Bearer dfp_your_key" \
  -H "Content-Type: application/json" \
  -d '{"query": "someuser"}'

What a Threads result looks like

From footprint.results[]
{
  "platform": "threads",
  "registered": true,
  "checkedAt": "2026-10-15T09:53:18.375Z",
  "identity": "username"
}

The full response shape - breaches, web mentions, matches versus socialMatches, and what method means - is in running a lookup.

Related platforms

Every one of these is checked in the same request as Threads.

More social media platforms: VK, Weibo, Linktree, Myspace, Snapchat · all social media

Threads lookup FAQ

Can I check a phone number on Threads?
Not directly. Threads can be reached from username. Phone numbers are checked on the messaging and social apps that sign people up by phone.
How fast is a Threads check?
Threads is checked on a full lookup, which streams results as they land - the first matches arrive in around 60 milliseconds and the whole set typically completes in a few seconds.
What happens if Threads blocks the check?
Threads is left out of the response. We never report a platform we could not confirm as "not registered" - a missing platform means unconfirmed, not absent.
Does the API return the Threads profile itself?
No. You get whether a profile exists for the input you sent, and when that was established. No profile contents, photos, followers or private data are collected or returned.

Check Threads and 885+ other platforms in one request

Free to start, no card. Then pay as you go, or pick a plan when your volume grows.