← Go back

What Is the Difference Between Holder Attestation and Verified Resolution?

Published 2026-11-14 · Reviewed 2026-11-14 · By the Ingenious AI team

The short answer

Attestation is someone saying it: the case states 'submitted' and 'provider response recorded' are labelled holder attestations because the brand holder reports them. Verified resolution is the system seeing it: a re-scan confirms the target no longer resolves or exists. TakedownCoop's case code holds the two apart in the data itself — resolution_basis records which kind of 'resolved' a case earned — and never conflates them.

Run the free brand scan — one domain, no account, no card

What is attestation versus verified resolution?

Holder attestation and verified resolution are the two bases on which a takedown case can advance. Attestation records a person's report — I filed it; they replied; they say it is down. Verification records an observation — the recheck probed the target and found it gone. The distinction is written into the case system's design comments: a holder claiming resolution is attestation; only a probe makes it verification.

What is attestation versus verified resolution?

Holder attestation and verified resolution are the two bases on which a takedown case can advance. Attestation records a person's report — I filed it; they replied; they say it is down. Verification records an observation — the recheck probed the target and found it gone. The distinction is written into the case system's design comments: a holder claiming resolution is attestation; only a probe makes it verification.

The scan behind this page works in one pass over your whole street. It generates typosquat, homoglyph, affix and TLD-swap candidates from your domain, checks every one against real DNS resolution, searches Certificate Transparency logs for lookalike certificates, and tries a public, no-login check for fake profiles using your exact brand handle. For attestation versus verified resolution, that means the first artefact you work from is evidence — what resolved, what holds a certificate, what could not be checked — rather than a screenshot someone sent you.

How the scan ranks and records it

Prioritisation is built into the result list. A hit that resolves and holds a certificate scores 90; resolving without a certificate, 80; registered but not resolving, 50 with a certificate and 40 without; a name seen only in Certificate Transparency logs scores 35, or 30 when it neither resolves nor is registered. You therefore deal with attestation versus verified resolution in the order an impersonator would exploit it — live doors first — while the scan states plainly which checks it could not perform.

Why a takedown tool argues with its own users

It would be easier — and better for demo screenshots — to let any 'resolved' button close a case unconditionally. The product refuses, for a reason any processor or insurer will explain: an evidence timeline is only worth exporting if its claims are graded. A timeline that mixes 'the host emailed us' with 'we verified the site is down' as identical 'resolved' events is a story; one that labels each is a record.

The labelling costs the honest filer nothing and catches the dangerous moment — the premature close. Providers do reply 'actioned' about actions that are partial, temporary or mistaken, and holders do misread replies under time pressure. With attestation recorded as attestation, the case stays open until the probe agrees, and the seven-day recheck supplies the probe automatically. The system is not doubting you; it is refusing to let a third party's email be the last word about your brand.

A worked example, end to end

A fictional electronics brand, Voltic at voltic.io, gets a host reply saying its clone store has been 'removed'. The response is recorded on the case — as an attestation, with the reply's text. The scheduled recheck probes the domain two days later: it still resolves, now to a parking page with the same store 'returning soon'. Because the case never closed, there is nothing to resurrect — the owner escalates to the registrar with a timeline showing a claimed removal, a probe contradicting it, and dates for both. That timeline, attestation and verification kept visibly apart, is what the brand's payment processor accepts without a single follow-up question.

Turning evidence into a filing

A complaint says 'this is fake'; a packet proves it. The Pro packet generator turns a confirmed hit into a channel-correct evidence packet — one for the registrar, one for the host, and separate ones for Meta, Google Ads, marketplaces and app stores where they apply — each with a filing checklist written for that channel. The honesty rule is printed in every packet: TakedownCoop prepares the evidence and never claims to submit to a channel it cannot actually submit to. Filing stays with you or your agent, which is also why the evidence has to stand on its own.

  1. Record submissions and provider replies as attestations — that is what they are
  2. Never close a case on an email; wait for the recheck's probe
  3. Check the resolution basis before quoting any 'resolved' figure
  4. Export timelines with bases intact when processors or insurers ask
  5. Treat a contradicted attestation as escalation evidence, not as an embarrassment

After you file: tracking the case

What happens next is tracked, not hoped for. Each target becomes a case — domain, fake store, social profile or scam ad — moving through evidence collected, packet built, submitted, provider response, resolved or reappeared. TakedownCoop distinguishes what you attest (that you submitted, that a provider replied) from what is verified by re-scan (that the item is actually gone), and it schedules a recheck seven days after a case is submitted so silence from a provider becomes a prompt, not a dead end.

Where efforts like this usually go wrong

The commonest failure with attestation versus verified resolution is treating it as a message instead of a case. A report typed from memory, sent from the wrong account, missing its ticket number within the week — each is a small thing, and together they are why impersonators outlast brands that were right about everything. The artefacts exist to remove memory from the loop: the evidence block is generated, not recalled; the checklist is written for the channel, not improvised; the case holds the IDs, not an inbox thread nobody can find in month two.

There is also a sequencing mistake: acting on the loudest artefact instead of the highest-priority one. A furious customer message about a dormant name feels urgent; a quiet scan result showing a live, certified clone is urgent. The priority score exists to arbitrate exactly that conflict — 90 before 40, live before loud — and the teams that follow it spend their filing hours where the money is actually leaving.

Keeping it from coming back

Closing the loop matters because clones come back under new names and new accounts. Re-appearance monitoring re-scans and regenerates packets; the verified-genuine page lets a cautious customer verify your real door before paying anyone; and the case timeline — every event, in order — exports as JSON or CSV when a processor, insurer or marketplace asks how you handled it. That is the co-op model applied to attestation versus verified resolution: walk the street, knock with evidence, keep watch.

Frequently asked questions

Where is the distinction kept?

In the case record itself: resolution_basis separates attestation from verification, and the two attestation states are labelled in the state definitions.

Can a case be resolved by attestation alone?

It can be recorded as resolved on a holder's claim, but the basis stays 'attestation' — visibly different from a verification-basis resolution, forever.

Why do processors and insurers care?

Because they act on timelines. A graded record — claim versus observation — is auditable; a flattened one is not.

Does verification require my involvement?

No. The recheck probes the target itself; that automation is exactly what makes the verification independent of any person's say-so.

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

Related guides