IP cleanliness report

103.105.164.223

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

Checked:2026-10-15 06:08:28 Wave Broadband · AS11404 United States · Francisco · Low confidence
19
REPUTATION
Higher scores mean fewer current risk signals
01 · Executive finding

Severe risk signals

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

单源匿名网络信号欺诈或攻击风险偏高
Checked2026-10-15 06:08:28 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 attention4
IP TypeISP / Static Residential (hosting signal) (3 consistent type signals) 36 / 40
VPN Detection1 hit ⚠️ 3 / 8
Proxy Detection1 hit ⚠️ 3 / 7
Scamalytics ScoreVery high(100) ❌ 0 / 5
Key passed checks4
BGP RouteAnnounced and visible ✅ 2 / 2
Bot DetectionNot bot ✅ 1 / 1
proxycheck RiskLow(Risk=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.

Base75
Deductions-17
Clean confirmation0
Final19
Risk-signal deductionsSingle-source anonymizer signal · Elevated fraud or attack risk-17
IP TypeISP / Static Residential (hosting signal) (3 consistent type signals)36 / 40
VPN Detection1 hit ⚠️3 / 8
Proxy Detection1 hit ⚠️3 / 7
Scamalytics ScoreVery high(100) ❌0 / 5
All score checksSources 16/16 · Ceiling 94
Deduction:Single-source anonymizer signalDeducted directly from the base scoreDeducted-3
Deduction:Elevated fraud or attack riskDeducted directly from the base scoreDeducted-14
IP TypeISP / Static Residential (hosting signal) (3 consistent type signals)Pass36 / 40
VPN Detection1 hit ⚠️Review3 / 8
Proxy Detection1 hit ⚠️Review3 / 7
Tor DetectionNot Tor ✅Pass5 / 5
Scamalytics ScoreVery high(100) ❌Risk0 / 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 ExposureNo reliable exposure dataNo match—
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 Wave Broadband (AS11404)
Location US · Indiana · Francisco (Low confidence)
Location typeVPN exit location5 geolocation sources returned
City sources differ materially; the aggregate city is only a current database estimate.
Country / regionHigh confidence
United States (US)3/4 available sources agree
State / provinceMedium confidence
Indiana2/2 available sources agree
City estimateLow confidence
Francisco1/2 available sources agree
Postal codeLow confidence
476491/1 available sources agree
TimezoneMedium confidence
America/Chicago2/2 available sources agree
Reference coordinatesMedium confidence
38.33, -87.452/4 available sources agree · coordinate spread about 0 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoUSCaliforniaSan Jose37.34, -121.89America/Los_Angeles
IP2LocationUSIndianaFrancisco38.33, -87.45America/Chicago
ipapi.comSGCentral SingaporeDistrict 061.29, 103.85Asia/Singapore
proxycheck.ioUSCaliforniaPalo Alto37.44, -122.14America/Los_Angeles
ipapi.isUnited StatesIndianaOakland City38.33, -87.45America/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 RDAPComplete

Network identity3

IPinfoComplete
IP2LocationComplete
ipapi.isComplete

Routing and ASN2

RIPEstatComplete
Team CymruComplete

Proxy and reputation3

proxycheck.ioComplete
ipapi.comComplete
ScamalyticsComplete

Threat intelligence6

Spamhaus DROPComplete
IPsumComplete
Feodo TrackerComplete
Tor ProjectComplete
DShieldComplete
Blocklist.deComplete

Internet exposure1

Shodan InternetDBComplete
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-15 06:08:28
06.1 · Report field snapshot
FieldValue
IP Address103.105.164.223
Reputation Score19/100
Cleanliness LevelHigh-weight signals
IP TypeSingle-ISP / Static Residential
CountryUnited States
State / provinceIndiana
City estimateFrancisco · Low confidence · 1/2 available sources agree
Postal code47649
TimezoneAmerica/Chicago
Reference coordinates38.33, -87.45
ISPWave Broadband
ASNAS11404
Proxy/VPNNo
Proxy TypeNone
Datacenter IPNo
Tags单源匿名网络信号, 欺诈或攻击风险偏高
Last Checked2026-10-15 06:08:28
06.2 · Scoring and interpretation
What does the score for 103.105.164.223 mean?

A score of 19/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?

103.105.164.223 is a ISP IP on Wave Broadband (AS11404) in US Francisco.

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