Why Do Honest Scan Results Say 'Could Not Be Checked'?
Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team
The short answer
Because the alternative is fabrication. When a platform login wall blocks the public profile check, or a Certificate Transparency source fails, TakedownCoop's scanner records that the check could not be performed — the landing page states the rule plainly: 'Anything we cannot check, we say so — never a made-up result.' A result with stated limits is evidence; a result with invented completeness is a liability.
What is honest 'could not be checked' results?
'Could not be checked' is a first-class scan verdict, not an error message. It appears where a public, no-login profile check meets a login redirect or a bot block, and where CT sources answer with an error — the two places the scanner's own code names. The verdict preserves the difference between 'no threat found' and 'no finding possible', which are opposite conclusions.
What is honest 'could not be checked' results?
'Could not be checked' is a first-class scan verdict, not an error message. It appears where a public, no-login profile check meets a login redirect or a bot block, and where CT sources answer with an error — the two places the scanner's own code names. The verdict preserves the difference between 'no threat found' and 'no finding possible', which are opposite conclusions.
Detection starts with the free scan on TakedownCoop's home page. From your one genuine domain, the scanner builds the candidate set an impersonator would plausibly register — typosquats made by deleting, transposing, duplicating or substituting letters, homoglyph lookalikes, affix combinations, and TLD swaps — and tests each candidate against live DNS. That order matters for honest 'could not be checked' results: generation first, evidence second, and nothing is called a hit until DNS or a certificate log says it is real.
How the scan ranks and records it
The results are ranked, not dumped. The scanner's own priority scores put a resolving lookalike with a certificate at 90 and one without at 80, registered-but-dormant names at 50 or 40 depending on whether a certificate exists, and CT-only discoveries at 35 or 30. Certificate Transparency evidence is filtered for relevance — shared certificates carrying unrelated names are not treated as evidence against your brand — and any check that could not be performed is reported as exactly that, never converted into a reassuring claim.
The most valuable sentence in the report
Consider what each alternative would do to a takedown. If a blocked profile check were reported as 'no profile found', a brand could repeat that claim in a filing — and be wrong, in writing, in front of the platform that hosts the profile. If a failed CT lookup were reported as 'no certificates', the evidence block would assert something the scanner never saw. Abuse desks forgive an incomplete packet; they do not forgive an invented one, and neither do courts of opinion.
The discipline also protects the scan's positive findings. A tool willing to state its failures precisely is believable when it reports a resolving lookalike at priority 90 with DNS detail. That is why the rule is structural — it is in the scanner's verdict strings, the CT failure notes and the landing page's promise — rather than a tone choice in the results template.
A worked example, end to end
A fictional outfitter, Trailhead Co. at trailheadco.com, scans and gets: three DNS hits, CT checked with its count shown, one platform reporting no profile at the exact handle, and one answering with a redirect to a login page — recorded as could not be checked. The owner verifies that platform manually from a logged-in account, finds nothing, and only then treats the social surface as reviewed. The scan's packets for the DNS hits go out the same day, their credibility untouched by the one honest blank.
Turning evidence into a filing
Evidence only helps if it arrives in the shape the channel expects. TakedownCoop's packet generator produces one packet per channel — registrar, host, Meta, Google Ads, marketplace, app store — each with that channel's own subject line and filing checklist, built on the same evidence block: genuine brand, lookalike domain, detection method, DNS and CT evidence, and priority. Packets are a Pro feature ($49/mo; Agency $99/mo covers multiple client brands), and they are prepared for the brand owner or their authorised agent to file.
- Read 'could not be checked' as an open task, never as a clean result
- Verify blocked profile checks manually from a logged-in account
- Re-run a scan whose CT note reports a failure before treating CT as clear
- Keep the honest verdicts in the evidence — filings inherit the scan's credibility
- Distrust any report, from any tool, that never admits a limit
After you file: tracking the case
The follow-through is where most takedowns quietly die, so the product tracks it as a case. States run from evidence collected through packet built, submitted and provider response, to resolved — and a case can be re-opened as reappeared when monitoring finds the same threat back. Submitted and provider-response states are recorded as holder attestations, honestly labelled, while a verified resolution needs a re-scan showing the target is gone. The recheck after submission is set at seven days.
Where efforts like this usually go wrong
A second failure is overreach — padding a filing with suspicions the evidence does not carry. TakedownCoop's scan is careful to separate what it confirmed from what it could not check, and a filing should inherit that discipline exactly: claim the resolving domain, the certificate, the screenshots you actually hold, and stop there. Reviewers act fastest on filings whose every sentence they can verify, and a single inflated claim taxes all the true ones beside it.
Finally, do not let a win delete the record. Brands that close a takedown by celebrating and clearing the folder meet the reappearance defenceless; brands that keep the case — evidence, tickets, verified resolution and all — meet it with precedent. In this product the record is not paperwork after the work. Kept properly, it is most of the work, because the second filing is always the one that ends the pattern.
Keeping it from coming back
Impersonators rotate, so a one-off filing is a snapshot, not a solution. Monitoring re-scans the domain, and when a known threat reappears the case re-opens and its packet regenerates. Pair that with the verified-genuine page — a public page where customers can confirm they are dealing with the real brand — and the timeline export (JSON and CSV) that processors and insurers ask for, and honest 'could not be checked' results stops depending on whoever happens to notice the fake next.
Frequently asked questions
Where can 'could not be checked' appear?
In the profile check — login redirects and bot blocks — and in Certificate Transparency, where a source failure is recorded in the CT note.
Does it mean the scan failed?
No. It means one specific check could not be performed publicly, and the scan said so instead of guessing. The DNS and CT results stand on their own.
What should I do about a blocked profile check?
Check that platform manually from a logged-in account. The public check's limit is the login wall, and only an account gets past it.
Why not just log in and check everything?
The scan is public and no-login by design — no account, no card, no credentials. Its checks are the ones that can be done honestly in public.
Keep exploring
TakedownCoop home — run the free brand scan · All TakedownCoop guides · Pricing — Free, Pro and Agency · Get a license key · Takedown cases · My street (dashboard) · Terms · Privacy · Ingenious AI — all platforms