Location, ISP, ASN, timezone and coordinates for 48.239.135.35.
This is Microsoft Corporation (United States New Jersey Newark, AS8075), a datacenter / cloud address.
Datacenter addresses are used for server hosting, API calls and automated crawling — they do not represent real end-users. Evaluate using request frequency, user-agent and behavioral chains; do not allow or block based on IP ownership alone.
Independent offline databases (ip2region vs GeoLite2) may disagree on an IP's location; both are third-party judgments for reference only. The page's primary location prefers ip2region.
Data source: ip2region+GeoLite2 (local offline databases)
Security Assessment & Risk
Local Weather
Loading weather…
IP History Archive
- 2026-09-16 英国 新泽西州 Newark Microsoft Corporation · AS8075 Datacenter / Cloud
Deep Analysis
AS8075 (Microsoft Corporation) manages the 48.239.0.0/16 prefix block (approximately 65536 addresses) in the Datacenter / Cloud category. Microsoft Azure / Microsoft 365 infrastructure, the world's second-largest cloud. The IP 48.239.135.35 resides in United States New Jersey Newark (timezone Europe/London); its position within this block determines routing behavior and connectivity characteristics.
No reverse DNS (PTR) record is configured, which is common for dynamically assigned or CGNAT'd addresses but limits reverse verification capability. Datacenter IPs generally have properly configured PTR records; the absence here is unusual and may indicate a legacy allocation or misconfiguration.
Based on local classification and Spamhaus real-time reputation, no blacklist entries detected, associated risks: datacenter. The Cloud server / datacenter category indicates this IP is part of normal Datacenter / Cloud infrastructure and carries low inherent risk. As a datacenter address, risk-control focus should be on request patterns (user-agent, frequency, behavior chains) rather than the IP alone.
Recommendation: 48.239.135.35 is a datacenter/cloud IP — it may host legitimate services (APIs, CDNs, bots) or serve as an attack vector. Evaluate each request context: allow known API integrations, challenge or block unknown automated traffic, and never trust the client-reported IP for geo-based decisions.
Datacenter IPs are frequently used for legitimate API integrations, automated monitoring and infrastructure tasks — evaluate each request context before blocking. If you need to distinguish automation from real-user traffic, focus on request headers (User-Agent, Accept) and behavioral patterns rather than IP reputation alone.
Online Tools
Port Scan
Network Diagnostics
Supports connectivity testing, port scanning and DNS latency comparison.
Open Tool →WHOIS Info
Querying WHOIS registration info...
Location Map
Map location unavailable (limited IP geolocation accuracy)