IP cleanliness report

203.12.0.153

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

Checked:2026-11-14 08:54:13 Launtel · AS134697 Australia · Brisbane · 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.

Vulns
Checked2026-11-14 08:54:13 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 (1 consistent type signals) 18 / 40
Scamalytics ScoreLow(7) ✅ 4 / 5
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
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.

Base68
Deductions-8
Clean confirmation0
Final55
Risk-signal deductionsVulns-8
IP TypeDatacenter IP (1 consistent type signals)18 / 40
Scamalytics ScoreLow(7) ✅4 / 5
Port ExposureIndexed; no high-risk exposure observed1 / 2
All score checksSources 16/16 · Ceiling 55
Deduction:VulnsDeducted directly from the base scoreDeducted-8
IP TypeDatacenter IP (1 consistent type signals)Risk18 / 40
VPN Detection3 pass ✅Pass8 / 8
Proxy Detection3 pass ✅Pass7 / 7
Tor DetectionNot Tor ✅Pass5 / 5
Scamalytics ScoreLow(7) ✅Pass4 / 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 Launtel (AS134697)
Location AU · Queensland · Brisbane (Medium confidence)
Location typeHosting/datacenter location5 geolocation sources returned
Country / regionHigh confidence
Australia (AU)4/4 available sources agree
State / provinceHigh confidence
Queensland5/5 available sources agree
City estimateMedium confidence
Brisbane5/5 available sources agree
Postal codeMedium confidence
40002/2 available sources agree
TimezoneHigh confidence
Australia/Brisbane5/5 available sources agree
Reference coordinatesMedium confidence
-27.46, 153.035/5 available sources agree · coordinate spread about 1 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoAUQueenslandBrisbane-27.47, 153.03Australia/Brisbane
IP2LocationAUQueenslandBrisbane-27.47, 153.03Australia/Brisbane
ipapi.comAUQueenslandBrisbane-27.45, 153.02Australia/Brisbane
proxycheck.ioAUQueenslandBrisbane-27.47, 153.03Australia/Brisbane
ipapi.isAustraliaQueenslandBrisbane-27.47, 153.03Australia/Brisbane
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 · LAUNBN · 203.12.0.0/24 · 203.12.0.0 - 203.12.0.255Complete

Network identity3

IPinfoAU · AS134697 Launtel · 203.12.0.153.v4.dyn.launtel.auComplete
IP2LocationAU · AS134697 · LauntelComplete
ipapi.isAustralia · AS134697 · LAUNTEL PTY LTDComplete

Routing and ASN2

RIPEstatAS134697 · 203.12.0.0/24 · APNIC · Visibility 10%Complete
Team CymruAS134697 · 203.12.0.0/23 · LAUNTEL-AS-AP - Launtel, AUComplete

Proxy and reputation3

proxycheck.ioAustralia · LAUNTEL PTY LTD · business · Risk 0Complete
ipapi.comAU · AS134697Complete
ScamalyticsFraud 7/100 · DatacenterComplete

Threat intelligence6

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

Internet exposure1

Shodan InternetDBPorts 80, 443, 2222, 3478, 25565 · videogameComplete
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-11-14 08:54:13
06.1 · Report field snapshot
FieldValue
IP Address203.12.0.153
Reputation Score55/100
Cleanliness LevelReview
IP TypeDatacenter / Hosting
CountryAustralia
State / provinceQueensland
City estimateBrisbane · Medium confidence · 5/5 available sources agree
Postal code4000
TimezoneAustralia/Brisbane
Reference coordinates-27.46, 153.03
ISPLauntel
ASNAS134697
Proxy/VPNNo
Proxy TypeNone
Datacenter IPYes
TagsVulns
Last Checked2026-11-14 08:54:13
06.2 · Scoring and interpretation
What does the score for 203.12.0.153 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?

203.12.0.153 is a datacenter IP on Launtel (AS134697) in AU Brisbane.

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