threads.com
No scorethe page couldn’t be read
In WikidataThreads: social networking site operated by Meta Platforms
No scorethe page couldn’t be read
In WikidataThreads: social networking site operated by Meta Platforms
This site asks bots like ours not to read its pages, so we didn’t. What public records say is below; the score needs the page.
Among the top 1K sites.
A popularity band, not a visit count.
Tranco: #597 · Chrome UX Report: Top 1,000 · Majestic Million: #448
| Source | Says | As of |
|---|---|---|
| TrancoA research ranking that combines several traffic and link sources, published daily. | #597 | list of 7 Oct 2026 |
| Chrome UX ReportRank buckets from Google’s real Chrome traffic, published monthly. | Top 1,000 | Aug 2026 |
| Majestic MillionRanks sites by how many separate networks link to them (links, not visits), published daily. CC BY 3.0 | #448 | list of 8 Oct 2026 |
No framework or CMS shows in the page; it uses SEO, Business tools.
Around it: SEO, Business tools.
threads.com TXT google-site-verification=iwbg2_0IjhDFg0htAQPuQSx5KOgJB8mzuX-OfbeB0PA
threads.com TXT facebook-domain-verification=majzldde6hpot8e5i03ci1wq5e4qiu
Business tools can stay listed after a site stops using them.
We couldn’t read the page; outside records are below.
Signals, not a judgement: missing details are common on small, honest sites.
A second opinion on its security setup: Mozilla’s HTTP Observatory grades the site when you open it. Ten checks before you buy · A signal looks wrong? Report it
Looks like: Forum or community.
We couldn’t read the page, so there are no words of its own to quote.
From what Wikidata says it is: we couldn’t read the page.
Q120281745: Threads, microblogging
Q120281745: Threads
Each name is quoted from its source. A brand and the company that owns it often go by different names.
Wikidata, the free knowledge base behind Wikipedia, lists this domain as the official website of this item. Volunteers write it; each item shows its sources.
User-agent: Amazonbot · Disallow: /
User-agent: Applebot-Extended · Disallow: /
User-agent: Brightbot · Disallow: /
User-agent: ClaudeBot · Disallow: /
User-agent: Google-Extended · Disallow: /
User-agent: GPTBot · Disallow: /
User-agent: PerplexityBot · Disallow: /
User-agent: * · Disallow: /
What its robots.txt and robots tags ask of AI crawlers. Each crawler chooses whether to follow it.
Read from what the page says about itself; we haven’t checked whether it’s true.
We couldn’t read the page, so we couldn’t look for traces.
AI traces: Couldn’t check
AI site builders leave traces in the sites they make. We look for the traces of 53 of them and show every match with the line it came from, so you can check it yourself.
We test this on 2,312 sites whose makers we know, and publish what we get wrong.
How we test it · Every builder we know · How to tell if a site was built with AI
No score: we couldn’t read the page, and outside records alone would mislead.
Registered in 1995; first archived in 2002.
In the web archive: captured in 25 of 25 years · see the first capture
| Scanned | Score | AI traces | Popularity |
|---|---|---|---|
| shown above | — | None found | Top 1K |
| — | None found | Top 1K |
Findings can change when a site changes or when we update our signatures; each scan keeps the version it used.
Only from what anyone can see: the site’s public pages and public records.
924 checks on 14 Oct 2026, with version 0.5.0 of our checks and version 1.1 of the score.
Automated findings from the site’s public home page and public records, as of 14 Oct 2026. They describe what we found, not the people or business behind the site, and they may be incomplete or out of date. This is information, not advice. Terms · Report an error
Is this your site? Ask for a correction.