Related Tools
How to Use
- 1Open the tool to see your user agent, platform, and browser details instantly.
- 2Click 'Detect My IP (WebRTC)' to gather IP address candidates from your browser.
- 3Review the detected IP addresses, connection type, and device information.
- 4Click 'Copy Details' to copy all visible values to your clipboard.
About What Is My IP + Device Info
What Is My IP + Device Info displays all the browser-visible metadata about your network connection and device in a single page. It shows WebRTC IP candidates (both local and public), your full user agent string, browser name and version, operating system and platform, screen resolution, preferred language, connection type (WiFi, cellular, ethernet), hardware concurrency (CPU core count), device memory estimate, and other details available through standard browser APIs. Everything loads instantly without requiring any server request or third-party lookup service.
IP addresses are the fundamental identifiers of internet communication, defined by the Internet Protocol (RFC 791 for IPv4, RFC 8200 for IPv6). Your public IP address — assigned by your Internet Service Provider (ISP) — is the address that websites, APIs, and online services see when you connect. Your local IP address (typically in the 192.168.x.x or 10.x.x.x range, as defined by RFC 1918) identifies your device within your home or office network. Understanding which IP your browser exposes is essential for network troubleshooting, privacy verification, development testing, and diagnosing NAT or firewall configurations.
The tool uses WebRTC (Web Real-Time Communication) to detect IP candidates. WebRTC is a browser API standardized by the W3C and designed for peer-to-peer communication (video calls, file sharing) that, as part of its ICE (Interactive Connectivity Establishment) connection setup process, gathers network interface information including IP addresses. This is the same mechanism used by video conferencing apps like Google Meet, Zoom, and Microsoft Teams to establish direct connections between participants. The ICE candidates collected during this process reveal both local and server-reflexive (public) addresses.
Developers and QA engineers use this tool to verify which IP and user agent their browser reports during testing — essential for debugging geolocation-based features, IP-based access controls, rate limiting, CDN configurations, and proxy setups. Network administrators use it to confirm that VPN tunnels are active and routing traffic correctly, or to verify that split-tunneling policies are working as intended. Security-conscious users check it to verify that their privacy tools (VPNs, proxies, Tor Browser) are masking their real IP address and not leaking information through WebRTC side channels.
The user agent string is a text identifier that your browser sends with every HTTP request, as specified in RFC 7231. It includes your browser name and version, operating system, device type, and rendering engine. Websites and APIs use it to serve compatible content, detect mobile devices, implement browser-specific workarounds, and analyze traffic patterns. Modern browsers are gradually reducing user agent detail for privacy — Chrome's User-Agent Client Hints initiative (documented on the Chromium project and MDN Web Docs) replaces the monolithic UA string with structured, opt-in headers — but the traditional user agent string remains widely used across the web.
All detection runs entirely client-side using standard browser APIs — WebRTC for IP detection, Navigator API for browser and platform details, Screen API for display information, and Network Information API for connection type. No data is sent to any external server or third-party service. Your IP address and device information are displayed only in your browser and never transmitted, logged, or stored in any form. This makes the tool fundamentally different from server-based IP checkers, which necessarily see and process your real IP address on their infrastructure.
Frequently Asked Questions
Will this always show my public IP address?
Not guaranteed. Browser privacy settings, VPN configurations, corporate firewalls, and browser extensions (like WebRTC leak blockers) may prevent WebRTC from exposing your public IP. In those cases, you may see only local network addresses (192.168.x.x, 10.x.x.x) or no IP candidates at all. This is actually a positive sign if you are using privacy tools designed to hide your IP.
What is a user agent string?
A user agent is a text string your browser sends with every HTTP request. It typically contains your browser name and version (e.g., Chrome/120), operating system (e.g., Windows NT 10.0), device type, and rendering engine (e.g., AppleWebKit). Websites use it to serve compatible content, and analytics tools use it to track browser and device statistics.
Is my data sent to any server?
No. All detection uses client-side browser APIs running entirely in your browser. Your IP address, user agent, screen resolution, and all other information are displayed locally on the page and never transmitted to any server, database, or third-party service.
Can I use this to check if my VPN is working?
Yes — this is one of the most common use cases. If your VPN is active and properly configured, the detected IP should show your VPN server's address rather than your real ISP-assigned IP. If you see your real IP despite having a VPN connected, your VPN may have a WebRTC leak — check your VPN client's settings for WebRTC leak protection.
What is the difference between local and public IP?
Your local (private) IP (e.g., 192.168.1.100 or 10.0.0.5) identifies your specific device within your home or office network — it is assigned by your router. Your public IP is the address visible to the internet, assigned by your ISP. Multiple devices on the same network share a single public IP through NAT (Network Address Translation). Websites see your public IP; devices on your local network see your local IP.
Why does this use WebRTC instead of a server-side IP lookup?
WebRTC allows IP detection entirely in the browser without sending any request to an external server. Server-side IP detection (like most 'what is my IP' services) requires your browser to make a request to a remote server, which then reads your IP from the connection. The WebRTC approach is more private because your data stays on your device, but it may not always reveal the public IP due to browser privacy restrictions.
What is the Network Information API?
The Network Information API is a browser API that provides information about your device's network connection, including the connection type (WiFi, cellular, ethernet), effective bandwidth estimate, and whether the connection is metered. It is supported in Chrome and Edge but not in Firefox or Safari. When available, this tool displays the connection type to help diagnose network-related issues.
Can websites track me using my IP address?
Your public IP address can reveal your approximate geographic location (city-level, not street address) and your ISP. Websites can use it for analytics, geolocation-based content, and fraud detection. However, IP addresses change periodically (especially on mobile networks) and are shared by multiple devices on the same network, so they are not a reliable unique identifier. For stronger privacy, use a VPN or Tor to mask your real IP.