# Centinel

> Centinel stops sophisticated crawlers before they extract publisher content, even when they use real browsers and residential proxies.

Centinel identifies crawlers that imitate real readers — real-browser automation,
residential proxies, and AI scraper APIs — and lets publishers block,
verify-and-allow, or watchlist them per agent.

## Product
- [How it works](https://www.centinelanalytica.com/how-it-works): See which crawlers reach your content, decide who gets access, and protect what they target.
- [Integrations](https://www.centinelanalytica.com/integrations): Deploy Centinel alongside the CDN, reverse proxy, or CMS you already run.
- [Free AI crawler audit](https://www.centinelanalytica.com/free-audit): Get a report of the crawler families reaching your content and where it is exposed.

## Guides
- [How to verify AI agents](https://www.centinelanalytica.com/blog/how-to-verify-ai-agents): How to tell a real AI agent from a spoofed one. IP ranges, reverse-DNS, TLS fingerprints, request signing, and the policy on top.
- [What is AI agent traffic?](https://www.centinelanalytica.com/blog/what-is-ai-agent-traffic): AI agent traffic is a new class of traffic: training crawlers, retrieval crawlers, agentic workflows, and spoofed scrapers. How it differs from old bots, and what publishers can do.
- [Why manage AI agents, not just block them](https://www.centinelanalytica.com/blog/why-monetize-ai-agents-not-just-block-them): Blocking everything leaves money on the table. The three paths every publisher needs are block, verify-and-allow, and watchlist. Per-agent policy beats one site-wide setting.
- [Why an interstitial challenge page is inevitable](https://www.centinelanalytica.com/blog/interstitial-page-content-protection): Passive bot detection fails against modern scrapers. A challenge page is the one reliable way to protect your content from AI crawlers.
- [How to detect browser automation beyond user agents](https://www.centinelanalytica.com/blog/detect-browser-automation): How to catch browser automation when the user agent lies. Use TLS fingerprints, HTTP/2 signals, CDP artifacts, and behavior.
- [Patched Chromium browsers explained](https://www.centinelanalytica.com/blog/patched-chromium-browsers): How scrapers patch Chromium to hide automation fingerprints, and why navigator.webdriver checks no longer catch them.
- [TLS fingerprinting explained](https://www.centinelanalytica.com/blog/tls-fingerprinting-explained): How TLS fingerprinting spots bots by the shape of their handshake. JA3, JA4, and why it catches scrapers that user-agent checks miss.
- [GPTBot vs ClaudeBot vs Bytespider: Comparison](https://www.centinelanalytica.com/blog/gptbot-vs-claudebot-vs-bytespider): A close look at the three most active AI crawlers. Who runs each one, how it behaves, and what it takes from your site.
- [robots.txt for AI bots: Complete guide](https://www.centinelanalytica.com/blog/robots-txt-ai-bots-guide): How to set up robots.txt for AI crawlers. Every directive, every major bot, and why robots.txt alone is not enough.
- [How to block AI crawlers](https://www.centinelanalytica.com/blog/how-to-block-ai-crawlers): A plain walkthrough of every way to block AI crawlers, from robots.txt to edge detection, and the tradeoff each one carries.
- [What is an AI crawler?](https://www.centinelanalytica.com/blog/what-is-an-ai-crawler): How AI crawlers differ from search engine bots, what they collect, and why they matter to your business.
- [What is web scraping?](https://www.centinelanalytica.com/blog/what-is-web-scraping): How web scraping works, why companies do it, where the law stands, and how AI changed it.

## Company
- [About](https://www.centinelanalytica.com/about): The team and mission behind Centinel.
- [Careers](https://www.centinelanalytica.com/careers): Help build bot protection for publishers.
- [Contact](https://www.centinelanalytica.com/contact): Talk with the Centinel team.

## Optional
- [Full sitemap](https://www.centinelanalytica.com/sitemap.xml)