52.123.202.22
The IP address 52.123.202.22/32 was attributed to Microsoft Corporation (ASN 8075) within the 52.120.0.0/14 block. The asset functioned as a cloud compute web server, listening on ports 80 and 443 with TLS certificates issued for *.azureedge.net. Geolocation data indicated Redmond, Washington, United States, though RTT measurements contradicted the physical distance associated with the claimed location.
Threat analysis revealed no known campaigns, blacklists, or active attacker indicators. The address maintained a Low Risk reputation score of 20. Behavioral analysis showed no honeypot hits or enumeration strikes. Despite the low risk classification, signal contradictions regarding geolocation and data coherence were present. The recommendation was to monitor the address for changes due to these inconsistencies.
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 | 52.120.0.0/14 |
| 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 | 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:21+00:00 |
| Valid Until | 2027-02-24T04:41:21+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha384RSA |
| Validity Period | 180 days |
| Serial Number | 4900C057996847873E4B88AD15000000C05799 |
| Thumbprint | B635D5853C040E364FC761D8EE823253C8782AAF |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 50% | 2 | 3 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 25% | 1 | 1 |
| Overall | 20% | 5 | 6 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-09-09 18:48:19 UTC |
| Last Seen | 2026-09-09 18:48:19 UTC |
| Profile Built | 2026-09-09 19:05:49 UTC |
| Data Freshness | Live |
| Signal Types | 22 |
| Total Observations | 22 |
Full dossier details are available via our API.