Domain WHOIS Examples by TLD · Example 305 of 992 in Generic

WHOIS for .expert (nic.expert)

GEThttps://api.deepinfo.com/v1/lookup/whois

The WHOIS record of nic.expert, in the .expert registry's format.

TLD: .expert
Type: generic

.expert is a generic top-level domain.

The example requests the WHOIS record of nic.expert, the registry's own domain by convention, so the response shows the .expert registry's WHOIS format: compare raw, the text as the WHOIS server returned it, with parsed, the same record in Deepinfo's fields.

Request

curl

curl 'https://api.deepinfo.com/v1/lookup/whois?domain=nic.expert' \
  -H 'apikey: YOUR_API_KEY' \
  -H 'Accept: application/json'

Python

import requests

url = "https://api.deepinfo.com/v1/lookup/whois"

params = {
    "domain": "nic.expert"
}

headers = {
    "apikey": "YOUR_API_KEY",
    "Accept": "application/json"
}

response = requests.get(url, params=params, headers=headers)
response.raise_for_status()
print(response.json())

JavaScript

const url = "https://api.deepinfo.com/v1/lookup/whois?domain=nic.expert";

const response = await fetch(url, {
  method: "GET",
  headers: {
    "apikey": "YOUR_API_KEY",
    "Accept": "application/json"
  },
});

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

package main

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

func main() {
	req, err := http.NewRequest("GET", "https://api.deepinfo.com/v1/lookup/whois?domain=nic.expert", nil)
	if err != nil {
		panic(err)
	}
	req.Header.Set("apikey", "YOUR_API_KEY")
	req.Header.Set("Accept", "application/json")

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()

	body, err := io.ReadAll(res.Body)
	if err != nil {
		panic(err)
	}
	fmt.Println(string(body))
}

Java

import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;

public class Main {
    public static void main(String[] args) throws Exception {
        HttpRequest request = HttpRequest.newBuilder()
            .uri(URI.create("https://api.deepinfo.com/v1/lookup/whois?domain=nic.expert"))
            .header("apikey", "YOUR_API_KEY")
            .header("Accept", "application/json")
            .GET()
            .build();

        HttpResponse<String> response = HttpClient.newHttpClient()
            .send(request, HttpResponse.BodyHandlers.ofString());

        System.out.println(response.body());
    }
}

using System;
using System.Net.Http;

using var client = new HttpClient();

var request = new HttpRequestMessage(HttpMethod.Get, "https://api.deepinfo.com/v1/lookup/whois?domain=nic.expert");
request.Headers.Add("apikey", "YOUR_API_KEY");
request.Headers.Add("Accept", "application/json");

using var response = await client.SendAsync(request);
Console.WriteLine(await response.Content.ReadAsStringAsync());

PHP

<?php

$curl = curl_init();

curl_setopt_array($curl, [
    CURLOPT_URL => 'https://api.deepinfo.com/v1/lookup/whois?domain=nic.expert',
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'apikey: YOUR_API_KEY',
        'Accept: application/json',
    ],
]);

$response = curl_exec($curl);

if ($response === false) {
    throw new RuntimeException(curl_error($curl));
}

echo $response . PHP_EOL;

Ruby

require 'net/http'
require 'uri'

uri = URI('https://api.deepinfo.com/v1/lookup/whois?domain=nic.expert')

request = Net::HTTP::Get.new(uri)
request['apikey'] = 'YOUR_API_KEY'
request['Accept'] = 'application/json'

response = Net::HTTP.start(uri.hostname, uri.port, use_ssl: uri.scheme == 'https') do |http|
  http.request(request)
end

puts response.body

Response

200 OK · application/json

Shortened for this page: raw: first 4,000 of 9,509 characters

Response Body

