WHOIS API: Raw WHOIS data, exactly as served
The port‑43 record for any TLD that still answers, with nothing stripped or reformatted. Parse it your own way.
- The
whois_serverthat answered, on every response - Every line kept, notices and comments included
- A 422 that points to RDAP when a TLD has no port 43
1 credit per call, $0.001 at the base rate. 100 free credits to start.
vercel.com
Answered by whois.verisign-grs.com
Amazon Registrar, Inc.
registrar, read from the raw record
Domain Name: VERCEL.COM Registry Domain ID: 10966907_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.registrar.amazon Registrar URL: http://registrar.amazon.com Updated Date: 2026-05-16T15:54:35Z
- Created
- 4 Oct 1999
- Expires
- 4 Oct 2029
- Raw lines
- 55
What is the WHOIS API?
The WHOIS API returns the raw WHOIS record for a domain exactly as the registry’s port-43 server sent it, together with the name of the server that answered. It covers any TLD that still runs a WHOIS service, costs one credit per lookup, and hands off to RDAP with a free 422 where WHOIS is gone.
- Reviewed 29 Sep 2026
- Examples are real API responses
At a glance
- Endpoint
GET /domains/{domain}/whois- Authentication
- Bearer API key
- Price
- 1 credit · $0.001
- Free to start
- 100 credits on sign-up
- Response
- JSON, no envelope
- TLDs with a port-43 server mapped
- 881
- source of the server map, synced 24 Sep 2026
- IANA
- text, nothing parsed or reordered
- Verbatim
How the WHOIS API works
- 1
Send a domain
GET /; the input is reduced to its registrable root.domains/ {domain}/ whois - 2
The right server
The TLD’s port-43 server comes from IANA data plus registry-documented overrides, and is queried in its own wire format.
- 3
The text, untouched
You get
rawandwhois_server. A TLD without WHOIS returns 422 and costs nothing.
WHOIS vs RDAP
Two protocols for the same registration data. Both endpoints cost one credit; pick by what your code needs.
| Aspect | WHOIS APIThis page | RDAP API |
|---|---|---|
| Protocol | Plain text over TCP port 43 (RFC 3912) | JSON over HTTPS (RFC 9083) |
| Structure | Free text; labels vary by registry | Standard fields: status, events, entities, nameservers |
| For generic TLDs | Sunset by ICANN on 28 Jan 2025 | ICANN’s definitive source since 28 Jan 2025 |
| Coverage here | 881 TLDs with a port‑43 server | 1,202 TLDs natively, 1,373 with the WHOIS fallback |
| Best for | Archives, audits and parsers you already own | Applications that read fields |
WHOIS API use cases
What teams build with the WHOIS API, and the behaviour you can write code against.
What you can build
Registrar and EPP-status audits
Read the sponsoring registrar, IANA ID, and EPP status codes like clientTransferProhibited straight from the raw record, including registry-specific lines no structured parser standardizes.
Evidence-grade archives
Store the exact bytes a registry served alongside the
whois_serverthat answered, as a defensible snapshot for abuse reports, UDRP filings, or legal holds.Change monitoring by text diff
Pull the raw record on a schedule and diff the text to catch registrar transfers, nameserver moves, and expiry shifts the moment the registry publishes them.
What you can count on
Verbatim, never reshaped
The raw field is the exact bytes from the registry’s port-43 server, with no field extraction or normalization, so registrar-specific and free-text lines survive intact.
Names the source server
Every response returns the
whois_serverthat actually answered, so you can reproduce the query and cite where the text came from.Clean 422 handoff to RDAP
A TLD that no longer serves port-43 returns 422 with a message pointing to the /rdap endpoint, instead of a blank body you have to guess about.
Metered per call, refunded on failure
One credit per successful lookup. Upstream failures are refunded, and the Credits-Charged header reports each charge.
WHOIS API examples
Signed out, real responses captured from the API. Signed in, a live request on your own key, metered like any other call.
Showing real example responses. Sign in to run live requests; new accounts start with 100 free credits.
https://tabapi.com/api/v1/domains/vercel.com/whoisExample response: real capture, 29 Sep 2026; verbatim port-43 record.
Lifecycle
- Registered
- 4 Oct 1999
- 27 years ago
- Updated
- 16 May 2026
- 6 months ago
- Expires
- 4 Oct 2029
- in 2 years
Registration
- Registrar
- Amazon Registrar, Inc.IANA 468
- Registrar WHOIS
- whois.registrar.amazon
- Registry ID
- 10966907_DOMAIN_COM-VRSN
- Status
- client transfer prohibited
- Name servers
- a.zeit-world.co.uk
- b.zeit-world.org
- e.zeit-world.com
- f.zeit-world.net
- DNSSEC
- Unsigned
Raw record
- Domain Name: VERCEL.COM
- Registry Domain ID: 10966907_DOMAIN_COM-VRSN
- Registrar WHOIS Server: whois.registrar.amazon
- Registrar URL: http://registrar.amazon.com
- Updated Date: 2026-05-16T15:54:35Z
- Creation Date: 1999-10-04T19:30:47Z
- Registry Expiry Date: 2029-10-04T19:30:47Z
- Registrar: Amazon Registrar, Inc.
- Registrar IANA ID: 468
- Registrar Abuse Contact Email: trustandsafety@support.aws.com
- Registrar Abuse Contact Phone: +1.2024422253
- Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
- Name Server: A.ZEIT-WORLD.CO.UK
- Name Server: B.ZEIT-WORLD.ORG
- Name Server: E.ZEIT-WORLD.COM
- Name Server: F.ZEIT-WORLD.NET
{ "domain": "vercel.com", "whois_server": "whois.verisign-grs.com", "raw": "Domain Name: VERCEL.COM\r\n Registry Domain ID: 10966907_DOMAIN_COM-VRSN\r\n Registrar WHOIS Server: whois.registrar.amazon\r\n Registrar URL: http://registrar.amazon.com\r\n Updated Date: 2026-05-16T15:54:35Z\r\n Creation Date: 1999-10-04T19:30:47Z\r\n Registry Expiry Date: 2029-10-04T19:30:47Z\r\n Registrar: Amazon Registrar, Inc.\r\n Registrar IANA ID: 468\r\n Registrar Abuse Contact Email: trustandsafety@support.aws.com\r\n Registrar Abuse Contact Phone: +1.2024422253\r\n Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited\r\n Name Server: A.ZEIT-WORLD.CO.UK\r\n Name Server: B.ZEIT-WORLD.ORG\r\n Name Server: E.ZEIT-WORLD.COM\r\n Name Server: F.ZEIT-WORLD.NET\r\n DNSSEC: unsigned\r\n URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/\r\n>>> Last update of whois database: 2026-09-28T17:10:28Z <<<\r\n\r\nFor more information on Whois status codes, please visit https://icann.org/epp\r\n\r\nNOTICE: The expiration date displayed in this record is the date the\r\nregistrar's sponsorship of the domain name registration in the registry is\r\ncurrently set to expire. This date does not necessarily reflect the expiration\r\ndate of the domain name registrant's agreement with the sponsoring\r\nregistrar. Users may consult the sponsoring registrar's Whois database to\r\nview the registrar's reported date of expiration for this registration.\r\n\r\nTERMS OF USE: You are not authorized to access or query our Whois\r\ndatabase through the use of electronic processes that are high-volume and\r\nautomated except as reasonably necessary to register domain names or\r\nmodify existing registrations; the Data in VeriSign Global Registry\r\nServices' (\"VeriSign\") Whois database is provided by VeriSign for\r\ninformation purposes only, and to assist persons in obtaining information\r\nabout or related to a domain name registration record. VeriSign does not\r\nguarantee its accuracy. By submitting a Whois query, you agree to abide\r\nby the following terms of use: You agree that you may use this Data only\r\nfor lawful purposes and that under no circumstances will you use this Data\r\nto: (1) allow, enable, or otherwise support the transmission of mass\r\nunsolicited, commercial advertising or solicitations via e-mail, telephone,\r\nor facsimile; or (2) enable high volume, automated, electronic processes\r\nthat apply to VeriSign (or its computer systems). The compilation,\r\nrepackaging, dissemination or other use of this Data is expressly\r\nprohibited without the prior written consent of VeriSign. You agree not to\r\nuse electronic processes that are automated and high-volume to access or\r\nquery the Whois database except as reasonably necessary to register\r\ndomain names or modify existing registrations. VeriSign reserves the right\r\nto restrict your access to the Whois database in its sole discretion to ensure\r\noperational stability. VeriSign may restrict or terminate your access to the\r\nWhois database for failure to abide by these terms of use. VeriSign\r\nreserves the right to modify these terms at any time.\r\n\r\nThe Registry database contains ONLY .COM, .NET, .EDU domains and\r\nRegistrars."}WHOIS API reference
The same contract as the API reference: parameters, response fields, and the request in five languages.
/ api/ v1/ domains/ {domain}/ whoisWHOIS is a legacy protocol. For modern, structured domain registration data, use the RDAP API instead.
Parameters
domainstringin pathRequiredRegistrable domain; reduced to the registrable root.
Example
vercel.com
Response
domainstringThe registrable domain.
whois_serverstring | nullThe port-43 WHOIS server that answered.
rawstringThe raw WHOIS response text, verbatim.
Errors: invalid_domain (400), insufficient_credits (402), unprocessable (422, no WHOIS server for this TLD), upstream_error (502). See error codes.
curl "https://tabapi.com/api/v1/domains/vercel.com/whois" \
-H "Authorization: Bearer sk_live_..."{
"domain": "vercel.com",
"whois_server": "whois.verisign-grs.com",
"raw": "Domain Name: VERCEL.COM\r\n Registry Domain ID: 10966907_DOMAIN_COM-VRSN\r\n Registrar WHOIS Server: whois.registrar.amazon\r\n Registrar URL: http://registrar.amazon.com\r\n Updated Date: 2026-05-16T15:54:35Z\r\n Creation Date: 1999-10-04T19:30:47Z\r\n Registry Expiry Date: 2029-10-04T19:30:47Z\r\n Registrar: Amazon Registrar, Inc.\r\n Registrar IANA ID: 468\r\n Registrar Abuse Contact Email: trustandsafety@support.aws.com\r\n Registrar Abuse Contact Phone: +1.2024422253\r\n Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited\r\n Name Server: A.ZEIT-WORLD.CO.UK\r\n Name Server: B.ZEIT-WORLD.ORG\r\n Name Server: E.ZEIT-WORLD.COM\r\n Name Server: F.ZEIT-WORLD.NET\r\n DNSSEC: unsigned\r\n URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/\r\n>>> Last update of whois database: 2026-09-28T17:10:28Z <<<\r\n\r\nFor more information on Whois status codes, please visit https://icann.org/epp\r\n\r\nNOTICE: The expiration date displayed in this record is the date the\r\nregistrar's sponsorship of the domain name registration in the registry is\r\ncurrently set to expire. This date does not necessarily reflect the expiration\r\ndate of the domain name registrant's agreement with the sponsoring\r\nregistrar. Users may consult the sponsoring registrar's Whois database to\r\nview the registrar's reported date of expiration for this registration.\r\n\r\nTERMS OF USE: You are not authorized to access or query our Whois\r\ndatabase through the use of electronic processes that are high-volume and\r\nautomated except as reasonably necessary to register domain names or\r\nmodify existing registrations; the Data in VeriSign Global Registry\r\nServices' (\"VeriSign\") Whois database is provided by VeriSign for\r\ninformation purposes only, and to assist persons in obtaining information\r\nabout or related to a domain name registration record. VeriSign does not\r\nguarantee its accuracy. By submitting a Whois query, you agree to abide\r\nby the following terms of use: You agree that you may use this Data only\r\nfor lawful purposes and that under no circumstances will you use this Data\r\nto: (1) allow, enable, or otherwise support the transmission of mass\r\nunsolicited, commercial advertising or solicitations via e-mail, telephone,\r\nor facsimile; or (2) enable high volume, automated, electronic processes\r\nthat apply to VeriSign (or its computer systems). The compilation,\r\nrepackaging, dissemination or other use of this Data is expressly\r\nprohibited without the prior written consent of VeriSign. You agree not to\r\nuse electronic processes that are automated and high-volume to access or\r\nquery the Whois database except as reasonably necessary to register\r\ndomain names or modify existing registrations. VeriSign reserves the right\r\nto restrict your access to the Whois database in its sole discretion to ensure\r\noperational stability. VeriSign may restrict or terminate your access to the\r\nWhois database for failure to abide by these terms of use. VeriSign\r\nreserves the right to modify these terms at any time.\r\n\r\nThe Registry database contains ONLY .COM, .NET, .EDU domains and\r\nRegistrars."
}WHOIS API pricing
Buy credits once, from $10: $1 buys 1,000 credits, every endpoint draws on the same balance, and credits never expire.
- Per call
- 1 credit
- $0.001 at the base rate.
- Volume bonus
- Up to +10%
- More credits on bigger packs: +2% from $200, +5% from $500, +10% from $1,000.
- Free to start
- 100 credits
- On sign-up, no card required: 100 calls.
- Failed calls
- 0 credits
- Errors are never charged.
Use WHOIS API from your agent
Your agent can call it as the getWhois tool on the TabAPI MCP server, or over HTTP with the agent skill. Same key, same price: 1 credit per call.
WHOIS API FAQ
Short answers. The docs have the long ones.
Get a free WHOIS API key
Create a key, send one header, get JSON back.
curl "https://tabapi.com/api/v1/domains/vercel.com/whois" -H "Authorization: Bearer $TABAPI_KEY"