IPure IP purity check

IP purity report

38.45.155.85

86/ 100

Clean

confidence: high

Good reputation; at the IP level it rarely draws extra verification.

Based on signals observed from public and partner data sources at 2026-09-20 08:51 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
Business broadband
Native / broadcast
Native IP
Network
AS174 Cogent Communications
Reverse DNS
none
Devices seen in subnet
no data

Suitability

What it is good for

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

AI services

ChatGPT · Claude · Gemini

90

Excellent fit

No notable obstacle found for this use case

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

85

Excellent fit

No notable obstacle found for this use case

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

92

Excellent fit

No notable obstacle found for this use case

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

93

Excellent fit

No notable obstacle found for this use case

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

89

Excellent fit

No notable obstacle found for this use case

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

Email sending

SMTP · marketing email

83

Good fit

Main issue: 1 open ports

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

Evidence

Why it got this score

  • −10

    1 open ports

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

    What it means
    Scanners see ports open on this IP. With admin ports such as 22 or 3389 it is almost certainly a server, not a home router.
    Which uses care
    Barely looks at it: AI services
    Why it is weighted this way
    Mainly corroboration that "this is a server", which the datacenter item already charged for, so only a few points here; AI-type scenarios weight it at 0.3 to avoid charging the same fact three times.
    Can it be fixed
    Close or restrict ports that do not need public access (firewall, non-default port, fail2ban); scanners update within days, then re-check. One of the few items you can change yourself.
  • −5

    No rDNS record

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

    What it means
    This IP has no reverse hostname (PTR record). Addresses allocated by established carriers usually have one.
    Which uses care
    Cares most: Email sending
    Why it is weighted this way
    A few points only: a missing PTR is a weak "unknown origin" signal, not a stain. Email cares more, since receiving servers check it.
    Can it be fixed
    Most hosts let you set a PTR in the control panel; set it to a sensible hostname.
  • −3

    IP type: Business broadband

    Business broadband is broadly trusted, though a small share are proxy exits

    What it means
    A business broadband address: generally trusted, though some corporate exits are used as proxies.
    Which uses care
    Cares most: AI services, Social sign-up, Gaming platforms, Cross-border e-commerce; Barely looks at it: Email sending
    Why it is weighted this way
    A small deduction meaning "slightly less certain than residential".
    Can it be fixed
    An inherent attribute of the IP or its range; nothing a user can change short of a different IP.
  • −1

    Abuse reports (abuseipdb)

    Confidence 2%, 1 reports in the last 90 days

    What it means
    Someone reported this IP to an abuse database (AbuseIPDB), typically for SSH brute force, port scanning or comment spam. The reporter may have seen a program on this machine, or a previous tenant.
    Which uses care
    Cares most: Social sign-up, Email sending
    Why it is weighted this way
    Counted at half the database's confidence. Sign-up scenarios care most: IPs with bulk-registration or credential-stuffing history are their first priority to block.
    Can it be fixed
    Reports age out; with no new reports for 90 days the score drops. If your machine is the one scanning, check for implanted software first.
  • +5

    Native IP

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

    What it means
    Registered and used in the same country, allocated directly by a local carrier: a "native IP".
    Which uses care
    Cares most: Streaming / short video, Gaming platforms; Barely looks at it: Email sending
    Why it is weighted this way
    A bonus: region-based checks will not trip.
    Can it be fixed
    An inherent attribute of the IP or its range; nothing a user can change short of a different IP.

Reputation

Blocklists and abuse history

Not listed on any of the 8 blocklists checked (Spamhaus ZEN, SpamCop, PSBL, blocklist.de, UCEPROTECT L1, s5h.net, DroneBL, SpamRats).

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

Open ports observed: 22

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
    207ms
  • team-cymru
    98ms
  • ip-api.com
    69ms
  • proxycheck.io
    160ms
  • abuseipdb
    104ms
  • cloud-ranges
    11ms
  • tor-exits
    11ms
  • rdns
    173ms
  • shodan-internetdb
    78ms
  • dnsbl
    196ms

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