Validate DKIM in Google Sheets & Excel
Formula
Check DKIM records by the row. Verifies each domain's DKIM DNS records — Google Sheets or Excel, auto-refreshing.
=VERVE("dkimvalidator", A2, "field", "host")=VERVE.CALL("dkimvalidator", A2, "field", "host")A2 holds the domain you're 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("dkimvalidator", "google.com", "field", "host")=VERVE.CALL("dkimvalidator", "google.com", "field", "host")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.
| Input | Type | Where it goes | Description |
|---|---|---|---|
domainRequired | string | argument 2 | The domain to validate the DKIM record for (e.g. google.com) |
selector | string | "selector", value | The DKIM selector to look up (the label before ._domainkey). When omitted, a list of common selectors is tried (e.g. google) |
Passing an option
=VERVE("dkimvalidator", A2, "selector", "google")=VERVE.CALL("dkimvalidator", A2, "selector", "google")What lands in your sheet
The "field" pair is what makes the formula resolve to one cell. The name 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("dkimvalidator", A2)=VERVE.CALL("dkimvalidator", A2)Good for finding out what a source returns, but it is not a formula you can fill down: 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. Leave the cells below and to the right empty.
Available fields
#PREMIUM(field) rather than a value, so a locked field never looks like a real answer.| Use as "field" | Type | Example cell value | Description |
|---|---|---|---|
selector | string | DKIM selector used for DNS record lookup | |
host | string | Domain name being validated | |
dkim_host | string | Full DKIM DNS record hostname with selector | |
cname_target | object | CNAME target if present in DNS record | |
has_dkim_record | boolean | Whether DKIM record exists in domain DNS | |
dkim_record | string | Complete DKIM record value and public key | |
dkim_records_count | number | Number of DKIM records found for domain | |
version | string | DKIM protocol version from record | |
key_type | string | Public key algorithm type used | |
key_bits | number | Length of the DKIM public key in bits. 2048 or higher is the current recommendation; below 1024 is dangerously weak. 0 indicates a revoked key (empty p= value), and null means no decodable key is present | |
is_test_mode | boolean | Whether the record sets t=y (testing mode). In testing mode receivers are told to treat mail as if DKIM were not deployed, so signatures carry no enforcement weight | |
issues_foundPremium | array[1] | Array of detected issues with DKIM configuration | |
└ issues_found.0.codePremium | string | Error code identifying the specific issue | |
└ issues_found.0.typePremium | string | Severity level of the issue | |
└ issues_found.0.messagePremium | string | Human-readable description of the issue | |
valid | boolean | Overall DKIM record validity status | |
risk_scorePremium | number | Composite 0-100 email-signing weakness score derived from the key length, testing mode and hash algorithm — higher means the deployed DKIM key offers less real protection (a revoked or sub-1024-bit key scores high; a 2048-bit enforced key scores low) | |
risk_levelPremium | string | 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 — 5 credits per row looked up. How you write it differs, because the two runtimes batch at different points.
=VERVE("dkimvalidator", A2:A100, "field", "host")Give the arguments ranges and the answers spill down from the cell you typed in. Sheets custom functions run synchronously and in isolation, so dragged cells can't 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.
=VERVE.CALL("dkimvalidator", A2, "field", "host")Drag or double-click the fill handle — no range form and none needed. Excel's runtime is asynchronous, so the add-in coalesces the calls a fill produces into a single batched request on its own.
Don't 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() won't catch it; test with LEFT(cell, 4) = "#ERR" instead.
| 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 | The preview formula was copied as-is. Swap the placeholder for a cell reference. |
#ERR No "x" in dkimvalidator | An option name that this source doesn't take. The message lists the ones it does. |
#ERR No data point "…" | The "field" path isn't in the response. Check the dot-path against the table above. |
#PREMIUM(field) | The field exists but your plan doesn't include it. |
#ERR Out of credits | The month'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 doesn't 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.
Other ways to use Validate DKIM
Set up Validate DKIM on VerveSheets, or reach the same source a different way. Your VerveSheets account and credits work on all of them — one key, one balance.
Frequently asked questions
Does Validate DKIM work in both Google Sheets and Excel?
Yes — the same source, the same arguments, the same result. Google Sheets calls it =VERVE("dkimvalidator", A2, "field", "host") and Excel namespaces it as =VERVE.CALL("dkimvalidator", A2, "field", "host"). Filling a whole column is the one place the two differ: Sheets takes ranges directly, Excel fills down.
Do the cells recalculate on their own?
They recalculate when the sheet does — on edit, on open, or on a manual recalc. Each recalculation is a fresh call and spends credits, so for a large static column it's worth copying the results and pasting them as values.
How many credits does a filled column cost?
5 credits per row looked up, on both platforms and however you fill it. Repeated identical lookups in the same column are charged once. Batching changes how many HTTP calls are made, never the credit count.
Can I share the sheet without sharing my key?
Yes. The key is stored against your account, not in the file. Collaborators see the values already in the cells; formulas only recalculate for someone who has connected their own account.
Why is a cell showing #ERR instead of an error?
So you can read the reason. Excel can't display a custom message on a real spreadsheet error, so the add-in returns the explanation as text on both platforms instead.