> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/private-panels/studies/duplicate-ip-protection.md).

# Duplicate IP protection

To prevent fraud, Private Panels will flag respondents who answer surveys from the same IP. When we find two surveys with the same IP, a little alert will pop up in the **Study Overview** page. This feature only works when [Who can take the screener](/private-panels/screeners/survey-status.md) setting is either **Anyone** or **Study Participants**.

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/3edavy7GDlFJUPHPA8F9/37061498801684)

## How to turn this off

You can also turn this setting off on the **Screener Settings** page.

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/JgiJ6wqun5yQpqouFZix/37061498802708)

## Find a survey response by IP

In a **Study**, click the **Quick Search** input field. You can either type out the entire **IP** (e.g. 123.1.2.3), or type **ip:XXX.XX.XX.XX** which has the ability to match multiple IPs (e.g. ip:127.1.2.3)

![](https://content.gitbook.com/content/T7fhyut5rrQHwe5QRGot/blobs/q07VB3razFQ1iHVXiI4P/37061498804116)

To find panelist profiles who share the same IP, [read this article](/private-panels/panel-management/track-panelist-ip-and-country.md).

{% hint style="info" %}
**Note:** Private Panels was previously managed outside of Dscout, so you may see a different logo and URL in some places. If you have any questions, contact <support@dscout.com>.
{% endhint %}


---

# 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://help.dscout.com/private-panels/studies/duplicate-ip-protection.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.