TLD Lookup API

GET Endpoint

https://api.apiverve.com/v1/tldlookup

Code Examples

Here are examples of how to call the TLD Lookup API in different programming languages:

curl -X GET \
  "https://api.apiverve.com/v1/tldlookup" \
  -H "X-API-Key: your_api_key_here"

const response = await fetch('https://api.apiverve.com/v1/tldlookup', {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
});

const data = await response.json();
console.log(data);

import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

response = requests.get('https://api.apiverve.com/v1/tldlookup', headers=headers)

data = response.json()
print(data)

const https = require('https');
const url = require('url');

const options = {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
};

const req = https.request('https://api.apiverve.com/v1/tldlookup', options, (res) => {
  let data = '';
  res.on('data', (chunk) => data += chunk);
  res.on('end', () => console.log(JSON.parse(data)));
});

req.end();

<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/tldlookup');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'GET');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'X-API-Key: your_api_key_here',
    'Content-Type: application/json'
]);

$response = curl_exec($ch);
curl_close($ch);

$data = json_decode($response, true);
print_r($data);

?>

package main

import (
    "fmt"
    "io"
    "net/http"

)

func main() {
    req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/tldlookup", nil)

    req.Header.Set("X-API-Key", "your_api_key_here")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}

require 'net/http'
require 'json'

uri = URI('https://api.apiverve.com/v1/tldlookup')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

request = Net::HTTP::Get.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'

response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))

using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;

class Program
{
    static async Task Main(string[] args)
    {
        using var client = new HttpClient();
        client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");

        var response = await client.GetAsync("https://api.apiverve.com/v1/tldlookup");
        response.EnsureSuccessStatusCode();

        var responseBody = await response.Content.ReadAsStringAsync();
        Console.WriteLine(responseBody);
    }
}

Authentication

The TLD Lookup API requires authentication via API key. Include your API key in the request header:

X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the TLD Lookup API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the TLD Lookup API:

Response

The TLD Lookup API returns responses in JSON, XML, YAML, and CSV formats:

Example Responses

{
  "status": "ok",
  "error": null,
  "data": {
    "tld": "com",
    "found": true,
    "type": "generic",
    "organization": "VeriSign Global Registry Services"
  }
}

<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <tld>com</tld>
    <found>true</found>
    <type>generic</type>
    <organization>VeriSign Global Registry Services</organization>
  </data>
</response>

status: ok
error: null
data:
  tld: com
  found: true
  type: generic
  organization: VeriSign Global Registry Services

Response Structure

All API responses follow a consistent structure with the following fields:

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

Headers

Required and optional headers for TLD Lookup API requests:

Learn more about request headers →

GraphQL AccessALPHA

Access TLD Lookup through GraphQL to combine it with other API calls in a single request. Query only the tld lookup data you need with precise field selection, and orchestrate complex data fetching workflows.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

POST https://api.apiverve.com/v1/graphql

query {
  tldlookup(
    input: {
      tld: "com"
    }
  ) {
    tld
    found
    type
    organization
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The TLD Lookup API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call TLD Lookup directly from browser-based applications without proxy servers.

Browser Usage: You can call TLD Lookup directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.

Learn more about CORS support →

Rate Limiting

TLD Lookup API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all TLD Lookup users.

Learn more about rate limiting →

Rate Limit Headers

When rate limits apply, each TLD Lookup response includes headers to help you track your usage:

Handling Rate Limits

Free Plan: When you exceed your rate limit, TLD Lookup returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.

Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.

Best Practices for TLD Lookup:

• Monitor the rate limit headers to track your TLD Lookup usage (Free plan only)
• Cache tld lookup responses where appropriate to reduce API calls
• Upgrade to Pro or Mega for guaranteed no-throttle TLD Lookup performance

Note: TLD Lookup rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using TLD Lookup on Free tier.

Error Codes

The TLD Lookup API uses standard HTTP status codes to indicate success or failure:

Learn more about error handling →

Need help? Contact support with your X-Request-ID for assistance.

Integrate TLD Lookup with SDKs

Get started quickly with official TLD Lookup SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.

Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.

JitPack

Integrate TLD Lookup with No-Code API Tools

Connect the TLD Lookup API to your favorite automation platform without writing code. Build workflows that leverage tld lookup data across thousands of apps.

ZapierConnect TLD Lookup to 6,000+ apps

MakeBuild visual tld lookup workflows

PipedreamCode-friendly tld lookup automation

n8nSelf-host your tld lookup workflows

Power AutomateUse TLD Lookup in Microsoft 365

Frequently Asked Questions

People who used this also used...

Based on your interest in TLD Lookup, you might also like these APIs:

VPN Proxy Detector

VPN Detector is a simple tool for detecting VPN usage. It returns a boolean value indicating whether the IP address is using a VPN or not.

1 credit per call

USB Vendor Lookup

USB Vendor Lookup allows you to identify USB device manufacturers and products by their vendor ID and product ID. It uses the Linux USB ID Repository, which contains thousands of USB vendor and product identifiers.

1 credit per call

Tor Node Detector

Tor Detect is an API that checks whether a given IP address belongs to a known Tor exit node. Useful for security, access control, and analytics.

1 credit per call