IP purity report

38.45.65.47

23/ 100

Very high risk

confidence: high

Reputation is burned; almost every platform will block it.

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

Proxy exit

Profile

What this IP is

Country / region: United States · North Carolina · Durham
IP type: Business broadband
Native / broadcast: Native IP
Network: AS174 Little Creek Solutions
Reverse DNS: none
Devices seen in subnet: 13

Suitability

What it is good for

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

AI services

ChatGPT · Claude · Gemini

Borderline

Main issue: Proxy IP

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

Not recommended

Main issue: Proxy IP

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

Borderline

Main issue: Proxy IP

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

Borderline

Main issue: Proxy IP

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

Not recommended

Main issue: Blocklist hit: Spamhaus ZEN

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

Email sending

SMTP · marketing email

Best avoided

Main issue: Blocklist hit: Spamhaus ZEN

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

Evidence

Why it got this score

−45
Blocklist hit: Spamhaus ZEN
XBL — compromised host / open proxy; SBL CSS — automatically detected spam source
What it means
A Spamhaus listing means this IP was confirmed sending spam, or the machine is compromised and being used as a relay.
Which uses care
Cares most: Email sending; Barely looks at it: AI services, Social sign-up, Streaming / short video, Gaming platforms
Why it is weighted this way
This is behavioural evidence, not a profile guess, so it is a hard cap and fatal for email. It carries little weight for scenarios that ignore mail reputation, such as AI services.
Can it be fixed
Fix the cause first (shut down the compromised service, remove malware), then request removal from Spamhaus; usually resolved within days.
−15
Proxy IP
Only 1 data source flags it as a proxy; the evidence is limited, so it counts at half weight
What it means
A source marks this address as a proxy exit without saying whether it is a VPN, a datacenter proxy or something else.
Which uses care
Cares most: AI services, Social sign-up, Streaming / short video, Gaming platforms, Cross-border e-commerce
Why it is weighted this way
Only one source says so, so it counts at half weight.
Can it be fixed
These labels are usually applied to whole ranges and are hard to clear by behaviour; moving to an unlabeled range is the practical fix.
−8
21 known vulnerabilities
Mostly matched from software version banners; it shows the machine is unmaintained, and platform risk systems do not look at this directly: CVE-2025-32728, CVE-2023-51767, CVE-2026-59996 and more
What it means
Scanners matched the version banners of exposed services to published CVE numbers. Most are just version matches, not confirmed exploitable holes.
Which uses care
Barely looks at it: AI services
Why it is weighted this way
It shows the machine is unmaintained, another sign of "server"; platform risk systems never count CVEs on an IP. Capped at 8 points (20 before 2026-09-26, which pushed ordinary VPS into "very high risk" for one fact charged three times).
Can it be fixed
Update the system and the services exposed to the internet (sshd above all); scanners update within days, then re-check.
−6
4 open ports
Open ports: 111, 3128, 10007, 10012
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.
+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

Listed on 1 of 8 blocklists checked: Spamhaus ZEN.

abuseipdb abuse confidence 0%

Open ports observed: 111, 3128, 10007, 10012

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
195ms
team-cymru
9ms
ip-api.com
34ms
proxycheck.io
66ms
abuseipdb
90ms
cloud-ranges
5ms
tor-exits
5ms
rdns
7ms
shodan-internetdb
32ms
dnsbl
218ms

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