# 135.18.128.214 — IP Intelligence Summary

135.18.128.214 is an IPv4 address operated by Divya Quamara (AS8075), geolocated to Virginia, United Kingdom. It belongs to datacenter or hosting infrastructure. As of November 1, 2026, IPDebrief rates it High Risk (70/100); no anonymizing service was detected.

- Canonical page: https://ipdebrief.com/135.18.128.214
- Last updated: 2026-11-01

## Ownership

- Organization: Divya Quamara
- Network name: cloud
- Allocated block: 135.18.128.0/17
- ASN: AS8075 (https://ipdebrief.com/asn/8075)
- Regional registry: ARIN
- Cloud / hosting provider: Microsoft Azure

## Location

- City: Virginia
- Region: VA
- Country: United Kingdom
- Time zone: Europe/London

## Network classification

- Infrastructure type: CloudCompute
- Datacenter / hosting: yes
- Residential: no
- Mobile: no
- Anycast: no
- Tor exit node: no
- VPN: no
- Proxy: no

## Risk assessment

- Assessment: High Risk (70/100)
- Blocklist listings: 0
- Suspicious activity indicators: no
- Spam source: no

## Exposed services

- 80/tcp — http
- 443/tcp — https

## Analyst narrative

IP 135.18.128.214 was assessed as a High Risk asset with a risk score of 70. Ownership traces to ASN 8075 (Microsoft Azure) within the 135.18.128.0/17 CIDR block. Network role analysis classified the infrastructure as a Microsoft Azure cloud compute web server running Microsoft-IIS/10.0. Traffic analysis confirmed TLS certificates issued for fe2.update.microsoft.com.

Geolocation data presented contradictions, with sources assigning the location to Virginia and United Kingdom. RTT measurements of 28ms conflicted with the minimum possible latency of 131.1ms for a 6553km distance. Campaign correlation tools flagged a high likelihood with 28 correlated IPs and certificate matches. Neighborhood analysis identified two threat siblings within the /24 subnet.

Despite a low confidence score of 0.0833 and zero blacklist entries, the profile recommendation categorized the threat severity as critical. The primary recommendation was to block the IP address, citing a high risk score with strong threat evidence. Firewall rules were generated for iptables, nginx, and pf formats to mitigate the risk.

## Nearby addresses

- 135.18.128.208 (https://ipdebrief.com/135.18.128.208)
- 135.18.128.209 (https://ipdebrief.com/135.18.128.209)
- 135.18.128.210 (https://ipdebrief.com/135.18.128.210)
- 135.18.128.211 (https://ipdebrief.com/135.18.128.211)
- 135.18.128.212 (https://ipdebrief.com/135.18.128.212)
- 135.18.128.213 (https://ipdebrief.com/135.18.128.213)
- 135.18.128.215 (https://ipdebrief.com/135.18.128.215)
- 135.18.128.216 (https://ipdebrief.com/135.18.128.216)
- 135.18.128.217 (https://ipdebrief.com/135.18.128.217)

## Addresses sharing infrastructure

- 128.85.113.131 — Same TLS certificate (https://ipdebrief.com/128.85.113.131)
- 128.85.113.132 — Same TLS certificate (https://ipdebrief.com/128.85.113.132)
- 128.85.113.133 — Same TLS certificate (https://ipdebrief.com/128.85.113.133)
- 128.85.113.134 — Same TLS certificate (https://ipdebrief.com/128.85.113.134)
- 128.85.113.136 — Same TLS certificate (https://ipdebrief.com/128.85.113.136)
- 128.85.113.137 — Same TLS certificate (https://ipdebrief.com/128.85.113.137)
- 128.85.113.138 — Same TLS certificate (https://ipdebrief.com/128.85.113.138)
- 128.85.113.139 — Same TLS certificate (https://ipdebrief.com/128.85.113.139)
- 128.85.113.140 — Same TLS certificate (https://ipdebrief.com/128.85.113.140)
- 130.213.27.176 — Same TLS certificate (https://ipdebrief.com/130.213.27.176)
- 130.213.27.177 — Same TLS certificate (https://ipdebrief.com/130.213.27.177)
- 130.213.27.178 — Same TLS certificate (https://ipdebrief.com/130.213.27.178)

---

Source: IPDebrief, "135.18.128.214 IP intelligence", https://ipdebrief.com/135.18.128.214, updated 2026-11-01. Assessments are probabilistic.