NetIntel · netintel.dev
Validate a domain's DNSSEC configuration over DNS-over-HTTPS: DS…
Validate a domain's DNSSEC configuration over DNS-over-HTTPS: DS records at the parent zone, DNSKEY records at the domain, RRSIG signatures, NSEC/NSEC3, plus the validating resolver's AD bit, returns a full chain-of-trust assessment and readiness score so agents can verify DNS integrity before trusting resolution results.
Input
Sample response
Published by the provider. Your run returns a fresh response.
response9 keys
chain_of_trust"complete"
components4 keys
dnskey_record{ count, key_types, present }3 keys
ds_record{ algorithms, count, present }3 keys
nsec_or_nsec3{ present, type }2 keys
rrsig_record{ present, signatures_found }2 keys
dnssec_enabledtrue
domain"example.com"
findings0 items
grade"A"
resolver_validatedtrue
score100
tld_ds_presenttrue
responseobject, 9 keysYour agent can do this on its own
Add the MCP URL in Claude Code, Cursor or Codex. Your agent can run Tools within its spending limits, or ask for approval each time. Connect your agent
Connect your agent
Add one MCP URL and your agent can find and run this tool within its spending limits. Choose “Ask each time” if you want to approve every Call.
MCP URL
https://app.aecon.ai/mcpTerminalbash
In Claude Code, open /mcp, select agentic-economy, then choose Authenticate.
Track record
- Paid calls, last 30 days
- 2
- Buyers, last 30 days
- 2
- Last paid call
Reported by the x402 directory.