> For the complete documentation index, see [llms.txt](https://vulnableone.gitbook.io/vulnableone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vulnableone.gitbook.io/vulnableone/offensive-treasure/red-team/reconnaissance/search-victim-owned-websites.md).

# Search Victim-Owned Websites

Adversaries may search websites owned by the victim for information that can be used during targeting. Victim-owned websites may contain a variety of details, including names of departments/divisions, physical locations, and data about key employees such as names, roles, and contact info. These sites may also have details highlighting business operations and relationships.[\[1\]](https://www.comparitech.com/blog/vpn-privacy/350-million-customer-records-exposed-online/)

## Extract Link From HTML

```basic
cat index.html | sed 's/href=/\nhref=/g' | \grep href=\" | \sed 's/.*href="//g;s/".*//g' | sort | uniq
cat index.html | sed 's/src=/\nsrc=/g' | \grep src=\" | \sed 's/.*src="//g;s/".*//g' | sort | uniq
cat index.html | grep -Po '<img[^>]*src="\K[^"]*(?=")'
```

{% code title="Grep From Site" %}

```powershell
# Specify the URL of the web page you want to extract attributes from
$url = "https://example.com"

# Use Invoke-WebRequest to fetch the web page content
$response = Invoke-WebRequest -Uri $url

# Check if the request was successful
if ($response.StatusCode -eq 200) {
    # Extract src and href attributes using regular expressions
    $htmlContent = $response.Content
    $srcMatches = [System.Text.RegularExpressions.Regex]::Matches($htmlContent, 'src="([^"]+)"')
    $hrefMatches = [System.Text.RegularExpressions.Regex]::Matches($htmlContent, 'href="([^"]+)"')

    # Print the extracted src attributes
    Write-Host "SRC attributes:"
    foreach ($match in $srcMatches) {
        Write-Host $match.Groups[1].Value
    }

    # Print the extracted href attributes
    Write-Host "HREF attributes:"
    foreach ($match in $hrefMatches) {
        Write-Host $match.Groups[1].Value
    }
} else {
    Write-Host "Failed to retrieve the web page. Status code: $($response.StatusCode)"
}
```

{% endcode %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://vulnableone.gitbook.io/vulnableone/offensive-treasure/red-team/reconnaissance/search-victim-owned-websites.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
