# How to check someone's identity without demanding proof

> Choose a proportionate identity check, ask about one unclear detail and understand what public profiles, photos and live calls can establish.

By LustAI Editorial · Published September 5, 2026 · 6 min read
Section: [Privacy & safety](https://heylust.app/blog/topic/privacy) · Canonical: https://heylust.app/blog/how-to-verify-a-stranger-is-real

## In short

- Choose a check that fits the decision you are making, rather than requesting someone's whole identity.
- A live conversation can add context, but it cannot certify honesty or make a financial request safe.
- Check organizations through contact details you find independently of the sender.
- Someone can decline verification, and you can decide not to continue.

You can ask for a small, respectful check and still accept that complete certainty is unavailable. First decide what you need to know for the next step: who is responding, whether a claim fits, or whether an organization made a request. A photo or call cannot answer all those questions. Keep your own private details out of the exchange.

## What are you actually trying to verify?

“Are they real?” often hides several different questions. A person can be physically present in a call while using a nickname. Someone can own an established account while making a dishonest request. A stranger can be exactly who they claim to be and still cross your boundaries.

Match the check to the decision. Continuing a conversation about cooking requires less certainty than meeting in person. Sending money introduces a separate financial decision that a friendly call does not settle. You can feel comfortable with one activity and decline the next.

Before asking for proof, complete this sentence: “I need enough confidence to decide whether to…” If the answer is “keep chatting,” a clarification may be enough. If it is “share my address,” reconsider whether that step is needed at all. You are choosing a limit, not issuing an identity certificate.

## How do you ask about a small inconsistency?

Suppose someone from an online book group says they are organizing a Saturday reading. Later, they mention that the library closes on Saturdays. You can ask: “Is the reading at the library, or somewhere else?” That targets the unclear detail without accusing them of lying.

Their reply might explain that the event is at a café. You can then check the event's public listing if you are considering attending. Notice how little personal information either person needs to exchange. Your full name, home address and identification documents do not resolve the venue question.

Avoid turning the conversation into a surprise memory test. People forget details and phrase things differently. Ask about material contradictions that affect your decision, rather than tallying every wording change. The guide to [setting boundaries with someone new online](https://heylust.app/blog/how-to-set-boundaries-with-someone-new-online) helps when your need is more space, rather than more evidence.

## Can a public profile or old photograph help?

A public profile can supply context, but age, activity and a large contact list do not certify the current sender. Read what is actually being claimed. A page that discusses books may support a shared interest; it does not establish that a payment request came from a library.

Image-search dates need care too. [TinEye's explanation of its discovery dates](https://help.tineye.com/article/248-what-does-tineye-first-found-on-mean) says they record when its crawler found an image, not necessarily when the image was first published. Do not use the earliest result to declare who owns a picture or when it was taken.

If you search an image, stick to a public profile picture and inspect matching pages in context. An absent match leaves the question open. Keep private pictures and identity documents out of search uploads; [photo privacy before sharing](https://heylust.app/blog/photo-safety-what-not-to-share) applies to verification requests as much as ordinary conversation.

## What does a live call add?

A brief call can help you understand whether you enjoy talking and whether the conversation fits what you already know. Ask naturally about the shared topic. For the book-group example, you might discuss which chapter the reading will cover. You do not need a performance involving dates, documents or precise gestures.

A live exchange is still limited evidence. The [DC attorney general's consumer alert](https://oag.dc.gov/release/attorney-general-schwalb-issues-consumer-alert-3) describes fabricated audio and video used to imitate people. A convincing face or familiar voice therefore cannot validate a request by itself. Avoid treating any homemade call test as a guarantee.

You could say: “A short call would help before we make plans. Would that work for you?” They can decline. Our guide to [asking before switching to video](https://heylust.app/blog/asking-before-switching-to-video) includes options that preserve choice. If the alternative does not meet your needs, keep the relationship at its current level or step back.

## How do you check a claim about an organization?

Use a route that does not depend on the message you are checking. [EFF's phishing guidance](https://ssd.eff.org/module/how-avoid-phishing-attacks) recommends confirming unexpected requests through a different trusted channel. Find the organization's website or use an existing app, rather than signing in through a link from the sender.

In the book-group example, imagine being asked to pay a venue deposit through a personal payment link. You can contact the venue through its own public contact details and ask whether that arrangement exists. A screenshot of a booking is still material supplied by the person making the request.

Do not ask a staff member to disclose someone's private records. Keep your question about the public event or payment process: “Is this your official booking method?” If the organization cannot confirm the request, you can decline it. You do not need to uncover the sender's legal identity first.

## What can you try without making the exchange uncomfortable?

Use a short sequence, stopping once you have enough information for your chosen decision. More questions do not automatically produce more certainty. Make the next step proportionate to what is at stake.

1. **Name the next decision.** For example: “We're considering the public reading, not exchanging home addresses.” Keep the check focused on that plan.
2. **Ask about one unclear fact.** You could say: “Which venue is hosting it? The messages mention two places.” Leave room for a simple correction.
3. **Offer an optional call.** You could say: “Would ten minutes of voice or video help us plan?” Do not demand a document or a private photo in return.
4. **Verify external claims independently.** Find the venue or organization's official contact route yourself. Avoid using a link provided as both the claim and its proof.
5. **Decide and state the limit.** You could say: “That's still too uncertain for me, so I'm keeping this to chat.” No accusation is required.

## When have you checked enough for now?

Choose a stopping point before another check becomes another demand. For the reading event, a confirmed public venue may answer the practical question. It does not require you to keep searching for the organizer's home, relatives or employment history. Once the plan is clear, return to deciding whether you want to attend.

If the central request remains unclear, you can stop without an answer. “I'm going to pass on this plan” is enough. Uncertainty is information about what you can comfortably agree to today; it is not an obligation to investigate further.

## What if they say your question proves you do not trust them?

A check can be reasonable even when someone dislikes it. You can acknowledge the discomfort without dropping your boundary: “You don't have to provide anything you're uncomfortable sharing. I also won't make the plan without enough information.” Both people retain a choice.

If they demand your documents, account access or money to demonstrate good faith, stop the exchange. More disclosure is not the price of asking a question. If the next step is meeting, follow [a separate plan for meeting an online friend](https://heylust.app/blog/meeting-an-online-friend-in-person); identity confidence does not replace practical planning.

If pressure becomes threatening, seek help from someone you trust or a local victim-support service. You can end the conversation without proving deception. Our [privacy and online safety guides](https://heylust.app/blog/topic/privacy) offer further ways to protect your information while you decide what comes next.

## Questions people ask

**Is it rude to ask for a short call?**

You can ask politely and explain what would help you feel comfortable. Leave room for a refusal and decide whether another format meets your needs.

**Should we exchange identity documents?**

An informal chat is not a secure document-verification process. Avoid exchanging passports, licences or account credentials to reassure each other.

**Does a verified badge prove someone is safe?**

Read what that particular service says its badge checks. No badge establishes a person's future conduct or makes every request trustworthy.

**What if they have almost no public profile?**

A small public footprint is not proof of a false identity. You can keep the connection limited if the available information is not enough for your next step.

## Sources

- [TinEye (2019). What does TinEye “first found on” mean?](https://help.tineye.com/article/248-what-does-tineye-first-found-on-mean) · TinEye
- [EFF (2024). How to: Avoid Phishing Attacks](https://ssd.eff.org/module/how-avoid-phishing-attacks) · Electronic Frontier Foundation
- [DC Office of the Attorney General (2025). Attorney General Schwalb Issues Consumer Alert to Protect District Residents from Deepfake Telemarketing Scams](https://oag.dc.gov/release/attorney-general-schwalb-issues-consumer-alert-3) · District of Columbia Office of the Attorney General

---
LustAI Blog · https://heylust.app/blog · Editorial policy: https://heylust.app/blog/about