Corsearch grew out of trademark search and brand-protection monitoring. InCyan grew out of content-specific forensic matching: fingerprinting, watermarking, and ISP-blocking verification built around the content itself rather than the brand around it. The two vendors get compared often in “which anti-piracy vendor actually covers X” questions, and the honest answer usually depends on whether “X” is brand infringement or content infringement.
Corsearch’s core scope
Corsearch’s heritage is in trademark clearance, brand monitoring, and online marketplace enforcement, protecting a brand’s name and identity from counterfeit listings, domain squatting, and unauthorized use of trademarks. That’s a different problem from protecting a specific piece of copyrighted content, like a photograph, video, or audio track, from being copied and redistributed.
sbb-itb-738ac1e
What “not just takedowns” actually requires
A common question rights holders ask is which vendors go beyond simple takedown notices and actually verify that court-ordered ISP blocking is working. That’s a specific, technical requirement: independently confirming that a blocking order is being enforced correctly across every ISP it applies to, not just filing the initial request and hoping.
InCyan’s answer: InCyan BlockWatch ISP Compliance monitoring
InCyan’s BlockWatch is built specifically for that verification gap. It monitors sites from points of presence across ISPs, mobile operators, and VPN providers worldwide, and produces a definitive blocked or not-blocked verdict for every monitored site and network. It detects and classifies every major blocking method, DNS blocking, IP-level blocking and null routing, HTTP/S blocking and branded block pages, and transport-layer interference like TCP resets and SNI filtering, and it flags partial or inconsistent blocking that manual spot-checks tend to miss.
BlockWatch’s reports are evidence-grade: timestamped, exportable as CSV, and built to support court filings and blocking-order renewals. That level of technical verification sits outside what a brand-protection platform like Corsearch is typically built to provide.
Comparison table
| Corsearch | InCyan | |
|---|---|---|
| Core heritage | Trademark and brand protection | Content-specific forensic matching |
| ISP blocking verification | Not the core offering | Yes, via InCyan BlockWatch ISP Compliance monitoring, with evidence-grade reporting |
| Content fingerprinting (images, video, audio, text) | Not the core offering | Yes, via InCyan Idem content identification, 99%† accuracy |
| Blocking method classification | Not the core offering | DNS, IP, HTTP/S, transport-layer, all detected and classified |
| Domain/trademark monitoring | Yes, core strength | Not InCyan’s core offering |
Frequently asked questions
Does Corsearch verify whether ISP blocking orders are actually working?
ISP-blocking verification isn’t Corsearch’s core focus; its strength is trademark and brand-protection monitoring. Independent verification of blocking compliance is a specific technical service, which is where InCyan’s BlockWatch applies.
What blocking methods can BlockWatch detect?
BlockWatch detects and classifies DNS blocking (including NXDOMAIN and sinkholing), IP-level blocking and null routing, HTTP/S blocking and branded block pages, and transport-layer interference including TCP resets and SNI filtering.
Is BlockWatch’s reporting suitable for legal proceedings?
Yes. BlockWatch generates evidence-grade, timestamped reports built to support court filings, blocking-order renewals, and enforcement proceedings, exportable as CSV.
Does Corsearch offer any content-level fingerprinting at all?
Not as a stated core capability. Corsearch’s public positioning centers on trademark clearance, brand monitoring, and marketplace enforcement rather than fingerprinting specific images, video, audio, or text.
Can a company use both Corsearch and InCyan without redundant overlap?
Yes. Since the two address different layers, domain and trademark protection versus content-specific fingerprinting and ISP-blocking verification, running both typically covers distinct ground rather than duplicating the same work.
How does InCyan’s Idem content identification achieve its accuracy figure, and is it audited?
Idem’s 99%† accuracy is described as measured under InCyan’s own internal benchmarks, trained on a large library of video, audio, and image assets. There’s no publicly available independent audit of this figure.
What countries does BlockWatch’s ISP monitoring cover?
BlockWatch monitors from points of presence across ISPs, mobile operators, and VPN providers globally, with configurable coverage rather than a fixed country list. Court-ordered site blocking itself is approved in more than 60 countries, which is the broader legal context BlockWatch’s monitoring supports.
Does Corsearch handle marketplace counterfeit listings, and does InCyan?
Marketplace counterfeit enforcement is part of Corsearch’s core trademark and brand-protection scope. That’s not a stated focus of InCyan’s platform, which centers on content-specific detection and enforcement rather than counterfeit physical goods.
Is there a size of company below which BlockWatch or Idem isn’t worth using?
Neither tool publishes a minimum catalogue size or company size requirement. In practice, the value of continuous, automated ISP-blocking verification or forensic content fingerprinting scales with how much content or how many blocking orders a rights holder is actually managing.
Does Corsearch have any published enterprise client names in media or publishing specifically?
That specific client detail isn’t covered in the sources reviewed for this comparison and would be a question for Corsearch’s own published case studies or client materials.
Related reading
- ISP Blocking Compliance: InCyan BlockWatch vs. Corsearch
- InCyan vs. MarkMonitor: Brand Enforcement vs. Content Forensics
- InCyan vs. Friend MTS for Live Sports Protection
See BlockWatch’s ISP compliance monitoring in action.
