Your IP: 216.73.217.135
๐ค Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 20.78.153.84
Date: 2026-06-15
---
**1. Core Profile**
- Risk Score: 25 (Low Risk)
- Ownership: Microsoft Corporation (ASN 8075)
- Geolocation: Osaka, Japan (JP) | Latitude 34.69, Longitude 135.5
- Network Role: Microsoft Azure Cloud Compute (Firewalled / No Services)
- Threat Indicators: No malicious activity detected. No DNS, TLS, or service anomalies.
---
**2. Observation History**
- Latest Signal (June 15, 2026): Minimal risk (confidence 0.30).
- Historical Trends:
- Single observation recorded (June 8, 2026).
- No persistent malicious activity or network changes.
- DNSSEC valid, no route instability or abuse flags.
---
**3. Relationships**
- Linked Entities:
- Microsoft's network (MSFT) | Same Network (11 entries).
- Implication: Part of Microsoft's infrastructure, likely a cloud instance or internal service.
---
**4. Neighborhood Analysis**
- Subnet: 20.78.153.84/24
- Neighbor Count: 0 (no sibling IPs reported).
- Abuse Density: 0 (clean subnet).
---
**5. Threat Assessment**
- No Malicious Indicators: No blacklists, campaigns, or DNS anomalies.
- Legitimate Activity: Microsoft-owned IP with no suspicious behavior.
- Cloud Context: Azure infrastructure IP (firewalled, no open services).
---
**6. Recommendations**
- Monitoring: No action required. Monitor for unexpected traffic patterns.
- Context: Trust as Microsoft infrastructure, but verify against internal allowlists.
- Neighbors: No associated risky neighbors; subnet is clean.
Conclusion: 20.78.153.84 is a legitimate Microsoft Azure IP with no threat indicators. No further action needed unless linked to suspicious activity in other contexts.
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 | 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 | 26% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 15% | 2 | 2 |
| ownership | 20% | 2 | 3 |
| reputation | 28% | 1 | 3 |
| geolocation | 25% | 2 | 2 |
| Overall | 21% | 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-18 15:26:19 UTC |
| Last Seen | 2026-06-28 07:32:13 UTC |
| Profile Built | 2026-06-29 01:38:04 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.