Network Diagnostics and More
Checking test service
Menu
Tool guide limitationsGuides explain the intended workflow but cannot cover every device, provider or operating condition.

Interfaces and external services can change. Follow the current on-screen controls, check dates and vendor documentation, and verify important results independently before acting on them.

Important: Do not rely on this result alone for purchasing, configuration, security, safety, compliance, contractual or fault-diagnosis decisions. Results can be incomplete, delayed, misleading or wrong. Verify important findings with the relevant provider, manufacturer documentation and an appropriate independent test or qualified professional.

← All tool guides

Technical diagnostics

Public IP Intelligence guide

Review public registration, routing, ASN, RPKI route-origin state, provider, reverse-DNS and approximate-location evidence for a public IP address.

Open Public IP Intelligence

What you need

  • Public IPv4 or IPv6 address, or Check my public IP

How to use it

  1. 1Enter a public IP address or detect the current connection address.
  2. 2Run the intelligence lookup.
  3. 3Review each fact alongside its source and limitation.
  4. 4Export CSV or JSON if required.

Understanding the results

  • The registered organisation, announcing network and customer-facing ISP can be different organisations.
  • RPKI valid means the observed origin is covered by a matching authorisation; invalid or unknown requires operator investigation but does not by itself prove malicious routing.
  • Location is an estimate for a network range and is never proof of a device or person's physical position.

Recommended next actions

  • Confirm material ownership, route-origin or abuse findings with the relevant Regional Internet Registry and network operator.

Common problems

  • Registry redaction, shared hosting, VPNs, carrier-grade NAT, mobile routing and free-source rate limits can reduce detail.

Privacy and security

  • The submitted public IP is sent to the hosted checker and named public registry, routing and geolocation services; it is not included in analytics or saved by the page.

Worked example

Scenario
Investigating a public resolver
Example input
1.1.1.1
How to read it
The tool separates registration, routed prefix, origin ASN, RPKI state, provider and approximate-location evidence and identifies the source of each fact.

Limitations

  • The result does not establish identity, device ownership or a precise physical location.
  • Free approximate-location evidence may be unavailable while authoritative registry and routing evidence still succeeds.

Do not rely on one result for a production, security, safety, purchasing or contractual decision. Verify important findings independently.