104.43.251.173
IP Intelligence Briefing: 104.43.251.173
Date: 2026-06-08
---
**1. Core Profile**
- Risk Score: Low Risk (25/100)
- Ownership: Microsoft Corporation (ASN 8075)
- Geolocation:
- City: Des Moines, IA, US
- Latitude: 41.6015 | Longitude: -93.6127
- Accuracy: 830 km (low confidence due to RTT anomaly)
- Network Role: Microsoft Azure CloudCompute (firewalled, no services detected)
- Threat Indicators: No malicious activity, spam, or known attacker associations.
---
**2. Observation History**
- Latest Activity: 2026-06-08
- Key Signals:
- Geolocation: Confirmed as Des Moines, IA, but RTT (53ms) contradicts 7,066 km distance (potential spoofing).
- Network Classification: Stable Azure infrastructure (no route changes).
- Operator Score: Minimal risk (0.13).
- DNSSEC: Validated.
---
**3. Relationships**
- Linked Entities:
- Microsoft Network: Repeatedly associated with "MSFT" network (BGP prefix 104.40.0.0/13).
- No Other Associations: No DNS, domains, or certificates linked.
---
**4. Neighborhood Analysis**
- Subnet: 104.43.251.173/24
- Neighbor Count: 0 active IPs (isolated host).
- Abuse Density: 0% (clean subnet).
---
**5. Actionable Insights**
- No Immediate Threat: Low-risk IP with no malicious indicators.
- Monitor Geolocation Anomalies: Investigate RTT discrepancies if suspicious activity arises.
- Cloud Infrastructure: Likely a legitimate Azure VM; no need for blocking unless new threats emerge.
- Subnet Isolation: No neighboring IPs to monitor for lateral movement.
Recommendation: Maintain current monitoring posture. No firewall rules or mitigation actions required at this time.
---
Source: 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 | 27% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 15% | 2 | 2 |
| ownership | 24% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 33% | 2 | 3 |
| Overall | 22% | 10 | 16 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-19 09:36:02 UTC |
| Last Seen | 2026-06-28 08:39:21 UTC |
| Profile Built | 2026-06-29 02:45:24 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 22 |
Full dossier details are available via our API.