Your IP: 216.73.216.123
π€ Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 172.191.151.49/32
*Generated via IPDebrief Threat Intelligence Platform*
---
**1. Core Profile**
- Risk Score: 80 (High Risk)
- Ownership: Registered to Divya Quamara (Microsoft Azure infrastructure)
- Geolocation: Washington, VA, US (cloud-hosted, no precise coordinates)
- Network Role: Microsoft Azure CloudCompute instance (firewalled, no services exposed)
- Threat Indicators: No malicious activity detected (clean subnet, no abuse signals).
---
**2. Observation History (30-Day Trend)**
- No persistent threats or malicious campaigns observed.
- Stability: Route stability score indicates intermittent routing changes (0/10).
- Historical signals show no DNS anomalies, open ports, or TLS certificate issues.
---
**3. Relationships & Network Context**
- Linked Entities:
- Subnet: `172.191.151.49/24` (clean, no abuse density).
- Cloud Provider: Microsoft Azure (cloud-hosted, infrastructure-type: CloudCompute).
- Neighbors: No sibling IPs detected in the /24 subnet.
---
**4. Threat & Risk Analysis**
- No Malicious Indicators: No malware, phishing, or C2 activity detected.
- DNS & Services: No open ports, TLS certs, or HTTP banners observed.
- Abuse Risk: Low (abuse density: 0).
---
**5. Recommended Actions**
- Monitor: Track routing stability and cloud infrastructure changes.
- No Blocking Required: No immediate threat to network defenses.
- Investigate: Verify ownership legitimacy if unusual activity emerges.
---
*End of Briefing*
*Generated by IPDebrief Threat Intelligence Platform*
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.191.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
No certificate
Issued by β
N/A
| 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 | 13% | 1 | 1 |
| services | 19% | 2 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 15% | 1 | 2 |
| geolocation | 19% | 2 | 2 |
| Overall | 21% | 10 | 13 |
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-06-01 11:44:00 UTC |
| Last Seen | 2026-06-21 07:24:20 UTC |
| Profile Built | 2026-06-21 07:30:03 UTC |
| Data Freshness | Live |
| Signal Types | 17 |
| Total Observations | 19 |
π 17 signal types Β· 19 observations collected
This report is generated from 17+ 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.
Full dossier details are available via our API.
βΉοΈ 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.