Digital Footprint checks VK from an username as part of every lookup, alongside 886+ 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.
Instant tier for username lookups - answered in well under a second
VK is checked from a username. The response says whether that handle exists on VK - registered: true or registered: false - with the moment that was established in checkedAt. An email address on its own cannot reach VK; 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.
VK is in the instant tier: with ?instant=true it is among the first platforms answered, in well under a second. On a full lookup it is checked alongside every other platform and streamed as it lands.
If VK 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".
curl -X POST "https://api.digifootprint.dev/v1/lookup?wait=true" \
-H "Authorization: Bearer dfp_your_key" \
-H "Content-Type: application/json" \
-d '{"query": "someuser"}'{
"platform": "vk",
"registered": true,
"checkedAt": "2026-08-30T01:50:27.217Z"
}The full response shape - breaches, web mentions, matches versus socialMatches, and what method means - is in running a lookup.
Every one of these is checked in the same request as VK.
?instant=true it is answered in well under a second. A full lookup streams it as soon as it lands.