IPure IP purity check

IP purity report

104.194.8.56

33/ 100

High risk

confidence: high

Most platforms will add verification or block outright; consider replacing it.

Based on signals observed from public and partner data sources at 2026-09-23 04:15 UTC. This describes IP-level risk only; platforms' internal risk data is not visible to us.

Profile

What this IP is

Country / region
United States · California · Los Angeles
IP type
Hosting / data center
Native / broadcast
Native IP
Network
AS23470 ReliableSite.Net LLC
Reverse DNS
none
Devices seen in subnet
16

Suitability

What it is good for

Each use case weighs the evidence differently; these are not one overall score.

AI services

ChatGPT · Claude · Gemini

2

Best avoided

Main issue: IP type: Hosting / data center

Least tolerant of data center and proxy exits: more likely to get degraded service, verification prompts or account limits. Spam history does not matter here

Social sign-up

X · Discord · Telegram · Reddit

6

Best avoided

Main issue: IP type: Hosting / data center

Sign-up is the strictest checkpoint: data center / proxy exits are more likely to be asked for phone verification or refused, and IPs with bulk-registration history are blocked far more often

Streaming / short video

TikTok · Netflix · YouTube

24

Best avoided

Main issue: Known VPN exit

Native IP and low sharing matter most: a broadcast IP reads as a region mismatch, and shared exits get throttled

Gaming platforms

Steam · PSN · Epic · Nintendo

22

Best avoided

Main issue: IP type: Hosting / data center

Region locks, regional pricing and gifting all follow the IP's location, so broadcast IPs tend to be treated as cross-region; data center exits carry a high risk of restrictions

Cross-border e-commerce

Amazon · eBay · Shopee

14

Best avoided

Main issue: IP type: Hosting / data center

Linked-account store closures are driven first by shared IPs, and only then by data center ranges

Email sending

SMTP · marketing email

26

Not recommended

Main issue: Blocklist hit: DroneBL

Blocklists make or break deliverability, while sending from a data center IP is normal and is not penalised

Evidence

Why it got this score

  • −25

    IP type: Hosting / data center

    Hosting / data center IPs are the main source of automated traffic

  • −20

    Known VPN exit

    Only 1 data source flags it as a VPN; the evidence is limited, so it counts at half weight

  • −12

    Blocklist hit: DroneBL

    Listed by DroneBL

  • −10

    2 open ports

    Includes admin ports 22: clear evidence of a server rather than home broadband

  • −5

    No rDNS record

    No PTR record; IPs allocated by established carriers usually have one

  • +5

    Native IP

    Registered and used in the same country, allocated directly by a local carrier

Reputation

Blocklists and abuse history

Listed on 1 of 8 blocklists checked: DroneBL.

  • abuseipdb abuse confidence 0%, 1 reports in 90 days

Open ports observed: 22, 443

Limits

What an IP check cannot tell you

Each platform's internal risk labels
Platforms keep their own IP reputation data and ban records and do not publish them. No hit in public sources does not mean a platform has nothing on this IP.
Whether the IP is truly exclusive
Sharing is only the number of devices observed in the same subnet. It cannot show who else is using this exit right now, or what they are doing.
Which accounts this IP has been tied to
Account-to-IP links exist only inside each platform. Accounts previously banned on this IP are invisible to us.
Device, browser and behaviour
Risk systems look at IP + device fingerprint + behavioural rhythm together. A clean IP with an odd fingerprint or behaviour still gets blocked.
Whether the account profile matches the IP
When sign-up country, phone number, payment method, language or time zone disagree with the IP's location, platforms verify further. That is unrelated to IP purity.

Sources

Data sources and responses

  • rdap
    362ms
  • team-cymru
    205ms
  • ip-api.com
    125ms
  • proxycheck.io
    262ms
  • abuseipdb
    367ms
  • cloud-ranges
    6ms
  • tor-exits
    6ms
  • rdns
    870ms
  • shodan-internetdb
    304ms
  • ipwho.is
    362ms
  • dnsbl
    392ms

Machine-readable versions of this report: JSON · plain text · 中文报告