Updated 2026-08-30
You can find social media accounts by phone number with the same lookup endpoint as email and username, but the honest headline is that very few platforms let a number be confirmed. Phone lookups are in beta, and this page says exactly what comes back.
Send the number in E.164 form as phone (or as query, where it is detected). The response has the same shape as every other lookup: one entry per platform that answered, with registered, method and checkedAt. The difference is the size of the sweep. platformsChecked is the number of platforms a phone number can reach, not the 887 an email or handle is run against, and the response is honest about that number instead of inflating it.
curl -X POST "https://api.digifootprint.dev/v1/lookup?wait=true" \
-H "Authorization: Bearer dfp_your_key" \
-H "Content-Type: application/json" \
-d '{"phone": "+14155550123"}'{
"query": "+14155550123",
"platformsChecked": 1,
"matches": 1,
"socialMatches": 1,
"derivedMatches": 0,
"servedFromCache": false,
"results": [
{ "platform": "telegram", "registered": true, "method": "public_api", "checkedAt": "2026-08-30T11:20:41.902Z" }
],
"breaches": null,
"webMentions": null,
"phoneDetails": {
"valid": true,
"carrier": "Example Wireless",
"lineType": "mobile",
"countryCode": "US"
}
}Breach data and public web mentions are keyed on email addresses and handles, so for a phone query both are null: not consulted, and the field says so. The one thing a phone query gets that others do not is phoneDetails, covered below.
A phone number reaches 1 of the 887 platforms in the standard band - Telegram. That is the whole list, and it is short for a structural reason: most platforms give no way to confirm whether a number is registered, and the ones that once did have mostly closed it. We could pad the sweep with platforms that would answer null every time and report a larger platformsChecked. We do not, because a check guaranteed to return nothing is not coverage.
The rule that governs the rest of the API applies here with more force than anywhere: a platform we cannot confirm is omitted, never reported as registered: false. So a phone response naming one platform is not saying the number has no Instagram or TikTok account. It is saying nothing about those platforms at all. Coverage will grow as platforms that can be confirmed are added, and each platform page states which inputs it accepts, so the current state is always visible rather than promised.
What a phone number lacks in platform reach it partly makes up in metadata. phoneDetails reports whether the number is valid, the carrier it is assigned to, its lineType (mobile, landline or VoIP) and its countryCode. For signup risk the line type is often the useful bit: a VoIP number that exists on no platform is a different profile from a mobile number that has been on Telegram for years. When that source is not enabled for your account the block is null, and a field the provider could not fill is null inside it - never a confident placeholder.
If you hold more than one identifier for the same person, run the email and the number as separate lookups and read them together. The email gives you the footprint - social accounts, breach history, web mentions, a derived handle - and the number gives you validity, carrier and line type plus the few platforms it can reach. There is no cross-input inference: the API never asserts that the Telegram account found by number belongs to the Instagram account found by email, because it has not verified that and will not guess it. Start with finding accounts by email or by username when you can, and treat the phone lookup as a supplement.
A phone number is a more sensitive identifier than a handle, and the same beta coverage that limits this lookup also limits its potential for misuse: it confirms registration on a short list of platforms and returns no contents from any of them. It is built for signup risk, KYC and investigations on numbers a person has provided or that are already part of a case, not for locating or monitoring individuals. Our terms say so, and our privacy policy covers removal requests from anyone who is looked up. The wider picture - validity checks, carrier data and where phone fits in a risk stack - is on the phone number lookup API guide. Free lookups to start - see pricing.