150.171.110.22
The IP address 150.171.110.22 was identified as Microsoft Azure infrastructure within the 150.171.0.0/16 block, attributed to Microsoft Corporation (ASN 8075) in Redmond, Washington. The profile indicated a low-risk reputation with a risk score of zero and zero blacklists. Network role analysis classified the address as cloud compute hosting web server services on ports 80 and 443, secured by a Microsoft TLS certificate for *.azureedge.net. Neighborhood data for the 150.171.110.22/24 subnet showed an abuse density of 0.0909 and a mostly clean classification with two threat siblings. Behavioral analysis recorded zero honeypot hits, WAF violations, or enumeration strikes. The intent was classified as legitimate infrastructure, and the recommendation was to allow traffic with an info-level severity due to the absence of significant risk indicators.
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 | 150.171.0.0/16 |
| RIR | APNIC |
| 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 | 0% (None) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Not signed |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Web Server |
| Network Tier | Hosting — Infrastructure provider without advanced routing |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| Closed Ports | 22, 25, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | *.azureedge.net |
| Valid From | 2026-08-28T04:41:19+00:00 |
| Valid Until | 2027-02-24T04:41:19+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha384ECDSA |
| Validity Period | 180 days |
| Serial Number | 61000533C46C550BDF05AF121D0000000533C4 |
| Thumbprint | 2B569D5A305178CD39CD44E3B028BA2E14DF8241 |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 27% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 33% | 2 | 4 |
| ownership | 27% | 2 | 3 |
| reputation | 13% | 1 | 2 |
| geolocation | 27% | 2 | 3 |
| Overall | 23% | 10 | 16 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-09-08 13:46:47 UTC |
| Last Seen | 2026-09-15 19:33:31 UTC |
| Profile Built | 2026-09-15 19:46:20 UTC |
| Data Freshness | Live |
| Signal Types | 24 |
| Total Observations | 29 |
Full dossier details are available via our API.