134.33.185.96
IP address 134.33.185.96/32 resolved as a Microsoft Azure cloud compute server within the 134.33.128.0/17 CIDR block. The host operated Microsoft-IIS/10.0 on ports 80 and 443 with HTTP/2 enabled, returning a 403 status code during probes. The TLS certificate identified the subject as fe2.update.microsoft.com under Microsoft Update Secure Server CA 2.1. Risk assessment assigned a Low Risk score of 25 with zero blacklist entries and no association with known campaigns. However, geolocation validation flagged a contradiction between the reported Boston, US location and measured Round-Trip Time physics, indicating a 6380km distance against a 23ms latency. The immediate subnet classification remained clean with zero abuse density. Intelligence analysts recommended monitoring the asset due to signal contradictions despite the absence of active malicious behavior.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Divya Quamara |
| ASN | AS8075 |
| Network Name | cloud |
| CIDR Block | 134.33.128.0/17 |
| RIR | ARIN |
| Country | US |
| 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 | 40% (Fair) |
| SPF | Present |
| DMARC | Present |
| 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 | Microsoft-IIS/10.0 |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | fe2.update.microsoft.com |
| Valid From | 2026-01-22T20:47:39+00:00 |
| Valid Until | 2027-01-22T20:47:39+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 365 days |
| Serial Number | 330000028D431F2E04AD2C43C900000000028D |
| Thumbprint | FEAF9A057ECBDE927A412A3049696E740E6A8E1D |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 33% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 27% | 2 | 3 |
| ownership | 27% | 2 | 3 |
| reputation | 13% | 1 | 2 |
| geolocation | 19% | 2 | 2 |
| Overall | 22% | 10 | 15 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-09-01 10:18:43 UTC |
| Last Seen | 2026-09-20 20:41:48 UTC |
| Profile Built | 2026-09-20 20:57:14 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 29 |
Full dossier details are available via our API.