IP cleanliness report

38.110.204.189

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

Checked:2026-10-18 11:36:02 Cogent Communications · AS174 United States · Washington · Medium confidence
94
REPUTATION
Higher scores mean fewer current risk signals
01 · Executive finding

High purity / few risk signals

The current aggregate contains relatively few negative signals. You can continue with a real connection test on the destination service.

Checked2026-10-18 11:36:02 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 attention2
IP TypeISP / Static Residential (hosting signal) (3 consistent type signals) 36 / 40
Port ExposureIndexed; no high-risk exposure observed 1 / 2
Key passed checks6
BGP RouteAnnounced and visible ✅ 2 / 2
Bot DetectionNot bot ✅ 1 / 1
Proxy Detection3 pass ✅ 7 / 7
proxycheck RiskLow(Risk=0) ✅ 5 / 5
Scamalytics ScoreLow(0) ✅ 5 / 5
Tor DetectionNot Tor ✅ 5 / 5
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.

Base93
Deductions0
Clean confirmation+3
Final94
IP TypeISP / Static Residential (hosting signal) (3 consistent type signals)36 / 40
Port ExposureIndexed; no high-risk exposure observed1 / 2
Clean network confirmationApplied only with zero deductions and sufficient evidence for the network type.+3
All score checksSources 16/16 · Ceiling 94
IP TypeISP / Static Residential (hosting signal) (3 consistent type signals)Pass36 / 40
VPN Detection3 pass ✅Pass8 / 8
Proxy Detection3 pass ✅Pass7 / 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 ExposureIndexed; no high-risk exposure observedReview1 / 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 Single-ISP / Static Residential
Proxy Status No Proxy Detected
Network Cogent Communications (AS174)
Location US · District of Columbia · Washington (Medium confidence)
Location typeHosting/datacenter location5 geolocation sources returned
Country / regionHigh confidence
United States (US)4/4 available sources agree
State / provinceMedium confidence
District of Columbia2/4 available sources agree
City estimateMedium confidence
Washington2/4 available sources agree
Postal codeLow confidence
569441/2 available sources agree
TimezoneHigh confidence
America/New_York4/4 available sources agree
Reference coordinatesMedium confidence
38.95, -77.144/5 available sources agree · coordinate spread about 32 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoUSVirginiaAshburn39.04, -77.49America/New_York
IP2LocationUSDistrict of ColumbiaWashington38.9, -77.04America/New_York
ipapi.comUSTexasWebster29.55, -95.13America/Chicago
proxycheck.ioUSMarylandLanham38.97, -76.86America/New_York
ipapi.isUnited StatesDistrict of ColumbiaWashington38.89, -77.03America/New_York
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 · AS6079 RCNComplete
IP2LocationUS · AS6079 · Innolink Network Ltd · HostingComplete
ipapi.isUnited States · AS6079 · RCNComplete

Routing and ASN2

RIPEstatAS6079 · 38.110.204.0/24 · ARIN · Visibility 100%Complete
Team CymruAS6079 · 38.110.204.0/24 · RCN-AS - RCN, USComplete

Proxy and reputation3

proxycheck.ioUnited States · Innolink Network Ltd · business · Risk 0Complete
ipapi.comUS · AS174Complete
ScamalyticsFraud 0/100Complete

Threat intelligence6

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

Internet exposure1

Shodan InternetDBPorts 22Complete
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-18 11:36:02
06.1 · Report field snapshot
FieldValue
IP Address38.110.204.189
Reputation Score94/100
Cleanliness LevelFew signals
IP TypeSingle-ISP / Static Residential
CountryUnited States
State / provinceDistrict of Columbia
City estimateWashington · Medium confidence · 2/4 available sources agree
Postal code56944
TimezoneAmerica/New_York
Reference coordinates38.95, -77.14
ISPCogent Communications
ASNAS174
Proxy/VPNNo
Proxy TypeNone
Datacenter IPNo
TagsClean quality node
Last Checked2026-10-18 11:36:02
06.2 · Scoring and interpretation
What does the score for 38.110.204.189 mean?

A score of 94/100 means the current aggregated data contains relatively few negative signals. Classifications, check time, and matches are listed in the source details.

What type of IP is this?

38.110.204.189 is a ISP IP on Cogent Communications (AS174) in US Washington.

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
Check another IP Check browser routes