IP cleanliness report

160.21.78.135

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

Checked:2026-10-17 09:16:33 NIDEC-SANKYO · AS0 Japan · Chiyoda · Low confidence
52
REPUTATION
Higher scores mean fewer current risk signals
01 · Executive finding

Multiple risk signals

Signals requiring review are present. Check the evidence before important use and retest after changing routes.

单源匿名网络信号
Checked2026-10-17 09:16:33 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 TypeDatacenter IP (1 consistent type signals) 18 / 40
VPN Detection1 hit ⚠️ 3 / 8
Proxy Detection1 hit ⚠️ 3 / 7
proxycheck RiskReview(Risk=33) ⚠️ 3 / 5
Key passed checks4
BGP RouteAnnounced and visible ✅ 2 / 2
Bot DetectionNot bot ✅ 1 / 1
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.

Base55
Deductions-3
Clean confirmation0
Final52
Risk-signal deductionsSingle-source anonymizer signal-3
IP TypeDatacenter IP (1 consistent type signals)18 / 40
VPN Detection1 hit ⚠️3 / 8
Proxy Detection1 hit ⚠️3 / 7
proxycheck RiskReview(Risk=33) ⚠️3 / 5
All score checksSources 16/16 · Ceiling 55
Deduction:Single-source anonymizer signalDeducted directly from the base scoreDeducted-3
IP TypeDatacenter IP (1 consistent type signals)Risk18 / 40
VPN Detection1 hit ⚠️Review3 / 8
Proxy Detection1 hit ⚠️Review3 / 7
Tor DetectionNot Tor ✅Pass5 / 5
Scamalytics ScoreLow(0) ✅Pass5 / 5
proxycheck RiskReview(Risk=33) ⚠️Review3 / 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 Datacenter / Hosting
Proxy Status No Proxy Detected
Network NIDEC-SANKYO (AS0)
Location JP · Tokyo · Chiyoda (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
Japan (JP)4/4 available sources agree
State / provinceHigh confidence
Tokyo3/3 available sources agree
City estimateLow confidence
Chiyoda1/3 available sources agree
Postal codeLow confidence
100-00011/2 available sources agree
TimezoneHigh confidence
Asia/Tokyo3/3 available sources agree
Reference coordinatesMedium confidence
35.7, 139.743/5 available sources agree · coordinate spread about 4 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoJPTokyoTokyo35.69, 139.69Asia/Tokyo
IP2LocationJPKyotoKyoto35.01, 135.77Asia/Tokyo
ipapi.comJPTokyoChiyoda35.7, 139.76Asia/Tokyo
proxycheck.ioJPTokyoChiyoda City35.69, 139.75Asia/Tokyo
ipapi.isJapanKyotoKyoto35.01, 135.77Asia/Tokyo
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 RDAPJP · JP-GMONETIRD-20260311 · 160.21.72.0/21 · 160.21.72.0 - 160.21.79.255Complete

Network identity3

IPinfoJP · AS58325 Hydra Communications LtdComplete
IP2LocationJP · AS58325 · Gmo Netird Inc. · ProxyComplete
ipapi.isJapan · AS58325 · Hydra Communications LtdComplete

Routing and ASN2

RIPEstatAS58325 · 160.21.76.0/22 · RIPE · Visibility 99.69%Complete
Team CymruAS58325 · 160.21.76.0/22 · BANDWIDTH-ASIA - Hydra Communications Ltd, GBComplete

Proxy and reputation3

proxycheck.ioJapan · GMO NetIRD, inc · hosting · Risk 33Complete
ipapi.comJP · AS0Complete
ScamalyticsFraud 0/100 · VPNComplete

Threat intelligence6

Spamhaus DROPnot_listedComplete
IPsumnone · 0 feedsComplete
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-17 09:16:33
06.1 · Report field snapshot
FieldValue
IP Address160.21.78.135
Reputation Score52/100
Cleanliness LevelMultiple signals
IP TypeDatacenter / Hosting
CountryJapan
State / provinceTokyo
City estimateChiyoda · Low confidence · 1/3 available sources agree
Postal code100-0001
TimezoneAsia/Tokyo
Reference coordinates35.7, 139.74
ISPNIDEC-SANKYO
ASNAS0
Proxy/VPNNo
Proxy TypeNone
Datacenter IPYes
Tags单源匿名网络信号
Last Checked2026-10-17 09:16:33
06.2 · Scoring and interpretation
What does the score for 160.21.78.135 mean?

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

160.21.78.135 is a datacenter IP on NIDEC-SANKYO (AS0) in JP Chiyoda.

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