IPure IP purity check

IP purity report

38.145.220.39

78/ 100

Fair

confidence: high

Usable; platforms with strict risk controls may occasionally show a CAPTCHA.

Based on signals observed from public and partner data sources at 2026-09-24 20:00 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 · Redondo Beach
IP type
Residential
Native / broadcast
Native IP
Network
AS18978 Enzu Inc
Reverse DNS
www.apple.com.cn
Devices seen in subnet
56

Suitability

What it is good for

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

AI services

ChatGPT · Claude · Gemini

68

Borderline

Main issue: Known VPN exit

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

66

Borderline

Main issue: Known VPN exit

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

74

Good fit

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

77

Good fit

Main issue: Known VPN exit

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

73

Good fit

Main issue: Known VPN exit

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

Email sending

SMTP · marketing email

62

Borderline

Main issue: Blocklist hit: SpamRats

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

Evidence

Why it got this score

  • −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: SpamRats

    Listed by SpamRats

  • −6

    2 open ports

    Open ports: 2053, 2087

  • −3

    Shared exit

    56 devices observed in the same subnet

  • +5

    Native IP

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

  • +6

    Spamhaus ZEN: residential range declaration

    PBL — range judged dynamic by Spamhaus

  • +8

    IP type: Residential

    Residential broadband is the IP type risk systems trust most

Reputation

Blocklists and abuse history

Listed on 1 of 7 blocklists checked: SpamRats. 1 list(s) could not be queried this time.

  • abuseipdb abuse confidence 0%

Open ports observed: 2053, 2087

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
    429ms
  • team-cymru
    169ms
  • ip-api.com
    102ms
  • proxycheck.io
    226ms
  • abuseipdb
    2305ms
  • cloud-ranges
    10ms
  • tor-exits
    10ms
  • rdns
    1338ms
  • shodan-internetdb
    239ms
  • dnsbl
    1335ms

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