# Ssl Certificate Checker — REST API endpoint `ssl-certificate-checker`

Return the TLS certificate details of a public hostname: validity, issuer, subject, expiry and days remaining, protocol, key size, signature algorithm, serial, SHA-256 fingerprint and SANs. The scan can take a while; when status is "in_progress" call again after retry_after_seconds.

- Category: network
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/ssl-certificate-checker/execute (no API keys, 60 req/min per IP)
- Network tool: fetches a fixed, hard-coded public upstream (never a private host).
- Reference page: https://findutils.com/api/ssl-certificate-checker/
- Same tool on the other surface: https://findutils.com/mcp/ssl-certificate-checker/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/ssl-certificate-checker/execute \
  -H "Content-Type: application/json" \
  -d '{
    "domain": "example.com"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/ssl-certificate-checker
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `domain` | string | yes | Hostname to check, e.g. "example.com". A URL is accepted; only the hostname is used. |

Example arguments (verified):

```json
{
  "domain": "example.com"
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:ssl_certificate_checker`. Full MCP reference: https://findutils.com/mcp/ssl-certificate-checker/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt