There's nothing TLD-specific about it. So, it should work on one TLD as well as any other.
Reverse DNS lookups use a special TLD - in-addr.arpa. This is used for reverse DNS lookups regardless of the TLD of the domain name. You prepend the IP address (with the octets in reverse order) to in-addr.arpa and look for a PTR record.
Whether or not this works depends on whether or not the registrant of the IP address has set-up a PTR record for the address.
Outside of the corporate and university worlds, the registrant of the IP address is most typically a hosting company. Some may delegate to their customers. Most don't. Most will set-up PTR records to their customer's domains either automatically or on request.
Here's a good tutorial on the subject:
[freesoft.org...]
One thing i'm not sure on is that when i know a .co.uk name is on a server so i get it's IP, the results show me all the .coms/.nets that are on that machine but none of the .co.uk's
Only ONE PTR record can be assigned per IP address. That is true, even if the IP address has multiple domain names assigned to it.
So, I'm not sure what tool you are using that is showing multiple domain names for an IP address. Could be it is doing the reverse DNS lookup, then speculatively attempting a forward DNS lookup on alternate TLDs, and displaying them as well if the IP address matches.
If that's the case, I'd suggest urging the author to add additional TLDs. :)