| Field | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} | |
| No info available. | ||
| Field | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} | |
| No contact details present. | ||
| Field | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} | |
| No DNS details. | ||
| Field | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} | |
| No registrar details. | ||
Domain registration records are public listings that describe who controls a name, when it was created, and when it is due to expire. They help you confirm ownership, check timing, and review the basic setup for a website or mail domain.
You enter a fully qualified name and receive a concise summary that highlights the registrar, creation and expiry dates, current status, and the nameserver set. A longer view organizes the same facts into focused sections so you can scan contacts, DNS details, and the raw response when deeper checking is needed.
For a quick reality check, compare the expiry window with your renewal plan and verify that nameservers match your intended host. If contacts are redacted, focus on registrar and status to confirm that the domain is active and transferable only under allowed conditions.
Small differences in timestamps can produce one day swings around midnight, so interpret age and days to expiry as approximate calendar counts. When comparing different domains, use the same input format each time and avoid adding protocols or paths.
If you manage several names, capture each result on the same day and look for consistent registrar references and a stable nameserver footprint.
The tool queries domain registration data and organizes the response into a summary plus sections for general info, contacts, DNS, and registrar. Uniform terms from the ecosystem are used where available, including WHOIS status strings and registrar identifiers. Domain Name System (DNS) nameservers are listed as provided by the data source.
Two convenience measures are computed from timestamps returned by the provider. The first is the number of whole days since creation, which reflects an approximate age. The second is the number of days until the expiry date, rounded up so expiring today is shown as one day.
These counts are derived from the difference between your device time and the ISO timestamps in the response. Values near midnight can differ by one depending on local time and the timestamp precision in the record.
| Symbol | Meaning | Unit/Datatype | Source |
|---|---|---|---|
t(create) |
Creation timestamp | ISO datetime → milliseconds | Provider field create_date |
t(expire) |
Expiry timestamp | ISO datetime → milliseconds | Provider field expire_date |
now |
Current time on device | milliseconds since epoch | Device clock |
86 400 000 |
Milliseconds in one day | ms | Constant |
create_date = 2025‑10‑01T00:00:00Z; expire_date = 2025‑11‑01T00:00:00Z; device time at 2025‑10‑14T00:00:00Z.| Field | Type | Min | Max | Step/Pattern | Error Text | Placeholder |
|---|---|---|---|---|---|---|
| Domain | string | — | — | ^(?!-)[A-Za-z0-9-]{1,63}(?<!-)(\.[A-Za-z0-9-]{1,63})+$ |
Domain is required. or Enter a valid domain such as “example.com”. | example.com |
Units, precision, and rounding: Days are computed using whole‑millisecond differences. Age uses floor; time to expiry uses ceiling. Decimal separators follow the default locale when underlying timestamps include fractional seconds.
| Input | Accepted Families | Output | Encoding/Precision | Rounding |
|---|---|---|---|---|
| Domain name | ASCII labels with dots; no scheme or path | Summary, tables, JSON copy | UTF‑8 text; JSON pretty‑printed | Days floor or ceiling as noted |
Networking and storage behavior: A single HTTPS request is issued to a WHOIS data provider via a CORS proxy, with a nine second abort timer. Responses are parsed as JSON. No persistent browser storage is used for inputs or results.
Diagnostics and determinism: Identical inputs will generally return identical summaries when the upstream data has not changed. Results can change at any time as the registry record updates.
Security considerations: The provider key is embedded client‑side with simple character shifting before use. Treat it as obfuscated, not secret. Do not paste sensitive information into free‑form fields of third‑party portals linked by the registrar.
postal_code and zip_code is normalized in labels only.Privacy & compliance: Requests are issued from the page to a third‑party WHOIS API via HTTPS. Outputs can include contact information depending on the registry response; handle any copies appropriately under your local privacy rules.
Domain registration checks return a summary of control, timing, and DNS endpoints.
Example: if expiry reads 14 days and nameservers differ from your host, renew first and correct delegation after confirmation.
The page issues a live request and renders the response. It does not write inputs or results to persistent browser storage.
Network requests are required to fetch records.They reflect the registry or registrar source at the time of lookup. Fields can be redacted or delayed depending on policy and caching.
ASCII domains with dot‑separated labels are accepted. Protocols and paths are stripped before validation.
No. A live request to a WHOIS data source is required to return current information.
Usage depends on the underlying data service plan and rate limits. Heavy use may be throttled by the provider.
Run a lookup and open the DNS section. Compare each listed nameserver with your intended host configuration.
Registries and registrars often redact personal fields. Use registrar name, status, and dates to verify control in such cases.
Values within one day of midnight can flip due to rounding. Treat them as an immediate renewal signal.