WHOIS Lookup

A validated WHOIS request for example.com.

How it works

• Validate the domain (or public IP) and reject private/internal targets.
• Ask the platform API, which queries the configured WHOIS/RDAP provider.
• Normalize registrar, status, dates, nameservers and public organization fields.

• Registration records are dated by the registry and are not live DNS data.

Methodology

1. Validate the target as a registrable domain or public IP and reject internal/private targets.
2. Query the deployment's configured WHOIS/RDAP provider with the validated target only.
3. Normalize the registration fields and expose only publicly available data.

Time model

• Time source: UTC.
• Timezone: The registration record is fetched at request time and its dates are registry timestamps, not browser-local times.
• Locale: Dates are ISO-8601 instants; no locale-specific formatting is applied.
• Daylight saving: Registry timestamps are absolute instants; daylight-saving transitions do not affect them.
• Reference date: There is no reference-date input; the result reflects the registration record when the request is served.

Usage

1. Enter a domain (for example example.com) or a public IP address.
2. Run the lookup.
3. Read the registrar, status, dates and nameservers that the registry makes public.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

Domain

{
  "target": "example.com"
}

Public IP

{
  "target": "93.184.216.34"
}

Limitations

Server processing and data flow

WHOIS and RDAP require a raw network connection that a browser cannot make, so this lookup runs on the Gampangin API. Your domain is sent to our server, which queries the configured WHOIS/RDAP provider and returns normalized fields.

The target is not retained or logged, the response is no-store and sets no cookie, and the provider credential stays on the server.