# SSL Cipher Suite & Security Scanner (`andok/ssl-cipher-checker`) Actor

Audit TLS versions and negotiated cipher suites for a list of domains to ensure compliance and robust web security.

- **URL**: https://apify.com/andok/ssl-cipher-checker.md
- **Developed by:** [Andok](https://apify.com/andok) (community)
- **Categories:** Business, Developer tools
- **Features:** Limited permissions
- **Stats:** 4 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.47 / 1,000 host scans

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## TLS Cipher Suite Scanner

Scan TLS cipher suites to detect weak or deprecated configurations across your entire domain inventory. Outdated ciphers like RC4 or CBC-mode suites remain a top finding in compliance audits, and many teams lack visibility until a scanner flags them. Check hundreds of hosts in parallel and get structured results ready for reporting.

### Features

- **Cipher suite detection** — identifies the exact cipher suite negotiated during the TLS handshake
- **Protocol version reporting** — reports TLS 1.2, TLS 1.3, or older protocol versions for each host
- **Certificate validation** — checks whether the server certificate is authorized and trusted
- **ALPN negotiation** — reports Application-Layer Protocol Negotiation results (h2, http/1.1)
- **Bulk scanning** — check hundreds of domains concurrently in a single run
- **Flexible input** — accepts plain domains, URLs, or objects with `domain`/`url` fields

### Input

| Field | Type | Required | Default | Description |
|-------|------|----------|---------|-------------|
| `domains` | `array` | Yes | — | List of domains or hostnames to scan (e.g., `example.com`). Also accepts URLs or objects with `domain`/`url` fields |
| `timeoutSeconds` | `integer` | No | `15` | Connection timeout per domain in seconds (1-60) |
| `concurrency` | `integer` | No | `10` | Number of domains to scan in parallel (1-50) |

#### Input Example

```json
{
  "domains": [
    "google.com",
    "github.com",
    "example.com"
  ],
  "concurrency": 20
}
```

### Output

Each domain produces one dataset record with the negotiated TLS parameters and certificate status.

Key output fields:

- `domain` (`string`) — the hostname that was scanned
- `status` (`string`) — scan result status (`OK` or `ERROR`)
- `protocol` (`string`) — negotiated TLS version (e.g., `TLSv1.3`)
- `cipher` (`string`) — negotiated cipher suite name (e.g., `TLS_AES_256_GCM_SHA384`)
- `authorized` (`boolean`) — whether the server certificate is trusted
- `alpn` (`string`) — negotiated ALPN protocol (e.g., `h2`)
- `error` (`string | null`) — error message if the connection failed
- `checkedAt` (`string`) — ISO 8601 timestamp

#### Output Example

```json
{
  "domain": "github.com",
  "status": "OK",
  "protocol": "TLSv1.3",
  "cipher": "TLS_AES_128_GCM_SHA256",
  "authorized": true,
  "alpn": "h2",
  "error": null,
  "checkedAt": "2026-03-09T12:00:00.000Z"
}
```

### Pricing

| Event | Cost |
|-------|------|
| Host Scan | $0.001 |

Pay only for hosts successfully scanned. Respects your per-run spending limit.

### Use Cases

- **Security audits** — verify that all enterprise endpoints use TLS 1.2+ with strong cipher suites
- **PCI DSS compliance** — confirm no deprecated protocols or weak ciphers are in use across payment-processing domains
- **Vendor risk assessment** — bulk-scan third-party domains to evaluate their TLS configurations before onboarding
- **Infrastructure migration** — validate cipher suite consistency after moving to new hosting or CDN providers
- **Scheduled monitoring** — run weekly scans to detect cipher downgrades or misconfigurations after server changes

### Related Actors

| Actor | What it adds |
|-------|-------------|
| [Security Headers Analyzer](https://apify.com/andok/security-headers-analyzer) | Audit HTTP security headers (HSTS, CSP, etc.) to complement TLS-level checks |
| [SSL Certificate Monitor](https://apify.com/andok/ssl-certificate-monitor) | Monitor certificate expiry dates alongside cipher suite auditing |
| [Subdomain Finder](https://apify.com/andok/subdomain-finder) | Discover all subdomains first, then feed them into cipher scanning |

# Actor input Schema

## `domains` (type: `array`):

List of domains or hostnames to scan for TLS cipher suites (e.g., example.com). Also accepts full URLs or objects with domain/url fields.

## `timeoutSeconds` (type: `integer`):

Connection timeout per domain in seconds. Increase for hosts behind firewalls or with slow TLS handshakes.

## `concurrency` (type: `integer`):

Number of domains to scan in parallel. Higher values speed up large batches but may trigger network-level rate limiting.

## Actor input object example

```json
{
  "domains": [
    "google.com"
  ],
  "timeoutSeconds": 15,
  "concurrency": 10
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `resultsCsv` (type: `string`):

No description

## `run` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        "google.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("andok/ssl-cipher-checker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "domains": ["google.com"] }

# Run the Actor and wait for it to finish
run = client.actor("andok/ssl-cipher-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    "google.com"
  ]
}' |
apify call andok/ssl-cipher-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,andok/ssl-cipher-checker"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/FQaLeDs2nmaYlOxhr/builds/oAYZ96PwKDEdBaOWm/openapi.json