IP tools for a clearer connection

Start with the question you need to answer. Each tool explains its source, result and limits.

Measured from your browser

See the exit IP used for different websites. Compare IPv4 and IPv6 exits, filter destinations and retry missing results.

Live provider query

Check two named threat feeds. See the evidence, its age and its limits before deciding what to investigate.

Live provider query

Review separately sourced network listings and exit observations. Understand what each result can and cannot establish.

Live provider query

Choose what to inspect. See each source, result and coverage limit in one place.

Live provider query

Check number formats, numbering regions and rule-based types. Your number stays in this tab.

Live provider query

Understand common patterns and estimated guessability. Analyze a candidate locally, with no password upload.

Calculated in your browser

Generate random IPv4 and IPv6 addresses in your browser. Choose a range, then copy a batch as text or JSON.

Measured from your browser

See what your browser reports about its settings, screen and graphics. Inspect locally and compare two snapshots.

Calculated in your browser

Create random passwords or word-based passphrases locally. Choose the requirements that fit your destination.

Calculated in your browser

Generate random numeric codes locally, with fixed length and leading zeros preserved.

Calculated in your browser

Read mail routes, timestamps and authentication claims with private, local analysis.

Live provider query

Inspect response headers and redirects, with probe locations and TLS verification results.

Calculated in your browser

Convert ranges, merge networks or split prefixes with exact IPv4 and IPv6 arithmetic.

Live provider query

Look up domain registration through RDAP. Read the registrar, dates, status, nameservers and privacy notices from the responsible registry.

Live provider query

Resolve a hostname to IPv4, IPv6 and CNAME records. Inspect each DNS response and source-linked CDN hints.

Live provider query

Check a public IPv4 address against two named mail blocklists, with source health checks and clear limits.

Measured from your browser

Measure download, upload, ping and jitter with OpenSpeedTest. Start the test below to check this browser’s connection.

Remote diagnostics

Check one TCP port or a fixed preset from our server. See connection success, refusal, timeout and probe restrictions.

Remote diagnostics

Check a public target from a remote probe, or measure this browser’s HTTP timing to this site.

Remote diagnostics

Inspect route hops to a public target from a named remote Globalping probe, including missing replies.

Measured from your browser

Understand different IP addresses across websites: separate IPv4 from IPv6, investigate proxy routing and learn how to verify observed exits with the outbound IP tool.

Live provider query

Find approximate location, network and registration evidence for a public address. Private addresses are classified locally.

Measured from your browser

Check whether this browser can reach separate IPv4-only and IPv6-only endpoints, and see the public address used for each.

Measured from your browser

See the addresses this browser exposes through WebRTC and compare public candidates with fresh HTTP observations. A difference needs investigation; this is not a VPN safety certificate.

Live provider query

Find DNS records, compare named resolvers and understand the response.

Live provider query

Find the PTR records published for a public IPv4 or IPv6 address. A PTR record is not a list of every website on that server.

Live provider query

Read internet number registration data using RDAP, the structured successor to traditional WHOIS.

Live provider query

Find the origin networks observed for a public IP, or look up an autonomous system number and its holder. Routing observations are not subscriber identities.

Calculated in your browser

Calculate IPv4 and IPv6 network ranges, address counts and masks. Everything is calculated in your browser.

Find the right check for the job

Choose IP tools by the question

These IP tools cover browser connections, public network records, and local calculations. Start with the result you need rather than running every test in the directory.

If a support form asks for your current public address, open the homepage. If you already have an address from a log or message, IP lookup provides location estimates and network registration context. These are different tasks: looking up an entered address does not show that your device currently uses it.

For unexpected routing, outbound IP detection compares what named destinations observe from this browser. The IPv6 test instead checks separate IPv4-only and IPv6-only endpoints. Use the first to investigate destination differences and the second to investigate protocol reachability.

The cards above describe the remaining operations and their inputs. Before starting, check whether the measurement runs locally, in your browser, on our server, or at a remote probe. A remote ping cannot reproduce your own Wi-Fi path, and a subnet calculation does not discover connected devices.

Read the source behind network tools

A connection observation, registry record, and location estimate answer different questions. A registered organization is not necessarily the person using an address, and a city marker is not an exact physical location. Keep the field name and source with any value you quote.

