Skip to content

WhoisFreaks status

Answered our latest tool-list check 13 hours ago with 22 tools. It will be marked verified after 3 successful checks in 7 days.

Answered (30 days)
2 of 2 checks
Last seen working
17 Nov, 00:17 UTC
Last commit
—
Licence
Not stated

Live checks

We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.

  • Answered
  • Needs sign-in
  • No answer
Checked (UTC)ResultResponse timeTools
17 Nov, 00:17Answered4.1 s22
16 Nov, 00:16Answered3.1 s22

Tools (22)

Read from the server on 17 Nov 2026.

liveWhoisLookup
Get the current WHOIS registration record for a domain, queried live from WHOIS servers and RDAP. Use this to find who owns a domain now, its registrar, creation and expiry dates, name servers or status. For past owners and changes over time use whoisHistory. For many domains at once use bulkWhoisLookup. To find domains owned by a person, email or company use reverseWhoisLookup. To check whether a
bulkWhoisLookup
Get the current WHOIS records of up to 100 domains in one request, queried live. Use this instead of calling liveWhoisLookup many times, for example to audit a domain portfolio or enrich a list of domains taken from logs. For one domain use liveWhoisLookup. Lists of more than 100 domains go in several calls; files of up to 3 million domains are handled by the Bulk Tool in the WhoisFreaks billing d
whoisHistory
Get the historical WHOIS records of a domain: deduplicated snapshots ordered from newest to oldest, going back as far as 1986. Use this to see previous owners, registrar transfers, past contacts, name server changes, or when a domain expired and was re-registered. For only the current record use liveWhoisLookup. For DNS changes over time use dnsHistory. Costs 2 credits. Every record comes back in
reverseWhoisLookup
Find domains whose WHOIS records contain a given email, registrant name or company, or whose name contains a keyword, across 4.6 billion WHOIS records. Use this to map everything a person or organisation has registered, for example when investigating a phishing actor or auditing a company's domain portfolio. Provide exactly one of email, owner, company or keyword. To look up the owner of one known
ipWhoisLookup
Get the registry WHOIS record for an IPv4 or IPv6 address: who the IP block is allocated to. Use this to find the owning organisation, CIDR range, AS number and abuse contact of an IP, for example to report abuse. For city, ISP and coordinates use ipGeolocation. For VPN, proxy, Tor and threat signals use ipSecurity. For details about the autonomous system itself use asnWhoisLookup. For domains hos
asnWhoisLookup
Get the registry WHOIS record for an autonomous system (ASN): the network operator behind a set of IP routes. Use this when you have an AS number (for example from ipWhoisLookup or ipGeolocation output) and need the operator's name, country, contacts or the IP prefixes it announces. If you only have an IP address, call ipWhoisLookup first to get its ASN. Returns the organisation name and descripti
dnsLookup
Resolve a domain's current DNS records live: A, AAAA, MX, NS, CNAME, SOA, TXT and SPF. With ipAddress it also does a reverse (PTR) lookup of an IP address. Use this to see where a domain points now: its IP addresses, mail servers, name servers, or TXT records such as SPF, DKIM and DMARC. For how records changed over time use dnsHistory. To go the other way and find domains that use a given IP, mai
bulkDnsLookup
Resolve the current DNS records of up to 100 domains, and the PTR records of up to 100 IP addresses, in one request. Use this instead of calling dnsLookup many times, for example to check the mail servers of a list of domains or to name a list of IPs from logs. Provide domainNames, ipAddresses, or both. For one domain or IP use dnsLookup. Lists longer than 100 go in several calls; files of up to 3
dnsHistory
Get the historical DNS records of a domain, showing how its A, MX, NS and other records changed over time. Use this for investigations and migrations: earlier hosting IPs (for example the origin IP behind a CDN), past mail servers, or name server changes. For the current records only use dnsLookup. For ownership changes use whoisHistory. Costs 2 credits per page. Returns past records with the date
reverseDnsLookup
Find domains whose DNS records point to a given value: an IP address or range, mail server, name server or other record value. Use this to see which other sites share a hosting IP, which domains use a mail server or name server, or to map infrastructure during an investigation. Set type to match the value: a for an IPv4 address or range (default), aaaa for IPv6, mx for a mail server, ns for a name
ipGeolocation
Look up where an IPv4 or IPv6 address is located and which network it belongs to. Use this for country, region, city, coordinates, ISP, ASN, connection type and local currency, for example to localise a visitor or see where a server is hosted. The location is an estimate and is most reliable at country level. For many IPs at once use bulkIpGeolocation. For VPN, proxy, Tor and threat signals use ip
bulkIpGeolocation
Look up the location and network of up to 100 IPv4 or IPv6 addresses in one request. Use this instead of calling ipGeolocation many times, for example to map the visitors or attackers in a log. For one IP use ipGeolocation. For threat signals on many IPs use bulkIpSecurity. Costs 1 credit per IP answered. Returns one entry per IP, with the same fields as ipGeolocation. Behavior: read-only. Makes o
ipSecurity
Check the reputation of an IPv4 or IPv6 address: VPN, proxy (including residential), Tor exit node, privacy relay, spam and known-attacker activity, bots by type and operator, and whether it belongs to a cloud provider or a corporate secure web gateway. Use this for fraud checks, sign-up or login screening, or triaging a suspicious IP from logs. For many IPs at once use bulkIpSecurity. For locatio
bulkIpSecurity
Check the reputation of up to 100 IPv4 or IPv6 addresses in one request: VPN, proxy, Tor, relay, spam, known-attacker and bot signals for each. Use this instead of calling ipSecurity many times, for example to screen the IPs behind a wave of sign-ups or failed logins. For one IP use ipSecurity. For location only use bulkIpGeolocation. Costs 1 credit per IP answered. An invalid IP returns its own e
domainAvailability
Check whether a domain name is available to register, using both DNS and WHOIS data. Use this before suggesting or buying a domain name. Set suggestions=true to also get alternative names with other extensions, each marked available or not; count sets how many (5-100). To check a list of names, or one name across many extensions, use bulkDomainAvailability. For details about who owns a registered
bulkDomainAvailability
Check whether many domain names can be registered, in one request: either up to 100 full domain names, or one name across up to 100 extensions (TLDs). Use this to pick an available name across extensions such as .com, .io and .ai (pass domain and tlds), or to check a list of candidate names (pass domainNames). For one name, or for name ideas, use domainAvailability with suggestions=true. Uses API
subdomainLookup
List the known subdomains of a domain (for example api.example.com or mail.example.com) from the WhoisFreaks subdomain database. Use this for attack-surface mapping, finding exposed services, or auditing a company's hosts. It looks up subdomains already discovered by WhoisFreaks rather than scanning the target, so it only knows subdomains that have been observed. To get a subdomain's DNS records u
domainDiscovery
Find registered domains that look like typo variants of a brand name (typosquats such as paypa1.com or paypal-secure.net), or that match a wildcard pattern, across more than 1,500 TLDs. Use this for brand protection, phishing detection, or tracking look-alike registrations. Provide exactly one of keyword or pattern. For subdomains that imitate a brand on unrelated domains, such as login.paypa1.exa
subdomainTyposquatting
Find subdomains, on any domain, that contain a typo variant of a brand name or match a wildcard pattern as one of their labels, for example login.paypa1.example.com. Phishing pages often hide a brand inside a subdomain of an unrelated domain, so these hosts never show up in domainDiscovery. Use this for brand protection and phishing hunting. Provide exactly one of keyword or pattern. For the subdo
domainReputation
Assess how risky a domain is, live: a verdict (safe, low_risk, suspicious, malicious or unknown) with its confidence and severity, a trust score with the positive and negative signals behind it, DGA (algorithmically generated name) analysis, matches in threat-intelligence feeds, email security (SPF, DKIM, DMARC and mail servers), and a recommended action. Its DKIM check probes only a few selectors
sslLookup
Get the SSL/TLS certificate a domain currently serves, fetched live. Use this to check expiry dates, the issuer, covered hostnames (SANs) or key type, or to debug HTTPS errors. Set chain=true to include intermediate and root certificates when diagnosing trust-chain problems, and sslRaw=true only when you need the raw OpenSSL output, which is long. For DNS records use dnsLookup; for domain ownershi
apiKeyUsage
Show how much of the WhoisFreaks API key's allowance is used: pay-as-you-go credits bought and used, and the subscription's status, request limit, requests used and surcharge requests. Use this before a large job (a bulk lookup, many pages of reverse WHOIS or typosquatting results) to check there is enough left, or when a lookup fails with a plan or credit limit error. Returns the key (masked), it