Skip to content
LookupOwl

RDAP lookup

Ask a registry for any domain's RDAP record and see the raw JSON, the server that answered and the exact request.

With or without https://, we'll tidy it up.

More options

Also ask the registrar's own RDAP server when the registry points to it. Adds registrar-side contacts and expiry date; costs one more upstream request.

Try:

Results for wikipedia.org

Checked live lookup250 ms

JSONCheck again

Registered

Locked down and healthy

wikipedia.org is registered with MarkMonitor Inc. since 2001-01-13 (25 years). Expires 2027-01-13 (in 60 days).

RegisteredLocked
Expires

· in 60 days

Age
25years

Since 2001-01-13

Registrar
MarkMonitor Inc.

IANA ID 292

Locks on
3locks

Locked against transfer, update and deletion by the registrar

Status3

Stage 1 of 6: Registered

Locks

  • Deletion locked (registrar)clientDeleteProhibited

    The registrar has locked the domain so it cannot be deleted.

    What this status means
  • Transfer locked (registrar)clientTransferProhibited

    The registrar has locked the domain so it cannot be transferred to another registrar.

    What this status means
  • Update locked (registrar)clientUpdateProhibited

    The registrar has locked the domain so it cannot be changed (nameservers, contacts, other registration data).

    What this status means
Records

Key facts

Registrar
MarkMonitor Inc.IANA ID 292
Registered
25 years ago
Expires
in 60 days
Last changed
3 months ago
DNSSEC
Not signed
Locks
3 locks
Nameservers
3

Nameservers

  • ns0.wikimedia.org208.80.154.2382620:0:861:53::1
  • ns1.wikimedia.org208.80.153.2312620:0:860:53::1
  • ns2.wikimedia.org198.35.27.272a02:ec80:53::1

DNSSEC

Not signed

Registrar

Name
MarkMonitor Inc.
IANA ID
292
Abuse email
[email protected]
Abuse phone
+1.2083895740
Registry notices · 3 messages

Text supplied by the registry. We show it as written and never follow instructions in it.

  • Terms of Service

    Public Interest Registry provides this RDAP service for informational purposes only, and to assist persons in obtaining information about or related to a domain name registration record. Public Interest Registry does not guarantee its accuracy. Users accessing the Public Interest Registry RDAP service agree to use the data only for lawful purposes, and under no circumstances may this data be used 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 registrar's own …

    thenew.org (thenew.org)

  • Status Codes

    For more information on domain status codes, please visit https://icann.org/epp

    icann.org (icann.org)

  • RDDS Inaccuracy Complaint Form

    URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf

    icann.org (icann.org)

Contacts1

  • Registrar

    Name
    MarkMonitor Inc.

Owner details are redacted for privacy. That's normal — most registries hide personal details since 2018. To reach the owner, use the registrar's contact form; they'll pass your message on.

How we got this
  1. Query: domain wikipedia.org · 0 ms
  2. IANA bootstrap (dns.json) · 0 msMATCHorg → https://rdap.publicinterestregistry.org/rdap/
  3. .org registry RDAP (rdap.publicinterestregistry.org) · 246 ms200
