IP cleanliness report

107.180.190.2

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

Checked:2026-11-19 03:44:41 THUNDERBOX INC · AS400072 United States · Sunrise · Low confidence
67
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-11-19 03:44:41 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 TypeBusiness IP (3 consistent type signals) 28 / 40
VPN Detection1 hit ⚠️ 3 / 8
Proxy Detection1 hit ⚠️ 3 / 7
Scamalytics ScoreLow(17) ✅ 4 / 5
Key passed checks4
BGP RouteAnnounced and visible ✅ 2 / 2
Bot DetectionNot bot ✅ 1 / 1
proxycheck RiskLow(Risk=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.

Base70
Deductions-3
Clean confirmation0
Final67
Risk-signal deductionsSingle-source anonymizer signal-3
IP TypeBusiness IP (3 consistent type signals)28 / 40
VPN Detection1 hit ⚠️3 / 8
Proxy Detection1 hit ⚠️3 / 7
Scamalytics ScoreLow(17) ✅4 / 5
All score checksSources 16/16 · Ceiling 75
Deduction:Single-source anonymizer signalDeducted directly from the base scoreDeducted-3
IP TypeBusiness IP (3 consistent type signals)Review28 / 40
VPN Detection1 hit ⚠️Review3 / 8
Proxy Detection1 hit ⚠️Review3 / 7
Tor DetectionNot Tor ✅Pass5 / 5
Scamalytics ScoreLow(17) ✅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 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 Business IP
Proxy Status No Proxy Detected
Network THUNDERBOX INC (AS400072)
Location US · Florida · Sunrise (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
United States (US)4/4 available sources agree
State / provinceHigh confidence
Florida3/3 available sources agree
City estimateLow confidence
Sunrise1/3 available sources agree
Postal codeLow confidence
333261/1 available sources agree
TimezoneHigh confidence
America/New_York3/3 available sources agree
Reference coordinatesMedium confidence
26.15, -80.333/5 available sources agree · coordinate spread about 5 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoUSVirginiaLeesburg39.12, -77.56America/New_York
IP2LocationUSFloridaSunrise26.16, -80.29America/New_York
ipapi.comUSFloridaPembroke Pines26.13, -80.38America/New_York
proxycheck.ioUSNew YorkNew York40.71, -74.01America/New_York
ipapi.isUnited StatesFloridaPlantation26.16, -80.29America/New_York
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 RDAPCAMPLINK · 107.180.128.0/18 · NET-107-180-128-0-1Complete

Network identity3

IPinfoUS · AS400072 THUNDERBOX INCComplete
IP2LocationUS · AS400072 · Camplink · HostingComplete
ipapi.isUnited States · AS400072 · THUNDERBOX INCComplete

Routing and ASN2

RIPEstatAS400072 · 107.180.160.0/19 · ARIN · Visibility 100%Complete
Team CymruAS400072 · 107.180.160.0/19 · THUND-20 - THUNDERBOX INC, USComplete

Proxy and reputation3

proxycheck.ioUnited States · Camplink · business · Risk 0Complete
ipapi.comUS · AS400072Complete
ScamalyticsFraud 17/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-11-19 03:44:41
06.1 · Report field snapshot
FieldValue
IP Address107.180.190.2
Reputation Score67/100
Cleanliness LevelReview
IP TypeBusiness IP
CountryUnited States
State / provinceFlorida
City estimateSunrise · Low confidence · 1/3 available sources agree
Postal code33326
TimezoneAmerica/New_York
Reference coordinates26.15, -80.33
ISPTHUNDERBOX INC
ASNAS400072
Proxy/VPNNo
Proxy TypeNone
Datacenter IPNo
Tags单源匿名网络信号
Last Checked2026-11-19 03:44:41
06.2 · Scoring and interpretation
What does the score for 107.180.190.2 mean?

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

107.180.190.2 is a business IP on THUNDERBOX INC (AS400072) in US Sunrise.

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