Updated 2026-08-27
Read profiles through a viewer such as nitter.app — your browser talks to the viewer, never to X's servers, so X gets no visit, no cookie, no IP. For stronger anonymity add a VPN so the viewer doesn't see your IP either.
Three different parties could identify you, and they need different countermeasures:
| Who could see you | What they'd see | Countermeasure |
|---|---|---|
| X itself | IP, browser fingerprint, cookies — even logged out | Don't visit X: use a viewer or RSS |
| The viewer site | Your IP and requested pages | VPN or Tor |
| The profile owner | Nothing. X has no "who viewed me" feature | None needed |
Visiting x.com logged-out still hands X your IP address and a workable browser fingerprint, and X sets cookies that link your visits together. If your goal is only "don't tie this reading to my X account", logging out is enough. If the goal is "X shouldn't have a record of me at all", it isn't.
With a viewer like nitter.app, your browser requests pages from us and we fetch from X server-side. X sees our servers, not you. There is no account, no sign-up, and the pages work without JavaScript for anything already cached — which also means they work in hardened browsers that block scripts.
Add a VPN and the viewer only sees the VPN exit's IP. Tor works too — cached pages render fine in Tor Browser. One honest caveat: a cold (never-cached) profile triggers our automated-browser check before a live fetch, and Tor exits score badly on such checks, so a first-ever view of an obscure profile may not go through on Tor. Anything cached — which includes every popular profile — reads fine.
The quietest option: subscribe to an account's feed at rss.gurify.com and read new posts in your RSS reader. After the one-time setup, you visit no website at all.
Only public posts are readable — anonymity tools don't open protected accounts. And interacting (liking, replying, following) always requires an account, which is by definition not anonymous.
X sees a visit from your IP with your browser fingerprint and sets cookies. It can't tie it to an account you never log into, but it is not nothing. Reading through a viewer means X never sees the visit at all.
No. X has no profile-view notifications for anyone, and a viewer adds a second wall — the request to X comes from the viewer's servers.
Yes for all cached pages. A never-viewed profile's first fetch requires passing an automatic bot check, which low-reputation Tor exits sometimes fail; VPNs are generally fine.
Cached profiles and posts render without JavaScript. JS is needed only the first time an uncached profile is fetched (for the bot check).