# IP Intelligence Briefing: 135.232.184.208
## Executive Summary
IP address 135.232.184.208 is classified as Low Risk (Risk Score: 25) with no active threat indicators. The address is associated with Microsoft Azure cloud infrastructure in Chicago, IL, USA, and demonstrates stable operational characteristics with no observed malicious activity.
## Technical Profile
- IP Address: 135.232.184.208/32
- Risk Score: 25 (Low Risk)
- Provider: Microsoft Azure (ASN 8075)
- Network Block: 135.232.0.0/16
- Geolocation: Chicago, IL, US (41.88°N, -87.63°W)
- Infrastructure Type: CloudCompute
- Network Role: Firewalled / No Services
## Threat Assessment
- Known Attacker: No
- Tor Exit Node: No
- Spam Source: No
- Blacklist Status: Listed on 1 of 8 DNSBLs
- Abuse Confidence Score: Not applicable
- Threat Persistence: No persistent malicious activity detected
- Campaign Affiliation: None identified
## Network Behavior
- Open Ports: None detected
- TLS Certificate: Not present
- HTTP Services: Not detected
- DNS Records: No reverse PTR resolution
- Email Reputation: No sender score calculated
- Control Plane: BGP prefix 135.232.0.0/14, route stability flags indicate minimal operator score (0.1304)
## Neighborhood Analysis
- Subnet: 135.232.184.0/24
- Abuse Density: 0%
- Active Siblings: 0
- Threat Siblings: 0
- Classification: Clean
## Historical Observations
Analysis of 20 signal observations reveals consistent classification as Microsoft Azure cloud infrastructure with no transitions to malicious behavior. Recent signals (2026-08-05) confirm:
- Cloud infrastructure classification maintained
- No attacker/attacker IP indicators
- No spam source designation
- No Tor exit node characteristics
## Related Entities
- Network Relationships: Multiple same-network associations identified (cloud infrastructure network)
- Associated Networks: 135.232.0.0/16 family networks
## Recommended Actions
No immediate firewall or blocking actions recommended. The IP exhibits characteristics of legitimate cloud infrastructure with low risk profile. Monitor for any changes in network role or service exposure.
---
*Intelligence generated from IPDebrief analysis platform. Data sourced from real-time network observations and historical signal analysis.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | Divya Quamara |
| ASN | AS8075 |
| Network Name | cloud |
| CIDR Block | 135.232.0.0/16 |
| RIR | ARIN |
| Country | US |
| Abuse Contact | Available via RDAP |
π DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No β PTR hostname does not resolve back to this IP (weak signal) |
π DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
βοΈ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Firewalled / No Services |
| Network Tier | Hosting β Infrastructure provider without advanced routing |
π Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | β |
| HTTP Title | β |
π TLS Certificate
| SANs | None |
| Valid From | β |
| Valid Until | β |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 42% | 2 | 5 |
| routing | 13% | 1 | 1 |
| services | 19% | 2 | 2 |
| ownership | 30% | 2 | 3 |
| reputation | 28% | 1 | 3 |
| geolocation | 25% | 1 | 1 |
| Overall | 26% | 9 | 15 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-07-23 20:04:56 UTC |
| Last Seen | 2026-08-12 17:50:39 UTC |
| Profile Built | 2026-08-12 17:58:30 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 21 |
Full dossier details are available via our API.