In this post
The question arrives every day in some variation: can you find out who sent the anonymous question?
You cannot. And that is not a technical limitation someone will fix tomorrow — it is the product. An anonymous question app that reveals the sender has stopped being an anonymous question app.
What the app knows
Two things get confused: what the server records in order to work, and what you see on screen.
| Data | Does the server need it? | Do you see it? |
|---|---|---|
| Message content | yes | yes |
| Send time | yes | usually |
| Sender's network address | yes, to contain abuse | no |
| Device identifier | sometimes, to contain abuse | no |
| Name, email or profile of the sender | never requested | no |
The last row is the one that matters. In most services of this kind, the sender does not log in. They open a link, type and send. The service cannot tell you who they are because it does not know either.
The middle rows do exist, and it is honest to say so. Every internet service logs network addresses — without that there is no way to block someone sending a hundred messages a minute. The difference between a serious service and an irresponsible one is not whether it logs: it is what the log is used for and who it is shown to.
If an anonymous messaging app offers you the IP or location of the sender, it is not an anonymous messaging app. It is an identification tool sold under another name — and you are on the wrong side of it when you are the sender.
Why the "revealers" are a scam
Searching for "find out who sent" returns dozens of sites. They all follow one of three models:
1. Payment for an invented answer. You paste the link, pay, and get a name. The name is generated. There is no way for the site to know — it has no access to the original service's database.
2. A login request. "Sign in so we can analyse." Here the product is you: the credential handed over is worth more than any fee.
3. An extension install. The extension asks for permission to read the content of the pages you open. It does read them — all of them, including your bank's.
None works because none can. Access to the records lives inside the service's server, and no service exposes that through a public API. If one did, anonymity would end the next day and the product would die.
What to do when a message crosses the line
Here the conversation changes. The right question stops being who sent it and becomes how do I make it stop.
The good news is that you do not need to know who it is. The five steps above are the order that works.
Where apps fail at this
We tested several apps in this category before building our own, and the pattern was consistent: the mechanic is well made, and moderation, where it exists, is buried.
Three things that genuinely matter and rarely show up:
Block and report on every message. Not in a settings menu, not in a support form. Right there, on the message, at the moment the person is reading what hurt them. The distance between the offence and the button determines whether it gets used.
Moderation that acts first. A filter at the entrance is different from a report afterwards. A report afterwards means someone already read it.
Notifications that do not leak the message. This is the detail almost nobody checks: if the notification shows the question on the lock screen, the content escapes every filter — the person reads it before anything can act. That is exactly what we changed in version 2.4 of our own app, and it is the change we are proudest of despite being invisible.
An anonymous question app is safe in proportion to what it does before the message reaches anyone's eyes. Everything after that is damage repair.
What to say to a teenager about this
If you are responsible for someone using this kind of app, the most useful conversation is not about banning. It is about what to do when a bad message arrives — because one will, and the instinct of the person receiving it is to hide it.
Three sentences that work better than a ban:
- "If something bad arrives, show me before you delete it." Evidence first,
venting second.
- "Blocking is not weakness, it is closing a door." Many teenagers avoid
blocking because they think it reveals that they cared.
- "You can take the link down any time." The felt obligation to keep the link
live is real and rarely spoken about.
Frequently asked questions
Does the app store the sender's IP?
Servers log network addresses to operate and to contain abuse — that is standard for any internet service and applies to essentially every app in this category. What does not happen is that data being shown to the message's recipient. If it were, the product would stop being anonymous and become an identification tool.
Are there apps that reveal the sender?
There are sites and extensions promising it. None work: they have no access to the original service's server. Their business model is charging for an invented answer, or asking for your login to 'analyse' — at which point the data handed over is yours.
Can a court order reveal it?
In a criminal case, a competent authority can request records from the service. That is a formal process run by police or courts, not something a user does through the app. For a serious threat, the path is filing a report with the screenshots in hand.
Does blocking reveal who I blocked?
No. Blocking acts on the message source without exposing identity on either side.