File: fierce.1

package info (click to toggle)
fierce 1.6.0-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 452 kB
  • sloc: python: 942; perl: 510; makefile: 5
file content (140 lines) | stat: -rw-r--r-- 3,909 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
.TH FIERCE 1
.SH NAME
fierce \- DNS scanner that helps locate non-contiguous IP space and hostnames against specified domains.
.SH SYNOPSIS
.B fierce
.RI
[-h] [--domain DOMAIN] [--connect] [--wide] [--traverse NUMBER]
[--search SEARCH [SEARCH ...]] [--range RANGE] [--delay DELAY]
[--subdomains SUBDOMAINS [SUBDOMAINS ...] | --subdomain-file SUBDOMAIN_FILE]
[--dns-servers DNS_SERVERS [DNS_SERVERS ...] | --dns-file DNS_FILE] [--tcp]

.SH DESCRIPTION
.PP
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, OpenVAS, 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.
Originally written by RSnake along with others at http://ha.ckers.org/.
This is simply a conversion to Python 3 to simplify and modernize the codebase.
.SH OPTIONS
\fB\-h\fR, \fB\-\-help\fR
.RS 4
show this help message and exit
.RE

\fB\-\-domain\fR \fIDOMAIN\fR
.RS 4
domain name to test
.RE

\fB\-\-connect\fR
.RS 4
attempt HTTP connection to non-RFC 1918 hosts
.RE

\fB\-\-wide\fR
.RS 4
scan entire class c of discovered records
.RE

\fB\-\-traverse\fR \fINUMBER\fR
.RS 4
scan NUMBER IPs before and after discovered records. This respects Class C boundaries and won't enter adjacent subnets.
.RE

\fB\-\-search\fR \fISEARCH\fR [\fISEARCH\fR ...]
.RS 4
filter on these domains when expanding lookup
.RE

\fB\-\-range\fR \fIRANGE\fR
.RS 4
scan an internal IP range, use cidr notation
.RE

\fB\-\-delay\fR \fIDELAY\fR
.RS 4
time to wait between lookups
.RE

\fB\-\-subdomains\fR \fISUBDOMAINS\fR [\fISUBDOMAINS\fR ...]
.RS 4
use these subdomains
.RE

\fB\-\-subdomain-file\fR \fISUBDOMAIN_FILE\fR
.RS 4
use subdomains specified in this file (one per line)
.RE

\fB\-\-dns-servers\fR \fIDNS_SERVERS\fR [\fIDNS_SERVERS\fR ...]
.RS 4
use these dns servers for reverse lookups
.RE

\fB\-\-dns-file\fR \fIDNS_FILE\fR
.RS 4
use dns servers specified in this file for reverse lookups (one per line)
.RE

\fB\-\-tcp\fR
.RS 4
use TCP instead of UDP
.RE
.SH EXAMPLES
.PP
Something basic:
.nf
.RS
$ fierce --domain google.com --subdomains accounts admin ads
.RE
.fi
.PP
Scan 10 IP addresses before and after discovered domains to find coniguous blocks using the \`\-\-traverse\` flag:
.nf
.RS
$ fierce --domain facebook.com --subdomains admin --traverse 10
.RE
.fi
.PP
Limit nearby IP traversal to certain domains with the \`--search\` flag:
.nf
.RS
$ fierce --domain facebook.com --subdomains admin --search fb.com fb.net
.RE
.fi
.PP
Attempt an `HTTP` connection on domains discovered with the `--connect` flag:
.nf
.RS
$ fierce --domain stackoverflow.com --subdomains mail --connect
.RE
.fi
.PP
Exchange speed for breadth with the `--wide` flag, which looks for nearby domains on all IPs of the [/24](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#IPv4_CIDR_blocks) of a discovered domain:
.nf
.RS
$ fierce --domain facebook.com --wide
.RE
.fi
.PP
Zone transfers are rare these days, but they give us the keys to the DNS castle. [zonetransfer.me](https://digi.ninja/projects/zonetransferme.php) is a very useful service for testing for and learning about zone transfers:
.nf
.RS
$ fierce --domain zonetransfer.me
.RE
.fi
.PP
To save the results to a file for later use we can simply redirect output:
.nf
.RS
$ fierce --domain zonetransfer.me > output.txt
.RE
.fi
.PP
Internal networks will often have large blocks of contiguous IP space assigned. We can scan those as well:
.nf
.RS
$ fierce --dns-servers 10.0.0.1 --range 10.0.0.0/24
.RE
.fi