I can't perceive the difference between domainzomg.com and instantdomainsearch.com. The latter is using plain old ajax. Theoretically I'm not even sure if I should see a difference. A plain old ajax call will get sent on an existing sleeping HTTP 1.1 connection, and should take 1 packet each for the request and response. WebSocket can't get any better than that.<p>tl;dr: Request/Response model on the web is already fast enough for small data. Use WebSocket where it matters, like a firehose of updates in either direction.
Semi-hidden feature:<p>"red/black trees" -> "redtrees.com", "blacktrees.com", "red-trees.com", "red-tre.es", ...<p>Also, <a href="http://domainzomg.com/somedomainname" rel="nofollow">http://domainzomg.com/somedomainname</a> should work if you just want to fire off a quick query.<p>Caveat:<p>Domainzomg is really a brainstorming tool, so it just uses DNS lookups and a fairly permissive list of TLDs. Red definitely means "taken", but green doesn't necessarily mean "available", it just means "this domain doesn't seem to have a DNS entry". Check with a real registrar for availability, use domainzomg for brainstorming.
People should really reconsider using third party tools hosted elsewhere to check domain name availability.<p>I only use my own tool on my own server and I check the registries directly to avoid ISP snooping for nx-domain queries.
Small usability suggestion: set the anchor portion of the URL after results return or a predefined timeout. It took me way too many clicks of the back button to get back to the front page.