IPDebrief

135.18.128.214

IP Intelligence Dossier
Your IP: 216.73.216.142

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.

{ } JSON
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

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.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

🌍 Geolocation

Country🇬🇧 United Kingdom
RegionVA
CityVirginia
TimezoneEurope/London
Latitude36.67
Longitude-78.39

🏢 Ownership & Registration

OrganizationDivya Quamara
ASNAS8075
Network Namecloud
CIDR Block135.18.128.0/17
RIRARIN
CountryUS
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo — PTR hostname does not resolve back to this IP (weak signal)

🔐 DNS Hygiene

Hygiene Score40% (Fair)
SPFPresent
DMARCPresent
FCrDNSNot verified
DNSSECNot signed
CAANot configured

☁️ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeWeb Server
Network TierHosting — Infrastructure provider without advanced routing
CloudHosting

🔌 Services & Open Ports

PortServiceProtocolBanner
80httptcp—
443httpstcp—
Closed Ports22, 25, 3389, 8080, 8443 (2 open / 7 scanned)
ServerWeb server detected
HTTP Title—

🔐 TLS Certificate

🔒
CN=fe2.update.microsoft.com, OU=DSP, O=Microsoft, L=Redmond, S=WA, C=US
Issued by CN=Microsoft Update Secure Server CA 2.1, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Self-signed: No
SANsfe2.update.microsoft.com
Valid From2026-01-22T20:47:39+00:00
Valid Until2027-01-22T20:47:39+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period365 days

🛡️ Public Network Snapshot

Origin ASNAS8075
Network Prefix135.18.0.0/16
Route mappingFound
HSTSNot detected
CSPNot detected
HTTP/2Enabled

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
27%
23
routing
13%
11
services
35%
24
ownership
27%
23
reputation
13%
12
geolocation
27%
23
Overall24%1016
Coverage: 6/6 dimensions · Data sufficiency: sufficient
Data CoherenceContradictory (48%) — 3 contradiction(s)
AttributionVery Low (20%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement
⚠ Geo sources disagree on country: US, GB
⚠ TLS certificate claims US but primary geo says GB

📅 Observation Timeline 🔄 Live

First Seen2026-10-22 14:09:34 UTC
Last Seen2026-11-07 05:10:06 UTC
Profile Built2026-11-01 13:28:34 UTC
Data FreshnessLive
Signal Types23
Total Observations26
🔍 23 signal types · 26 observations collected
This report is generated from 23+ independent intelligence signals including ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds, behavioral fingerprinting, and more.
Full dossier details are available via our API.
{ } JSON API 📧 Enterprise Access

❓ Frequently Asked Questions About 135.18.128.214

Who owns the IP address 135.18.128.214?

135.18.128.214 is registered to Divya Quamara. The address falls within the 135.18.128.0/17 network block. Registration is held at ARIN.

Where is 135.18.128.214 located?

Geolocation data places 135.18.128.214 in Virginia, VA, United Kingdom. The local time zone is Europe/London. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.

Is 135.18.128.214 malicious or safe?

135.18.128.214 currently carries a high risk assessment, meaning indicators associated with malicious or abusive activity have been observed. This assessment is generated from continuously collected signals and can change over time.

What ports are open on 135.18.128.214?

Responsive ports observed on 135.18.128.214 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.

Is 135.18.128.214 a VPN, proxy, or data center address?

135.18.128.214 is classified as cloud infrastructure and hosting infrastructure based on network ownership and behavioural analysis.

🏘️ Related IP Addresses

Nearby addresses in 135.18.128.0/17

Addresses sharing infrastructure

Browse related networks

ℹ️ About This Report

All data shown is publicly available network metadata — IP addresses do not reliably identify individuals. Assessments are probabilistic and should not be used as sole basis for access control decisions. To report an issue or request data review, contact admin@ipdebrief.com.