Read unavailable and incomplete states as part of the result. A timed-out request does not by itself establish an outage. An undetected protocol is not proof that the device lacks support. Matching exit addresses cover the destinations that responded; they cannot establish every application's route or certify VPN safety.

Compare the same address family, destination, and measurement origin. Otherwise, two apparently conflicting results may simply describe different connections.

Build a network troubleshooting report

Record the expected behavior, actual failure, active network, VPN state, and observation time. Run the smallest relevant check, change one condition, then repeat it. Save both results so you can explain what changed.

For incoming IPv4 problems, follow the CGNAT checks before assuming a router rule is enough. For other tasks, use each tool's explanation below its interface. The methodology and data sources describe measurement boundaries and provider roles.

Review copied reports before sharing. Include the query, source, timestamp, and error needed to reproduce the issue; remove credentials and unrelated personal details.

Choosing and using IP tools

Which IP tools should I use first for a connection problem?

Start with the symptom and select the smallest observation that can distinguish its likely causes. Copy the current public address for a support request, compare named browser destinations for an unexpected exit, or inspect a particular DNS record for a naming problem. Network tools become easier to interpret when you know where the request originates. Record a baseline before changing a VPN, router setting or network, then repeat the same operation under the new condition.

Check the current public address

Compare website exits

Which check helps when support asks for my public address?

Use the homepage while connected through the network and browser involved in the problem. A public observation describes the source visible to the receiving endpoint; it may belong to a shared gateway, VPN or relay. Your router and operating system can also show local addresses used within a private network. Ask which value support needs before copying it. Looking up an arbitrary address from an old log does not establish that your current browser uses it.

Find the right address for the task

How do lookup, registration and reverse DNS network tools differ?

An entered public address can be associated with an approximate location, an allocated range, or a published PTR hostname. Those are separate records with separate sources. Registration identifies an administrative object, while reverse DNS returns a name chosen by the address operator. Neither supplies a reliable household address or a complete list of hosted websites. Read the relevant field label and source before treating two results as contradictory.

IP lookup

Read registration records

Read PTR records

Should I investigate DNS or connectivity when a website fails?

First preserve the exact error and determine whether the problem affects one name, one browser or several destinations. A published A or AAAA record establishes an answer from the selected resolver, without proving that the application responds. A remote connection result adds a different observation from a different origin. Use network troubleshooting to separate those layers instead of assuming a successful lookup proves the whole path works. Keep the selected record type and resolver in the report.

Inspect DNS records

Inspect remote reply evidence

How can I tell where these network tools run?

Read the operation description before submitting a target. Some calculations and text analysis run locally in the tab. Other checks contact endpoints directly from your browser, use the site server, or request a named remote Globalping probe. These origins observe different paths. A remote traceroute does not reproduce the route from your laptop, and a local range calculation sends no discovery packets. The source, protocol and time should travel with any copied result.

Read the measurement methods

Can matching exit results prove that my VPN covers every app?

Matching observations cover the successful requests and address families tested in that run. Another application, destination or protocol may use a different rule. Missing results reduce coverage rather than counting as matches. For useful network troubleshooting, repeat the same checks before and after one deliberate configuration change, preserve the destination names, and compare IPv4 separately from IPv6. A browser report is evidence about those requests, not a general anonymity certificate.

Check destination-specific exits

Inspect browser ICE evidence

What should I do when IP tools return an empty or failed result?

Keep the actual status, provider and time. A timeout, unsupported runtime, missing record and successful negative answer have different meanings. Repeating once after a temporary interruption may help; repeated blind requests can add noise or trigger limits. These IP tools preserve unavailable states so you can decide whether to investigate the target, your path or the measurement service. A missing field should stay missing until a relevant source provides it.

Check source roles and availability

What information belongs in a useful support report?

Include the affected operation, input format, expected behavior, actual error, observation time, address family, active network and relevant VPN state. Keep the source URL or probe label when it explains the observation point. Compare a baseline with a single changed condition rather than sending many unrelated screenshots. Review copied output for passwords, tokens, internal names and unrelated personal information. This gives support a repeatable question without turning a diagnostic report into an unnecessary disclosure.

Find a relevant walkthrough