IP cleanliness report

198.16.206.233

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

Checked:2026-10-17 10:03:15 EBOX · AS1403 Canada · Montréal · Medium confidence
90
REPUTATION
Higher scores mean fewer current risk signals
01 · Executive finding

High purity / few risk signals

The current aggregate contains relatively few negative signals. You can continue with a real connection test on the destination service.

单源匿名网络信号
Checked2026-10-17 10:03:15 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 attention2
Proxy Detection1 hit ⚠️ 3 / 7
Port ExposureIndexed; no high-risk exposure observed 1 / 2
Key passed checks6
BGP RouteAnnounced and visible ✅ 2 / 2
Bot DetectionNot bot ✅ 1 / 1
IP TypeResidential Network / Multi-source Confirmed (2 consistent type signals) 40 / 40
proxycheck RiskLow(Risk=0) ✅ 5 / 5
Scamalytics ScoreLow(4) ✅ 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.

Base93
Deductions-3
Clean confirmation0
Final90
Risk-signal deductionsSingle-source anonymizer signal-3
Proxy Detection1 hit ⚠️3 / 7
Port ExposureIndexed; no high-risk exposure observed1 / 2
All score checksSources 16/16 · No score ceiling
Deduction:Single-source anonymizer signalDeducted directly from the base scoreDeducted-3
IP TypeResidential Network / Multi-source Confirmed (2 consistent type signals)Pass40 / 40
VPN Detection3 pass ✅Pass8 / 8
Proxy Detection1 hit ⚠️Review3 / 7
Tor DetectionNot Tor ✅Pass5 / 5
Scamalytics ScoreLow(4) ✅Pass5 / 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 Residential / Multi-source Confirmed
Proxy Status No Proxy Detected
Network EBOX (AS1403)
Location CA · Quebec · Montréal (Medium confidence)
Location typeProxy exit location5 geolocation sources returned
Country / regionHigh confidence
Canada (CA)4/4 available sources agree
State / provinceHigh confidence
Quebec5/5 available sources agree
City estimateMedium confidence
Montréal5/5 available sources agree
Postal codeLow confidence
H1A 0A11/3 available sources agree
TimezoneHigh confidence
America/Toronto5/5 available sources agree
Reference coordinatesMedium confidence
45.51, -73.585/5 available sources agree · coordinate spread about 1 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoCAQuebecMontréal45.51, -73.59America/Toronto
IP2LocationCAQuebecMontreal45.51, -73.59America/Toronto
ipapi.comCAQuebecMontreal45.52, -73.58America/Toronto
proxycheck.ioCAQuebecMontreal45.5, -73.57America/Toronto
ipapi.isCanadaQuebecMontréal45.51, -73.59America/Toronto
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 RDAPEBOX-NET-198-16-128-0-1 · 198.16.128.0/17 · NET-198-16-128-0-1Complete

Network identity3

IPinfoCA · AS1403 EBOX · 198-16-206-233.qc.ftth.ebox.netComplete
IP2LocationCA · AS1403 · EBOX · ProxyComplete
ipapi.isCanada · AS1403 · EBOXComplete

Routing and ASN2

RIPEstatAS1403 · 198.16.200.0/21 · ARIN · Visibility 99.69%Complete
Team CymruAS1403 · 198.16.200.0/21 · EBOX - EBOX, CAComplete

Proxy and reputation3

proxycheck.ioCanada · EBOX · residential · Risk 0Complete
ipapi.comCA · AS1403Complete
ScamalyticsFraud 4/100Complete

Threat intelligence6

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

Internet exposure1

Shodan InternetDBPorts 443, 7547 · eol-productComplete
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 10:03:15
06.1 · Report field snapshot
FieldValue
IP Address198.16.206.233
Reputation Score90/100
Cleanliness LevelFew signals
IP TypeResidential / Multi-source Confirmed
CountryCanada
State / provinceQuebec
City estimateMontréal · Medium confidence · 5/5 available sources agree
Postal codeH1A 0A1
TimezoneAmerica/Toronto
Reference coordinates45.51, -73.58
ISPEBOX
ASNAS1403
Proxy/VPNNo
Proxy TypeNone
Datacenter IPNo
Tags单源匿名网络信号, Clean quality node
Last Checked2026-10-17 10:03:15
06.2 · Scoring and interpretation
What does the score for 198.16.206.233 mean?

A score of 90/100 means the current aggregated data contains relatively few negative signals. Classifications, check time, and matches are listed in the source details.

What type of IP is this?

198.16.206.233 is a residential IP on EBOX (AS1403) in CA Montréal.

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
Check another IP Check browser routes