IP Fraud Score API: Risk JSON for 8.8.8.8

An IP fraud score API returns a numeric risk score plus operator and anonymization flags so you can gate a signup without storing a full geolocation payload. On ipXapi that is GET https://ipxapi.com/api/fraud-score?ip= with Authorization: Bearer. The official quick-start IP is 8.8.8.8.

Basic is $29.99/mo with a 7-day trial or 50 requests. This is a different path from GET /api/ip (city/ASN). Docs: ipxapi.com (quick-start / playground).

Request: fraud score for 8.8.8.8

curl 'https://ipxapi.com/api/fraud-score?ip=8.8.8.8' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer YOUR_KEY'

Response: official 8.8.8.8 sample

{
"ip": "8.8.8.8",
"fraud_score": 0,
"risk_level": "low",
"risk_label": "Low Risk",
"is_high_risk": false,
"operator": {
"organization": "Level 3",
"isp": "Google LLC",
"asn": "15169",
"hostname": "dns.google"
},
"location": {
"country": null,
"country_code": "US",
"state": "California",
"city": "Mountain View",
"postal_code": "94043",
"latitude": 37.422,
"longitude": -122.085
},
"datacenter": { "is_datacenter": true },
"anonymization": {
"is_vpn": false,
"is_tor": true,
"is_proxy": false,
"is_server": true,
"is_search_engine_bot": true
},
"external_blacklists": { "is_blacklisted": false },
"checked_at": "2026-01-23T12:54:54Z"
}

In this fixture fraud_score is 0 and is_high_risk is false, but anonymization.is_tor is true and is_datacenter is true. Do not collapse “low score” with “residential user”. location.country is null while country_code is US — read the fields that exist.

Sibling endpoints (same Bearer)

• GET /api/abuse-check — abuse / blacklist-oriented check (same ip query style in docs).
• GET /api/ip — geolocation envelope (city, ASN) used in the geolocation post.

MCP for agents: https://mcp.ipxapi.com (the path ipxapi.com/mcp 404s).

Go live

FAQ

Is 8.8.8.8 “fraudulent”?

The published sample scores it 0 / low, with datacenter and Tor flags set. Treat it as a fixture, not a policy.

Start the trial and score 8.8.8.8 →