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.212.190.121
Date: 2026-06-10
---
**1. Core Profile**
- Risk Score: 50 (Moderate Risk)
- Provider: Microsoft Azure (CloudCompute)
- Ownership: Divya Quamara (AS8075)
- Geolocation: Des Moines, IA, US (High confidence via multi-signal inference)
- Network Role: Cloud-hosted infrastructure (no open services detected)
- Threat Indicators: No malicious activity, no DNS/IP abuse, no blacklist entries.
---
**2. Observation History**
- Geolocation Validity: Confirmed via 3 signals (accuracy: ±150km).
- Threat Signals: No abuse or malicious activity observed in 30-day history.
- Subnet Stability: Subnet (172.212.190.0/24) has 0.33 abuse density (mostly clean).
---
**3. Relationships**
- Connected Entities:
- Linked to Microsoft Azure cloud networks.
- No known malicious relationships or campaigns.
- DNS: No PTR records or domain associations.
---
**4. Neighborhood Analysis**
- Subnet: 172.212.190.0/24
- Neighbors:
- 172.212.190.20 (risk: 25)
- 172.212.190.85 (risk: 25)
- Abuse Density: Low (0.33). No high-risk siblings.
---
**5. Recommendations**
- Monitor: Track for unexpected service changes or new threat signals.
- Firewall: No immediate blocking required (moderate risk, no malicious activity).
- Validation: ICMP validation failed; confirm network access rules for accuracy.
---
Conclusion: This IP is a legitimate Microsoft Azure cloud instance with no current threat indicators. Moderate risk is likely due to cloud infrastructure characteristics. No immediate action required, but ongoing monitoring is advised.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | Divya Quamara |
| ASN | AS8075 |
| Network Name | β |
| CIDR Block | β |
| RIR | ARIN |
| Country | β |
| 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 | 30% | 2 | 3 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 20% | 2 | 3 |
| reputation | 22% | 1 | 2 |
| geolocation | 33% | 2 | 3 |
| Overall | 21% | 10 | 14 |
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-05-23 00:18:42 UTC |
| Last Seen | 2026-06-28 20:11:41 UTC |
| Profile Built | 2026-06-29 08:15:29 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 21 |
π 18 signal types Β· 21 observations collected
This report is generated from 18+ 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.