Whois spice - Summary of domain's whois info + registrar links for available domains

![screen shot 2014-06-26 at 4 16 30 pm](https://cloud.githubusercontent.com/assets/8975/3404532/10e924be-fd72-11e3-9890-249c61a72ca3.png)

![screen shot 2014-06-26 at 4 16 54 pm](https://cloud.githubusercontent.com/assets/8975/3404533/1288b9ec-fd72-11e3-8f04-29187d0f9227.png)

What does your instant answer do?
Provides whois info for a domain and registrar links for available domains.

What problem does your instant answer solve (Why is it better than organic links)?
Whois info isn't available in the DDG organics, and when you go to most whois sites, you have to type in a captcha and wade through ugly output.

What is the data source for your instant answer? (Provide a link if possible)
http://whoisxmlapi.com

Why did you choose this data source?
Clean JSON output that can be used for both whois information and available domains.

Are there any other alternative (better) data sources?
Didn't find anything better.

What are some example queries that trigger this instant answer?
whois duckduckgo.com
whois http://duckduckgo.com
register duckduckgo.com
is available duckduckgo.com
who owns duckduckgo.com

Which communities will this instant answer be especially useful for? (gamers, book lovers, etc)
Entrepreneurs, programmers, sysadmins.

Is this instant answer connected to a DuckDuckHack instant answer idea?
Here are some mentions of this idea:
https://duck.co/ideas/idea/1076/domain-whois-information-with-a-simple-command
https://duck.co/ideas/idea/184/improving-whois-information-the-instant-answer-p
https://duck.co/ideas/idea/1092/domain-information-from-wolfram

Which existing instant answers will this one supersede/overlap with?
I believe that there was a 'whois' instant answer but it's no longer working. Compared to the old version, at least as I understand it, I think this version adds more triggers and registrar links when a domain is available.

Are you having any problems? Do you need our help with anything?
This could clearly use some design help :). And in general, any feedback and ideas would be great.
Better to have the endpoint in HTTP instead of HTTPS (it's a little bit faster that way).