IP cleanliness report

43.168.123.116

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

Checked:2026-10-24 14:33:11 Tencent Cloud Computing (Beijing) Co · AS0 United States of America · Quay · Low confidence
45
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-24 14:33:11 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 TypeCloud/VPS Datacenter (TENCENT CLOUD) (2 consistent type signals) 15 / 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.

Base65
Deductions0
Clean confirmation0
Final45
IP TypeCloud/VPS Datacenter (TENCENT CLOUD) (2 consistent type signals)15 / 40
Port ExposureIndexed; no high-risk exposure observed1 / 2
All score checksSources 16/16 · Ceiling 45
IP TypeCloud/VPS Datacenter (TENCENT CLOUD) (2 consistent type signals)Risk15 / 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 Datacenter / Hosting
Proxy Status No Proxy Detected
Network Tencent Cloud Computing (Beijing) Co (AS0)
Location US · New Mexico · Quay (Low confidence)
Location typeHosting/datacenter location5 geolocation sources returned
City sources differ materially; the aggregate city is only a current database estimate.
Country / regionHigh confidence
United States of America (US)3/4 available sources agree
State / provinceMedium confidence
New Mexico2/2 available sources agree
City estimateLow confidence
Quay1/2 available sources agree
Postal codeLow confidence
884331/1 available sources agree
TimezoneMedium confidence
America/Denver2/2 available sources agree
Reference coordinatesMedium confidence
34.96, -103.792/4 available sources agree · coordinate spread about 6 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoUSCaliforniaLos Angeles34.05, -118.24America/Los_Angeles
IP2LocationUSNew MexicoQuay34.96, -103.81America/Denver
ipapi.comCNBeijingHaidian (Haidian Qu)39.99, 116.29Asia/Shanghai
proxycheck.ioUSNew MexicoTucumcari34.96, -103.73America/Denver
ipapi.isSingaporeSingaporeSingapore1.28, 103.85Asia/Singapore
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 RDAPUS · ACE-SG · 43.168.123.0/24 · 43.168.123.0 - 43.168.123.255Complete

Network identity3

IPinfoUS · AS139341 ACEComplete
IP2LocationUS · AS139341 · Tencent Cloud Computing (Beijing) Co. Ltd. · HostingComplete
ipapi.isSingapore · AS139341 · ACEVILLE PTE.LTD.Complete

Routing and ASN2

RIPEstatAS139341 · 43.168.123.0/24 · APNIC · Visibility 100%Complete
Team CymruAS139341 · 43.168.123.0/24 · ACE-AS-AP - ACE, SGComplete

Proxy and reputation3

proxycheck.ioUnited States · ACE SG · business · Risk 0Complete
ipapi.comCN · AS0 · DatacenterComplete
ScamalyticsFraud 0/100Complete

Threat intelligence6

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

Internet exposure1

Shodan InternetDBPorts 80, 443, 8080Complete
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-24 14:33:11
06.1 · Report field snapshot
FieldValue
IP Address43.168.123.116
Reputation Score45/100
Cleanliness LevelMultiple signals
IP TypeDatacenter / Hosting
CountryUnited States of America
State / provinceNew Mexico
City estimateQuay · Low confidence · 1/2 available sources agree
Postal code88433
TimezoneAmerica/Denver
Reference coordinates34.96, -103.79
ISPTencent Cloud Computing (Beijing) Co
ASNAS0
Proxy/VPNNo
Proxy TypeNone
Datacenter IPYes
TagsNo tags recorded
Last Checked2026-10-24 14:33:11
06.2 · Scoring and interpretation
What does the score for 43.168.123.116 mean?

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

43.168.123.116 is a datacenter IP on Tencent Cloud Computing (Beijing) Co (AS0) in US Quay.

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