4.172.11.173
IP Address 4.172.11.173/32 was attributed to Microsoft Corporation under ASN 8075 within the 4.160.0.0/12 block. The profile classified the address as Microsoft Azure Cloud Compute infrastructure located in Toronto, Ontario, Canada, though TLS certificate data indicated a United States origin. Despite ownership by a major enterprise entity, the reputation assessment assigned a High Risk status with a risk score of 70.
Threat analysis indicated one DNSBL listing against 8 total lists, yet no specific threat indicators were recorded for known attacker or spam source activity. Control plane metrics showed mixed signals with low attribution confidence. The profile generated a recommendation to block traffic with critical severity based on the high risk score with strong threat evidence. Firewall rules were advised to drop inbound traffic from this IP. The data contained internal contradictions regarding geographic location and DNSBL counts versus threat listings.
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 | 4.160.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 | 40% (Fair) |
| SPF | 1/2 domains |
| DMARC | 2/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 | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | *.trouter.skype.comgo.trouter.io |
| Valid From | 2026-08-27T08:47:03+00:00 |
| Valid Until | 2027-02-23T08:47:03+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha384RSA |
| Validity Period | 180 days |
| Serial Number | 4100CA6DB6099A9A5F842F17DD000000CA6DB6 |
| Thumbprint | 995CE802F2CDA6979BAF057DDBB28DCC54C264CE |
🎯 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 | 13% | 1 | 1 |
| Overall | 21% | 9 | 14 |
| Data Coherence | Mixed Signals (68%) — 2 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
⚠ TLS certificate claims US but primary geo says CA
📅 Observation Timeline 🔄 Live
| First Seen | 2026-09-04 00:22:17 UTC |
| Last Seen | 2026-09-26 20:08:56 UTC |
| Profile Built | 2026-09-26 20:21:47 UTC |
| Data Freshness | Live |
| Signal Types | 23 |
| Total Observations | 33 |
Full dossier details are available via our API.