## IP Intelligence Briefing: 20.204.136.73/32
Classification: Microsoft Azure Infrastructure (Low Risk)
Date: [Current Date]
Analyst: IPDebrief Intelligence
---
Executive Summary
IP address 20.204.136.73/32 belongs to Microsoft Corporation (AS8075) and operates within the Microsoft Azure cloud infrastructure network (20.192.0.0/10). Current risk assessment indicates Low Risk (Score: 25). The IP is geolocated to Pune, Maharashtra, India, and presents as firewalled with no publicly accessible services. One elevated-risk neighbor (20.204.136.58, Risk Score: 65) detected in the /24 subnet warrants monitoring.
---
Ownership and Network Attribution
| Attribute | Value |
|---|---|
| Organization | Microsoft Corporation |
| ASN | AS8075 |
| Network Block | 20.192.0.0/10 |
| CIDR | 20.204.136.73/32 |
| RIR | ARIN |
| Registration | Enterprise cloud infrastructure |
Network Role: Microsoft Azure (Cloud Infrastructure)
---
Geolocation Data
| Field | Value |
|---|---|
| Country | India (IN) |
| Region | Maharashtra (MH) |
| City | Pune |
| Coordinates | 18.58°N, 73.92°E |
| Timezone | Asia/Kolkata |
| GeoSources | 1 (Consensus: True) |
---
Risk Assessment
Overall Risk Score: 25/100 (Low Risk)
Risk Breakdown:
- Provider Score: 0
- Authority Score: 0
- Stability Score: 0
Threat Indicators:
- Known Attacker: False
- Tor Exit Node: False
- Spam Source: False
- Blacklist Count: 0
- Pulsedive Risk: N/A
- DNSBL Listed: 1 of 8 total lists
Abuse Confidence: Not applicable (legitimate cloud infrastructure)
---
Technical Profile
DNS Resolution:
- PTR Hostnames: None
- Forward Resolution: Not confirmed
- Hosted Domains: 0
- SPF/DMARC Records: None detected
Services:
- Open Ports: None detected
- TLS Certificate: None
- HTTP Title: None
- Server Banner: None
- Service Purpose: Firewalled / No Services
Control Plane:
- RPKI State: Valid
- DNSSEC: Valid
- Route Stability: False
- Route Changes (30d): 0
- MOAS: False
---
Observation History (19 Signals)
Most Recent Activity (June 2026):
- Multiple geolocation sources confirming Pune, India location
- Threat indicators detected (Pulse Count: 2)
- Port scanning activity observed
- Operator Score: 0.1304 (Minimal)
- Data Sufficiency: 6 of 6 dimensions covered
Temporal Analysis:
- Ownership Changes: 0
- Threat Observation Count: 1
- Threat Persistence Days: 0
- Persistently Malicious: False
---
Neighborhood Analysis (20.204.136.0/24)
Subnet Classification: Mostly Clean
| Metric | Value |
|---|---|
| Abuse Density | 0 |
| Inherited Risk | 5 |
| Total Siblings | 2 |
| Active Siblings | 0 |
| Threat Siblings | 2 |
Elevated-Risk Neighbor Identified:
- IP: 20.204.136.58
- Risk Score: 65 (Medium-High)
- Authority Score: 50
- Recommendation: Monitor for lateral movement or coordinated activity
---
Relationship Graph
- Total Relationships: 12
- Type: Same Network (MSFT)
- Target: Microsoft Azure infrastructure
- Analysis: All relationships indicate legitimate Microsoft network associations; no external or suspicious entities detected.
---
Recommended Actions
SOC Analyst Guidance:
1. Block/Allow Decision: Monitor and allow with logging. This is legitimate Microsoft Azure infrastructure with low risk profile.
2. Firewall Rules: No immediate blocking required. Standard allow rules for Microsoft Azure traffic apply.
3. Monitoring Priority: Low to Medium due to:
- Elevated-risk neighbor (20.204.136.58) in same /24 subnet
- One DNSBL listing (investigate if traffic patterns change)
4. Correlation Points:
- Monitor for traffic patterns to/from 20.204.136.58
- Track any changes in risk score or service exposure
- Verify Azure service legitimacy if traffic appears anomalous
5. Investigative Notes:
- IP represents cloud infrastructure, not traditional server endpoint
- Firewalled state indicates minimal public-facing services
- Historical data shows consistent cloud infrastructure usage
---
Conclusion
IP 20.204.136.73/32 is classified as Microsoft Azure infrastructure with a Low Risk profile. The IP exhibits characteristics of legitimate cloud infrastructure with no active threat indicators. The presence of one elevated-risk neighbor in the same subnet warrants continued monitoring but does not indicate immediate threat. No blocking recommended; standard Azure traffic handling procedures apply.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
๐ข Ownership & Registration
| Organization | Microsoft Corporation |
| ASN | AS8075 |
| Network Name | MSFT |
| CIDR Block | 20.192.0.0/10 |
| RIR | ARIN |
| Country | United States |
| 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 | 27% | 2 | 3 |
| routing | 8% | 1 | 1 |
| services | 15% | 2 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 22% | 1 | 3 |
| geolocation | 19% | 2 | 2 |
| Overall | 20% | 10 | 14 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
๐ Observation Timeline ๐ Live
| First Seen | 2026-05-27 19:22:15 UTC |
| Last Seen | 2026-06-29 04:37:37 UTC |
| Profile Built | 2026-06-29 04:43:03 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 21 |
Full dossier details are available via our API.