[ad]
The first stage of penetration testing is usually passive information gathering and enumeration (active information gathering). This is where tools like dnsenum come in, the purpose of DNSenum is to gather as much information as possible about a domain.
The program currently performs the following operations:
- Get the host’s addresse (A record).
- Get the namservers (threaded).
- Get the MX record (threaded).
- Perform axfr queries on nameservers (threaded).
- Get extra names and subdomains via google scraping (google query = “allinurl: -www site:domain”).
- Brute force subdomains from file, can also perform recursion on subdomain that have NS records (all threaded).
- Calculate C class domain network ranges and perform whois queries on them (threaded).
- Perform reverse lookups on netranges ( C class or/and whois netranges) (threaded).
- Write to domain_ips.txt file ip-blocks.
The output file domain_ips.txt will contain non-contiguous IP blocks:
127.0.0.1/32
127.0.0.8/31
You can download DNSenum v1.2 here:
Or you can read more here.
Glenn says
Where do i get the Net::IP modules for windows installations , as i have to use windows box at work , thanks .
Changlinn says
This is all good and well, but isn’t it better to learn how to do this manually. A little nslookup/dig ping -a and http://www.onsamehost.com
and some google hacking and you are done, and much richer for the experience.
Pantagruel says
@Changlinn
Even pen testers get lazy, we also like the get as much info possible by using as little as tools possible.
But I guess most of us already have written a script to get these details.
Darknet says
Yah I was gonna say why not look at it the other way? I know exactly how to do it and all the steps…why not use a tool that can automate it. It’s like saying don’t use Nessus or any VA scanner…manually test each machine on the network, each open port and each service. Hell why use nmap or any port scanner? Just manually craft the packets to send to each port with hping and listen for the results with wireshark.
d347hm4n says
@Glenn use it in a vm, then you wil have the linux net::ip modules