appin60 pricing: domain WHOIS API
Is appin60 yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
56% complete: 5 of the 9 fields on our checklistSee the 9 fields
$5.00per 1,000 domainsWe haven't run appin60 through our domain WHOIS API benchmark yet.We rank 363 plans for domain WHOIS APIs by price. Half the plans cost $1.50 or less per 1,000 domains. This plan costs less per 1,000 domains than 12% of the 363 plans.Searchwire's $10 pack is the cheapest paid plan per 1,000 domains. Searchwire's domain WHOIS API costs nothing beyond the plan price. C99.nl's $25 yearly plan costs the least for 10,000 domains a month: $2.08.Enterno, IPAddress.to and Robtex are the best domain WHOIS API providers in the Datacircle benchmark.
Plan: Pay per call (x402) appin60's only plan
Call:
GET / domain/ lookup appin60's only call for this APIAPI: Domain WHOIS API one of appin60's 6 APIs
- Company enrichment API
- Tech stack API
- Domain WHOIS API
- Email verification API
- Email finder API
- Web scraping API
About this item
- Freshness. We don't know how fresh this plan's data is.
- 5 of the 9 fields on our checklist. Registrar, Created on, Expires on, Name servers, Statuses.
- Nothing to buy first. You pay per call.
- One call. You send
domaintoGET /. The call returns the domain's WHOIS record.domain/ lookup - Who can get it: with conditions. Keep data: no API terms. Use data: no API terms.
appin60: domain WHOIS API alternatives
appin60 alternatives: other domain WHOIS API providers by price
We list other providers' plans closest to this plan in price per 1,000 domains.
| This planappin60, pay as you go | How.is, pay as you go | fetcher.cloud, pay as you go | Companyfacts, $10 pack | Call402, pay as you go | |
|---|---|---|---|---|---|
| $ per 1,000 domains | $5.00 | $5.00 | $5.00 | $5.00 | $5.00 |
| Completeness | 56% | 56% | 44% | 67% | 56% |
| Billing | pay as you go | pay as you go | pay as you go | pay first | pay as you go |
| Pay | per call | per call | per call | $10 | per call |
| Enough for | as many as you pay for | as many as you pay for | as many as you pay for | 2,000 calls | as many as you pay for |
| Freshness | unknown | live | live | unknown | unknown |
| Who can get it | anyone, with no account or API key, paying each call in USDC on Base or Arbitrum (x402) | anyone, with no account or API key, paying each call in USDC from a wallet: x402 on Base | any agent that can make an HTTP request and hold a wallet with USDC on Base | anyone | anyone, with no account or API key, paying each call in USDC from a wallet: x402 on Base |
Sources
From each provider's own pricing page and docs, and from what providers tell us. We read this row from these pages on 2026-11-08.
Product details
The key fields this plan's answer can hold, then each filled column in its row on the sheet.
- Registrant, not in the answer
- Registrar
- Created on
- Updated on, not in the answer
- Expires on
- Name servers
- Statuses
- DNSSEC, not in the answer
- Abuse contact, not in the answer
| $ per 1,000 domains | $5.00 |
|---|---|
| Per | call |
| Billing | pay as you go |
| Also pays for | nothing else |
|---|
| Their pitch | Look up a domain before trusting it: registrar, creation date and age in days, expiry, status flags and nameservers from RDAP, plus A/AAAA/MX/CAA records and email authentication (SPF, DMARC policy). Flags young domains (under 30 days), near expiry, missing SPF/DMARC and p=none. Useful for phishing and vendor checks, outreach hygiene and incident triage. |
|---|
| Keep data | no API terms |
|---|---|
| Use data | no API terms |
| Pay | per call |
|---|
| Batch | 1 |
|---|
| Answer | in the call |
|---|
| You send | domain |
|---|---|
| Method | GET |
| Path | /domain/lookup |
| Plan | Pay per call (x402) |
|---|---|
| Who can get it | anyone, with no account or API key, paying each call in USDC on Base or Arbitrum (x402) |
The 14 fields the plan's answer can hold
domain, registrar, creation date, domain age days, expiry date, status flags, nameservers, A records, AAAA records, MX records, CAA records, SPF record, DMARC policy, problems