.my WHOIS Lookup
.my is the country-code extension of Malaysia, administered by MYNIC Berhad. Look up a .my 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
.my WHOIS Lookup: MYNIC Records and Their Blocks
.my is the country-code extension of Malaysia, delegated into the root zone on 8 June 1987 and operated by MYNIC Berhad. Queries are answered by whois.mynic.my on port 43, and in our measurement on 12 August 2026 the reply carried fifty-eight field labels. The extension has no registered RDAP endpoint, so port 43 is the only channel for registration data, and the zone carries a DS record in the root.
That width comes from four separate contact blocks. Alongside the registrant, administrative and technical contacts there is a billing block, and all four carry their own lines for name, organisation, street, city, state, postal code, country, phone, fax and email. The billing role appears in no schema at all for many extensions; here the party responsible for paying for the record is kept as an identity of its own. Having the role makes it possible to tell who manages a record from who pays for it.
Withholding in these blocks separates the person from the organisation. In the record we measured, the registrant's name was closed on privacy grounds while the organisation name arrived open, and the billing block was closed in full. Dates are present as well, and in our sample exactly twenty-five years separated creation from expiry. Our result screen fills twelve fields. For another schema of comparable width, see .us WHOIS lookup; for a different arrangement of roles in Asia, .in WHOIS lookup.
About the .my extension
- Extension
- .my
- WHOIS server
- whois.mynic.my
- RDAP endpoint
- This extension has no RDAP endpoint in the IANA bootstrap registry.
- Registry
- MYNIC Berhad, Malaysia
- Delegated
- 8 June 1987
- Measured field count
- 58 field labels (12 August 2026)
- Contact blocks
- Registrant, administrative, technical and billing — four separate blocks
- Measured sample
- mynic.my: registered 8 January 2008, expires 8 January 2033
WHOIS FAQ
What is the billing block in a .my record for?
It keeps the party responsible for paying for the record as a separate identity. Many extensions carry no such role at all and settle for registrant, administrative and technical contacts. Separating four roles makes it possible to tell, from the record alone, who inside an organisation manages the domain and who pays the invoice. In the record we measured, every line of this block was closed on privacy grounds.
Does a .my lookup show the registrant's name?
The name line arrives closed. In the 12 August 2026 measurement, the registrant's name was replaced by a marker stating that it was withheld for privacy. The organisation line, by contrast, was open, so the legal entity behind the address could be read. Identity is therefore not closed wholesale: lines that could be tied to a person are withheld, while those belonging to the organisation are left open.
Why is the organisation open when the name is closed?
Because privacy protection is aimed at natural persons. The name of an organisation is commercial information and nothing stands in the way of publishing it, whereas name, address, phone and email lines that can be tied to an individual are withheld. The record we measured showed the distinction plainly: the organisation was readable while the name, address and contact lines carried a privacy marker in their place.
Which dates appear in a .my record?
Three arrive: creation, last updated and the registry expiry date. In the record we measured, creation was dated 8 January 2008 and expiry 8 January 2033, exactly twenty-five years apart. Long-running records do occur in this extension, so an expiry date here is no reason to assume a short renewal cycle. All three dates are carried through to the result screen.
Is there an RDAP endpoint for the .my extension?
There is not. In our measurement on 12 August 2026 IANA's bootstrap list carried no RDAP address for .my. The single channel for registration data is the server on port 43. That means the reply arrives as unstructured plain text, which is precisely why correct parsing of the labels matters in an output of fifty-eight fields.
How does the DNSSEC state appear for .my domains?
A dedicated DNSSEC field sits at the end of the reply, and in the record we measured its value was a signed delegation. The extension itself is signed too: we confirmed a DS record for .my in the root zone in the same measurement. With both in place, a chain of validation runs from the root down to the address. Our result screen reports the state of the individual name as its own field.