IP cleanliness report

23.237.102.130

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

Checked:2026-11-02 08:11:02 FDCservers.net · AS30058 Canada · Toronto · Medium confidence
22
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-11-02 08:11:02 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(19) ✅ 4 / 5
proxycheck RiskVery high(Risk=100) ❌ 0 / 5
Port ExposureIndexed; no high-risk exposure observed 1 / 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.

Base45
Deductions-23
Clean confirmation0
Final22
Risk-signal deductionsVPN · Elevated fraud or attack risk-23
IP TypeDatacenter IP (4 consistent type signals)18 / 40
VPN Detection2 hit ❌0 / 8
Proxy Detection1 hit ⚠️3 / 7
Scamalytics ScoreLow(19) ✅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
Deduction:Elevated fraud or attack riskDeducted directly from the base scoreDeducted-15
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(19) ✅Pass4 / 5
proxycheck RiskVery high(Risk=100) ❌Risk0 / 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 VPN Exit
Proxy Status VPN Exit
Network FDCservers.net (AS30058)
Location CA · Ontario · Toronto (Medium confidence)
Location typeVPN exit location5 geolocation sources returned
Country / regionHigh confidence
Canada (CA)4/4 available sources agree
State / provinceHigh confidence
Ontario4/4 available sources agree
City estimateMedium confidence
Toronto3/4 available sources agree
Postal codeLow confidence
M2J 1R31/2 available sources agree
TimezoneHigh confidence
America/Toronto4/4 available sources agree
Reference coordinatesMedium confidence
43.7, -79.394/5 available sources agree · coordinate spread about 9 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoCAOntarioToronto43.71, -79.4America/Toronto
IP2LocationCAOntarioToronto43.65, -79.38America/Toronto
ipapi.comCAOntarioToronto43.72, -79.41America/Toronto
proxycheck.ioCAOntarioToronto (North York)43.77, -79.33America/Toronto
ipapi.isUnited StatesFloridaDestin30.39, -86.5America/Chicago
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 RDAPFDCSERVERS-TORONTO · 23.237.102.0/23 · NET-23-237-102-0-1Complete

Network identity3

IPinfoCA · AS30058 FDCservers.netComplete
IP2LocationCA · AS30058 · FDCservers.net LLC · HostingComplete
ipapi.isUnited States · AS30058 · FDCservers.netComplete

Routing and ASN2

RIPEstatAS30058 · 23.237.102.0/23 · ARIN · Visibility 100%Complete
Team CymruAS30058 · 23.237.102.0/23 · FDCSERVERS - FDCservers.net, USComplete

Proxy and reputation3

proxycheck.ioCanada · FDCservers.net · hosting · Risk 100Complete
ipapi.comCA · AS30058 · DatacenterComplete
ScamalyticsFraud 19/100 · VPN · DatacenterComplete

Threat intelligence6

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

Internet exposure1

Shodan InternetDBPorts 40001Complete
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-02 08:11:02
06.1 · Report field snapshot
FieldValue
IP Address23.237.102.130
Reputation Score22/100
Cleanliness LevelElevated signals
IP TypeVPN Exit
CountryCanada
State / provinceOntario
City estimateToronto · Medium confidence · 3/4 available sources agree
Postal codeM2J 1R3
TimezoneAmerica/Toronto
Reference coordinates43.7, -79.39
ISPFDCservers.net
ASNAS30058
Proxy/VPNYes
Proxy TypeVPN
Datacenter IPYes
TagsVPN, 欺诈或攻击风险偏高
Last Checked2026-11-02 08:11:02
06.2 · Scoring and interpretation
What does the score for 23.237.102.130 mean?

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

23.237.102.130 is a proxy IP on FDCservers.net (AS30058) in CA Toronto.

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