mysqldump output structure

The foreign key representing the ID of the adminstrative contact for this whois_record. It references the primary key in contact table.

The administrative contact is a person in charge of the administrative dealings pertaining to the company of the domain name

The foreign key representing the ID of the registrant for this whois_record. It references the primary key in contact table.

The domain name registrant is the owner of the domain name.

They are the ones who are responsible for keeping the entire WHOIS contact information up to date

The foreign key representing the ID of the technical contact for this whois_record. It references the primary key in contact table.

The technical contact is the person in charge of all technical questions regarding a particular domain name

The foreign key representing the ID of the zone contact for this whois_record.

The zone contact is the person who tends to the technical aspects of maintaining the domain’s name server and resolver software, and database files

The foreign key representing the ID of the billing contact for this whois_record. It references the primary key in the contact table.

The billing contact is the person who is authorized by the registrant to receive the invoice for domain name registration and domain name renewal fees

Name servers or DNS servers for the domain name.

The most important function of DNS servers is the translation (resolution) of human-readable domain names and hostnames into the corresponding numeric Internet Protocol (IP) addresses

The foreign key representing the ID of the registry data. It references the primary key in registry_data table.

Registry Data is typically a WHOIS record from a domain name registry.

Every domain name usually has up to 2 WHOIS records, one from the registry and one from the registrar.

The whois_record table represents the data from the registrar, whilst the registry_data table represents WHOIS data collected from the WHOIS registry.

Note that registry_data and whois_record has almost identical data structures. Certain gTLDs (e.g. most of .com and .net) have both types of WHOIS data, while most ccTLDs have only registry_data.

Hence, it’s recommended to look under both whois_record and registry_data when searching for a piece of information (e.g. registrant, created_date)

The date when the WHOIS record was collected on whoisxmlapi.com;

Note that it is different from created_date of whois_record or registry_data tables.

The date when the WHOIS record was updated on whoismlxapi.com;

Note that it is different from updated_date of whois_record or registry_data tables

A bit mask indicating which fields have been parsed in the record;

a binary value of 1 at position i points to a non-empty value field at that position;

the fields from the least significant bit to the most significant one are following: "createdDate", "expiresDate", "referralURL" (exists in "registryData" only), "registrarName", "status", "updatedDate", "whoisServer" (exists in "registryData" only), "nameServers", "administrativeContact", "billingContact", "registrant", "technicalContact", and "zoneContact";

for example, parse code 3₁₀ (11₂) means that the only non-empty fields are "createdDate" and "expiresDate", and parse code 8₁₀ (1000₂) means that the only non-empty field is "registrarName".

if you need to ascertain that a WHOIS record contains ownership information, compare parse code to 0010000000000₂ (512₁₀). It stands for non-empty field "registrant"; To check the parse code value, use bit operators. (In MySQL it will be parse_code & 0010000000000₂ = 0010000000000₂)

• 0 - no data errors;
• 1 - incomplete data;
• 2 - missing WHOIS data, it means that the domain name has no WHOIS record in the registrar/registry;
• 3 - this domain name is a reserved word.