# Zone Check

Zone Check offers a rapid, preliminary check for domain availability by leveraging cached zone file data.  Ideal for large-batch queries, it provides a high confidence indication of a domain's availability significantly faster than live registry checks.  For definitive, real-time availability and pricing, you can follow up with the standard Check Availability call.
The API first validates each submitted domain. Invalid domains are filtered out, and their count is returned in the removed field of the response.  If no valid domains remain after this process, the API returns a  response.
 The cached zone files used for this check are refreshed twice daily based on the latest available data from the registries.

Endpoint: POST /core/v1/zonecheck
Version: 1.3.1
Security: BasicAuth

## Request fields (application/json):

  - `domainNames` (array, required)
    Array of domains to check

## Response 200 fields (application/json):

  - `results` (array, required)

  - `results.domainName` (string, required)
    The domain name that was checked
    Example: "example.com"

  - `results.available` (boolean,null, required)
    If the domain is potentially available for purchase after checking for it's presense in the DNZ zone files.

  - `total` (number, required)
    Total number of records checked
    Example: 5

  - `removed` (number)
    Total number of domains removed from the check because they are invalid
    Example: 1

## Response 400 fields (application/json):

  - `message` (string)
    A human-readable message providing more details about the error
    Example: "Bad Request"

  - `details` (string,null)
    Additional context or information about the error
    Example: "'domainName' cannot be null"

## Response 415 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error
    Example: "The 'Content-Type' header must be 'application/json' for this request."

## Response 422 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error
    Example: "Unprocessable Entity"

## Response 429 fields (application/json):

  - `message` (string)
    A human-readable message providing more details about the error
    Example: "Rate Limit Exceeded"

## Response 500 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error.
    Example: "Internal Server Error"

  - `details` (string,null)
    Additional context or information about the error.
    Example: "Something went wrong."