BlackVeil DNS & Email Security Scanner

check_dnssec

Read-onlyIdempotent

Check DNSSEC status for a domain. Verifies whether DNS is tamper-proof and protected against cache poisoning and DNS spoofing attacks by validating DNSKEY and DS records. Reports whether DNSSEC is enabled and validating. Part of the scan_domain audit.

Input Schema

TableJSON Schema

Name	Required	Description
`domain`	Yes	Domain to check (e.g., example.com)
`format`	No	Output verbosity. Auto-detected if omitted.
`force_refresh`	No	Bypass cache and run a fresh check. Useful after DNS changes.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`score`	Yes
`passed`	Yes
`partial`	No
`category`	Yes
`findings`	Yes
`checkStatus`	No
`verdictWithheld`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026
- addedOutput schema / properties / verdictWithheld
```
Added value: +{
+  "type": "boolean"
+}
```
Changed2 schema fields changedAug 18, 2026
- addedOutput schema / properties / checkStatus
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```

Changed1 schema field changedJul 2, 2026

addedInput schema / properties / force_refresh

Added value: +{
+  "description": "Bypass cache and run a fresh check. Useful after DNS changes.",
+  "type": "boolean"
+}

Changed1 schema field changedMay 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "category": {
+      "type": "string"
+    },
+    "findings": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "passed": {
+      "type": "boolean"
+    },
+    "score": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "category",
+    "score",
+    "passed",
+    "findings"
+  ],
+  "type": "object"
+}

First observedApr 21, 2026

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds useful semantics about what the check validates (DNSKEY/DS) and what it reports, but says nothing about caching behavior, latency, or how results relate to the parent audit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core purpose and with no filler. The trailing audit-context clause is slightly tacked on but still earns its place as routing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers what is checked and reported. The one gap is sibling disambiguation, which matters given the many adjacent DNSSEC-related tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters (domain, format, force_refresh) are already documented in the schema. The description adds no format examples, default behavior, or refresh semantics beyond what the schema states, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Check DNSSEC status for a domain') and elaborates on what is validated (DNSKEY and DS records) and what is reported (enabled/validating). However, it never distinguishes itself from the close sibling check_dnssec_chain, leaving overlap for the agent to resolve.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trailing 'Part of the scan_domain audit' hints at where this fits in a larger workflow, but there is no explicit when-to-use guidance and no exclusion versus check_dnssec_chain, check_dnskey_strength, or check_nsec_walkability. Usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BlackVeil DNS & Email Security Scanner tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.