A match is a lead. Evidence comes next.

Public profile data can include a profile URL, displayed name, avatar or biography when the source makes those fields available. A link lets you inspect the original context.

Account-existence signals indicate that a service appears to recognize the supplied identifier. They may not reveal a public profile, identify the account owner, or establish recent activity.

Derived leads need additional checking. A handle suggested by the part of an email before the @ is a candidate, not a confirmed email-to-account link.

A successful HTTP response does not necessarily contain a profile. A website may return a sign-in screen, a CAPTCHA, a generic landing page or a missing-account message with the same status code.

Modules interpret service-specific responses. Useful evidence might be a matching username inside structured profile data or an explicit account-status response. Available fields and reliability vary by source; Opsis cannot make an upstream service disclose information it does not return.

Opsis uses positive and negative fixtures to check module behavior. A positive fixture is an identifier expected to exist; a negative fixture is expected not to exist. Both matter: a module that reports every input as a match is not a useful lookup.

These are samples at a point in time, not certification of every future result. Accounts can change, fixtures can become stale, and services can alter their responses or apply rate limits. Tests help identify problems; they do not establish a universal accuracy percentage.

A clean negative means the check found a recognized absence signal. A blocked request, timeout, unavailable credential or response the parser cannot understand is inconclusive. Do not turn an unavailable source into “this person has no account.”

A search can contain useful results even when some sources do not respond. Check the available profile evidence and the report’s coverage before deciding whether to investigate further.

1. Open the original public source when a link is provided.
2. Compare the exact identifier, not just a similar display name.
3. Look for independent context, such as a public cross-link or an address explicitly published on the profile.
4. Record the date and distinguish observations from your interpretation.
5. Keep uncertainty in the conclusion. A shared name, photo or handle is not proof of common ownership.

For a concrete workflow, read our reverse email lookup guide. If a result appears incorrect, contact support with the platform and issue; do not send passwords or account tokens.