20.210.91.220
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: 20.210.91.220
Date: 2026-06-08
---
**1. Core Profile**
- Risk Score: 25 (Low Risk)
- Ownership: Microsoft Corporation (ASN 8075)
- Geolocation: Tokyo, Japan (JP) | Latitude 35.68, Longitude 139.69
- Network Role: Microsoft Azure CloudCompute (Firewalled / No Services)
- Threat Indicators: No malicious activity detected (no indicators, blacklist entries, or campaigns).
---
**2. Observation History**
- Latest Observation (2026-05-31):
- Confirmed as Microsoft Azure infrastructure.
- No persistent malicious activity or ownership changes.
- Minimal risk score (0.13) with no DNSBL listings.
- Trend: Single observation with low confidence (0.21). No recent changes or anomalies.
---
**3. Relationships**
- Linked Entities:
- Directly tied to Microsoft Azure network (MSFT).
- No external hostnames, certificates, or subnets identified.
- Network Context: Part of a larger Microsoft Azure infrastructure block (20.192.0.0/10).
---
**4. Neighborhood Analysis**
- Subnet: 20.210.91.220/24
- Neighbor Count: 0 active IPs in subnet (no siblings or abuse density).
- Classification: Clean subnet with no reported threats.
---
**5. Recommendations**
- Monitor: Track for unexpected changes in ownership or service exposure.
- Verify: Confirm that this IP aligns with known Microsoft Azure infrastructure.
- No Action Required: No immediate mitigation needed due to low risk and no malicious indicators.
---
Source: IPDebrief Threat Intelligence Platform | Last Updated: 2026-06-08
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Microsoft Corporation |
| 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 | 60% (Good) |
| SPF | Present |
| DMARC | Present |
| 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 | 24% | 2 | 3 |
| ownership | 24% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 25% | 2 | 2 |
| Overall | 22% | 10 | 16 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Mixed Signals (68%) — 2 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
⚠ Geo sources disagree on country: JP, US
⚠ TLS certificate claims US but primary geo says JP
⚠ TLS certificate claims US but primary geo says JP
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-18 15:26:18 UTC |
| Last Seen | 2026-06-28 07:31:23 UTC |
| Profile Built | 2026-06-29 01:35:48 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 24 |
🔍 20 signal types · 24 observations collected
This report is generated from 20+ 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.