{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

Source{{ sourceBadge }} Evidence{{ evidenceBadge }} Renewal{{ renewalBadge }}
One domain, such as example.com. Plain load never sends the sample to a provider.
The default checks the registry-standard RDAP route before using the provider fallback.
ms
2,500–15,000 ms per source; the neutral default is 9,000 ms.
FieldValueSectionCopy
{{ row.label }}{{ row.value }}{{ row.section }}
Verification checks
{{ note.title }}

{{ note.detail }}

Cloud-init Network Config Generator Build cloud-init version 2 YAML for a static VM interface, with CIDR and route validation plus warnings for risky boot assumptions.
Nameserver Health Check Check a domain’s resolver-visible nameserver set and verify address coverage, SOA presence, and cross-resolver drift before a DNS cutover.
DNS Configuration Report Audit a domain's public DNS for authority, address and mail-policy gaps while comparing TTL horizons and resolver-visible evidence across common records.
MX Record Lookup Inspect a domain's MX route and compare public DNS answers while catching Null MX conflicts, unresolved exchanges, and alias targets.

A domain can have a healthy website while its registration is close to expiry, and it can have a current registration while its DNS is broken. Registration data answers a narrower set of questions: which registrar sponsors the name, which status restrictions are recorded, which lifecycle dates are published, and which nameservers the registry associates with the domain.

Registration Data Access Protocol (RDAP) returns structured HTTPS data. It standardizes fields and error responses that legacy WHOIS often presents as provider-specific text. RDAP is usually the better first source for a machine-readable record, while a WHOIS provider can still supply useful fallback evidence when RDAP is unavailable or sparse.

  • Status values can describe transfer, update, deletion, hold, or lifecycle restrictions. A domain may have several at once.
  • Lifecycle events record dates such as registration, last change, and expiration when the provider publishes them.
  • Nameservers describe registration-side delegation. Live DNS queries are still needed to confirm what resolvers and authoritative servers return.
  • Contacts may be redacted, replaced by privacy services, or omitted under registry and privacy policy.

An expiration date is not a guaranteed public release time. Auto-renewal, grace periods, redemption, deletion policy, registrar billing, and registry rules can all affect what happens next. Confirm renewal and recovery decisions with the registrar.

Public registration data supports troubleshooting and due diligence, but it does not prove legal ownership, account access, authorization, or control of the domain.

How to Use This Tool:

Look up one registrable domain and choose a source order that fits the evidence you need.

  1. Enter a domain such as example.com. A pasted HTTP or HTTPS URL is reduced to its hostname before the request.
  2. Choose the Lookup source order, set a 2.5–15 second per-source timeout if needed, and select Lookup. The next configured source begins only when the first fails or times out.
  3. Read the Registration record, then compare Evidence coverage and Verification checks. Record the observation time whenever the result supports a ticket, renewal, or handoff.

Interpreting Results:

The source badge identifies the provider that returned the normalized record. The evidence count shows how many declared identity, lifecycle, registrar, nameserver, and contact items were present. It measures completeness, not truth or authority.

  • Read every registration status before deciding that a transfer, update, deletion, or DNS change is possible.
  • Treat Days until expiry as calendar arithmetic from the observation timestamp. It is not a renewal recommendation or drop-date forecast.
  • Compare registration-side nameservers with live DNS NS answers before diagnosing delegation.
  • Missing public contacts usually mean redaction or unavailable fields, not that no responsible party exists.
  • Verify consequential findings with the registrar or relevant registry because sources can update at different times.

Technical Details:

RDAP discovery begins with the domain's top-level label. The IANA bootstrap registry maps that label to an RDAP service, and the domain is queried as a structured registration object. The response can contain status values, events, entities, public identifiers, links, and nameserver objects. WHOIS fallback data is normalized into the same reader-facing categories.

Lookup Core:

Source orderAttempt sequenceUse
RDAP first, WHOIS fallbackRegistry RDAP, then WHOIS provider if RDAP failsDefault structured lookup with recovery
RDAP onlyRegistry RDAP onlyKeep evidence on the standards-based path
WHOIS first, RDAP fallbackWHOIS provider, then registry RDAP if it failsCompare provider coverage or retry a sparse RDAP path

A successful record is normalized into five evidence categories. Domain identity has four declared items, lifecycle has three, registrar profile has five, nameserver presence has one, and public contact roles have four. The combined evidence badge therefore has a denominator of 17.

Formula Core:

Days until expiry are calculated from provider timestamps with one-day ceiling rounding, so any positive partial day counts as a remaining day.

d= ⌈texpiry−tobserved86400000⌉

d is the number of calendar-sized 24-hour periods remaining, and both timestamps are converted to milliseconds. Missing or unparseable dates produce Unknown rather than an estimate.

ConditionRenewal label
d < 0Past date
0 ≤ d ≤ 30Within 30 days
30 < d ≤ 90Within 90 days
d > 90More than 90 days

Evidence coverage is also deterministic. Each category percentage is returned items divided by declared items, multiplied by 100. A registrar category showing 2 of 5 means three expected registrar fields were absent; it does not rate the quality of the two values that were returned.

Status and Delegation Boundaries:

RDAP status strings describe the registered object and can map to Extensible Provisioning Protocol restrictions. They do not replace registrar account state. Likewise, registry-reported nameservers are registration evidence; recursive and authoritative DNS queries are required to prove the current delegation path and zone service.

Privacy and Accuracy Notes:

The entered domain is sent to the registry RDAP service and, depending on the selected source order and failures, may also be sent to the WHOIS data provider. Those services can observe and log the lookup.

  • Public contact details may contain personal or operational information. Review exported records before sharing them.
  • Provider omissions, redaction, rate limits, policy, and update delay can create sparse or conflicting records.
  • Expiration, status, and nameserver values can change after the recorded observation time.
  • Use the registrar account and registry or registrar support for ownership, authorization, billing, renewal, transfer, and recovery decisions.

References: