.agency WHOIS Lookup
.agency is a generic extension operated by Binky Moon. Look up a .agency address and see which details its record carries.
- 1.494 extensions
- IANA 1601 ICANN accredited
- 2 protocols — RDAP and WHOIS
Your IP address 216.73.216.31
.agency WHOIS Lookup: Records in an Agency Extension
.agency is a generic extension delegated into the root zone on 9 January 2014, and IANA's record names Binky Moon, LLC as the sponsoring organisation. That same record carries no WHOIS server, and in our measurement on 12 August 2026 port 43 returned no registration data at all. Queries are answered by the RDAP endpoint at rdap.identitydigital.services, and the zone carries a DS record in the root.
When we queried the registry's own name on 13 August 2026, the record held five events: registration on 26 November 2013, a transfer on 9 April 2014, expiry on 26 November 2026, the last change to the record and a database stamp. The transfer event answers a question none of the other dates does — the day the name moved from one registrar to another. It reports a change of custodian, not a change of owner.
Our result screen parses eight fields out of that record: the domain name, the creation, updated and expiry dates, the registrar, the name servers, the status codes and the DNSSEC state. The transfer date is not one of the eight; it stays readable in the separate tab holding the registry's raw reply. Run a .agency lookup and compare the two views. For a sibling extension whose record carried no transfer at all, see .show WHOIS lookup, and for another name answered by the same endpoint, .tools WHOIS lookup.
About the .agency extension
- Extension
- .agency
- WHOIS server
- This extension has no WHOIS service on port 43; registration data is published over RDAP.
- RDAP endpoint
- https://rdap.identitydigital.services/rdap
- Registry
- Binky Moon, LLC — the sponsoring organisation in the IANA record
- Delegated
- 9 January 2014
- Source of record data
- rdap.identitydigital.services
- Events
- registration, transfer, expiration, last changed and a database stamp
- Measured sample
- nic.agency: registered 26 November 2013, transferred 9 April 2014 (13 August 2026)
WHOIS FAQ
What does the transfer date in a .agency record mean?
A transfer event records the day a name moved from one registrar to another. In the nic.agency record we read on 13 August 2026, registration was dated 26 November 2013 and the transfer 9 April 2014. The gap tells you the company managing the name changed, not that the domain changed hands. There is no separate event for a change of owner: most transfers do involve one, but the record holds no field that confirms it.
Does a .agency WHOIS query still answer on port 43?
It does not. The WHOIS server field in IANA's .agency record is empty, and in our measurement on 12 August 2026 port 43 returned no registration data. The reason is policy: since 28 January 2025 RDAP has been the authoritative source of registration data for generic extensions, and the obligation to serve that data over the WHOIS protocol ended on the same date. Our lookup recognises the extension and goes straight to the RDAP endpoint.
Which fields appear in the result of a .agency lookup?
Eight fields were populated in our measurement: the domain name, the creation date, the updated date, the expiry date, the registrar, the name servers, the status codes and the DNSSEC state. All of them are parsed out of the RDAP reply, so a closed port 43 leaves no gap on screen. Details that are not parsed are not lost either: the registry's raw reply stays readable in a separate tab, and the transfer date can be read there.
Does a .agency record show the name of the owner?
Not at registry level. The only role present in our 13 August 2026 measurement was the registrar; no registrant identity or contact block was opened at all. Across generic extensions, contact data belonging to natural persons has been published in masked form since 25 May 2018 — the record itself stands, the personal fields arrive closed. If you need to reach the owner, the address for that is the contact channel of the registrar that sold the name.
Why is the transfer date missing from the result screen?
Because the result screen parses eight fields out of the RDAP reply and the transfer event is not one of them. The dates shown are the creation, updated and expiry dates. To read the transfer date, open the tab that carries the registry's raw reply — the event list stands there in full. Reading the parsed fields together with the raw reply is the most practical way to reconstruct the history of a record.
Who can remove the status codes on a .agency domain?
Status codes come from ICANN's common EPP vocabulary, and the prefix tells you who holds the authority: codes starting with client are set by the registrar and can be lifted by the registrar, while codes starting with server are set by the registry and the registrar cannot lift them. In the nic.agency record we measured on 13 August 2026 all three codes carried the server prefix, so deletion, transfer and updates were locked.
Is the .agency zone signed with DNSSEC?
The zone is signed: a DS record for .agency exists in the root, and we confirmed it in the measurement of 12 August 2026. Individual names are a separate question. In the record we read on 13 August 2026 the signing state came back closed, so a signed extension does not mean a signed address. The result screen keeps the two apart, which stops a signed zone from being mistaken for a signed domain.