Updated 2026-08-27
No. X (Twitter) does not show anyone who viewed their profile, and never has. Post authors see anonymous counts (impressions), never identities. Every app claiming to reveal profile visitors is guessing or phishing.
| Metric | Who sees it | Identifies visitors? |
|---|---|---|
| Post views (impressions) | Everyone, on each post | No — a number |
| Profile visits count | Owner, in analytics | No — a number |
| Video views | Everyone | No |
| Who viewed the profile | Nobody — the feature does not exist | |
This has been true for the platform's whole history. Unlike LinkedIn, which made profile visibility a product, X exposes only aggregates.
Apps and sites claiming to reveal profile visitors fall into three buckets, all bad: (1) guesswork dressed up — they rank accounts you already interact with; (2) engagement analysis — public likes/replies, which reflect interaction, not viewing; (3) phishing — they need your X login to "work", and the login is the product. X's API provides no visitor data, so no honest app can.
Viewing leaves no identifying trace. What does: accidentally liking an old post while scrolling, follow-then-unfollow (notifications fire immediately), and appearing in "suggested follows" through contact syncing. If you browse logged-in, those are the risks — none of them is "they saw my visit".
Logged-out browsing on x.com already leaves no owner-visible trace. Reading through nitter.app goes further: your visit never touches X's servers, there is no account to mis-click from, and post impressions aren't even incremented by your reading. Details in browsing X anonymously.
No. Premium adds analytics depth (better impression breakdowns), but visitor identities are not in the product, on any tier.
Yes, an anonymous count: owner analytics include a profile-visits number. It carries no identities. Reading via a viewer doesn't increment it.
No. X's API exposes no visitor data. A site asking for your login to show 'stalkers' is harvesting credentials — change your password if you tried one.
No. The request to X comes from the viewer's servers; your browser never contacts X. There is nothing for the owner to see.