{"id":223,"date":"2025-07-02T12:10:57","date_gmt":"2025-07-02T12:10:57","guid":{"rendered":"https:\/\/hosterlink.com\/blog\/?p=223"},"modified":"2025-07-02T12:10:57","modified_gmt":"2025-07-02T12:10:57","slug":"how-to-add-ai-domain-search-support-in-your-whois-json-file-in-whmcs","status":"publish","type":"post","link":"https:\/\/hosterlink.com\/blog\/how-to-add-ai-domain-search-support-in-your-whois-json-file-in-whmcs\/","title":{"rendered":"How to add .ai Domain Search Support in your whois.json file in WHMCS"},"content":{"rendered":"\n<p>The <code>.ai<\/code> domain extension has gained massive popularity, not just in Anguilla (its country of origin), but across global tech startups and AI-focused companies. If you\u2019re building your own domain lookup tool or integrating WHOIS functionality into your app, supporting <code>.ai<\/code> domains is a must.<\/p>\n\n\n\n<p>However, unlike some other TLDs, <code>.ai<\/code> WHOIS behaves a little differently\u2014so getting it right in your <code>whois.json<\/code> file is important.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Correct Configuration for <code>.ai<\/code> WHOIS<\/h2>\n\n\n\n<p>Here\u2019s the correct and working configuration you should add in your <code>whois.json<\/code> file:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>{\n  \"extensions\": \".ai\",\n  \"uri\": \"socket:\/\/whois.nic.ai\",\n  \"available\": \"Domain not found\"\n}<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83d\udd0d What Each Field Means<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><code>extensions<\/code><\/strong>: Specifies the domain extension this rule applies to. In this case, <code>.ai<\/code>.<\/li>\n\n\n\n<li><strong><code>uri<\/code><\/strong>: This is the WHOIS server for <code>.ai<\/code> domains. It uses the socket protocol to send a query to <code>whois.nic.ai<\/code>.<\/li>\n\n\n\n<li><strong><code>available<\/code><\/strong>: This string is searched in the WHOIS response to determine if a domain is available. For <code>.ai<\/code>, the server responds with <code>Domain not found<\/code> if the domain is unregistered.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">\u26a0\ufe0f Common Mistakes to Avoid<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Using the wrong match string<\/strong>: Many assume <code>.ai<\/code> returns <code>No match<\/code>, but the correct string is <code>Domain not found<\/code>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83e\uddea Test Before You Deploy<\/h3>\n\n\n\n<p>Always test your implementation. You can use a domain like <code>hosterlinktest1234.ai<\/code> (assuming it&#8217;s not registered) and confirm your tool correctly identifies it as <strong>available<\/strong>.<\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The .ai domain extension has gained massive popularity, not just in Anguilla (its country of origin), but across global tech startups and AI-focused companies. If you\u2019re building your own domain lookup tool or integrating WHOIS functionality into your app, supporting .ai domains is a must. However, unlike some other TLDs, .ai WHOIS behaves a little [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,10],"tags":[],"class_list":["post-223","post","type-post","status-publish","format-standard","hentry","category-hosterlink-notes","category-web-hosting"],"_links":{"self":[{"href":"https:\/\/hosterlink.com\/blog\/wp-json\/wp\/v2\/posts\/223","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hosterlink.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hosterlink.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hosterlink.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hosterlink.com\/blog\/wp-json\/wp\/v2\/comments?post=223"}],"version-history":[{"count":1,"href":"https:\/\/hosterlink.com\/blog\/wp-json\/wp\/v2\/posts\/223\/revisions"}],"predecessor-version":[{"id":224,"href":"https:\/\/hosterlink.com\/blog\/wp-json\/wp\/v2\/posts\/223\/revisions\/224"}],"wp:attachment":[{"href":"https:\/\/hosterlink.com\/blog\/wp-json\/wp\/v2\/media?parent=223"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hosterlink.com\/blog\/wp-json\/wp\/v2\/categories?post=223"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hosterlink.com\/blog\/wp-json\/wp\/v2\/tags?post=223"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}