Refentra
English
Go to tools

Public IP registry and routing lookup

Query the RDAP registry of the regional registry chosen by IANA and a RIPE RIS routing sample for a public IP you enter explicitly.

  • Named network services
  • Run explicit query
  • Observed result

Query the RDAP registry of the regional registry chosen by IANA and a RIPE RIS routing sample for a public IP you enter explicitly. Allocation and routing may differ. Organization and country fields are registry metadata, never a person or a precise location.

No result yet

Profile and limits

15s + ≤250ms cleanup wait; query;≤20 subqueries/≤64 cryptographic operations;2MiB received;65535B DNS packet/256 records/16 compression jumps;RDAP256KiB/depth24;TLS256KiB/8×64KiB certificates;2MiB output. Unsupported/missing proofs stay unknown; no automatic retries.

How to use

  1. Enter an ASCII public domain (Punycode for IDNs) or public IP; select the service/type.
  2. Review the named recipients and privacy policies, then explicitly consent and run.
  3. Inspect the timestamped fields/unknown states. Save reports locally if needed. Editing or Cancel terminates the query; Reset clears local state.

How to use

  1. 1. Public IP address

    Enter one public IPv4 or IPv6 address, not a domain or a type of service. Live requests remain gated. Before you choose Run, read the named RIR RDAP/RIPE recipients and the privacy notice.

  2. 2. Run explicit query

    8.8.8.8 only illustrates the syntax of a public IP. It is not a result observed here. If it is enabled, compare the allocation block that comes back with the RIS prefix/ASN observed independently.

  3. 3. Observed result

    Check the observation timestamp, the source and the UNKNOWN fields. Save locally. Edit or Cancel ends the request. There is no automatic retry and no silent substitution of providers.

Profile and limits

What does this result mean?

RDAP allocation and RIPE RIS routing are different observations and may disagree. Organization and country fields don't identify a person or a precise location.

How do I resolve rejected or missing input?

Private and reserved targets are rejected. Results from a provider that are missing, denied or unsupported stay unknown. That is not proof that the address or the route does not exist.

What are the limits of this tool?

Currently gated, so don't count on this endpoint being available. When you authorize Run, the backend sends the public IP to the services shown, and their policies apply. There is no zero-retention claim.