{
  "domain_name": "nic.expert",
  "raw": "{\n  \"rdapConformance\": [\n    \"rdap_level_0\",\n    \"icann_rdap_response_profile_1\",\n    \"icann_rdap_technical_implementation_guide_1\",\n    \"redacted\"\n  ],\n  \"notices\": [\n    {\n      \"title\": \"Terms of Service\",\n      \"description\": [\n        \"Access to RDAP information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or, if the record pertains to a TLD not operated by Identity Digital, then the corresponding primary Registry Operator for informational purposes only, and neither Identity Digital nor the Registry Operator guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Identity Digital, a Registrar, or Registry Operator except as reasonably necessary to register domain names or modify existing registrations. When using the RDAP service, please consider the following: the RDAP service is not a replacement for standard EPP commands to the SRS service. RDAP is not considered authoritative for registered domain objects. The RDAP service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the RDAP services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of RDAP service access. Abuse of the RDAP system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the RDAP records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to the data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/ Identity Digital Inc. and, if applicable, the primary Registry Operators reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.\"\n      ],\n      \"links\": [\n        {\n          \"value\": \"https://rdap.identitydigital.services/rdap/domain/nic.expert\",\n          \"rel\": \"terms-of-service\",\n          \"href\": \"https://www.identity.digital/policies/rdds-access-policy\",\n          \"type\": \"text/html\"\n        }\n      ]\n    },\n    {\n      \"title\": \"Status Codes\",\n      \"description\": [\n        \"For more information on domain status codes, please visit https://icann.org/epp\"\n      ],\n      \"links\": [\n        {\n          \"value\": \"https://rdap.identitydigital.services/rdap/domain/nic.expert\",\n          \"rel\": \"glossary\",\n          \"href\": \"https://icann.org/epp\",\n          \"type\": \"application/rdap+json\"\n        }\n      ]\n    },\n    {\n      \"title\": \"RDDS Inaccuracy Complaint Form\",\n      \"description\": [\n        \"URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf\"\n      ],\n      \"links\": [\n        {\n          \"value\": \"https://rdap.identitydigital.services/rdap/domain/nic.expert\",\n          \"rel\": \"help\",\n          \"href\": \"https://icann.org/wicf\",\n          \"type\": \"application/rdap+json\"\n        }\n      ]\n    }\n  ],\n  \"ldhName\": \"nic.expert\",\n…",
  "parsed": {
    "uid": "2026-08-12T10:04:10.300000+00:00",
    "create_date": "2013-12-04T18:38:46Z",
    "update_date": "2026-08-12T10:04:10Z",
    "expiry_date": "2026-12-04T18:38:46Z",
    "registrar": "registry operator acts as registrar (9999)",
    "registrant": {
      "name": null,
      "organization": null,
      "street": null,
      "city": null,
      "state": null,
      "postal_code": null,
      "country": null,
      "phone": null,
      "email": null
    },
    "name_servers": [
      "v0n0.nic.expert",
      "v0n1.nic.expert",
      "v0n2.nic.expert",
      "v0n3.nic.expert",
      "v2n0.nic.expert",
      "v2n1.nic.expert"
    ],
    "domain_status": [
      "serverdeleteprohibited",
      "servertransferprohibited",
      "serverupdateprohibited"
    ],
    "whois_server": null
  },
  "check_date": "2026-09-23T15:16:59Z",
  "parse_code": null
}

The raw field of this response, line by line.

Raw WHOIS Text

{
  "rdapConformance": [
    "rdap_level_0",
    "icann_rdap_response_profile_1",
    "icann_rdap_technical_implementation_guide_1",
    "redacted"
  ],
  "notices": [
    {
      "title": "Terms of Service",
      "description": [
        "Access to RDAP information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or, if the record pertains to a TLD not operated by Identity Digital, then the corresponding primary Registry Operator for informational purposes only, and neither Identity Digital nor the Registry Operator guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Identity Digital, a Registrar, or Registry Operator except as reasonably necessary to register domain names or modify existing registrations. When using the RDAP service, please consider the following: the RDAP service is not a replacement for standard EPP commands to the SRS service. RDAP is not considered authoritative for registered domain objects. The RDAP service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the RDAP services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of RDAP service access. Abuse of the RDAP system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the RDAP records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to the data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/ Identity Digital Inc. and, if applicable, the primary Registry Operators reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy."
      ],
      "links": [
        {
          "value": "https://rdap.identitydigital.services/rdap/domain/nic.expert",
          "rel": "terms-of-service",
          "href": "https://www.identity.digital/policies/rdds-access-policy",
          "type": "text/html"
        }
      ]
    },
    {
      "title": "Status Codes",
      "description": [
        "For more information on domain status codes, please visit https://icann.org/epp"
      ],
      "links": [
        {
          "value": "https://rdap.identitydigital.services/rdap/domain/nic.expert",
          "rel": "glossary",
          "href": "https://icann.org/epp",
          "type": "application/rdap+json"
        }
      ]
    },
    {
      "title": "RDDS Inaccuracy Complaint Form",
      "description": [
        "URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"
      ],
      "links": [
        {
          "value": "https://rdap.identitydigital.services/rdap/domain/nic.expert",
          "rel": "help",
          "href": "https://icann.org/wicf",
          "type": "application/rdap+json"
        }
      ]
    }
  ],
  "ldhName": "nic.expert",
…

Content-Type: application/json
ratelimit-limit: 10
ratelimit-remaining: 8
ratelimit-reset: 1
x-ratelimit-limit-second: 10
x-ratelimit-remaining-second: 8
deepinfo-request-id: 5f0c6a8e-1b2d-4c3e-9f4a-7b8c9d0e1f2a

Request

What this example sends. Every parameter is documented on Domain WHOIS; the exact request is in the code panel.

Parameter	Value
`domain`query	`nic.expert`

Reference updated September 24, 2026

Request

Related Examples