3.1netcraft ：子域名查詢
官網：http://searchdns.netcraft.com/
輸入要查詢的域名，即可得知子域名
3.2fierce ：子域名查詢
概述：
fierce 是使用多種技術來掃描目标主機ip位址和主機名的一個dns伺服器枚舉工具。運用遞歸的方式來工作。它的工作原理是先通過查詢本地dns伺服器來查找目标dns伺服器，然後使用目标dns伺服器來查找子域名。fierce的主要特點就是可以用來定位獨立ip空間對應域名和主機名。
參數：
root@kali:/home/dnt# fierce -h
usage: perl fierce.pl [-dns example.com] [options]
overview:
fierce is a semi-lightweight scanner that helps locate non-contiguous
ip space and hostnames against specified domains. it's really meant
as a pre-cursor to nmap, unicornscan, nessus, nikto, etc, since all
of those require that you already know what ip space you are looking
for. this does not perform exploitation and does not scan the whole
internet indiscriminately. it is meant specifically to locate likely
targets both inside and outside a corporate network. because it uses
dns primarily you will often find mis-configured networks that leak
internal address space. that's especially useful in targeted malware.
options:
-connect attempt to make http connections to any non rfc1918
(public) addresses. this will output the return headers but
be warned, this could take a long time against a company with
many targets, depending on network/machine lag. i wouldn't
recommend doing this unless it's a small company or you have a
lot of free time on your hands (could take hours-days).
inside the file specified the text "host:\n" will be replaced
by the host specified. usage:
perl fierce.pl -dns example.com -connect headers.txt
-delay the number of seconds to wait between lookups.
-dns the domain you would like scanned.
-dnsfile use dns servers provided by a file (one per line) for
reverse lookups (brute force).
-dnsserver use a particular dns server for reverse lookups
(probably should be the dns server of the target). fierce
uses your dns server for the initial soa query and then uses
the target's dns server for all additional queries by default.
-file a file you would like to output to be logged to.
-fulloutput when combined with -connect this will output everything
the webserver sends back, not just the http headers.
-help this screen.
-nopattern don't use a search pattern when looking for nearby
hosts. instead dump everything. this is really noisy but
is useful for finding other domains that spammers might be
using. it will also give you lots of false positives,
especially on large domains.
-range scan an internal ip range (must be combined with
-dnsserver). note, that this does not support a pattern
and will simply output anything it finds. usage:
perl fierce.pl -range 111.222.333.0-255 -dnsserver ns1.example.co
-search search list. when fierce attempts to traverse up and
down ipspace it may encounter other servers within other
domains that may belong to the same company. if you supply a
comma delimited list to fierce it will report anything found.
this is especially useful if the corporate servers are named
different from the public facing website. usage:
perl fierce.pl -dns examplecompany.com -search corpcompany,blahcompany
note that using search could also greatly expand the number of
hosts found, as it will continue to traverse once it locates
servers that you specified in your search list. the more the
better.
-suppress suppress all tty output (when combined with -file).
-tcptimeout specify a different timeout (default 10 seconds). you
may want to increase this if the dns server you are querying
is slow or has a lot of network lag.
-threads specify how many threads to use while scanning (default
is single threaded).
-traverse specify a number of ips above and below whatever ip you
have found to look for nearby ips. default is 5 above and
below. traverse will not move into other c blocks.
-version output the version number.
-wide scan the entire class c after finding any matching
hostnames in that class c. this generates a lot more traffic
but can uncover a lot more information.
-wordlist use a seperate wordlist (one word per line). usage:
perl fierce.pl -dns examplecompany.com -wordlist dictionary.txt
執行個體：threads 是線程數，可以自己指定
root@kali:/home/dnt# fierce -dns cnblogs.com -threads 100
trying zone transfer first...
unsuccessful in zone transfer (it was worth a shot)
okay, trying the good old fashioned way... brute force
checking for wildcard dns...
** found 99901599299.cnblogs.com at 42.121.252.58.
** high probability of wildcard dns.
now performing 2280 test(s)...
120.26.70.206 files.cnblogs.com
42.121.129.234 images.cnblogs.com
223.6.251.45 group.cnblogs.com
223.6.251.45 home.cnblogs.com
42.121.129.234 download.cnblogs.com
221.181.200.235 cdn.cnblogs.com
42.121.131.85 mail.cnblogs.com
42.121.129.234 downloads.cnblogs.com
223.6.251.45 news.cnblogs.com
223.6.251.45 ad.cnblogs.com
42.121.254.229 p.cnblogs.com
。。。。。。。。