172.213.217.88
IP Intelligence Dossier
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.213.217.88
Date: 2026-06-13
---
**1. Core Profile**
- Risk Score: 25 (Low Risk)
- Provider: Microsoft Azure (Cloud Infrastructure)
- Ownership: Registered to Divya Quamara (ASN 8075).
- Geolocation: Milan, Lombardy, Italy (45.46°N, 9.19°E).
- Network Role: Cloud-hosted, no public services detected (firewalled).
- Threat Indicators: No malicious activity, spam, or known attacker associations.
---
**2. Observation History**
- Last Seen: 2026-06-13 (1 day ago).
- Signals:
- Classified as CloudCompute (Microsoft Azure).
- Operator score: Minimal (0.13).
- DNSSEC valid, no DNSBL listings.
- Consistency: Single observation; no historical trends.
---
**3. Relationships**
- Linked Entities:
- Subnet: 172.213.217.88/24 (Azure infrastructure).
- No direct connections to known malicious networks, organizations, or domains.
---
**4. Neighborhood Analysis**
- Subnet: 172.213.217.88/24.
- Abuse Density: 0% (clean subnet).
- Neighbors: No active sibling IPs detected.
---
**5. Recommendations**
- Monitoring: Track for unexpected geolocation changes or service exposure.
- Firewall: Allow traffic to Azure-managed IPs (if necessary), but restrict non-essential access.
- Verification: Confirm ownership with Divya Quamara or Azure support if suspicious activity arises.
Conclusion: This IP is part of Microsoft Azure’s infrastructure in Milan, Italy. No current threats detected. Low-risk, but monitor for anomalies.
---
*Generated via IPDebrief intelligence tools. Data as of 2026-06-13.*
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 | 25% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 24% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 25% | 2 | 2 |
| Overall | 20% | 10 | 15 |
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-07 23:03:54 UTC |
| Last Seen | 2026-06-27 02:00:03 UTC |
| Profile Built | 2026-06-27 20:06:19 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 23 |
🔍 18 signal types · 23 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.