.me WHOIS Lookup
.me is the country-code extension of Montenegro, widely used for personal addresses. Look up a .me 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
.me WHOIS Lookup: Contact Blocks and Record Fields
.me is the country code extension of Montenegro, delegated into the root zone on 24 September 2007, with the government of Montenegro responsible for the zone. Queries are answered by whois.nic.me. In our measurement on 12 August 2026 the reply carried fifty-four field labels, several of them borrowed from generic practice: the registrar's IANA number, an abuse contact, EPP status codes and the address of ICANN's registration data inaccuracy form. The zone holds a DS record in the root.
The reply carries three contact blocks — registrant, admin and tech — and they are not closed to the same degree. In the record we measured, the registrant block still showed the organisation, the state and the country, while the name, street, phone and email lines had turned into REDACTED. In the admin and tech blocks everything was closed, the organisation line included. Three roles in one record, then, each behind a different veil.
What never closes is the technical and chronological part: creation, update and expiry dates to the second, name servers one per line, and status codes linked to ICANN's shared vocabulary. The record we measured was opened in 2008. To see another country code extension on the same template, try the .io WHOIS lookup; for a generic extension that lists the registrant as an entity on the RDAP side, the .biz WHOIS lookup page.
About the .me extension
- Extension
- .me
- WHOIS server
- whois.nic.me
- RDAP endpoint
- This extension has no RDAP endpoint in the IANA bootstrap registry.
- Registry
- Government of Montenegro
- Delegated
- 24 September 2007
- Fields measured
- 54 field labels (12 August 2026)
- Contact blocks
- Organisation may survive for the registrant; admin and tech are fully closed
- RDAP
- IANA's bootstrap registry defines no endpoint for .me
WHOIS FAQ
Does a .me WHOIS lookup show the owner of the domain?
Partly. In the record we measured, the organisation, state and country lines of the registrant block were readable, while the name, street, postal code, phone and email lines had become REDACTED. Seeing a company's name is quite possible; seeing an individual's is not to be expected. Where the holder is a natural person, the working route to contact runs through the reporting channel of the registrar named in the reply.
Why are the admin and tech blocks more closed than the registrant?
Because in those two roles the organisation line is closed as well. In the record we measured, the name, organisation, street, phone and email lines of the admin and tech blocks all read REDACTED, whereas the registrant block still showed its organisation. The practical meaning is this: you cannot reach the technical contact of an address through WHOIS, yet you can still see which organisation holds the registration.
If .me is a country code, why link to an ICANN form?
Because the registry follows the reply conventions of generic extensions even though the extension is a country code. Our measurement found the address of ICANN's registration data inaccuracy form at the end of the reply, a link to the shared vocabulary for status codes, and the registrar's IANA number. The result works in your favour: field names and their order match .com output, so reading the two records side by side takes no adjustment.
Can the age and expiry of a .me domain be read from WHOIS?
They can. The reply gives the creation date in Creation Date, the last modification in Updated Date and the end of the term in Registry Expiry Date, all in UTC; the record we measured was opened in 2008. Our result screen works out the age and the remaining term from those three values and shows both. As the term runs short we turn the indicator to a warning colour, so the renewal window is hard to miss.
Is there an RDAP endpoint for .me?
IANA's RDAP bootstrap registry defines no endpoint for .me, and our measurement on 12 August 2026 confirmed it. Since 28 January 2025 RDAP has been the definitive source for generic extensions, but .me is a country code extension and falls outside that arrangement. However closely the reply follows generic convention, the channel behind it is the port 43 WHOIS service — something to account for in any system that needs a machine-readable source.
What do the name server lines in a .me record tell you?
They tell you which servers resolve the domain; the record we measured listed four, one per line. These lines are the technical side of the record and privacy rules do not touch them, so they appear in full even where every contact field is closed. Which provider the servers belong to is a practical clue about where the address is hosted.
How is DNSSEC status read for a .me address?
The DNSSEC line in the reply describes the address you queried: signed when a DS record has been published for that name, unsigned when it has not. The extension itself is a separate matter — the .me zone holds a DS record in the root and is signed, which we verified during the measurement. A signed zone does not make individual addresses signed; that switch is thrown at the registrar.
How does an available .me name appear in a lookup?
Query a name nobody holds and the server reports that no match was found, with none of the fifty-four fields present — no dates, no registrar, no name servers. That means the name looks free to register. We keep such a result for five minutes, and results for registered names for six hours.