rimscan-cli 1.0.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- rimscan_cli-1.0.0/LICENSE +202 -0
- rimscan_cli-1.0.0/NOTICE +8 -0
- rimscan_cli-1.0.0/PKG-INFO +250 -0
- rimscan_cli-1.0.0/README.md +218 -0
- rimscan_cli-1.0.0/pyproject.toml +65 -0
- rimscan_cli-1.0.0/rimscan_cli/__init__.py +3 -0
- rimscan_cli-1.0.0/rimscan_cli/__main__.py +4 -0
- rimscan_cli-1.0.0/rimscan_cli/banner.py +48 -0
- rimscan_cli-1.0.0/rimscan_cli/cli.py +158 -0
- rimscan_cli-1.0.0/rimscan_cli/data/fingerprints.json +932 -0
- rimscan_cli-1.0.0/rimscan_cli/recon/__init__.py +0 -0
- rimscan_cli-1.0.0/rimscan_cli/recon/_common.py +62 -0
- rimscan_cli-1.0.0/rimscan_cli/recon/_http.py +65 -0
- rimscan_cli-1.0.0/rimscan_cli/recon/cert_audit.py +131 -0
- rimscan_cli-1.0.0/rimscan_cli/recon/dns_audit.py +196 -0
- rimscan_cli-1.0.0/rimscan_cli/recon/enumeration.py +192 -0
- rimscan_cli-1.0.0/rimscan_cli/recon/resolver.py +232 -0
- rimscan_cli-1.0.0/rimscan_cli/recon/secret_scan.py +241 -0
- rimscan_cli-1.0.0/rimscan_cli/recon/severity.py +15 -0
- rimscan_cli-1.0.0/rimscan_cli/recon/takeover.py +302 -0
- rimscan_cli-1.0.0/rimscan_cli/scanner.py +305 -0
- rimscan_cli-1.0.0/rimscan_cli.egg-info/PKG-INFO +250 -0
- rimscan_cli-1.0.0/rimscan_cli.egg-info/SOURCES.txt +39 -0
- rimscan_cli-1.0.0/rimscan_cli.egg-info/dependency_links.txt +1 -0
- rimscan_cli-1.0.0/rimscan_cli.egg-info/entry_points.txt +2 -0
- rimscan_cli-1.0.0/rimscan_cli.egg-info/requires.txt +8 -0
- rimscan_cli-1.0.0/rimscan_cli.egg-info/top_level.txt +1 -0
- rimscan_cli-1.0.0/setup.cfg +4 -0
- rimscan_cli-1.0.0/tests/test_cert_audit.py +92 -0
- rimscan_cli-1.0.0/tests/test_cli.py +204 -0
- rimscan_cli-1.0.0/tests/test_dns_audit.py +151 -0
- rimscan_cli-1.0.0/tests/test_enumeration.py +126 -0
- rimscan_cli-1.0.0/tests/test_fingerprints_real.py +45 -0
- rimscan_cli-1.0.0/tests/test_fixes.py +101 -0
- rimscan_cli-1.0.0/tests/test_fixes_more.py +137 -0
- rimscan_cli-1.0.0/tests/test_http.py +52 -0
- rimscan_cli-1.0.0/tests/test_regressions.py +155 -0
- rimscan_cli-1.0.0/tests/test_resolver.py +125 -0
- rimscan_cli-1.0.0/tests/test_scanner.py +215 -0
- rimscan_cli-1.0.0/tests/test_secret_scan.py +139 -0
- rimscan_cli-1.0.0/tests/test_takeover.py +179 -0
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright 2026 Rimscan
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
rimscan_cli-1.0.0/NOTICE
ADDED
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
rimscan-cli
|
|
2
|
+
Copyright 2026 Rimscan. Licensed under the Apache License, Version 2.0 (see LICENSE).
|
|
3
|
+
|
|
4
|
+
Third-party data
|
|
5
|
+
----------------
|
|
6
|
+
rimscan_cli/data/fingerprints.json is derived from the can-i-take-over-xyz project
|
|
7
|
+
(https://github.com/EdOverflow/can-i-take-over-xyz). The fingerprints remain subject to
|
|
8
|
+
that project's license and terms. Review them before redistributing the data file.
|
|
@@ -0,0 +1,250 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: rimscan-cli
|
|
3
|
+
Version: 1.0.0
|
|
4
|
+
Summary: External attack-surface reconnaissance for domains you own or are authorized to test.
|
|
5
|
+
Author: Rimscan
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://rimscan.cloud
|
|
8
|
+
Project-URL: Repository, https://github.com/Revenge8/Rimscan-cli
|
|
9
|
+
Project-URL: Issues, https://github.com/Revenge8/Rimscan-cli/issues
|
|
10
|
+
Keywords: security,reconnaissance,attack-surface,subdomain-takeover,dns
|
|
11
|
+
Classifier: Development Status :: 5 - Production/Stable
|
|
12
|
+
Classifier: Environment :: Console
|
|
13
|
+
Classifier: Intended Audience :: Information Technology
|
|
14
|
+
Classifier: Programming Language :: Python :: 3
|
|
15
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
18
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
19
|
+
Classifier: Topic :: Security
|
|
20
|
+
Requires-Python: >=3.10
|
|
21
|
+
Description-Content-Type: text/markdown
|
|
22
|
+
License-File: LICENSE
|
|
23
|
+
License-File: NOTICE
|
|
24
|
+
Requires-Dist: certifi>=2023.7.22
|
|
25
|
+
Requires-Dist: dnspython>=2.4
|
|
26
|
+
Requires-Dist: requests>=2.31
|
|
27
|
+
Requires-Dist: urllib3>=2.0
|
|
28
|
+
Provides-Extra: dev
|
|
29
|
+
Requires-Dist: pytest>=7; extra == "dev"
|
|
30
|
+
Requires-Dist: ruff>=0.5; extra == "dev"
|
|
31
|
+
Dynamic: license-file
|
|
32
|
+
|
|
33
|
+

|
|
34
|
+
|
|
35
|
+
# Rimscan CLI
|
|
36
|
+
|
|
37
|
+

|
|
38
|
+

|
|
39
|
+
|
|
40
|
+
Rimscan CLI is a standalone, database-free tool for external attack-surface
|
|
41
|
+
reconnaissance of domains you are authorized to test. It discovers subdomains,
|
|
42
|
+
resolves DNS and CNAME chains, audits DNS and TLS configuration, checks for common
|
|
43
|
+
exposed secrets, and identifies possible subdomain takeover candidates using public
|
|
44
|
+
fingerprints.
|
|
45
|
+
|
|
46
|
+
**Only scan domains you own or have explicit written permission to test.**
|
|
47
|
+
This tool is not a license to scan arbitrary third-party infrastructure.
|
|
48
|
+
|
|
49
|
+
## Installation
|
|
50
|
+
|
|
51
|
+
Requires Python 3.10 or newer.
|
|
52
|
+
|
|
53
|
+
```bash
|
|
54
|
+
python -m venv .venv
|
|
55
|
+
# Windows: .venv\Scripts\activate
|
|
56
|
+
source .venv/bin/activate
|
|
57
|
+
python -m pip install .
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
This installs the `rimscan-cli` command. `python -m rimscan_cli` works as well.
|
|
61
|
+
|
|
62
|
+
## Usage
|
|
63
|
+
|
|
64
|
+
```bash
|
|
65
|
+
rimscan-cli scan example.com
|
|
66
|
+
rimscan-cli scan example.com --output results.json
|
|
67
|
+
rimscan-cli scan example.com --authorized --secrets
|
|
68
|
+
rimscan-cli scan example.com --authorized --zone-transfer --nuclei
|
|
69
|
+
rimscan-cli scan example.com --quiet --fail-on high # CI use
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
Results are written to **stdout as JSON** (or to a file with `--output`).
|
|
73
|
+
The banner, progress lines and the findings summary go to **stderr**, so
|
|
74
|
+
`rimscan-cli scan example.com | jq .` always receives clean JSON. Use
|
|
75
|
+
`--quiet` to silence stderr completely. See [`examples/example-output.json`](examples/example-output.json)
|
|
76
|
+
for the shape of the output.
|
|
77
|
+
|
|
78
|
+
### Options
|
|
79
|
+
|
|
80
|
+
| Option | Description |
|
|
81
|
+
| --- | --- |
|
|
82
|
+
| `--authorized` | Confirm you own the target or may test it. Required by `--secrets`, `--zone-transfer` and `--nuclei`. |
|
|
83
|
+
| `--secrets` | Fetch a fixed list of well-known paths (`/.env`, `/config.js`, ...) and look for exposed credentials. |
|
|
84
|
+
| `--zone-transfer` | Attempt an AXFR against the domain's nameservers. |
|
|
85
|
+
| `--nuclei` | Run [Nuclei](https://github.com/projectdiscovery/nuclei) (installed separately) with `-etags dos,fuzz,intrusive`. |
|
|
86
|
+
| `--nuclei-rate-limit N` | Nuclei requests per second (default 75, at least 1). |
|
|
87
|
+
| `--include-third-party` | Let `--secrets` and `--nuclei` also probe hosts that CNAME to third-party services. Skipped by default. |
|
|
88
|
+
| `--bruteforce` | Also resolve a short list of common subdomain names. |
|
|
89
|
+
| `--no-certs` | Skip the TLS certificate audit. |
|
|
90
|
+
| `--sources LIST` | Comma-separated enumeration sources (default: all). |
|
|
91
|
+
| `--resolver IPS` | Comma-separated DNS resolver addresses. Applies to DNS lookups only; TLS and HTTP probes use the system resolver. |
|
|
92
|
+
| `--timeout SECONDS` | Network timeout, greater than 0 (default 10). |
|
|
93
|
+
| `-o`, `--output FILE` | Write JSON to a file instead of stdout. If the file cannot be written, the results are printed to stdout instead. |
|
|
94
|
+
| `--fail-on LEVEL` | Exit with status 1 if any finding is at or above `info`, `low`, `medium`, `high` or `critical`. |
|
|
95
|
+
| `-q`, `--quiet` | No banner, progress, summary or log warnings on stderr. |
|
|
96
|
+
| `--no-banner` | Do not print the banner. |
|
|
97
|
+
| `--verbose` | Debug logging. |
|
|
98
|
+
|
|
99
|
+
### Exit codes
|
|
100
|
+
|
|
101
|
+
| Code | Meaning |
|
|
102
|
+
| --- | --- |
|
|
103
|
+
| 0 | Scan finished (and no finding reached `--fail-on`). |
|
|
104
|
+
| 1 | A finding at or above the `--fail-on` severity was reported. |
|
|
105
|
+
| 2 | Invalid arguments, a missing `--authorized`, or an output file that could not be written. |
|
|
106
|
+
| 3 | With `--fail-on`: no finding reached the threshold, but the scan was incomplete (see below). |
|
|
107
|
+
| 130 | Interrupted. |
|
|
108
|
+
|
|
109
|
+
A scan is **incomplete** when every enumeration source failed or timed out (and
|
|
110
|
+
`--bruteforce` was not used), when a DNS lookup in the DNS audit failed (this includes the
|
|
111
|
+
nameserver lookups behind `--zone-transfer`), or when at least half of the discovered hosts
|
|
112
|
+
could not be resolved (timeouts or errors). A smaller number of failed lookups only adds a
|
|
113
|
+
warning. In that case "no findings" does not mean the target is clean: the JSON has
|
|
114
|
+
`"incomplete": true`, the reasons are listed under `warnings`, and CI runs using `--fail-on`
|
|
115
|
+
exit with status 3 instead of passing silently.
|
|
116
|
+
|
|
117
|
+
### Output
|
|
118
|
+
|
|
119
|
+
The JSON document contains `schema_version`, `tool` (name and version), `scanned_at`,
|
|
120
|
+
`domain`, `wildcard_dns`, `wildcard_filtered`, `sources` (the outcome of each enumeration
|
|
121
|
+
source), `subdomains`, `resolutions`, `takeover_findings`, `dns_findings`, `warnings`,
|
|
122
|
+
`incomplete`, and, when enabled, `certificate_findings`, `secret_findings`, `nuclei`,
|
|
123
|
+
`active_targets` and `skipped_hosts`. Secret values are redacted in the output: a match is
|
|
124
|
+
shown as its first and last four characters, and the surrounding context is built around the
|
|
125
|
+
match with every credential found on that line redacted. A private-key finding shows its
|
|
126
|
+
`-----BEGIN ... PRIVATE KEY-----` header in full, because the header is public and tells you
|
|
127
|
+
what kind of key was exposed; any key material that follows it on the same line is replaced by
|
|
128
|
+
`[...]`.
|
|
129
|
+
|
|
130
|
+
## Data sent to third parties
|
|
131
|
+
|
|
132
|
+
To find subdomains, the target domain name is sent to these public services:
|
|
133
|
+
|
|
134
|
+
- [crt.sh](https://crt.sh)
|
|
135
|
+
- [Cert Spotter](https://sslmate.com/certspotter)
|
|
136
|
+
- [AlienVault OTX](https://otx.alienvault.com)
|
|
137
|
+
- [RapidDNS](https://rapiddns.io)
|
|
138
|
+
- [Wayback Machine](https://web.archive.org)
|
|
139
|
+
- [Anubis (jldc.me)](https://jldc.me)
|
|
140
|
+
|
|
141
|
+
Use `--sources` to choose a subset. The tool identifies itself with the
|
|
142
|
+
User-Agent `rimscan-cli/<version> (+https://rimscan.cloud)`. Nothing is sent
|
|
143
|
+
to Rimscan or any other server.
|
|
144
|
+
|
|
145
|
+
## Scope and safety
|
|
146
|
+
|
|
147
|
+
This tool combines public data sources with direct network checks:
|
|
148
|
+
|
|
149
|
+
- **Default scan:** DNS lookups, TLS handshakes with discovered hosts, and at
|
|
150
|
+
most one HTTP request (HTTPS, then HTTP) to hosts whose CNAME points at a known
|
|
151
|
+
third-party service, to check takeover fingerprints. These requests are not retried and
|
|
152
|
+
redirects are not followed.
|
|
153
|
+
- **`--bruteforce`:** DNS lookups for a short wordlist.
|
|
154
|
+
- **`--secrets`:** GET requests for a fixed list of common paths on every selected host
|
|
155
|
+
(redirects are not followed). A request that fails, including one that breaks while its
|
|
156
|
+
body is being read, only skips that path.
|
|
157
|
+
- **`--zone-transfer`:** AXFR requests to the domain's nameservers, using each nameserver's
|
|
158
|
+
A records, or its AAAA records if it has none.
|
|
159
|
+
- **`--nuclei`:** the separately installed Nuclei scanner, which sends active
|
|
160
|
+
probes. Excluding the `dos`, `fuzz` and `intrusive` tags is not a guarantee
|
|
161
|
+
that every template is passive.
|
|
162
|
+
|
|
163
|
+
Safeguards that apply to every active step:
|
|
164
|
+
|
|
165
|
+
- Hosts that resolve to a non-public address (loopback, private, link-local) are never
|
|
166
|
+
probed, so a subdomain pointed at `127.0.0.1` or a cloud metadata address cannot make the
|
|
167
|
+
tool contact internal services.
|
|
168
|
+
- `--secrets` and `--nuclei` skip hosts that CNAME to a known third-party service
|
|
169
|
+
(the takeover fingerprints plus a built-in list of hosting platforms such as GitHub Pages,
|
|
170
|
+
Heroku, Netlify and Shopify), because those servers are not yours. Pass
|
|
171
|
+
`--include-third-party` only if you are authorized to test them. The list of hosts that
|
|
172
|
+
were probed or skipped is in `active_targets` and `skipped_hosts`. The built-in list also
|
|
173
|
+
contains large cloud providers (for example CloudFront, AWS load balancers and Azure web
|
|
174
|
+
apps), so on a target that is mostly hosted there the default active scan can cover only a
|
|
175
|
+
few hosts. Check `skipped_hosts.third_party` before reading "no findings" as "nothing
|
|
176
|
+
exposed".
|
|
177
|
+
- `--zone-transfer` never sends a request to a nameserver whose address is non-public.
|
|
178
|
+
- Redirect responses are never treated as file content by the secret scan.
|
|
179
|
+
- A server-supplied `Retry-After` header is ignored, so a scanned host cannot stall the tool
|
|
180
|
+
by asking it to wait.
|
|
181
|
+
- Caps: the TLS audit covers at most 100 hosts and the secret scan at most 50; a warning is
|
|
182
|
+
added to the JSON `warnings` (and logged) when a cap truncates the list.
|
|
183
|
+
|
|
184
|
+
Use it only against targets you are explicitly authorized to test. Respect
|
|
185
|
+
provider terms, rate limits, and the scope of the authorization you received.
|
|
186
|
+
|
|
187
|
+
The standalone CLI does not include Katana crawling, deep-scan tags, fuzzing,
|
|
188
|
+
SQL injection or XSS templates, SaaS authentication, billing, quotas,
|
|
189
|
+
notifications, a dashboard, Postgres, Redis, or Celery.
|
|
190
|
+
|
|
191
|
+
## Limitations and false positives
|
|
192
|
+
|
|
193
|
+
- **Passive enumeration is incomplete.** Sources only know names that appear in certificate
|
|
194
|
+
transparency logs, passive DNS or web archives. Hosts without a certificate history are
|
|
195
|
+
not found.
|
|
196
|
+
- **Takeover results are candidates, not proofs.** `vulnerable` means a fingerprint matched;
|
|
197
|
+
`likely` means the CNAME points at a takeover-prone service or dangles without a
|
|
198
|
+
confirming fingerprint. Verify manually before reporting. Detection works by CNAME suffix:
|
|
199
|
+
services identified by other means (for example nameserver delegation to DigitalOcean)
|
|
200
|
+
and S3 website endpoints are not covered.
|
|
201
|
+
- **Wildcard DNS.** Answers that match the zone's wildcard are filtered out. A real host that
|
|
202
|
+
shares its addresses or CNAME target with the wildcard is filtered too; the number of
|
|
203
|
+
filtered hosts is reported as `wildcard_filtered`.
|
|
204
|
+
- **DNS audit.** SPF and DMARC are checked at the domain you pass. For a subdomain, DMARC is
|
|
205
|
+
looked up at each parent down to two labels, which can be wrong under multi-label public
|
|
206
|
+
suffixes such as `co.uk`.
|
|
207
|
+
- **TLS audit.** Verification uses the certifi CA bundle, a TLS 1.2 floor and non-strict
|
|
208
|
+
X.509 checking, so results are the same on every supported Python version. Findings can
|
|
209
|
+
still differ from what a browser with another trust store reports.
|
|
210
|
+
- **Secret scan.** It looks at a fixed list of paths only. The 40-character AWS secret
|
|
211
|
+
pattern is reported only when "aws" or "secret" appears next to it and its entropy is high.
|
|
212
|
+
- **Enumeration sources fail often** (rate limits are common). Check `sources` and
|
|
213
|
+
`warnings` in the output. The crt.sh response is read up to 50 MB; for a domain with more
|
|
214
|
+
certificates than that, the source is reported as failed instead of returning a partial list.
|
|
215
|
+
- **DNS rebinding.** Non-public addresses are rejected using the lookup done during the scan.
|
|
216
|
+
A host's DNS could answer differently when the probe connects; the tool does not pin the
|
|
217
|
+
connection to the checked address.
|
|
218
|
+
|
|
219
|
+
## Rimscan, the hosted platform
|
|
220
|
+
|
|
221
|
+
`rimscan-cli` runs locally, on demand, and performs one-off reconnaissance.
|
|
222
|
+
|
|
223
|
+
[Rimscan](https://rimscan.cloud) is a hosted web platform built on the same reconnaissance
|
|
224
|
+
engine. Instead of running commands, you add a domain in a dashboard. The platform adds:
|
|
225
|
+
|
|
226
|
+
- **Continuous monitoring** on the Pro plan: targets are re-scanned automatically every
|
|
227
|
+
two days.
|
|
228
|
+
- **Deep Scan** (Pro): active crawling with Katana and payload-based testing for issues such
|
|
229
|
+
as SQL injection and XSS. This is intentionally outside the scope of this CLI.
|
|
230
|
+
- **A dashboard** with scan history and findings, severity and CVE information, and a
|
|
231
|
+
per-finding triage status.
|
|
232
|
+
|
|
233
|
+
See [rimscan.cloud](https://rimscan.cloud) for current plans and availability.
|
|
234
|
+
|
|
235
|
+
## Development
|
|
236
|
+
|
|
237
|
+
```bash
|
|
238
|
+
python -m pip install -e ".[dev]"
|
|
239
|
+
python -m ruff check .
|
|
240
|
+
python -m pytest
|
|
241
|
+
```
|
|
242
|
+
|
|
243
|
+
The test suite runs offline: all network and DNS access is mocked.
|
|
244
|
+
|
|
245
|
+
## License
|
|
246
|
+
|
|
247
|
+
This project is open source under the [Apache License 2.0](LICENSE). See
|
|
248
|
+
[LICENSE](LICENSE) for the complete license text. The takeover fingerprints are
|
|
249
|
+
sourced from [can-i-take-over-xyz](https://github.com/EdOverflow/can-i-take-over-xyz);
|
|
250
|
+
see [NOTICE](NOTICE) and review that project's terms before redistributing the fingerprint data.
|