Fully Qualified Domain API

GET Endpoint

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

Code Examples

Here are examples of how to call the Fully Qualified Domain API in different programming languages:

curl -X GET \
  "https://api.apiverve.com/v1/fullyqualifieddomain?ip=199.30.24.0" \
  -H "X-API-Key: your_api_key_here"

const response = await fetch('https://api.apiverve.com/v1/fullyqualifieddomain?ip=199.30.24.0', {
  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/fullyqualifieddomain?ip=199.30.24.0', 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/fullyqualifieddomain?ip=199.30.24.0', 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/fullyqualifieddomain?ip=199.30.24.0');
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/fullyqualifieddomain?ip=199.30.24.0", 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/fullyqualifieddomain?ip=199.30.24.0')
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/fullyqualifieddomain?ip=199.30.24.0");
        response.EnsureSuccessStatusCode();

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

Authentication

The Fully Qualified Domain 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 Fully Qualified Domain API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Fully Qualified Domain API:

Response

The Fully Qualified Domain API returns responses in JSON, XML, YAML, and CSV formats:

Example Responses

{
  "status": "ok",
  "error": null,
  "data": {
    "ip": "199.30.24.0",
    "baseDomain": "msn.com",
    "fqdn": "msnbot-199-30-24-0.search.msn.com",
    "tld": "com",
    "subdomain": "msnbot-199-30-24-0.search",
    "domainLevels": 5,
    "detected": true
  }
}

<?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>
    <ip>199.30.24.0</ip>
    <baseDomain>msn.com</baseDomain>
    <fqdn>msnbot-199-30-24-0.search.msn.com</fqdn>
    <tld>com</tld>
    <subdomain>msnbot-199-30-24-0.search</subdomain>
    <domainLevels>5</domainLevels>
    <detected>true</detected>
  </data>
</response>

status: ok
error: null
data:
  ip: 199.30.24.0
  baseDomain: msn.com
  fqdn: msnbot-199-30-24-0.search.msn.com
  tld: com
  subdomain: msnbot-199-30-24-0.search
  domainLevels: 5
  detected: true

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 Fully Qualified Domain API requests:

Learn more about request headers →

GraphQL AccessALPHA

Access Fully Qualified Domain through GraphQL to combine it with other API calls in a single request. Query only the fully qualified domain 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 {
  fullyqualifieddomain(
    input: {
      ip: "199.30.24.0"
    }
  ) {
    ip
    baseDomain
    fqdn
    tld
    subdomain
    domainLevels
    detected
  }
}

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

CORS Support

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

Browser Usage: You can call Fully Qualified Domain 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

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

Learn more about rate limiting →

Rate Limit Headers

When rate limits apply, each Fully Qualified Domain response includes headers to help you track your usage:

Handling Rate Limits

Free Plan: When you exceed your rate limit, Fully Qualified Domain 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 Fully Qualified Domain:

• Monitor the rate limit headers to track your Fully Qualified Domain usage (Free plan only)
• Cache fully qualified domain responses where appropriate to reduce API calls
• Upgrade to Pro or Mega for guaranteed no-throttle Fully Qualified Domain performance

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

Error Codes

The Fully Qualified Domain 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 Fully Qualified Domain with SDKs

Get started quickly with official Fully Qualified Domain 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 Fully Qualified Domain with No-Code API Tools

Connect the Fully Qualified Domain API to your favorite automation platform without writing code. Build workflows that leverage fully qualified domain data across thousands of apps.

ZapierConnect Fully Qualified Domain to 6,000+ apps

MakeBuild visual fully qualified domain workflows

PipedreamCode-friendly fully qualified domain automation

n8nSelf-host your fully qualified domain workflows

Power AutomateUse Fully Qualified Domain in Microsoft 365

Frequently Asked Questions

People who used this also used...

Based on your interest in Fully Qualified Domain, you might also like these APIs:

WHOIS Lookup

Whois Lookup is a simple tool for checking the registration of a domain name. It returns the name and contact information of the domain owner, the domain registrar, and more.

10 credits per call

URL Unshortener

URL Unshortener is a simple tool for unshortening shortened URLs. It returns the original URL before it was shortened.

5 credits per call

URL Title

URL Title is a simple tool for getting the title of a web page. It returns the title of the web page based on the URL provided.

5 credits per call