135.119.39.19
INTELLIGENCE BRIEFING: IP 135.119.39.19
Classification: Low Risk (Score: 25)
Provider: Microsoft Azure (ASN: 8075)
Infrastructure Type: CloudCompute
Ownership and Registration:
The IP address 135.119.39.19 is registered to Microsoft Azure under organization name "Divya Quamara" within the 135.119.0.0/16 CIDR block. The network is assigned to ARIN with abuse contact available via RDAP.
Geolocation:
Location data indicates Des Moines, Iowa, United States (Region: IA). Geographic consensus is confirmed across three sources with an accuracy radius of 200 km.
Network Profile:
The IP is classified as cloud infrastructure with no open ports detected. Forward resolution failed with zero forward hostnames. Email authentication records (SPF, DMARC) are absent. Control plane analysis shows the BGP prefix 135.119.0.0/16 with route stability flagged as false.
Threat Indicators:
Current threat assessment indicates zero known attacks, no Tor exit node activity, and zero blacklist hits. However, historical signals include at least one threat indicator observation recorded on 2026-08-13 with a threat confidence level of 0.75.
Neighborhood Analysis:
The /24 subnet (135.119.39.19/24) shows clean classification with zero abuse density. No sibling IPs were detected in the neighborhood scan.
Relationship Graph:
Relationships are limited to same-network associations with the network name "cloud". No external organization, hostname, or certificate relationships were identified.
Historical Observations:
Eighteen total observations recorded. Notable entries include:
- 2026-08-13: Threat indicators detected with pulse count of 1 (confidence: 0.75)
- 2026-08-06: Geolocation signal pointing to Boston (BOS) with confidence 0.7
Recommended Actions:
No specific firewall rules or mitigation recommendations were generated. The IP maintains a low-risk profile overall, though the historical threat indicator warrants continued monitoring.
SOC Analyst Notes:
This IP represents Microsoft Azure cloud infrastructure with a low overall risk score. While current indicators show minimal threat activity, the presence of historical threat signals suggests periodic monitoring is recommended. No immediate blocking action is advised based on current profile data.
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.119.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 | 35% | 2 | 3 |
| routing | 17% | 1 | 1 |
| services | 24% | 2 | 2 |
| ownership | 35% | 2 | 3 |
| reputation | 17% | 1 | 2 |
| geolocation | 17% | 1 | 1 |
| Overall | 24% | 9 | 12 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-08-03 05:13:46 UTC |
| Last Seen | 2026-08-13 04:35:43 UTC |
| Profile Built | 2026-08-13 04:46:11 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 19 |
Full dossier details are available via our API.