Skip to main content
Glama
badchars

osint-mcp-server

by badchars

dns_wildcard_check

Detect wildcard DNS configuration on domains by resolving random subdomains to identify potential security misconfigurations during reconnaissance.

Instructions

Check if a domain has wildcard DNS configured by resolving a random subdomain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to check for wildcard DNS

Implementation Reference

  • The implementation of the dns_wildcard_check tool, which performs a DNS lookup on a random subdomain to check for a wildcard configuration.
    export async function dnsWildcardCheck(domain: string): Promise<WildcardCheckResult> {
      const randomSub = crypto.randomBytes(8).toString("hex");
      const testSubdomain = `${randomSub}.${domain}`;
    
      try {
        const ips = await dns.resolve4(testSubdomain);
        return { domain, wildcard: true, testSubdomain, resolvedIps: ips };
      } catch {
        return { domain, wildcard: false, testSubdomain };
      }
    }
  • Result type definition for dns_wildcard_check.
    interface WildcardCheckResult {
      domain: string;
      wildcard: boolean;
      testSubdomain: string;
      resolvedIps?: string[];
    }
  • Registration of the dns_wildcard_check tool.
    const dnsWildcardCheckTool: ToolDef = {
      name: "dns_wildcard_check",
      description: "Check if a domain has wildcard DNS configured by resolving a random subdomain.",
      schema: {
        domain: z.string().describe("Domain to check for wildcard DNS"),
      },
      execute: async (args) => json(await dnsWildcardCheck(args.domain as string)),
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the method ('resolving a random subdomain') but lacks details on behavioral traits such as rate limits, network dependencies, error handling, or what constitutes a positive/negative result. This is inadequate for a tool with no annotation coverage.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero wasted words. It is front-loaded with the core purpose and method, making it highly concise and well-structured.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It fails to explain what the tool returns (e.g., boolean result, resolved IPs, confidence level) or other contextual details needed for effective use, leaving significant gaps for a tool performing network operations.

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%, with the single parameter 'domain' well-described in the schema. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage.

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

Purpose5/5

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

The description clearly states the specific action ('Check if a domain has wildcard DNS configured') and the method ('by resolving a random subdomain'), distinguishing it from sibling DNS tools like dns_lookup or dns_reverse that perform different DNS operations.

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 description implies usage for wildcard DNS detection but provides no explicit guidance on when to use this tool versus alternatives like dns_lookup for general resolution or st_subdomains for enumeration. No exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/badchars/osint-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server