.re WHOIS Lookup

.re is the country-code extension of Réunion, a French overseas region, administered by AFNIC. Look up a .re address and see the record.

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

Your IP address 216.73.216.31

.re WHOIS RECORD

.re WHOIS Lookup: Réunion Domain Name Records

.re is the country-code extension of Réunion, a French overseas region; it was delegated into the root zone on 7 April 1997 and is operated by AFNIC. Queries are answered by whois.nic.re on port 43, and in our measurement on 12 August 2026 the reply carried thirty-seven distinct labels. The extension also runs an RDAP endpoint at rdap.nic.re, and the zone carries a DS record in the root.

The reply is divided into blocks, and each block names its own source. In the record we measured, every one of those lines held the same value: FRNIC. Records for .re are therefore answered from the French national registry database, with the two extensions sharing one system. The practical consequence is that the field names, abbreviations and block layout you learn on the .fr side apply here as well, and a parser written for one extension works on the other.

The record reports status on three separate lines: a general status line, a second line giving the EPP equivalent of the same information, and a hold field saying whether the name has been suspended. All three were positive in the record we measured. The reply also carried the tag, algorithm and digest of the DNSSEC key for the queried name in full. Our result screen fills eight fields. For the principal extension on that same database, see .fr WHOIS lookup; for another that opens key material in the same way, .eu WHOIS lookup.

About the .re extension

Extension
.re
WHOIS server
whois.nic.re
RDAP endpoint
https://rdap.nic.re
Registry
AFNIC — the French national registry
Delegated
7 April 1997
Measured label count
37 labels (12 August 2026)
Source line
Every block reads source: FRNIC — the same database as .fr
Status fields
status, eppstatus and hold — three lines on the same question
COMMON QUESTIONS

WHOIS FAQ

Why do .re records appear to come from FRNIC?

Because the records are held in the French national registry database. In the reply we measured, every block ended with a source line, and each of them read FRNIC. Réunion is a French overseas region and its extension is run by the same organisation, AFNIC. The benefit to you is direct: the reply format is identical across the two extensions, so a reading habit learned on one carries over to the other.

What does the hold field in a .re record mean?

It is a dedicated field stating whether the name has been suspended. In the record we measured its value was NO, so the name was not on hold. A suspended address may not be live in technical terms, which is why the hold field deserves a look of its own alongside the status lines. Many extensions carry no such independent field and bury the same information inside their status codes.

Why are there two status lines in a .re reply?

One uses the registry's own vocabulary and the other the shared EPP vocabulary. In the record we measured, the first line held a general status in capitals and the second the EPP equivalent of the same state. Giving both is a courtesy to the reader: you understand the state without memorising codes, while a tool expecting codes finds its own line. Where the values differ, the EPP line is the technically binding one.

Does a .re record show the registrant?

Not directly. In the record we measured the registrant appeared as a handle, and no personal contact data was opened in the reply. AFNIC makes that data available on a limited basis through its own web interface, so expecting a name and address in the plain-text answer would be misplaced. The registrar side, by contrast, is open: its name, address, phone number and email all appear in the reply.

What are the key lines in a .re reply for?

They show the DNSSEC configuration of the name. In the record we measured, the key tag, the algorithm number and its name, the digest type and the digest itself were all written out in full. These lines are the registry-side counterpart of the DS record published in the zone, so you can compare them with the DNS values to check that the signature is being published correctly. Most extensions skip this detail and say only signed or unsigned.

What does the RDAP endpoint give for .re?

The endpoint at rdap.nic.re answered in the 12 August 2026 measurement. It listed sponsor, registrar, administrative, registrant and technical roles, and it showed a contact name. Among its events were registration, expiration, last changed and transfer. The RDAP side therefore gives one thing more than the port 43 reply: the date on which the name moved between registrars is available here.

How does an available .re name look in a lookup?

As a reply with no record block. In our measurement a name that was not registered drew no handle, date or name server lines from the server, and the result screen marked it as available. Availability works correctly for this extension. Results that look available are cached for five minutes and registered ones for six hours.