IP cleanliness report

38.213.253.2

Multi-source IP cleanliness, network ownership, and risk signals.

Checked:2026-10-25 18:31:14 Cogent Communications · AS174 United States · Chicago · Medium confidence
35
REPUTATION
Higher scores mean fewer current risk signals
01 · Executive finding

High-risk signals

Not recommended for IP-quality-sensitive sign-in, registration, payment, or long-lived account sessions. Replace the exit IP and retest first.

Proxy
Checked2026-10-25 18:31:14 Score scale0–100 Data coverage16 data sources
02 · Key findings

Risk and clear signals

Review signals that need attention first, followed by key clear findings; only decision-useful evidence is shown here.

Key evidence is ordered by impact; the complete scoring ledger can be expanded in Score composition below.
Needs attention3
IP TypeDatacenter IP (clean) (2 consistent type signals) 24 / 40
Proxy Detection2 hit ❌ 0 / 7
Port ExposureAnonymizer tag ❌ 0 / 2
Key passed checks6
BGP RouteAnnounced and visible ✅ 2 / 2
Bot DetectionNot bot ✅ 1 / 1
proxycheck RiskLow(Risk=0) ✅ 5 / 5
Scamalytics ScoreLow(0) ✅ 5 / 5
Tor DetectionNot Tor ✅ 5 / 5
VPN Detection3 pass ✅ 8 / 8
03 · Score composition

How the score was calculated

Shows the base score, risk deductions, clean confirmation, and final score; the full scoring ledger stays collapsed until needed.

Base67
Deductions-8
Clean confirmation0
Final35
Risk-signal deductionsProxy-8
IP TypeDatacenter IP (clean) (2 consistent type signals)24 / 40
Proxy Detection2 hit ❌0 / 7
Port ExposureAnonymizer tag ❌0 / 2
All score checksSources 16/16 · Ceiling 65
Deduction:ProxyDeducted directly from the base scoreDeducted-8
IP TypeDatacenter IP (clean) (2 consistent type signals)Risk24 / 40
VPN Detection3 pass ✅Pass8 / 8
Proxy Detection2 hit ❌Risk0 / 7
Tor DetectionNot Tor ✅Pass5 / 5
Scamalytics ScoreLow(0) ✅Pass5 / 5
proxycheck RiskLow(Risk=0) ✅Pass5 / 5
Abuse HistoryNo match—
IPsum threat intelligenceNo match—
Feodo TrackerNo match—
Spamhaus DROPNo match—
DShieldNo match—
Threat-feed consensusNo multi-source confirmationNo match—
BGP RouteAnnounced and visible ✅Pass2 / 2
Port ExposureAnonymizer tag ❌Risk0 / 2
Subnet QualityNo reliable neighbor dataNo match—
Bot DetectionNot bot ✅Pass1 / 1
04 · Network profile

Network identity and location

All geolocation fields remain visible; confidence represents source agreement, not GPS-level physical accuracy.

IP Type Proxy Exit
Proxy Status Public Proxy
Network Cogent Communications (AS174)
Location US · Illinois · Chicago (Medium confidence)
Location typeProxy exit location5 geolocation sources returned
Country / regionHigh confidence
United States (US)4/4 available sources agree
State / provinceMedium confidence
Illinois2/2 available sources agree
City estimateMedium confidence
Chicago2/2 available sources agree
Postal codeMedium confidence
606082/2 available sources agree
TimezoneMedium confidence
America/Chicago2/2 available sources agree
Reference coordinatesMedium confidence
41.87, -87.632/5 available sources agree · coordinate spread about 2 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoUSIllinoisChicago41.85, -87.65America/Chicago
IP2LocationUSIllinoisChicago41.88, -87.62America/Chicago
ipapi.comUSOhioCleveland41.51, -81.7America/New_York
proxycheck.ioUSTexasDallas32.78, -96.8America/Chicago
ipapi.isUnited StatesTexasDallas32.78, -96.81America/Chicago
05 · Data sources

Source coverage and completion

Lists each source used in this check and its completion state by role; scoring evidence and individual matches remain in the scoring and evidence sections.

Complete16
Not applicable0
Unavailable0
Sources16

Registry1

RIR RDAPCOGENT-A · 38.0.0.0/8 · NET-38-0-0-0-1Complete

Network identity3

IPinfoUS · AS174 Cogent Communications, LLCComplete
IP2LocationUS · AS174 · Octopus Web Services Limited · HostingComplete
ipapi.isUnited States · AS174 · Cogent Communications, LLCComplete

Routing and ASN2

RIPEstatAS174 · 38.213.253.0/24 · RADB · Visibility 23.79%Complete
Team CymruAS174 · 38.213.253.0/24 · COGENT-174 - Cogent Communications, LLC, USComplete

Proxy and reputation3

proxycheck.ioUnited States · Web Three Limited · business · Risk 0Complete
ipapi.comUS · AS174Complete
ScamalyticsFraud 0/100 · Proxy · DatacenterComplete

Threat intelligence6

Spamhaus DROPnot_listedComplete
IPsumnone · 0 feedsComplete
Feodo TrackerComplete
Tor ProjectComplete
DShieldComplete
Blocklist.deComplete

Internet exposure1

Shodan InternetDBPorts 22, 2000, 2332, 5555, 6001, 6002, 6060, 6505, 6666, 6667, 7777, 8887, 8888, 8889, 9100 · proxyComplete
06 · Report appendix

Report methodology and field snapshot

ScoringFixed-weight aggregation with separate risk deductions
GeolocationDatabase consensus, not the device’s physical location
Snapshot time2026-10-25 18:31:14
06.1 · Report field snapshot
FieldValue
IP Address38.213.253.2
Reputation Score35/100
Cleanliness LevelElevated signals
IP TypeProxy Exit
CountryUnited States
State / provinceIllinois
City estimateChicago · Medium confidence · 2/2 available sources agree
Postal code60608
TimezoneAmerica/Chicago
Reference coordinates41.87, -87.63
ISPCogent Communications
ASNAS174
Proxy/VPNYes
Proxy TypeProxy
Datacenter IPYes
TagsProxy
Last Checked2026-10-25 18:31:14
06.2 · Scoring and interpretation
What does the score for 38.213.253.2 mean?

A score of 35/100 means several sources returned signals requiring attention. Exact labels, check time, and original sources are listed in the report.

What type of IP is this?

38.213.253.2 is a proxy IP on Cogent Communications (AS174) in US Chicago.

How is the cleanliness score calculated?

The system queries 16 data sources covering proxy/VPN classification, malicious ranges, threat intelligence, ASN, and port exposure. Evidence is combined with fixed weights into a 0-100 score and is generated only when completeness requirements are met.

What score is safe?

There is no universal safe score for every website. IPRisk summarizes proxy, blacklist, network-type, and threat-intelligence signals; each service has its own rules and may use data not shown here.

06.3 · Related samples on the same ASN

This IP returned multiple risk signals. After changing the exit, return to the IP cleanliness check to retest it, then use the Environment Scan to confirm browser routing consistency.

Check another IP Check browser routes