52.115.63.226
52.115.63.226 is an IPv4 address operated by Microsoft Azure (AS8075), with approximate network location Washington, United States. It belongs to datacenter or hosting infrastructure. As of November 9, 2026, IPDebrief rates it Low Risk (0/100); no anonymizing service was detected.
🏢 Ownership & Registration
| Registered holder | Microsoft Corporation |
| ASN | AS8075 |
| Network Name | MSFT |
| CIDR Block | 52.96.0.0/12 |
| RIR | ARIN |
| Network registration 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 Posture
Results describe the queried names. SPF, DMARC and CAA are domain policies, not requirements for every IP. DNSSEC here describes reverse DNS; inconclusive validation does not mean unsigned.
Not assessed: 0 conclusive IP DNS checks.
| spf | Not checked |
| dmarc | Not checked |
| fcrDns | Not checked |
| dnssec | Not checked |
| caa | Not checked |
☁️ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Web Server |
| Network Tier | Hosting — Infrastructure provider without advanced routing |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 443 | https | tcp | — |
| Closed Ports | 22, 25, 80, 3389, 8080, 8443 (1 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | tr.teams.microsoft.com*.tr.teams.microsoft.comturn.teams.microsoft.com*.turn.teams.microsoft.com*.relay.teams.microsoft.comaz.relay.teams.cloud.microsoft*.az.relay.teams.cloud.microsoft*.eu.az.relay.teams.cloud.microsoft*.am.az.relay.teams.cloud.microsoft*.apac.az.relay.teams.cloud.microsoft |
| Valid From | 2026-10-27T19:51:21+00:00 |
| Valid Until | 2027-02-04T18:51:21+00:00 |
| TLS Protocol | Tls12 |
| Cipher Suite | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
| Signature Algorithm | sha384RSA |
| Validity Period | 99 days |
🛡️ Public Network Snapshot
| Origin ASN | AS8075 |
| Network Prefix | 52.112.0.0/14 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 17% | 1 | 1 |
| routing | 17% | 1 | 1 |
| services | 35% | 2 | 3 |
| ownership | 35% | 2 | 3 |
| reputation | 17% | 1 | 1 |
| geolocation | 29% | 2 | 2 |
| Overall | 25% | 9 | 11 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-11-09 19:11:55 UTC |
| Last Seen | 2026-11-13 10:06:31 UTC |
| Profile Built | 2026-11-09 19:19:14 UTC |
| Data Freshness | Live |
| Signal Types | 14 |
| Total Observations | 14 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 52.115.63.226
Who owns the IP address 52.115.63.226?
52.115.63.226 is registered to Microsoft Corporation. The address falls within the 52.96.0.0/12 network block. Registration is held at ARIN.
Where is 52.115.63.226 located?
Geolocation data places 52.115.63.226 in Washington, VA, United States. The local time zone is America/New_York. IP geolocation is approximate, not a precise physical address. Registration country and certificate organization addresses do not establish service location.
Is 52.115.63.226 malicious or safe?
52.115.63.226 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.
What ports are open on 52.115.63.226?
Responsive ports observed on 52.115.63.226 include 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.
Is 52.115.63.226 a VPN, proxy, or data center address?
52.115.63.226 is classified as cloud infrastructure and hosting infrastructure based on network ownership and behavioural analysis.