How AI assistants read threat-watch.com
What a machine reading this site receives: identity files, schema, crawler policy, the entity behind the name. Read weekly by a crawler, no model call. For the people who run THREAT‑WATCH; the catalogue page is for the people who choose it.
64/100
- Entity0/25
- Machine-readable33.9/35
- Retrieval access20/20
- Footprint10.2/20
Open Graph tags are incomplete
lowThe heaviest thing this reading found wrong, named in the words our fix list uses. Read off the site itself, not from a model.
22/100
Does anybody use it: audience (Tranco list, Chrome UX report, estimated organic visits), installs from registries, referring domains. Never votes, never reviews.
- Audience0/40
- Installsnot read
- References15.3/30
100/100
Is anybody home: the homepage answers, the content moves, something ships, somebody hires. Each part a dated reading from a public place; a part not read is left out and the total rescaled.
- Answers30/30
- Content moves30/30
- Shipsnot read
- Hiringnot read
- THREAT‑WATCH64
- Security medianof 456 rated58
- Atlas medianof 9977 rated58
- Retrieval botsopenverify
Whether the bots that decide citations are let in. Training bots are a separate list and are not counted here.
- llms.txtnoverify
A plain-text index at /llms.txt. Optional; read by some tools.
- Organization schemayes
schema.org Organization markup on the homepage, which is what a resolver reads a company's name and links from.
- Wikidata itemnone
Matched on the official website, never on the name. The substrate under the knowledge graph an engine resolves names against.
- Server-rendered words811swept
What a reader without JavaScript receives from the homepage.
- Identity score97/100swept
The analyzer's crawl-only section, 0-100: identity files, schema, crawler policy, sitemap. Not the analyzer score.
97/100
identity score
Not measured with the analyzer.
The full run asks four engines about this company by name. It runs on request, not on a schedule.
What is THREAT‑WATCH's Atlas Readiness?
64 of 100 on 2026-09-29, computed from four parts — entity, machine-readable, retrieval access, footprint — all four parts read. It places #74 of 364 rated Security tools.
Does THREAT‑WATCH let AI retrieval bots in?
Yes. On 2026-09-29, robots.txt at threat-watch.com disallowed none of the retrieval crawlers we check.
Does THREAT‑WATCH publish an llms.txt?
No: there was no /llms.txt at threat-watch.com on 2026-09-29.
Is THREAT‑WATCH a Wikidata entity?
No item whose official website is threat-watch.com was found on 2026-09-29.
How to read a row
- swept
- Read by a crawler: HTTP and parsing, no model call. Every row, every week.
- measured
- The full analyzer run, asked of four engines. Shown only where the company agreed to show it.
Can a retrieval engine find, resolve and quote this site? Four parts, each read by the sweep, each shown beside the total.
Entity 25 · Machine-readable 35 · Retrieval access 20 · Footprint 20
A part that was never read is left out and the total is rescaled to what was. It is never counted as zero.