Security & delivery
/api/v1/tls-configurationPacketFlo TLS Configuration API
Which TLS protocol versions a hostname accepts, what it negotiates by default (version, cipher, ALPN, SNI), certificate trust, and handshake timing, measured from this server. A protocol result is "supported", "not-supported", or "unable-to-test" when the check could not reach a clean verdict. Costs 4 credits per request.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Hostname or https:// URL (reduced to its hostname). Private and internal addresses are rejected. |
Example request
curl "https://packetflo.io/api/v1/tls-configuration?domain=example.com&api_key=YOUR_API_KEY"
Example response
{ "ok": true, "data": { "domain": "example.com", "ip": "172.66.147.243", "families": [ { "family": 4, "ip": "172.66.147.243", "status": "ok", "version": "TLSv1.3", "cipher": "TLS_AES_256_GCM_SHA384", "alpn": "h2", "certFingerprint": "61:53:A9:6F:...:22:00", "totalMs": 53, "error": null }, { "family": 6, "ip": "2606:4700:83b5:72db:f20d:0:ef6b:ff98", "status": "ok", "version": "TLSv1.3", "cipher": "TLS_AES_256_GCM_SHA384", "alpn": "h2", "certFingerprint": "61:53:A9:6F:...:22:00", "totalMs": 51, "error": null } ], "protocols": [ { "version": "TLSv1.3", "result": "supported" }, { "version": "TLSv1.2", "result": "supported" }, { "version": "TLSv1.1", "result": "supported" }, { "version": "TLSv1", "result": "supported" } ], "negotiated": { "version": "TLSv1.3", "cipher": "TLS_AES_256_GCM_SHA384", "alpn": "h2", "http2": true }, "sni": { "sent": true, "required": true }, "certificate": { "ok": true, "subject": "example.com", "issuer": "Cloudflare TLS Issuing ECC CA 3", "validFrom": "2026-07-29T22:10:08.000Z", "expiryDate": "2026-10-27T22:17:21.000Z", "daysRemaining": 35, "hostnameMatch": true, "hostnameMismatchReason": null, "chainLength": 4, "trusted": true, "trustError": null }, "timing": { "tcpMs": 26, "tlsHandshakeMs": 27, "totalMs": 53 }, "connectionError": null }, "meta": { "tool": "tls-configuration", "version": "v1" } }
Reading the result
Inspect protocol results, certificate trust and connection errors separately. unable-to-test does not prove that a TLS version is unsupported.
Response fields
| Field | What it tells you |
|---|---|
protocols | Per-version supported, not-supported or unable-to-test outcomes. |
negotiated / families | Selected TLS version, cipher and ALPN, plus available IPv4/IPv6 connection results. Unavailable values can be null. |
certificate | Certificate details, expiry, hostname match and trusted against the server's Node trust store. Certificate ok describes hostname matching; inspect trust separately. |
sni / timing | SNI behavior and connection timing in milliseconds. Indeterminate values are null. |
connectionError | Main-handshake failure, when present. Other checks can still return useful results. |
Scope and limits
Checks port 443 using several TLS connections, including protocol and no-SNI probes. Main connections allow five seconds; protocol probes allow four. Local TLS-library support can limit legacy tests. The negotiated cipher is not an exhaustive cipher-suite inventory.
Authentication and errors
Send your key in the x-api-key header, or the supported api_key query parameter. Each request uses 4 credits from the key's shared 300-credit rolling 24-hour budget. Credits are charged before parameter validation. Successful responses and quota errors include usage headers; GET and OPTIONS support CORS.
| API status | Meaning |
|---|---|
200 | The diagnostic returned a result in data, with ok: true and version information in meta. Read the diagnostic fields to determine the target's condition. |
400 | Invalid or blocked input, or a lookup/check failure that could not be returned as a diagnostic result. Read error for details. |
401 | Missing, invalid or revoked API key. |
429 | The request would exceed the key's available credit budget. |