Overview
TLS Check connects to the provided domain and port and runs a TLS handshake for each protocol version to determine which are supported. It identifies the highest negotiable version (like TLS 1.2/1.3), flags whether deprecated TLS 1.0/1.1 remain exposed, and returns a composite risk score summarizing the server's protocol security.
Live Test Check TLS Support Source →
Formula
One function covers the whole catalog: the first argument names the source, the rest are its inputs, and the "field" pair says which single value lands in the cell. Formulas covers the grammar that applies to all of them.
=VERVE("tlscheck", A2, "field", "highestVersion")=VERVE.CALL("tlscheck", A2, "field", "highestVersion")A2 holds the domain you are looking up. Drag the formula down and each row resolves on its own.
With literal values
Nothing has to come from a cell — typed values work the same way.
=VERVE("tlscheck", "amazon.com", "field", "highestVersion")=VERVE.CALL("tlscheck", "amazon.com", "field", "highestVersion")Inputs
Required inputs are positional, in the order below. Everything else is passed as a "name", value pair after them — the same shape as SUMIFS. Premium inputs are accepted on every plan but only take effect on plans that include them.
| Input | Type | Where it goes | Description |
|---|---|---|---|
domainRequired | string | argument 2 (A2) | The domain to check the TLS/SSL configuration for domain |
portOptional | integer | "port", value | The port to connect to (usually 443 for HTTPS) default 443 · range 1–65535 |
Passing an option
=VERVE("tlscheck", A2, "port", 443)=VERVE.CALL("tlscheck", A2, "port", 443)What lands in your sheet
The "field" pair is what makes the formula resolve to one cell. Its value is a dot-path from the table below, so swapping it is how you pull a different value — one formula per column.
Seeing everything at once
Drop the "field" pair and the formula returns the whole response instead: two columns, field name on the left and value on the right, spilling from the cell you typed in.
=VERVE("tlscheck", A2)=VERVE.CALL("tlscheck", A2)The second row's table would land on top of the first's, and every cell after the first reads #REF! (#SPILL! in Excel). Keep one per sheet, or name a field, and leave the cells below and to the right empty.
Response fields
Paths are relative to data. Each one is exactly what the "field" pair accepts, so swapping it is how you pull a different value into a cell. On a plan without a Premium field the cell reads #PREMIUM(field) rather than a value, so a locked field never looks like a real answer.
| Use as "field" | Type | Example cell value | Description |
|---|---|---|---|
domain | string | amazon.com | Domain name that was checked for TLS configuration |
tlsVersions | object | {…} | Whether the server completes a handshake at each protocol version, keyed TLSv1, TLSv1.1, TLSv1.2 and TLSv1.3 |
tlsVersions.TLSv1 | boolean | true | Whether TLS 1.0 protocol is supported by server |
tlsVersions.TLSv1.1 | boolean | true | Whether TLS 1.1 protocol is supported by server |
tlsVersions.TLSv1.2 | boolean | true | Whether TLS 1.2 protocol is supported by server |
tlsVersions.TLSv1.3 | boolean | true | Whether TLS 1.3 protocol is supported by server |
highestVersion | string | TLSv1.3 | The highest TLS version the server supports (e.g. TLSv1.3), or null if none were negotiable |
hasDeprecatedTLSPremium | boolean | true | Whether the server still supports deprecated TLS 1.0 or 1.1, which are insecure and disallowed by PCI-DSS |
isSecurePremium | boolean | false | Whether the server supports a modern TLS version (1.2/1.3) and does not expose any deprecated version |
riskScorePremium | number | 55 | Composite 0-100 risk score based on missing modern TLS and exposure of deprecated protocols (higher is riskier) |
riskLevelPremium | string | medium | Risk band derived from the score: low, medium or high |
Filling a whole column
Both platforms make one batched call for a column rather than one request per cell, and both cost the same — 2 credits per row looked up. How you write it differs, because the two runtimes batch at different points.
=VERVE("tlscheck", A2:A100, "field", "highestVersion")In Google Sheets, give the arguments ranges and the answers spill down from the cell you typed in. Custom functions there run synchronously and in isolation, so dragged cells cannot be coalesced — the range form is how a column becomes one call. The "field" pair is required here: a per-row two-column table has nowhere to spill. Use a full column per input (A2:A100, not A2) — a single-cell reference is read as row 1 only and the rest of the column comes back blank.
In Excel, type the formula once and fill down — no range form and none needed, because its runtime is asynchronous and the add-in coalesces the calls a fill produces into a single batched request. Do not hand VERVE.CALL a range: Excel flattens it into positional arguments, so A2:A100 arrives as a hundred separate arguments and the cell reads #ERR rather than filling.
Either way, column A holds your domain values and the answers land beside them, one row each, blank rows skipped.
When a cell doesn't fill
A failed lookup returns readable text starting with #ERR rather than a spreadsheet error, because Excel cannot show a custom message on a real error — you would get a bare #VALUE! with no reason. The trade-off is that IFERROR() will not catch it; test with LEFT(cell, 4) = "#ERR" instead. Error handling covers the rest.
| Cell reads | What happened |
|---|---|
#ERR Not connected | No API key saved. Open the side panel and connect your account. |
#ERR Replace <name> with a cell or value | A preview formula was copied as-is. Swap the placeholder for a cell reference. |
#ERR No "x" in tlscheck | An option name this source does not take. The message lists the ones it does. |
#ERR No data point "…" | The "field" path is not in the response. Check it against the table above. |
#PREMIUM(field) | The field exists but your plan does not include it. |
#ERR Out of credits | The cycle's credits are spent. Usage resets on your billing date. |
Before the formula works
The add-in reads the API key you saved once in the side panel — the key never goes in the formula, so a shared sheet does not leak it and a collaborator without access simply sees the last calculated values.
- Install the add-in for Google Sheets or Excel.
- Open the side panel and sign in, or paste a key from your dashboard.
- Type the formula above into any cell.
Use cases
- Payment Gateway Auditing
- Before onboarding merchant checkout domains, fintech compliance auditors check whether incoming endpoints accept legacy protocols like TLS 1.0 or 1.1.
- Deployment Pipeline Verification
- Flag outdated web server configurations during production releases by testing handshake support across all modern protocol versions before traffic switches over.
- Attack Surface Scanning
- Security analysts query customer-facing domains periodically to find legacy protocol support and review the highest negotiable version across exposed web ports.
- Vendor Security Assessments
- When evaluating SaaS suppliers, procurement teams inspect external hostnames to confirm that partner servers negotiate TLS 1.2 or 1.3.
Other ways to use Check TLS Support
Set up Check TLS Support on VerveSheets, or reach the same source a different way. Your VerveSheets account and credits work on all of them — one key, one balance.
Related
More in Networking: