Integration

WhoisFreaks integration

WhoisFreaks is a domain and IP intelligence API. Look up live, historical and reverse WHOIS records (by keyword, email, owner or company), WHOIS for IP addresses and ASNs, live, historical and reverse DNS records, domain availability with suggestions, SSL certificates and chains, subdomains, typosquatting lookalike domains, domain reputation (risk verdict, threat signals, email deliverability), and IP geolocation and reputation (VPN, proxy, Tor, bot detection); bulk WHOIS, DNS and availability checks take up to 100 names per call. Most lookups cost credits from your plan, and account usage shows what is left. The database file downloads, API key rotation, the XML output format and the bulk IP geolocation and reputation routes (whose response shape the vendor documents two ways) are not exposed. Authentication is your WhoisFreaks API key, sent as the apiKey query parameter.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in WhoisFreaks.Built from the 19 WhoisFreaks tools below, on the connection you add once.

What you can do with WhoisFreaks

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Live, 5 operations

  • bulk_dns_lookupBulk dns lookupPOSTReturns the live DNS records of up to 100 domains and the PTR records of up to 100 IP addresses in one request. 1 credit per successful lookup.
  • bulk_whoisBulk whoisPOSTReturns the live WHOIS records of up to 100 domains in one request, each in the same structure as whois_lookup. 1 credit per successful domain.
  • dns_lookupDns lookupGETReturns the live DNS records of a domain (A, AAAA, MX, NS, CNAME, SOA, TXT, SPF) or, with ipAddress, the PTR record of an IP. Pass domainName, ipAddress or both. 1 credit.
  • ssl_lookupSsl lookupGETReturns the SSL certificate a domain serves right now (subject, issuer, validity dates, extensions, public key) and, with chain=true, the whole chain from end-user to root; sslRaw=true adds the raw OpenSSL output.
  • whois_lookupWhois lookupGETReturns the current WHOIS record of a domain, fetched live from the authoritative WHOIS or RDAP servers: registrar, registrant and other contacts, creation, update and expiry dates, name servers, status codes and the raw WHOIS text. 1 credit.

Availability, 2 operations

  • bulk_domain_availabilityBulk domain availabilityPOSTChecks the availability of up to 100 domain names in one request and returns one availability result per domain.
  • check_domain_availabilityCheck domain availabilityGETChecks whether a domain is available for registration. With sug=true it also returns availability for the same name under other TLDs (count suggestions, default 5, at most 100). 1 credit, plus 1 per 5 suggestions.

Reverse, 2 operations

  • reverse_dnsReverse dnsGETFinds the domains whose DNS records point to a value: an IP address or CIDR range for A and AAAA, or a host or record value for MX, NS, CNAME, TXT and SOA (wildcards with exact=false). 5 credits per page of up to 100 records.
  • reverse_whoisReverse whoisGETFinds the domains registered to an owner: pass exactly one of keyword (a domain keyword), email, owner (registrant name) or company. Paginated, 50 records per page (100 in mini mode). 5 credits per page.

Security, 2 operations

  • domain_reputationDomain reputationGETAssesses a domain in real time: risk verdict and score, trust signals, DGA (algorithm-generated name) analysis, threat intelligence matches, security signals and email deliverability (SPF, DKIM, DMARC, MX, blacklists). 5 credits.
  • ip_reputationIp reputationGETReturns threat intelligence for an IPv4 or IPv6 address: threat score, VPN, proxy, residential proxy, Tor, relay, bot (type and operator), spam, known attacker, cloud and corporate gateway flags, plus location, network and ASN. 1 credit.

Asn whois, 1 operation

  • asn_whoisAsn whoisGETReturns WHOIS data for an Autonomous System Number: AS name, organization, country, domain, allocation status, IPv4 and IPv6 routes, upstreams, downstreams, peers and the raw WHOIS response. 1 credit.

Geolocation, 1 operation

  • ip_geolocationIp geolocationGETReturns the location of an IPv4 or IPv6 address (continent, country, region, city, coordinates, accuracy radius), its network, ASN and company, and the country's currency and calling code. 1 credit.

Historical, 1 operation

  • dns_historyDns historyGETReturns the historical DNS records of a domain from the WhoisFreaks DNS database, paginated (100 records per page). 2 credits per page.

History, 1 operation

  • whois_historyWhois historyGETReturns the historical WHOIS records of a domain, newest first, one entry per real change in registration data since 1986 (registrar, contacts, dates, name servers). 2 credits per 100 records.

Ip whois, 1 operation

  • ip_whoisIp whoisGETReturns the WHOIS registration of an IPv4 or IPv6 address from its Regional Internet Registry: network range, organization, administrative, technical and abuse contacts, routes and the raw WHOIS text. 1 credit.

Subdomain, 1 operation

  • find_subdomainsFind subdomainsGETLists the subdomains of a domain, nested ones included, with first and last seen dates; filter by creation date (after, before) and status (active or inactive). Paginated. 2 credits per page.

Typo, 1 operation

  • find_typosquat_domainsFind typosquat domainsGETFinds registered domains that look like typo variants of a brand: pass keyword (a single label) or a wildcard pattern, not both. Returns up to 100 domains per page with registration, expiry and last-seen dates. 5 credits per page.

Usage, 1 operation

  • get_account_usageGet account usageGETReturns the API key's subscription status, total credits, request limits, and served and surcharge request counts, to check how many credits are left.

Use WhoisFreaks from Claude Code, Cursor or Codex

Connect WhoisFreaks in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its WhoisFreaks operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect WhoisFreaks

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect WhoisFreaks once

    Add your WhoisFreaks connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

WhoisFreaks integration FAQ

What can you do with the WhoisFreaks integration?

LiveContext exposes 19 operations on WhoisFreaks, covering live, availability, reverse and security.

Popular integrations

Browse the whole catalog