IP cleanliness report

195.238.124.37

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

Checked:2026-10-18 11:52:05 Melbikomas UAB · AS56630 Lithuania · Vilnius · Medium confidence
39
REPUTATION
Higher scores mean fewer current risk signals
01 · Executive finding

High-risk signals

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

VPN
Checked2026-10-18 11:52:05 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 attention6
IP TypeDatacenter IP (4 consistent type signals) 18 / 40
VPN Detection2 hit ❌ 0 / 8
Proxy Detection1 hit ⚠️ 3 / 7
Scamalytics ScoreLow(16) ✅ 4 / 5
proxycheck RiskHigh(Risk=50) ⚠️ 2 / 5
Port ExposureAnonymizer tag ❌ 0 / 2
Key passed checks3
BGP RouteAnnounced and visible ✅ 2 / 2
Bot DetectionNot bot ✅ 1 / 1
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.

Base47
Deductions-8
Clean confirmation0
Final39
Risk-signal deductionsVPN-8
IP TypeDatacenter IP (4 consistent type signals)18 / 40
VPN Detection2 hit ❌0 / 8
Proxy Detection1 hit ⚠️3 / 7
Scamalytics ScoreLow(16) ✅4 / 5
2 more score-impacting items are included below.
All score checksSources 16/16 · Ceiling 55
Deduction:VPNDeducted directly from the base scoreDeducted-8
IP TypeDatacenter IP (4 consistent type signals)Risk18 / 40
VPN Detection2 hit ❌Risk0 / 8
Proxy Detection1 hit ⚠️Review3 / 7
Tor DetectionNot Tor ✅Pass5 / 5
Scamalytics ScoreLow(16) ✅Pass4 / 5
proxycheck RiskHigh(Risk=50) ⚠️Review2 / 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 ExposureAnonymizer tag ❌Risk0 / 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 VPN Exit
Proxy Status VPN Exit
Network Melbikomas UAB (AS56630)
Location LT · Vilnius · Vilnius (Medium confidence)
Location typeVPN exit location5 geolocation sources returned
Country / regionHigh confidence
Lithuania (LT)4/4 available sources agree
State / provinceMedium confidence
Vilnius4/5 available sources agree
City estimateMedium confidence
Vilnius5/5 available sources agree
Postal codeMedium confidence
010013/3 available sources agree
TimezoneHigh confidence
Europe/Vilnius5/5 available sources agree
Reference coordinatesMedium confidence
54.69, 25.285/5 available sources agree · coordinate spread about 1 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoLTVilniusVilnius54.69, 25.28Europe/Vilnius
IP2LocationLTVilniaus apskritisVilnius54.69, 25.28Europe/Vilnius
ipapi.comLTVilniusVilnius54.7, 25.27Europe/Vilnius
proxycheck.ioLTVilniusVilnius54.69, 25.28Europe/Vilnius
ipapi.isLithuaniaVilniusVilnius54.69, 25.28Europe/Vilnius
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 RDAPLT · LT-MELBICOM-20180808 · 195.238.124.0/22 · 195.238.124.0 - 195.238.127.255Complete

Network identity3

IPinfoLT · AS56630 Melbikomas UABComplete
IP2LocationLT · AS56630 · Melbikomas UAB · HostingComplete
ipapi.isLithuania · AS56630 · Melbikomas UABComplete

Routing and ASN2

RIPEstatAS56630 · 195.238.124.0/22 · RADB · Visibility 100%Complete
Team CymruAS56630 · 195.238.124.0/22 · MELBICOM-EU-AS - Melbikomas UAB, LTComplete

Proxy and reputation3

proxycheck.ioLithuania · Melbikomas UAB · hosting · Risk 50Complete
ipapi.comLT · AS56630 · DatacenterComplete
ScamalyticsFraud 16/100 · VPN · DatacenterComplete

Threat intelligence6

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

Internet exposure1

Shodan InternetDBPorts 22, 443, 500, 7011 · vpnComplete
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-18 11:52:05
06.1 · Report field snapshot
FieldValue
IP Address195.238.124.37
Reputation Score39/100
Cleanliness LevelElevated signals
IP TypeVPN Exit
CountryLithuania
State / provinceVilnius
City estimateVilnius · Medium confidence · 5/5 available sources agree
Postal code01001
TimezoneEurope/Vilnius
Reference coordinates54.69, 25.28
ISPMelbikomas UAB
ASNAS56630
Proxy/VPNYes
Proxy TypeVPN
Datacenter IPYes
TagsVPN
Last Checked2026-10-18 11:52:05
06.2 · Scoring and interpretation
What does the score for 195.238.124.37 mean?

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

195.238.124.37 is a proxy IP on Melbikomas UAB (AS56630) in LT Vilnius.

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