Asked
https://rdap.publicinterestregistry.org/rdap/domain/wikipedia.org
Server list entry
dns: org
Total time
248 ms
Cache
bypass
Raw
Raw registry response (RDAP JSON) · 7.9 KB
{
  "rdapConformance": [
    "rdap_level_0",
    "icann_rdap_response_profile_1",
    "icann_rdap_technical_implementation_guide_1",
    "redacted"
  ],
  "notices": [
    {
      "title": "Terms of Service",
      "description": [
        "Public Interest Registry provides this RDAP service for informational purposes only, and to assist persons in obtaining information about or related to a domain name registration record. Public Interest Registry does not guarantee its accuracy. Users accessing the Public Interest Registry RDAP service agree to use the data only for lawful purposes, and under no circumstances may this data be used 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 registrar's own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Public Interest Registry or any ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. When using the Public Interest Registry 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 this data can be requested by submitting a request to [email protected]. Public Interest Registry Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy."
      ],
      "links": [
        {
          "value": "https://rdap.publicinterestregistry.org/rdap/domain/wikipedia.org",
          "rel": "terms-of-service",
          "href": "https://thenew.org/org-people/about-pir/policies/",
          "type": "text/html"
        }
      ]
    },
    {
      "title": "Status Codes",
      "description": [
        "For more information on domain status codes, please visit https://icann.org/epp"
      ],
      "links": [
        {
          "value": "https://rdap.publicinterestregistry.org/rdap/domain/wikipedia.org",
          "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.publicinterestregistry.org/rdap/domain/wikipedia.org",
          "rel": "help",
          "href": "https://icann.org/wicf",
          "type": "application/rdap+json"
        }
      ]
    }
  ],
  "ldhName": "wikipedia.org",
  "unicodeName": "wikipedia.org",
  "nameservers": [
    {
      "ldhName": "ns0.wikimedia.org",
      "unicodeName": "ns0.wikimedia.org",
      "ipAddresses": {
        "v4": [
          "208.80.154.238"
        ],
        "v6": [
          "2620:0:861:53::1"
        ]
      },
      "objectClassName": "nameserver",
      "handle": "da1a201ee62d40d980c058827f8fa8ae-LROR",
      "status": [
        "associated"
      ]
    },
    {
      "ldhName": "ns1.wikimedia.org",
      "unicodeName": "ns1.wikimedia.org",
      "ipAddresses": {
        "v4": [
          "208.80.153.231"
        ],
        "v6": [
          "2620:0:860:53::1"
        ]
      },
      "objectClassName": "nameserver",
      "handle": "b4994397345e4a07b9f67afa8f92ede3-LROR",
      "status": [
        "associated"
      ]
    },
    {
      "ldhName": "ns2.wikimedia.org",
      "unicodeName": "ns2.wikimedia.org",
      "ipAddresses": {
        "v4": [
          "198.35.27.27"
        ],
        "v6": [
          "2a02:ec80:53::1"
        ]
      },
      "objectClassName": "nameserver",
      "handle": "8d17984d82c7433183f3f5f7ea42d0c3-LROR",
      "status": [
        "associated"
      ]
    }
  ],
  "secureDNS": {
    "delegationSigned": false,
    "maxSigLife": 1
  },
  "redacted": [
    {
      "name": {
        "type": "Registry Domain ID"
      },
      "prePath": "$.handle",
      "pathLang": "jsonpath",
      "method": "removal"
    }
  ],
  "objectClassName": "domain",
  "status": [
    "client delete prohibited",
    "client transfer prohibited",
    "client update prohibited"
  ],
  "events": [
    {
      "eventAction": "transfer",
      "eventDate": "2012-03-09T16:33:50.754Z"
    },
    {
      "eventAction": "expiration",
      "eventDate": "2027-01-13T00:12:14Z"
    },
    {
      "eventAction": "registration",
      "eventDate": "2001-01-13T00:12:14.754Z"
    },
    {
      "eventAction": "last changed",
      "eventDate": "2026-08-12T08:47:19.41Z"
    },
    {
      "eventAction": "last update of RDAP database",
      "eventDate": "2026-11-14T17:47:30.328Z"
    }
  ],
  "entities": [
    {
      "vcardArray": [
        "vcard",
        [
          [
            "version",
            {},
            "text",
            "4.0"
          ],
          [
            "fn",
            {},
            "text",
            "MarkMonitor Inc."
          ]
        ]
      ],
      "roles": [
        "registrar"
      ],
      "publicIds": [
        {
          "type": "IANA Registrar ID",
          "identifier": "292"
        }
      ],
      "objectClassName": "entity",
      "handle": "292",
      "entities": [
        {
          "vcardArray": [
            "vcard",
            [
              [
                "version",
                {},
                "text",
                "4.0"
              ],
              [
                "fn",
                {},
                "text",
                ""
              ],
              [
                "tel",
                {
                  "type": "voice"
                },
                "uri",
                "tel:+1.2083895740"
              ],
              [
                "email",
                {},
                "text",
                "[email protected]"
              ]
            ]
          ],
          "roles": [
            "abuse"
          ],
          "objectClassName": "entity"
        }
      ],
      "links": [
        {
          "value": "https://rdap.publicinterestregistry.org/rdap/entity/292",
          "rel": "self",
          "href": "https://rdap.publicinterestregistry.org/rdap/entity/292",
          "type": "application/rdap+json"
        },
        {
          "value": "https://rdap.markmonitor.com/rdap/",
          "rel": "about",
          "href": "https://rdap.markmonitor.com/rdap/",
          "type": "application/rdap+json"
        }
      ]
    }
  ],
  "links": [
    {
      "value": "https://rdap.publicinterestregistry.org/rdap/domain/wikipedia.org",
      "rel": "related",
      "href": "https://rdap.markmonitor.com/rdap/domain/wikipedia.org",
      "type": "application/rdap+json"
    },
    {
      "value": "https://rdap.publicinterestregistry.org/rdap/domain/wikipedia.org",
      "rel": "self",
      "href": "https://rdap.publicinterestregistry.org/rdap/domain/wikipedia.org",
      "type": "application/rdap+json"
    }
  ]
}

