Parsed and structured whois data guide, fields
|
As you can see in raw whois data guide, whois record can have different format and it's uncomfortably in some cases. Example: some customer having 300 domains and he need to know when each domain will expire, but whois domain records can have different format... Our structured (parsed) data helping to find necessary information, so customer can do not worry where to find domain's expiration date. The best way to understand how it working - try different domains and modes on online whois lookup demo, it's free tool. |
Structure of parsed whois data
|
| You can also see XML data that was downloaded through our Whois API: amd.com, intel.com, opencourt.us, eonline.ca. |
|
Description of fields and data format
| body | including all data |
|---|---|
| body.whois_record | consist of raw whois data that fetched from TLD registrar whois server |
| body.domain.registered | information about domain registration - "yes" or "no" |
| body.domain.name | requested domain name (example.com, red.com,...) |
| body.domain.status | domain status in registrar database(ok, pending,...) |
| body.domain.created | date when domain was registered (YYYY-MM-DD) |
| body.domain.created_timestamp | time and timezone related to "created" (HH:MM:SS or HH:MM:SS TIMEZONE) (added 13 Feb 2017) |
| body.domain.changed | date when domain record was changed (YYYY-MM-DD) |
| body.domain.changed_timestamp | time and timezone related to "changed" (HH:MM:SS or HH:MM:SS TIMEZONE) (added 13 Feb 2017) |
| body.domain.expires | date when domain will expire (YYYY-MM-DD) |
| body.domain.expires_timestamp | time and timezone related to "expires" (HH:MM:SS or HH:MM:SS TIMEZONE) (added 13 Feb 2017) |
| body.domain.nserver | list of NS servers linked with this domain (ns1.name.com, ns2.name.com,...) |
| body.domain.sponsor | domain's registrar organization (whois.name.com, whois.godaddy.com,...) |
| body.domain.handle | handle of registrar |
| body.domain.contact_email | contact email taken from one of records: owner, admin ,tech, billing (me@example.com) |
| body.domain.contact_person | contact name or organization taken from same record as contact_email (John Parker, Deposit Inc.) |
| body.owner.name | name of domain owner/registrant (John Parker, Jack Perison,...) |
| body.owner.organization | organization that is owner/registrant of domain (Deposit Inc., Public Seller,...) |
| body.owner.handle | handle of registrant |
| body.owner.email | email address of registrant |
| body.owner.phone | phone number of registrant |
| body.owner.fax | fax number of registrant |
| body.owner.address.not_parsed | part of address that was not assigned as street, zip, city, state, country |
| body.owner.address.street | owner's street |
| body.owner.address.city | owner's city |
| body.owner.address.state | owner's state |
| body.owner.address.zip | owner's zip code |
| body.owner.address.country | owner's country name or code |
| body.owner.raw_text | original raw data from owner's block |
| body.admin | same data structure as domain.owner but this data about domain's administrator |
| body.tech | same data structure as domain.owner but about technical responsible person/organization |
| body.billing | same data structure as domain.owner but about billing responsible person/organization |
|
Notice: sometimes raw whois data can be filled wrong, so parsed data can be incorrect according to incorrect raw data, our service not responsible if such data will be parsed incorrect. (example of wrong whois data) Notice: we do not responsible for incorrect data parsing if contacts or address information going as raw text and without field names. (example of data without field names) |
 | 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.