AttackerView
Check any website's security headers, HTTPS, DNS and email authentication (SPF, DKIM, DMARC) in seconds.
- Brand
- Unknown
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
Ask "is example.com secure?" and AttackerView runs a passive security check of the domain in a few seconds. No account or login needed. What it checks: - Security headers, Content Security Policy and clickjacking protection - HTTPS: the HTTP to HTTPS redirect and the TLS configuration - DNS, DNSSEC and CAA records - Email authentication: SPF, DKIM, DMARC and MTA-STS Each issue comes with its severity, the evidence and how to fix it, plus a link to a fix guide where one exists. The check makes one request to the homepage plus DNS and TLS lookups. It does not log in, crawl or send attacks, so it cannot find vulnerabilities in the application itself. For that, run a full AttackerView scan.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- No account required
- First tracked
- 2026-10-01
- Tool count
- 1
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competitive lineup
1 tool agents can invoke
AttackerView Claude Connector FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve AttackerView's Claude Connector discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.