ProofStrike
Research supported notice destinations with source provenance and clear qualified, possible, and unresolved states.
A possible or user-directed contact is not automatically eligible for sending; a creator or authorized representative reviews the destination before a consequential action.
Updated 2026-10-02
Recipient research is different from infringement discovery. Discovery can surface a submitted link or supported finding; recipient research investigates where a reviewed notice may be directed and records the source and status of that route.
A route with its source, route type, verification state, and review context visible to the authorized workflow.
A possible contact can need confirmation; an unresolved, blocked, incomplete, or temporarily unreachable destination is not silently promoted into a sendable one.
Supported automation can research recipients and prepare workflow steps. Before a consequential action, the creator or authorized representative reviews the facts, destination, and required attestations. A possible or user-directed contact is never automatically eligible for sending.
When an authorized workflow supports execution, outcome tracking keeps submission, delivery, recipient response, reported removal, and verified removal distinct.
The walkthrough uses no customer data or real-world action. The coverage page states the availability and limits for pilot evaluation.
Open walkthrough View coverageStart with the service provider's published copyright process and the U.S. Copyright Office DMCA Designated Agent Directory.
A recipient is useful only when its source, route type, verification state, and review context are visible.
Submission, delivery, recipient response, reported removal, and verified removal are different states.
Start with submitted links or supported findings, preserve the evidence, research the destination, authorize action, and track what happens next.