-1.png?height=120&name=Logo%20inline%20notagline%20(1)-1.png)
Our WHOIS and WHOIS-enriched products use retry mechanisms to improve data coverage. The system makes additional attempts when initial requests return incomplete or no data, ensuring more complete results.
Our WHOIS and WHOIS-enriched products benefit from retry mechanisms, either at the API request level or through backend processing, during which the system automatically makes additional attempts to collect WHOIS or domain data if the initial request is incomplete or unavailable. This maximizes data completeness while avoiding unnecessary charges.For WHOIS API and Bulk WHOIS API, retry behavior depends on the selected protocol mode. In Auto protocol mode, the system retries up to three times via WHOIS and, if needed, up to another three times via RDAP. In WHOIS protocol mode or RDAP protocol mode, the system retries up to three times for the chosen protocol. If data is retrieved, the parsed WHOIS record is returned; if all attempts fail, the result is marked with errorFlag = NO_DATA and no API credits are charged.
For the Newly Registered Domains (NRD2) feed, retries occur when the data_flag is INCOMPLETE_DATA or NO_DATA. Each candidate can be retried up to four times, with a 24-hour delay between attempts, while remaining in the zone files until a final status is confirmed.
For the Newly Registered Domains (NRD2) feed, retries occur when the data_flag is INCOMPLETE_DATA or NO_DATA. Each candidate can be retried up to four times, with a 24-hour delay between attempts, while remaining in the zone files until a final status is confirmed.