---
title: "Investigate a match"
description: "Look up who registered and hosts a matched hostname, capture its page, and keep a dated report."
---

> Documentation Index
> Fetch the complete documentation index at: https://use-protect.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Investigate a match

> **Protect plan**
>
> This feature needs the Protect plan. See [Plans and billing](https://use-protect.com/docs/account/plans-and-billing/).

A monitor match says a hostname or logo resembled yours. Before you act on one, you can gather dated evidence about the hostname: who registered it, where it resolves, and what its page does. Everything here is under **Subject facts** on a match in **Brand → Matches**.

Nothing on this page files a notice, dismisses a match or contacts anyone. Each lookup records what was observed and when, including failures and missing data.

## Look up the registration

Under **Registration lookup**, select **Look up registration**. Protect asks the domain's registry for its registration record and shows the registrar, domain statuses, dates, registry nameservers and any contacts the registry returned. Fields the registry withheld are listed under **Source-declared redactions**.

The record describes the registered domain, not the exact hostname that matched.

## Look up the network

Under **Network lookup**, select **Look up network**. Protect measures the hostname's DNS records and shows them under **Observed DNS history**, with the networks that announce up to eight of its public addresses and who those addresses are registered to. It also checks whether the addresses fall inside Cloudflare's published ranges; other providers are not checked.

> **Shared hosting is not shared ownership**
>
> An IP address, network or CDN shared with another site does not show who owns a site or where it is really hosted.

**Technical relationships** compares this hostname's latest measurement with other hostnames in your store that have been measured, and lists any shared IP address or announcing network. An empty list does not show that two hostnames are unrelated.

### Lookup limits

- Up to four hostnames can have a lookup pending per store.
- Each hostname accepts one new registration lookup and one new network lookup every ten minutes.
- Select **Refresh matches with registration evidence** or **Refresh matches with network evidence** to show a finished lookup on the match.

## Capture the page

**Security investigation** loads a public HTTPS page on the hostname and records what it contains. Neither mode submits a form.

1. **Choose a capture mode**

   **Passive HTML** reads the page's HTML without running scripts or loading other resources. **Visual browser capture** runs the page in a restricted browser and keeps a screenshot, the rendered HTML and a record of the requests the page made.
2. **Choose the page**

   Protect uses the page shown as **Default source**. To capture a different page on the same hostname, enter it under **Exact assessment URL (optional)**.
3. **Start the capture**

   **Security capture progress** shows the status, then the **Security assessment**: redirects, forms that ask for credentials and where they send them, the signals found, and the limits of the capture. A visual capture also offers the screenshot and request record as downloads.

Each hostname accepts one new capture every ten minutes. **Show security scan history** lists earlier captures; select **Inspect scan** to reopen one.

An assessment that finds nothing does not show that a page is safe.

### Record your conclusion

Choose a **Security analyst disposition** (**confirmed-phishing**, **confirmed-impersonation**, **rejected** or **inconclusive**), enter a reason and select **Save security analyst review**. A confirmed disposition needs a capture that succeeded.

The review is recorded against your Shopify user and applies to that one assessment. It does not dismiss the match, authorize a seller, approve a notice or create a filing.

### Download a security report

On a finished capture, select **Prepare security report**. The report freezes that capture together with the latest registration, network and review evidence, and marks anything missing or out of date. Download it as JSON, as a PDF, or as **manual reporting text**, which includes the reporting contacts known when the report was prepared. Check those contacts before you send anything.

A security report expires after 24 hours. Evidence gathered later needs a new report.

## Page category

Protect labels what a captured page is for: **retail**, **login-account**, **support**, **parked**, **content-publication** or **unknown**. **Observed page purpose** shows the signals behind the label. The support level shown is a rule count, not a probability.

To correct the label, choose a **Review page category**, enter a **Category reason** and select **Save category review**. Your category takes priority over later automatic ones. It applies to the hostname across all monitors and changes nothing else about the match.

## Keep a record of reports you send

Protect does not send security reports. When you report a site yourself, record it under **Manual security-response journal**: select **Record external response activity** and choose the activity.

| Activity | Use it for |
|---|---|
| **Manual submission** | A report you sent. Enter where you sent it as an HTTPS or `mailto:` address. |
| **Recipient reply**, **Follow-up note**, **Recheck note**, **Counter-notice** | Something that happened after a submission. Enter the entry number of that submission. |

Entries cannot be edited. To correct one, add a **Follow-up note**. Earlier entry numbers are listed under **View subject evidence**.

## Download an investigation report

Under **Investigation report**, select **Prepare investigation report**. Protect prepares a dated PDF and a full JSON file for the hostname, covering every monitor that matched it, with the evidence references, observed DNS history and notes on missing data.

The report freezes the evidence held when you request it. It does not rescan the site, and the status line shows when it expires.

Source: https://use-protect.com/docs/brand/investigate-a-match/index.mdx
