20.46.120.13
Threat Intelligence Briefing for IP 20.46.120.13/32
Summary:
The IP address 20.46.120.13/32 is associated with Microsoft Corporation (Microsoft Azure) and registered to AS8075. Geolocation data indicates it resides in Tokyo, Japan (35.68°N, 139.69°E). No threat indicators, malicious campaigns, or abuse reports are linked to this IP.
Key Findings:
1. Ownership & Network Role:
- Owned by Microsoft Corporation (AS8075).
- Classified as CloudCompute infrastructure (Microsoft Azure).
- No residential, mobile, or Tor network associations.
2. Threat Assessment:
- Low Risk (riskScore: 25).
- No malicious indicators (no malware, phishing, or exploitation activity).
- No DNS-based threats, spam, or blacklisted activity.
3. Geolocation & Stability:
- Located in Tokyo, Japan (JP).
- Stability Score: 0 (no observed instability).
- DNSSEC Valid: Confirmed.
4. Network Relationships:
- Linked to MSFT networks (Microsoft Azure).
- No sibling IPs or subnet abuse detected in the 20.46.120.13/24 subnet.
5. Behavioral & Technical Insights:
- No open ports, TLS certificates, or HTTP services detected.
- BGP Prefix: 20.40.0.0/13 (Microsoft Azure).
- Route Stability: Stable (no recent route changes).
Recommendations:
- No immediate security actions or firewall rules required.
- Monitor for unexpected behavior changes, as this IP is part of a cloud infrastructure.
- Cross-reference with internal assets to confirm expected traffic patterns.
Conclusion:
This IP is a legitimate Microsoft Azure asset with no signs of compromise. No actionable threats detected. Maintain standard monitoring practices for cloud infrastructure.
*Data sourced from IPDebrief threat intelligence platform.*
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
| SANs | None |
| Valid From | — |
| Valid Until | — |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 24% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 20% | 2 | 3 |
| reputation | 28% | 1 | 3 |
| geolocation | 33% | 2 | 3 |
| Overall | 21% | 10 | 16 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:04:08 UTC |
| Last Seen | 2026-06-27 03:47:08 UTC |
| Profile Built | 2026-06-27 21:53:50 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 24 |
Full dossier details are available via our API.