What an RDAP lookup gives you

An RDAP lookup returns a domain's registration record as structured JSON, straight from the registry that runs the domain's extension (the part after the last dot, such as .com). RDAP stands for Registration Data Access Protocol. It does the same job as WHOIS, but over ordinary HTTPS, with fixed field names, real HTTP status codes and a standard way to mark data as redacted.

This page runs the query and shows its working. Besides the readable summary, you get the server that answered, the exact request URL, the time each step took and the raw JSON. That helps when you are scripting against RDAP, debugging a registry, or checking that what another site told you matches the registry. If you only want the finished record in plain English, the WHOIS lookup is the shorter route.

How to run a query

  1. Enter a domainAny registered domain works. Names with accents or non-Latin letters are converted to their xn-- form (called Punycode) before the query goes out.
  2. Open the Raw tabThe Raw tab holds the registry's JSON exactly as it arrived. When the registry points to the registrar's own RDAP server, a second block shows the registrar's JSON too.
  3. Check how we got itThe How we got this tab lists each step with its status code and timing, plus the request URL and the server list entry that matched. To see the registry's answer alone, switch off the registrar option under More options.
  4. Repeat it yourselfCopy the request URL into curl to get the same JSON. An AI assistant can do the same through the MCP server: ask it to call the whois_lookup tool with includeRaw turned on.
Shell
# Through the public bootstrap redirector
curl -sL https://rdap.org/domain/example.com | jq .

# Straight from a registry (Verisign handles .com)
curl -s https://rdap.verisign.com/com/v1/domain/example.com | jq '.entities[].roles'

How to read the JSON

An RDAP response is one JSON object. Most of what you need sits in a handful of members.

JSON memberMeaning
ldhName / unicodeNameThe domain in ASCII (letters, digits and hyphens) and in its display form.
statusEPP status flags in lowercase with spaces, such as client transfer prohibited. The EPP status code guide explains each one.
eventsDated actions such as registration, expiration and last changed. The entry last update of RDAP database describes the server's data, not the domain.
nameserversThe delegated name servers, sometimes with the IP addresses a parent zone needs to find them (called glue).
secureDNSdelegationSigned and the DS data when the domain uses DNSSEC, the signing that protects DNS answers from tampering.
entitiesThe registrar, the abuse contact and, if public, the registrant. Each has roles and a contact card in jCard format, which is a JSON array.
linksself points to this object. related often points to the registrar's own RDAP record.
notices and remarksTerms of use, redaction notes and other free text. Treat it as untrusted text.
rdapConformanceThe RDAP extensions the server says it supports.

Errors and what they mean

