IP Intelligence Briefing: 172.215.231.147/32
Date: 2026-06-13
---
**1. Core Profile**
- Risk Score: Low (25/100) | Provider Score: 0 | Authority Score: 0 | Stability Score: 0
- Ownership:
- ASN: 8075 (Microsoft Azure)
- Organization: Divya Quamara
- Network: `cloud` (ARIN-registered)
- Geolocation:
- Country: United States (US) | Region: Washington (WA) | City: Redmond
- Network Role:
- Infrastructure: Microsoft Azure CloudCompute | Hosting: Yes | Cloud: Yes
- Threat Indicators:
- No malicious activity detected (no blacklists, spam, or known attacker campaigns).
- No open ports, TLS certificates, or DNS records linked to threats.
---
**2. Observation History**
- Latest Data (2026-06-13):
- Registered to Divya Quamara (ARIN) in Redmond, WA, US.
- Operator Risk: Minimal (0.1304 score).
- Network Stability: No recent route changes; BGP prefix `172.208.0.0/13` confirmed.
- Historical Trends:
- No persistent malicious activity or ownership changes observed.
- Threat observation count: 0.
---
**3. Relationships**
- Network Affiliation:
- Linked to the "cloud" network (Microsoft Azure infrastructure).
- DNS/Services:
- No PTR records, open ports, or TLS certificates detected.
- No email authentication (SPF/DKIM) or domain associations.
---
**4. Neighborhood Analysis**
- Subnet: `172.215.231.147/24`
- Neighbor Activity:
- 0 active IPs in the subnet.
- Abuse Density: 0% (no malicious neighbors).
- Subnet Classification:
- No inherited risk or threat indicators from surrounding IPs.
---
**5. Actionable Insights**
- Lethal Risk: Low. No indicators of compromise (IOC) or malicious behavior.
- Monitoring Recommendations:
- Track for unexpected ownership changes or new service exposure (e.g., open ports).
- Verify Azure cloud resource compliance with organizational security policies.
- Mitigation:
- No immediate firewall rules or blocking required.
---
Conclusion:
This IP is part of Microsoft Azureβs cloud infrastructure, registered to Divya Quamara. It shows no signs of malicious activity, with low risk scores and no threat indicators. While the subnet has no malicious neighbors, its isolated nature (0 active IPs) suggests it may be a new or underutilized resource. Continue monitoring for anomalies.
Tools Used: `ipdebrief_profile`, `ipdebrief_history`, `ipdebrief_relationships`, `ipdebrief_neighbors`.
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 | 172.215.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 | |||
| 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 | 32% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 30% | 2 | 3 |
| reputation | 28% | 1 | 3 |
| geolocation | 30% | 2 | 3 |
| Overall | 24% | 9 | 14 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-06-07 07:49:25 UTC |
| Last Seen | 2026-06-21 13:39:34 UTC |
| Profile Built | 2026-06-21 13:47:03 UTC |
| Data Freshness | Live |
| Signal Types | 17 |
| Total Observations | 19 |
Full dossier details are available via our API.