.website WHOIS Lookup

.website is a generic extension operated by Radix. Look up a .website address and see what the record contains.

  • 1.494 extensions
  • IANA 1601 ICANN accredited
  • 2 protocols — RDAP and WHOIS

Your IP address 216.73.216.31

.website WHOIS RECORD

.website WHOIS Lookup: Record and Registrar Fields

.website is a generic extension that entered the root zone on 22 May 2014, operated by Radix. Port 43 queries are answered by whois.nic.website, which returned fourteen fields in our measurement on 12 August 2026, and an RDAP endpoint runs at rdap.radix.host. The zone holds a DS record in the root.

In our measurement on 12 August 2026 the reply returned fourteen fields: the creation, updated and expiry dates, the registrar's name and IANA number, an email and phone number for abuse reports, the name servers, the status codes and the DNSSEC state. There is no registrant line; identity data is held at the registrar that sold the name, and the reply states that company's name openly.

This schema answers one question well: when you need to report a problem with a .website address, the record itself tells you who to approach. The reply carries both the registrar's name and the email and phone number set aside for abuse reports. Run a .website lookup and see those lines. For the other extensions of the same operator, see .online WHOIS lookup and .site WHOIS lookup.

About the .website extension

Extension
.website
WHOIS server
whois.nic.website
RDAP endpoint
https://rdap.radix.host/rdap
Registry
Radix Technologies Inc.
Delegated
22 May 2014
Fields measured
14 fields (12 August 2026)
Record identifier
The suffix on the number points to the infrastructure holding the record
RDAP
rdap.radix.host — only the registrar role is listed
COMMON QUESTIONS

WHOIS FAQ

What does a .website WHOIS lookup show?

The reply carried fourteen fields in our measurement: the creation, updated and expiry dates, the registrar's name and IANA number, an email and phone number for abuse reports, the name servers, the status codes and the DNSSEC state. Our result screen fills nine of them. No registrant name or contact line appears in the reply.

Where do complaints about a .website address go?

The reply sets aside two lines for exactly this: the registrar's abuse email and abuse phone number. Both were populated in the record we measured. Reports of misuse go first to the company that sold the name, because it holds the authority to act on the address. If that leads nowhere, the registry is the next level up, and following the order in turn helps a report get processed.

Does a .website WHOIS lookup show the domain holder?

It does not. No field for a registrant, an admin or a technical contact exists at registry level, and no such line appeared in the record we measured. What the reply does carry plainly is the name of the registrar that sold the domain, its IANA number and an email address and phone number for abuse reports. Where identity is needed, approaching that registrar is the step that works.

Does a .website record carry creation and expiry dates?

It does. The reply gives the creation date, the last modification and the expiry date in UTC and to the second, and the same three values arrive as events on the RDAP side. Our result screen derives the domain's age and its remaining term from them, so there is nothing to work out by hand.

What does the RDAP endpoint give for .website?

The rdap.radix.host endpoint returns the same record as JSON; in our measurement the only role was the registrar and the events amounted to registration, expiry and last change. The scope matches the port 43 reply and the difference is form. A structured reply is safer in automated systems because the position of each field is fixed.

How does an available .website name appear in a lookup?

Query a name nobody holds and the registry reports that no match was found, with none of the fourteen fields present. That means the name looks free to register. We keep such a result for five minutes only and registered ones for six hours, the short window being there because a name that looks free can be taken quickly.