# IPQualityScore

Fraud scores and reputation flags for IPs, emails, and phones from IPQualityScore.

URL: https://osintverse.com/docs/providers/ipqs

IPQualityScore returns risk signals for an IP, email, or phone — fraud score, proxy/VPN/Tor, deliverability and disposable flags, carrier and line type — as one structured card on SearchIn, GraphIn transforms, and the OSINTOne API.

## Capabilities

* IP reputation with fraud score, proxy/VPN/Tor, ISP, ASN, and geolocation
* Email validation with deliverability, disposable, catch-all, and fraud score
* Phone validation with carrier, line type, VOIP/prepaid flags, and fraud score
* Recent-abuse and bot/crawler signals when IPQS returns them

## Data

IPQualityScore scores traffic and contact identifiers against its fraud models. SearchIn wraps the IP, email, and phone JSON endpoints only. It does not run URL scanners or device fingerprinting.

## What you get back

* Fraud score with risk badges
* Proxy / VPN / Tor and abuse flags for IPs
* Deliverability and disposable flags for emails
* Carrier and line type for phones

## UI workflow

Open SearchIn and choose IP, Email, or Phone.

Select IPQualityScore as the provider.

Review the fraud score, flags, and enrichment fields on the result card.

## Sample queries

| Input type | Query                     | Notes                               |
| ---------- | ------------------------- | ----------------------------------- |
| `ip`       | `8.8.8.8`                 | Proxy/VPN and fraud score           |
| `email`    | `alex.rivera@example.com` | Deliverability and disposable check |
| `phone`    | `+15550001111`            | Carrier and line type               |

## Pricing

`ip` **$0.10** · `email` **$0.10** · `phone` **$0.10**

## Best for

* Screening an IP for proxy, VPN, or Tor before trusting location
* Checking whether an email is disposable or high-risk before deeper people search
* Confirming phone carrier and VOIP signals next to identity providers

## How it works & why through OSINTverse

### How the request runs

1. You submit an IP, email, or phone from SearchIn, a GraphIn transform, or POST /v1/search with provider ipqs.
2. SearchIn calls the matching IPQualityScore JSON endpoint (IP, email, or phone) with the upstream API key.
3. The response is normalised into one reputation match — fraud score, flags, and enrichment fields — plus a source summary.
4. The card renders on the desk; related IPs, emails, phones, and locations land on the case graph for pivots.

**Coverage.** IPQualityScore scores IPs for proxy, VPN, Tor, and abuse; validates emails for deliverability and disposable risk; and enriches phones with carrier, line type, and fraud score. SearchIn wraps those three lookups only — not URL scanning or device fingerprinting.

### Why route IPQualityScore through OSINTverse

- A $0.10 query returns a readable fraud card — no IPQS dashboard for a one-off check.
- The same prepaid wallet covers IPQS next to Shodan, Hunter, and breach providers.
- IPs, emails, and phones drop into the case graph so you can pivot into host or identity sources.

|  | IPQualityScore directly | Through OSINTverse |
| --- | --- | --- |
| Getting started | IPQualityScore sells its own plans and API credits. The API key is bound to that account and each IP, email, or phone call consumes their credits. | Sign in, top up from $10, and run IPQualityScore the same minute — no vendor contract, seat, or sales call. |
| What a query costs | Plan, credit pack, or contract pricing set by the vendor and paid up front. | Pay per query from your prepaid balance — IPQualityScore starts at $0.10 for email lookups, with the exact price shown before you run it. |
| Failed lookups | Handled under the vendor's own credit and refund policy. | Automatically refunded to your wallet — a search that fails upstream after billing is not charged. |
| Output format | A vendor-specific response shape you normalise and render yourself. | Normalised result panels plus the raw JSON, returned by the same POST /v1/search contract as every other integration. |
| Cross-source work | Copy-paste between vendor dashboards to follow a lead into another dataset. | Results join one case graph, so you can pivot an entity into any of the other 16 integrations in a click. |
| Running it for a team | Per-seat or per-account access, billed and administered per analyst. | One shared team wallet with roles, provider allowlists, enforced MFA, and audit history — no per-seat fee. |
| Volume work | Script the vendor API yourself, including retries, polling, and rate handling. | Bulk search takes up to 50 queries across selected providers in one submission (max 100 jobs), with per-job status and partial-failure handling. |

- **One wallet, no subscriptions.** Top up prepaid USD from $10 and spend it a query at a time across all 17 integrations. No monthly fee, no seat count — and the balance never expires.
- **Failed searches are refunded.** If an upstream provider errors or times out after the charge, the search is marked refunded and the money goes back to your wallet automatically.
- **One API for every source.** The same POST /v1/search contract and x-api-key header work for every integration, so adding a source to your automation is a one-word change.
- **Cases and pivot graph.** Results land in a named case you can reopen. Entities become graph nodes you can pivot from into any other integration without retyping.
- **Team wallets and controls.** Share one balance with roles, provider allowlists, enforced MFA, and audit history — instead of buying a vendor seat for every analyst.
- **Exports built in.** Download any result as JSON, CSV, or PDF, and export the case graph as PNG, SVG, entities CSV, or graph JSON.

### Good to know

- This integration is IP, email, and phone reputation only — not URL scanners or device fingerprinting.
- Scores reflect IPQualityScore’s models at query time; a clean score is not proof of legitimacy.
- Phone country formatting follows IPQS; prefer E.164 (+…) for best hit rates.

## API example

Try `ipqs` free with mock data in the API sandbox: https://osintverse.com/developers/sandbox

```bash
curl -X POST https://apiv1.osintverse.com/v1/search \
  -H "x-api-key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"provider":"ipqs","input_type":"ip","query":"8.8.8.8"}'
```

> Invalid `provider` + `input_type` pairs return HTTP 422. Confirm combinations with [GET /v1/providers](https://osintverse.com/docs/api/overview) or the [pricing matrix](https://osintverse.com/docs/pricing).

Run this in the [SearchIn UI](https://osintverse.com/searchin/search) or create an [API key](https://osintverse.com/dashboard/api). Full HTTP reference: [search workflow](https://osintverse.com/docs/api/search). Marketing overview: [IPQualityScore integration](https://osintverse.com/integrations/ipqs).