> For the complete documentation index, see [llms.txt](https://wiki.smhuda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.smhuda.com/pentesting/osint/ip-network-blocks-owned-by-a-company.md).

# IP / Network Blocks owned by a Company

{% embed url="<https://github.com/smhuda/NetblockTool>" %}

***

### Quick Run <a href="#user-content-quick-run" id="user-content-quick-run"></a>

<pre><code>git clone https://github.com/NetSPI/NetblockTool.git

<strong>cd NetblockTool &#x26;&#x26; pip3 install -r requirements.txt
</strong><strong>
</strong>python3 NetblockTool.py -v Company
</code></pre>

### Common Use Cases <a href="#user-content-common-use-cases" id="user-content-common-use-cases"></a>

Simple run. Get results from Google dorking and ARIN database:

`python3 NetblockTool.py Company`

Include the verbose flag to print status updates:

`python3 NetblockTool.py -v Company`

Extract netblocks owned by your target company’s subsidiaries:

`python3 NetblockTool.py -v Company -s`

Extract point of contact information:

`python3 NetblockTool.py -v Company -p`

Get as much information as possible, including netblocks found using wildcard queries, points of contact, geolocation data, and physical addresses:

`python3 NetblockTool.py -wpgav Company -so`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.smhuda.com/pentesting/osint/ip-network-blocks-owned-by-a-company.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.