dnsx

Name: dnsx
Availability: InStock
Author: Dave

Resolve DNS records and brute-force subdomains from domain lists.

15|1|Updated Feb 12, 2026

Search Tags:#reconnaissance #dns #brute-force #subdomain #network tools #dns records

Ready to run

npx skills add https://github.com/AeonDave/malskill --skill dnsx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dnsx
Source: https://github.com/AeonDave/malskill/tree/main/offensive-tools/recon/dnsx
Command: npx skills add https://github.com/AeonDave/malskill --skill dnsx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill rapidly resolves large lists of domain names and subdomains, performs DNS brute-forcing, and extracts various DNS record types, streamlining network reconnaissance.

Core Features & Use Cases

Bulk DNS Resolution: Quickly resolve IPs for numerous subdomains.
DNS Brute-Force: Discover subdomains by testing against a wordlist.
Record Extraction: Extract A, CNAME, MX, TXT, NS, and PTR records.
Use Case: When tasked with identifying all live subdomains for a target company, use this Skill to resolve a provided list of potential subdomains and filter out non-existent ones.

Quick Start

Resolve a list of subdomains from the file subs.txt.

Frequently Asked Questions about dnsx

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I brute-force subdomains and resolve DNS records for a large list of domains?▼

DNS brute-force and resolution for large domain lists is performed by testing against a wordlist to discover subdomains and extracting A, CNAME, MX, TXT, NS, and PTR records. The tool filters wildcard DNS entries and validates live records from large datasets.

What is the best way to extract A, CNAME, and MX records during network reconnaissance?▼

Extracting A, CNAME, and MX records during network reconnaissance is done by resolving target domain lists to identify live DNS entries. The tool rapidly queries numerous subdomains to retrieve specific DNS record types and filter out non-existent results.

Can I use custom resolvers and rate limiting for bulk DNS resolution?▼

Custom resolvers and rate limiting are supported for bulk DNS resolution. You can configure these settings to manage query speed and validate live DNS entries efficiently when processing large datasets of subdomains.

How do I filter wildcard DNS records when discovering subdomains?▼

Filtering wildcard DNS records during subdomain discovery is handled automatically by the tool. It validates live DNS entries and removes false positives caused by wildcard configurations, ensuring accurate subdomain identification from brute-force attempts.

Does DNS brute-forcing work effectively for identifying all live subdomains of a target company?▼

DNS brute-forcing works effectively for identifying live subdomains by testing potential names against a target domain using a wordlist. The tool quickly resolves the provided list, extracts available DNS records, and filters out non-existent entries.

Why does DNS resolution fail or return false positives on certain domain lists?▼

DNS resolution failures and false positives on domain lists often stem from wildcard DNS records. The tool addresses this by filtering wildcard entries and validating live DNS results, ensuring accurate data extraction from large reconnaissance datasets.