IP cleanliness report

117.55.225.63

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

Checked:2026-10-17 12:54:44 UBRCBRVL293 · AS0 Australia · Canberra · Medium confidence
55
REPUTATION
Higher scores mean fewer current risk signals
01 · Executive finding

Needs review

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

Checked2026-10-17 12:54:44 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 (4 consistent type signals) 18 / 40
Scamalytics ScoreMedium(25) ⚠️ 2 / 5
proxycheck RiskReview(Risk=33) ⚠️ 3 / 5
Key passed checks5
BGP RouteAnnounced and visible ✅ 2 / 2
Bot DetectionNot bot ✅ 1 / 1
Proxy Detection3 pass ✅ 7 / 7
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.

Base63
Deductions0
Clean confirmation0
Final55
IP TypeDatacenter IP (4 consistent type signals)18 / 40
Scamalytics ScoreMedium(25) ⚠️2 / 5
proxycheck RiskReview(Risk=33) ⚠️3 / 5
All score checksSources 16/16 · Ceiling 55
IP TypeDatacenter IP (4 consistent type signals)Risk18 / 40
VPN Detection3 pass ✅Pass8 / 8
Proxy Detection3 pass ✅Pass7 / 7
Tor DetectionNot Tor ✅Pass5 / 5
Scamalytics ScoreMedium(25) ⚠️Review2 / 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 UBRCBRVL293 (AS0)
Location AU · Australian Capital Territory · Canberra (Medium confidence)
Location typeHosting/datacenter location5 geolocation sources returned
Country / regionMedium confidence
Australia (AU)2/4 available sources agree
State / provinceMedium confidence
Australian Capital Territory2/2 available sources agree
City estimateMedium confidence
Canberra2/2 available sources agree
Postal codeLow confidence
26121/1 available sources agree
TimezoneMedium confidence
Australia/Sydney2/2 available sources agree
Reference coordinatesMedium confidence
-35.28, 149.132/3 available sources agree · coordinate spread about 0 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoUSCaliforniaLos Angeles34.05, -118.24America/Los_Angeles
IP2LocationAUAustralian Capital TerritoryCanberra-35.28, 149.13Australia/Sydney
ipapi.comAUNew South WalesSydney-33.85, 151.2Australia/Sydney
proxycheck.ioUSCaliforniaLos Angeles (Downtown Los Angeles)34.05, -118.26America/Los_Angeles
ipapi.isAustraliaAustralian Capital TerritoryCanberra-35.28, 149.13Australia/Sydney
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 RDAPAU · UBRCBRVL293-324 · 117.55.225.0/24 · 117.55.225.0 - 117.55.225.255Complete

Network identity3

IPinfoUS · AS35916 MULTACOM CORPORATIONComplete
IP2LocationAU · AS35916 · 5G Network Operations Pty Ltd · HostingComplete
ipapi.isAustralia · AS35916 · MULTACOM CORPORATIONComplete

Routing and ASN2

RIPEstatAS35916 · 117.55.225.0/24 · APNIC · Visibility 99.69%Complete
Team CymruAS35916 · 117.55.225.0/24 · MULTA-ASN1 - MULTACOM CORPORATION, USComplete

Proxy and reputation3

proxycheck.ioUnited States · MULTACOM CORPORATION · hosting · Risk 33Complete
ipapi.comAU · AS0 · DatacenterComplete
ScamalyticsFraud 25/100 · DatacenterComplete

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 12:54:44
06.1 · Report field snapshot
FieldValue
IP Address117.55.225.63
Reputation Score55/100
Cleanliness LevelReview
IP TypeDatacenter / Hosting
CountryAustralia
State / provinceAustralian Capital Territory
City estimateCanberra · Medium confidence · 2/2 available sources agree
Postal code2612
TimezoneAustralia/Sydney
Reference coordinates-35.28, 149.13
ISPUBRCBRVL293
ASNAS0
Proxy/VPNNo
Proxy TypeNone
Datacenter IPYes
TagsNo tags recorded
Last Checked2026-10-17 12:54:44
06.2 · Scoring and interpretation
What does the score for 117.55.225.63 mean?

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

117.55.225.63 is a datacenter IP on UBRCBRVL293 (AS0) in AU Canberra.

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