Skip to main content
Every triage report includes a coverage object that reports which analysis steps ran successfully. Use it to interpret partial results honestly.

Fields

profile_scraped
boolean
required
true if Tumban successfully loaded the profile page and extracted bio, images, and links.
external_search_completed
boolean
required
true if the web search for external mentions of the profile completed.
Number of links Tumban traversed during analysis. Counts every URL followed from the profile bio or surfaced via referrer cross-reference — not only social profiles, despite the name. A value of 0 means the profile had no traversable outbound links.
blocked_by_login
string[]
URLs Tumban could not analyze because they required login. Treated as neutral; not used to inflate the risk score.
referrer_domains_received
integer
Number of referrer domains you supplied with the scan via metadata.referrer_domains (an array of domain names). Tumban does not read analytics platforms on your behalf — this field counts only what you passed in. When you do not supply referrer_domains, this is 0.
referrer_domains_after_filter
integer
Referrer domains remaining after Tumban filters out search engines and analytics platforms.
referrer_matches_found
integer
Number of the referrer domains you supplied that Tumban corroborated against the profile’s external web-search results — i.e. a supplied referrer domain also appeared among the URLs found mentioning the profile elsewhere on the web. This is not a match against a prohibited-platform list.

When you’ll see partial coverage

A scan that experienced one or more step failures (slow page, login wall, transient model error) today comes back with status: "completed" and the partial-coverage details recorded inside the coverage object itself — social_links_checked may be lower than expected, individual URLs may show up under blocked_by_login, and so on. Inspect coverage before drawing conclusions about edges; the recommendation and risk_score are still meaningful, but they were produced from a narrower input set. Scans that experienced step failures still come back as status: "completed" — the coverage object is the canonical record of what ran and what was skipped (see Status values). Read from coverage to detect partial pipelines; do not gate partial-handling logic on the status field.