52.111.229.36
Intelligence Briefing: 52.111.229.36/32
The IP address 52.111.229.36/32 was assessed as Low Risk with a reputation score of 25. Ownership records assigned the address to Microsoft Corporation (ASN 8075) within the 52.96.0.0/12 block. Geolocation data placed the endpoint in Washington, Virginia, United States. Network analysis identified open ports 80 (HTTP) and 443 (HTTPS), with TLS certificate validation confirming the domain external.omex.office.net. Threat intelligence feeds detected no malicious indicators, the address was not listed on any blacklists, and it was not associated with known attack campaigns. Infrastructure profiling classified the asset as Microsoft Azure cloud compute hosting a web server. No defensive action was warranted based on the profile data.
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.96.0.0/12 |
| 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 | 0/2 domains |
| DMARC | 0/2 domains |
| FCrDNS | Not verified |
| DNSSEC | Not signed |
| CAA | Not configured |
| Domains Checked | 2 domains |
☁️ 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 | Microsoft-Azure-Application-Gateway/v2 |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | external.omex.office.net*.external.omex.office.net |
| Valid From | 2026-08-29T11:14:13+00:00 |
| Valid Until | 2027-02-25T11:14:13+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha384RSA |
| Validity Period | 180 days |
| Serial Number | 5500CA68C06DF0CF678C1D7589000000CA68C0 |
| Thumbprint | EEFC3C2B8BE231C5905C49408AD3CEF8FA21C623 |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 43% | 2 | 5 |
| routing | 13% | 1 | 1 |
| services | 33% | 2 | 4 |
| ownership | 27% | 2 | 3 |
| reputation | 13% | 1 | 2 |
| geolocation | 33% | 2 | 4 |
| Overall | 27% | 10 | 19 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-08-29 00:59:42 UTC |
| Last Seen | 2026-09-27 07:02:17 UTC |
| Profile Built | 2026-09-27 07:11:15 UTC |
| Data Freshness | Live |
| Signal Types | 23 |
| Total Observations | 39 |
Full dossier details are available via our API.