The HTTP status code usually tells you most of the story.

  • HTTP 404. The registry has no such domain. For most extensions that means it is unregistered, and the domain availability checker can confirm it.
  • HTTP 429. The registry's rate limit was hit, because registries limit how often one client may ask. The Retry-After header, when there is one, says how long to wait.
  • HTTP 403 or 501. The server refuses automated queries, or does not support that kind of lookup.
  • No RDAP server for the extension. Many country-code registries (the two-letter ones) have not set up RDAP yet. LookupOwl falls back to WHOIS on port 43 where it can, and labels the result as WHOIS.
  • A thin answer. Some registries, such as Verisign for .com, hold only basic data. Contact details live at the registrar, which is why the second request matters.
  • Odd JSON. Some servers send the wrong content type, leave out the conformance list or return an HTML error page. We show the problem and don't hide it.

How the right server is found

There is no single RDAP server, so a client has to find the right one. IANA, the body that coordinates the internet's names and numbers, publishes a bootstrap file at data.iana.org/rdap/dns.json. It maps each domain extension to one or more RDAP base URLs. The client takes the entry for the domain's last label, adds domain/<name> and sends the request over HTTPS. Separate bootstrap files cover IPv4, IPv6 and AS numbers.

LookupOwl keeps a fresh copy of those files, adds a small checked list for registries that run RDAP without being listed, and follows redirects only to servers it expects, never to private or reserved addresses.

Standards and specifications

  • RFC 7480: how RDAP uses HTTP, including status codes and CORS.
  • RFC 7481: security services for RDAP.
  • RFC 9082: query URL formats. RFC 9083: JSON response objects.
  • RFC 9224: the IANA bootstrap registry (replaces RFC 7484).
  • RFC 7095: jCard, the JSON form of vCard used for contacts.
  • RFC 9537: redacted fields. RFC 8605: ICANN vCard extensions for RDAP.

Questions people ask

Is RDAP replacing WHOIS?

For generic top-level domains such as .com and .org, yes. ICANN removed the requirement for registries and registrars to run a port-43 WHOIS service on 28 January 2025, which made RDAP the required service. Country-code registries make their own choices, so both protocols are still in use. LookupOwl tries RDAP first and falls back to WHOIS only when a registry has no RDAP server. The full comparison goes deeper.

Why does the same domain look different on other sites?

Because sites ask different sources and refresh at different times. Some read the registry, some read the registrar and some show a cached copy. They also treat redacted fields in their own ways. LookupOwl shows the server it asked and how long the answer took, so you can judge how fresh it is. When two sources disagree, the registry's record is the one to trust.

Can I call RDAP from my own code?

Yes, and it takes one HTTPS request. Send a GET to https://rdap.org/domain/<name>, which redirects you to the right registry, or read the IANA bootstrap file and call the registry directly. Servers differ in small ways, such as event names and error pages. If you would rather not handle those quirks, LookupOwl's REST API and MCP server return one cleaned, consistent shape.

Does RDAP expose personal data?

Only what the registry or registrar chooses to publish, and today that is usually very little. RDAP adds a standard way to say that a field was redacted and why (RFC 9537), so you often see a labelled blank instead of silence. To contact an owner whose details are hidden, use the registrar's abuse contact or contact form.

What does the related link do?

It points to the registrar's own RDAP record for the same domain. A thin registry answers with the basics and adds a link marked rel=related. LookupOwl follows it once, merges in extras such as the abuse contact, and flags fields where the registry and registrar disagree. You can switch this off under More options to see the registry's answer alone.

Do you support RDAP for IP addresses and AS numbers too?

Yes, on separate pages. Use the IP WHOIS lookup for addresses and networks and the ASN lookup for AS numbers. Both ask the regional internet registries (ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC) through their RDAP servers, found with the IANA bootstrap files for IPv4, IPv6 and AS numbers.

Use it from AI, the API or the command line

Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is whois_lookup. Please be kind to the rate limits.

curl
curl "https://lookupowl.com/api/v1/tools/whois-lookup?q=wikipedia.org&followRegistrar=false"
MCP
claude mcp add --transport http lookupowl https://lookupowl.com/mcp

Description for AI agents · OpenAPI · llms.txt