Check a post’s client & account signals
Paste an X/Twitter status URL to see the tweet’s client source, auto-scan the author’s recent posts for a usual client, and compare MATCH / UNUSUAL / FIRST SEEN — plus About Account fields.
How it works
Tweet client
The OAuth client label on that post (e.g. Twitter for iPhone, Twitter Web App).
Live usual-client scan
Fetches the author’s recent timeline (incl. replies), then loads source for up to 20 authored posts. Mode of those sources = usual. Retweets of others are skipped.
About Account
Public based_in, install channel (App Store / Play), location_accurate, username changes. Last scan can be cached in localStorage.
FAQ
Does UNUSUAL mean the account is hacked?
No. It only means this post’s client differs from the mode of recent authored posts we just scanned. People switch devices legitimately. Always verify with the account owner.
How is “usual client” computed?
On each Check we pull recent statuses (with replies), keep up to 20 unique IDs authored by that handle, fetch each post’s source, and take the mode (excluding nulls). FIRST SEEN only if zero historical sources.
Where is data stored?
The live scan runs every Check. Optionally the last scan result is cached in your browser’s localStorage. Nothing is uploaded to our server (static hosting + direct FxTwitter API calls).