How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

WhoisFreaks

WhoisFreaks is a domain and IP intelligence provider whose REST API suite covers live WHOIS, historical WHOIS, bulk and reverse WHOIS, IP and ASN WHOIS, live/historical/reverse DNS, domain availability with suggestions, typosquatting discovery, SSL certificate lookup, subdomain enumeration, IP geolocation, IP reputation and domain reputation. Alongside the live lookup APIs it ships bulk downloadable databases (WHOIS, DNS, subdomains, IP geolocation, IP security, ASN, newly registered domains, expiring and dropped domains, and daily phishing/malware/spam threat feeds), brand/domain/registrant monitoring services with email, Telegram and webhook alerts, ten officially maintained OpenAPI-generated SDKs, a Go CLI, an n8n community node, and an open-source MCP server exposing fourteen domain-intelligence tools to AI assistants. Authentication is a single apiKey query parameter across every endpoint.

agent ready

Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.

Kin Score

API Evangelist profiles WhoisFreaks the way a machine reads it — 52 machine-readable artifacts across 23 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — WhoisFreaks scores 68.8/100 (exemplar), with a separate agent-readiness read of 42/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 68.8/100 · exemplar
Contract Quality 17.0 / 25
Developer Ergonomics 15.5 / 20
Commercial Clarity 16.8 / 20
Operational Transparency 9.9 / 13
Governance 1.4 / 12
Discoverability 8.2 / 10
Agent readiness — 42/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics documented 4.0 / 8
Request/Response Examples partial 3.5 / 7
Rate-Limit Signaling documented 3.5 / 7
Typed Event Surface 6 / 6
Agent Skills derived 1.3 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
WhoisFreaks Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from WhoisFreaks's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/whoisfreaks/"
   title="WhoisFreaks on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/whoisfreaks.svg"
       alt="WhoisFreaks Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile WhoisFreaks

Each block below is one kind of artifact we hold for WhoisFreaks. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 23

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

WhoisFreaks MCP Server

Official open-source Model Context Protocol server (Java) exposing 14 WhoisFreaks domain-intelligence tools to MCP-compatible AI clients. Distributed as source and as the whoisf...

WhoisFreaks Account API

Account, API key, and usage utilities

WhoisFreaks ASN WHOIS API

Autonomous System Number WHOIS

WhoisFreaks Databases - ASN WHOIS API

ASN WHOIS database snapshots

WhoisFreaks Databases - DNS API

DNS database snapshots

WhoisFreaks Databases - Expiring & Dropped API

Expiring and dropped domain downloads

WhoisFreaks Databases - IP Geolocation API

IP geolocation database snapshots

WhoisFreaks Databases - IP Security API

IP security database snapshots

WhoisFreaks Databases - IP WHOIS API

IP WHOIS database snapshots

WhoisFreaks Databases - Newly Registered API

Newly registered domain downloads

WhoisFreaks Databases - Subdomains API

Subdomain database snapshots

WhoisFreaks Databases - Threat Feed API

The Databases - Threat Feed API from WhoisFreaks — 6 operation(s) for databases - threat feed.

WhoisFreaks Databases - WHOIS API

WHOIS database snapshots

WhoisFreaks DNS API

DNS lookup APIs (live, historical, reverse, bulk)

WhoisFreaks Domain Availability API

Check domain availability

WhoisFreaks Domain Reputation API

Real-time domain threat assessment and trust scoring

WhoisFreaks Geolocation API

IP geolocation lookup

WhoisFreaks IP Reputation API

IP threat intelligence

WhoisFreaks IP WHOIS API

IP address WHOIS

WhoisFreaks SSL API

SSL certificate lookup

WhoisFreaks Subdomains API

Subdomain enumeration

WhoisFreaks Typosquatting API

Detect typo variants of brand domains

WhoisFreaks WHOIS API

WHOIS lookup APIs (live, historical, reverse, bulk)

Scroll within the panel for all 23 ·

Open Collections 23

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scroll within the panel for all 23 ·

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.

Published pricing tiers and plan structures.

Whoisfreaks Plans

5 plans

PLANS

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Whoisfreaks Rate Limits

4 limits

RATE LIMITS

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Whoisfreaks Authentication

apiKey · 1 scheme

SECURITY

Whoisfreaks Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Resources

Every other property we hold for WhoisFreaks — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Access & Security 3

Authentication, authorization, and security posture

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/whoisfreaks · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of WhoisFreaks, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.