ssl_blacklist
abuse.ch SSL Blacklist (SSLBL): check whether a TLS certificate SHA1 fingerprint is blacklisted as malware / botnet C&C infrastructure (listing date and reason, e.g. "QuasarRAT C&C"), check an IP against the SSLBL botnet C2 IP list, or list the most recent blacklisted certificates filtered by rea...
This record as markdown: /tools/com-it-scorptech-x402/ssl-blacklist.md
What ssl_blacklist does on ScorpTech x402 API
AI agents call ssl_blacklist to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ip | string | — | IP to check against the SSLBL botnet C2 IP blacklist |
sha1 | string | — | certificate SHA1 fingerprint, 40 hex (colons / spaces allowed) |
limit | integer | — | list mode: entries 1-500 (default 50), newest first |
since | string | — | list mode: only listings on or after YYYY-MM-DD |
reason | string | — | list mode: substring filter on the listing reason, e.g. AsyncRAT |
Parameters from the server's own tool schema.
Why ssl_blacklist is rated Low
Even though ssl_blacklist only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs ssl_blacklist safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ssl_blacklist, this is the rule to start with:
ssl_blacklist is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every ssl_blacklist call is checked against it from then on.
Questions about ssl_blacklist
abuse.ch SSL Blacklist (SSLBL): check whether a TLS certificate SHA1 fingerprint is blacklisted as malware / botnet C&C infrastructure (listing date and reason, e.g. "QuasarRAT C&C"), check an IP against the SSLBL botnet C2 IP list, or list the most recent blacklisted certificates filtered by reason. Several thousand certificates; CC0, commercial use allowed. Cached locally, refreshed every 30 minutes. Price: $0.005 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/ssl-blacklist. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
ssl_blacklist accepts 5 parameters: ip, sha1, limit, since, reason. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for ssl_blacklist: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ScorpTech x402 API. Nothing to install.
ssl_blacklist is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ssl_blacklist rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for ssl_blacklist. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
ssl_blacklist is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue