Antibot Detector

Scenario: You're auditing a website's security posture as part of a penetration test.

How Antibot Detector Helps:

• Catalog all security layers protecting the application
• Identify potential gaps in bot protection coverage
• Document security technologies for reports
• Compare security implementations across different pages

Scenario: You want to understand what security technologies competitors are using.

How Antibot Detector Helps:

• Quickly survey security stacks across multiple competitor sites
• Identify industry trends in anti-bot adoption
• Export historical data for trend analysis
• Benchmark your own security against competitors

Scenario: You're learning about web security and want to understand how anti-bot systems work in practice.

How Antibot Detector Helps:

• See real-world examples of security technologies in action
• Understand which detection methods reveal each technology
• Compare different implementations across websites
• Learn by examining the open-source detection logic

Explanation: First-time detection on a domain takes longer because the cache is empty. Subsequent visits to the same domain will be much faster (typically <1 second) due to 12-hour caching.

Expected Performance:

• First visit: 2-4 seconds (building cache)
• Cached visits: <1 second (instant results)
• Cache hit rate: ~80% for typical browsing patterns

Note: Complex pages with many scripts may take slightly longer on first detection.

Common Issues:

• Chrome Version: Ensure you're using Chrome 88+ (Manifest V3 requirement)
• Folder Deleted: The extension folder must remain in its original location
• Permissions: Check file permissions allow Chrome to read the extension files
• Conflicting Extensions: Other extensions may interfere (try disabling temporarily)

Reset Steps:

1. Remove the extension from chrome://extensions
2. Delete and re-download/re-extract the extension files
3. Follow the installation steps again carefully
4. Check Chrome console for specific error messages

Why This Happens:

• Anti-bot services constantly evolve their implementations
• Some services use conditional loading (only appear for suspicious traffic)
• Detection rules may need updates for new service versions

How to Help:

1. Report false positives: Open a GitHub issue with the URL and detected technology
2. Report missing detections: Include the URL and which technology you know is present
3. Contribute rules: Submit a pull request with updated detection JSON files

Detection accuracy improves with community contributions!

Absolutely not. Antibot Detector is designed with privacy as a core principle:

• ✅ 100% local processing - all detection happens in your browser
• ✅ No telemetry - zero analytics, tracking, or data collection
• ✅ No external requests - doesn't communicate with any external servers
• ✅ Open source - you can audit the entire codebase on GitHub

Your browsing data and detection results never leave your computer.

Currently, Antibot Detector is Chrome-only (and Chromium-based browsers like Edge, Brave, Vivaldi).

Why Chrome-only? The extension uses Chrome's Manifest V3 API, which provides the best security and performance. While technically possible to port to Firefox, it would require significant adaptation due to Firefox's different extension architecture.

Community contributions welcome: If you're interested in porting to Firefox, feel free to fork the repo and submit a pull request!

License Requirement: Commercial use requires a separate license. However, Antibot Detector is best used as a reconnaissance tool, not for production scraping.

Better Solution for Commercial Scraping:

• Use Antibot Detector to identify what protection a site uses
• Use Scrapfly's API to bypass those protections automatically
• Scrapfly handles Cloudflare, DataDome, PerimeterX, Akamai, and more out-of-the-box

This workflow (detect → bypass with Scrapfly) is much more reliable than trying to build custom bypass logic for each anti-bot system.

Detection accuracy varies by technology type:

Confidence scores help you gauge reliability - higher scores (80%+) indicate very reliable detection.

Yes! Antibot Detector supports custom detection rules through the built-in Rules Editor:

1. Click the extension icon → Settings
2. Navigate to Rules Editor
3. Create a new JSON rule file or edit existing ones
4. Use the Import/Export feature to share rules with your team

Rule Structure: Detection rules are JSON-based and specify patterns for cookies, DOM elements, URLs, headers, and more.

Contribute: If you create rules for a new anti-bot service, please consider submitting them as a PR to help the community!

Antibot Detector is actively maintained with updates based on:

• New anti-bot services: Rules added as new technologies emerge
• Service updates: Existing rules updated when services change their implementations
• Bug fixes: Issues reported by the community are addressed promptly
• Performance improvements: Ongoing optimizations to detection speed

Stay updated: Watch the GitHub repository for release notifications, or check the Releases page for changelog details.

Auto-updates: Once the extension is published to the Chrome Web Store, it will update automatically. For now, manual updates are required (re-download and load unpacked).