IP cleanliness report

164.52.200.75

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

Checked:2026-11-14 10:02:02 E2E Networks Limited · AS132420 India · Delhi · Medium confidence
65
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 10:02: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 attention2
IP TypeDatacenter IP (clean) (2 consistent type signals) 24 / 40
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
Scamalytics ScoreLow(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.

Base77
Deductions-8
Clean confirmation0
Final65
Risk-signal deductionsVulns-8
IP TypeDatacenter IP (clean) (2 consistent type signals)24 / 40
Port ExposureIndexed; no high-risk exposure observed1 / 2
All score checksSources 16/16 · Ceiling 65
Deduction:VulnsDeducted directly from the base scoreDeducted-8
IP TypeDatacenter IP (clean) (2 consistent type signals)Risk24 / 40
VPN Detection3 pass ✅Pass8 / 8
Proxy Detection3 pass ✅Pass7 / 7
Tor DetectionNot Tor ✅Pass5 / 5
Scamalytics ScoreLow(0) ✅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 Datacenter / Hosting
Proxy Status No Proxy Detected
Network E2E Networks Limited (AS132420)
Location IN · Uttar Pradesh · Delhi (Medium confidence)
Location typeHosting/datacenter location5 geolocation sources returned
Country / regionHigh confidence
India (IN)4/4 available sources agree
State / provinceMedium confidence
Uttar Pradesh3/5 available sources agree
City estimateMedium confidence
Delhi2/5 available sources agree
Postal codeLow confidence
2013011/2 available sources agree
TimezoneHigh confidence
Asia/Calcutta5/5 available sources agree
Reference coordinatesMedium confidence
28.58, 77.35/5 available sources agree · coordinate spread about 10 km
View all geolocation sources5
SourceCountryRegionCityCoordinatesTimezone
IPinfoINDelhiDelhi28.65, 77.23Asia/Calcutta
IP2LocationINUttar PradeshNoida28.58, 77.33Asia/Calcutta
ipapi.comINDelhiDelhi28.54, 77.28Asia/Calcutta
proxycheck.ioINUttar PradeshNoida (Bakhtāwarpur)28.53, 77.35Asia/Calcutta
ipapi.isIndiaUttar PradeshNoida28.58, 77.33Asia/Calcutta
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 RDAPIN · E2E-NETWORKS-IN · 164.52.200.0/21 · 164.52.200.0 - 164.52.207.255Complete

Network identity3

IPinfoIN · AS132420 E2E NETWORKS · e2e-68-75.ssdcloudindia.netComplete
IP2LocationIN · AS132420 · E2E Networks Private Limited · HostingComplete
ipapi.isIndia · AS132420 · E2E Networks LimitedComplete

Routing and ASN2

RIPEstatAS132420 · 164.52.200.0/21 · APNIC · Visibility 99.69%Complete
Team CymruAS132420 · 164.52.200.0/21 · E2E-NETWORKS-IN - 282, Sector 19, INComplete

Proxy and reputation3

proxycheck.ioIndia · E2E Networks Limited · business · Risk 0Complete
ipapi.comIN · AS132420 · DatacenterComplete
ScamalyticsFraud 0/100Complete

Threat intelligence6

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

Internet exposure1

Shodan InternetDBPorts 80, 443, 3478, 8080 · self-signedComplete
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 10:02:02
06.1 · Report field snapshot
FieldValue
IP Address164.52.200.75
Reputation Score65/100
Cleanliness LevelReview
IP TypeDatacenter / Hosting
CountryIndia
State / provinceUttar Pradesh
City estimateDelhi · Medium confidence · 2/5 available sources agree
Postal code201301
TimezoneAsia/Calcutta
Reference coordinates28.58, 77.3
ISPE2E Networks Limited
ASNAS132420
Proxy/VPNNo
Proxy TypeNone
Datacenter IPYes
TagsVulns
Last Checked2026-11-14 10:02:02
06.2 · Scoring and interpretation
What does the score for 164.52.200.75 mean?

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

164.52.200.75 is a datacenter IP on E2E Networks Limited (AS132420) in IN Delhi.

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.

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