Docs/Sources/DKIM Grounding Data for AI Agents

DKIM Grounding Data for AI Agents

Validate DKIM records for a domain

OperationalCredits 10 per callp50 383msDomain Data

Overview

This tool inspects the DKIM record by performing DNS lookups for common selectors. It validates the syntax, surfaces the public-key length in bits, flags testing mode, and derives a composite email-signing posture score so you can tell at a glance whether a domain's DKIM key actually protects its mail.

Live Test DKIM Grounding Data for AI Agents Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as DKIMGroundingDataforAIAgents. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call
{
  "name": "DKIMGroundingDataforAIAgents",
  "arguments": {
    "domain": "github.com"
  }
}

You do not name the tool yourself; the model picks it. Asking about github.com in the terms this source covers is enough for it to reach for DKIMGroundingDataforAIAgents on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

ArgumentTypeDescription
domainRequiredstringThe domain to validate the DKIM record for
domain
selectorOptionalstringThe DKIM selector to look up (the label before ._domainkey). When omitted, a list of common selectors is tried

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "selector": "s1",
    "host": "github.com",
    "dkim_host": "s1._domainkey.github.com",
    "cname_target": null,
    "has_dkim_record": true,
    "dkim_record": "k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyn3fMCVpb7ryIRKOGXhXVGYmsWUitNlSckqGHOwNFZgFadplOrD+Qzf1XQkP7MH/VB/97DsAAJGtEXW1Uq71Hjnfr/DuBN/YfjF/gU70qEFb7q1sdIiNtjFL2TkOpoW+X/bhhPNheW/fYwyFb6ZHFM6LTgXyuimWRHTOUP3VjZzhNVda79nt+2WZYbS4l8HdMgWpTNHjpVw5PtXESA9KBg/evSRk5fIaXIX5eRXW3baoV9yVzD8O29/IL/DiSk+yNvaO0EHL5c4yGuZJhGzvpiznb2IDVdemJK4Dqzdy5FTN/SGYZhAEr7MguG3Z314hMS2scgMsOMgB64uj/6+6UwIDAQAB",
    "dkim_records_count": 1,
    "key_type": "rsa",
    "issues_found": [
      {
        "code": "V_TAG_NOT_FOUND",
        "type": "warning",
        "message": "The v tag is missing"
      },
      {
        "code": "STRICT_MODE",
        "type": "info",
        "message": "Strict flag set (t=s): the i= identity domain must exactly match d= (no subdomains)"
      }
    ],
    "valid": true,
    "key_bits": 2048,
    "is_test_mode": false,
    "risk_score": 0,
    "risk_level": "low"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
selectorstrings1DKIM selector used for DNS record lookup
hoststringgithub.comDomain name being validated
dkim_hoststrings1._domainkey.github.comFull DKIM DNS record hostname with selector
cname_targetobjectnullCNAME target if present in DNS record
has_dkim_recordbooleantrueWhether DKIM record exists in domain DNS
dkim_recordstringk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyn3fMCVpb7ryIRKOGXhXVGYmsWUitNlSckqGHOwNFZgFadplOrD+Qzf1XQkP7MH/VB/97DsAAJGtEXW1Uq71Hjnfr/DuBN/YfjF/gU70qEFb7q1sdIiNtjFL2TkOpoW+X/bhhPNheW/fYwyFb6ZHFM6LTgXyuimWRHTOUP3VjZzhNVda79nt+2WZYbS4l8HdMgWpTNHjpVw5PtXESA9KBg/evSRk5fIaXIX5eRXW3baoV9yVzD8O29/IL/DiSk+yNvaO0EHL5c4yGuZJhGzvpiznb2IDVdemJK4Dqzdy5FTN/SGYZhAEr7MguG3Z314hMS2scgMsOMgB64uj/6+6UwIDAQABComplete DKIM record value and public key
dkim_records_countnumber1Number of DKIM records found for domain
key_typestringrsaPublic key algorithm type used
issues_foundPremiumarray[2]Array of detected issues with DKIM configuration
issues_found.0.codePremiumstringV_TAG_NOT_FOUNDError code identifying the specific issue
issues_found.0.typePremiumstringwarningSeverity level of the issue
issues_found.0.messagePremiumstringThe v tag is missingHuman-readable description of the issue
validbooleantrueOverall DKIM record validity status
key_bitsnumber2048Length 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_modebooleanfalseWhether 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
risk_scorePremiumnumber0Composite 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_levelPremiumstringlowRisk band derived from the score: low, medium or high

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at host: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

StatusWhat it means
400 / 422The arguments did not validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Blocked by a key restriction or an IP allow-list. Never a bad identity.
404This source is not part of VerveContext. Check the catalog.
429Out of credits, or a brief rate limit. The message tells them apart.

A call costs 10 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Email Service Onboarding
When a new customer connects a sending domain, verify their public key length and check whether testing mode is active before sending campaigns.
Mail Security Auditing
To prevent spoofing across corporate domains, security analysts inspect DNS selectors to confirm valid DKIM records and flag keys shorter than 2048 bits.
Sender Deliverability Diagnostics
Deliverability consultants check whether outbound domains publish valid DKIM public keys or point to unresolved CNAME targets when diagnosing inbox placement drops.
Tenant Domain Verification
Flag missing or misconfigured DKIM records during custom domain setup so software platforms can alert workspace admins before outgoing notifications fail authentication.

Other ways to use DKIM Grounding Data for AI Agents

Set up DKIM Grounding Data for AI Agents on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

More in Domain Data:

Was this page helpful?