Whois API web service, domain whois api in XML and JSON
Welcome to our whois api web service, it will help you to get raw and parsed domain whois data in one simple HTTP request. You can use this API in your scripts, software. XML and JSON formatting making it accessible for Ajax request and JavaScript parsing. It's very simple - just one HTTP request! There are tree output format: raw data (without parsing), XML structured data, JSON structured data. Raw whois data If you requesting raw data it's cost less than parsed data and data looking like plain text, see examples: amd.com, intel.com, eonline.ca, opencourt.us. Raw data will be useful for customer who what to pay less and do not need data parsing or already having some whois parsed. You can find more information about raw data understanding in our raw whois data guide. Parsed whois data If you what to use some specific fields from whois record (expiration date, email, name, organization, ...) - you need to use parsed whois data. There are two different links, first for XML structured output and the second for JSON. There are XML structured output examples - amd.com, intel.com, opencourt.us, eonline.ca and JSON examples - amd.com, intel.com, opencourt.us, eonline.ca. More information about fields structure you can find in our parsed whois data guide. The best way to understand our service try our free online whois lookup demo. |
Free Trial
This is limited offer and will be available only during fixed period. Sign Up now and get Free Trial for testing our Whois API and Whois Lookup tools. We gift you 80 requests, do not need to purchase any subscriptions or credits. Free trial already in use after you will sign up, so you can start to test right now. |
Whois API errors handling
There are several type of errors:
incorrect_secret - your API link is broken, please check it twice
disallowed - no money on your balance
incorrect_domain - requested domain name is invalid
tld_not_supported - TLD not supported (see list of supported TLD below)
internal_error - some internal service error, try to repeat request later
You do not pay money for request if error happens.
If you requesting raw whois data - error will be outputted as plaint text:
But if you requesting parsed XML whois data - error will be outputted as structured XML
JSON error will be outputted as structured JSON:
incorrect_secret - your API link is broken, please check it twice
disallowed - no money on your balance
incorrect_domain - requested domain name is invalid
tld_not_supported - TLD not supported (see list of supported TLD below)
internal_error - some internal service error, try to repeat request later
You do not pay money for request if error happens.
If you requesting raw whois data - error will be outputted as plaint text:
But if you requesting parsed XML whois data - error will be outputted as structured XML
JSON error will be outputted as structured JSON:
Click for Access Whois in two easy steps! | ||
It's the cheapest offer for hosted whois service |
List of supported domain zones (121 TLD)
aero, ac.uk, af, ag, am, asia, at, au, be, best, bg, bi, biz, br.com, br, bz, cat, ca, cc, cd, ci, cf, co, club, ck, cn.com, cn, com, coop, co.il, co.za, cx, cz, de.com, de, dk, edu, ee, eu.com, eu, fi, fr, ga, gb.com, gb.net, gl, gy, hk, hn, hu.com, hu, ie, io, info, in, ir, is, it, je, jobs, jpn.com, jp, ke, kr.com, kr, kz, la, li, lt, lu, lv, md, me, mobi, ml, mx, my, com.my, net.my, org.my, name, net.au, net, nl, no, no.com, nu, online, org, org.il, org.ua, ovh, pl, pro, pt, pw, qc.com, re, ro, ru.com, ru, sa.com, sc, se.com, se.net, se, services, sg, si, site, sk, space, st, su, tel, th, tk, top, tl, travel, tv, tw, ua, uk.com, uk.net, us.com, us.org, us, uy.com, uz, vc, ve, website, ws, xyz, za.comNotice: feel free to contact us if you need to use domain zone that not present in current list, we do not include some domain zones because we thinking that it will be useless.
Terms of Service
By using of this service you agree with our terms. Our service - just tool that help customer to submit request to whois database.My-Addr Project not responsible for whois data use, all responsibility for data use taken by customer, fetched data can be used only for lawful cases.