Resources · Make integration

WhoisFreaks Make integrationAutomate WhoisFreaks with Make.

Can Make check a domain, a certificate or an IP address for you, without writing code? The WhoisFreaks Make integration gives you 20 modules, 13 actions and 7 searches, covering availability, WHOIS, DNS and SSL. This guide takes you from the connection to a first working scenario.

Try the WhoisFreaks integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the WhoisFreaks Make integration do for you?

The WhoisFreaks Make integration lets a Make scenario (the automation you build, a chain of modules) ask WhoisFreaks about domains, IP addresses and networks, then pass the answer to your other apps. Each module is one brick of that chain: here, a lookup or a search you drop in without code.

Screen names before a launch. Your marketing team drops a shortlist of product names into a sheet; Get a Bulk Domains Availability tells you which ones can still be registered, and Get a Live WHOIS Lookup shows who holds the others.

Spot lookalike domains. A security or brand team feeds Get Newly Registered Domains with WHOIS into a review channel, then runs Search Reverse WHOIS on a suspicious owner to see what else they registered.

Keep client sites healthy. An agency checks each client domain with Get a Live SSL Lookup and Search a Live DNS of a Domain after every migration, and posts anything odd to its ticketing tool.

What Make will not do here: WhoisFreaks has no trigger, so it never starts a scenario by itself. The scenario starts on its schedule or on an event from another app. The official doc also warns that its WhoisFreaks page is AI-generated and may contain mistakes, so test every module with Run once before you trust the output. If you are new to the editor, the Make training covers the basics, and Make pricing explains how operations are counted.

Many apps also have an n8n node. If your team already works in n8n, n8n vs Make lays out the criteria side by side.

Connect

How do you connect your WhoisFreaks account to Make?

  1. 01

    Copy your API key

    Log in to WhoisFreaks, open the dashboard and copy the API key displayed there. Your account needs purchased API credits or an active subscription plan before Make can use it.

  2. 02

    Open the connection window

    In your scenario, add any WhoisFreaks module and click Create a connection. The Connection name field is optional, but a clear name helps once you manage several accounts.

  3. 03

    Paste the key and save

    Enter the API key you copied, or follow the on-screen instructions, and confirm. That connection, your WhoisFreaks account linked to Make, is then reused by all 20 modules.

First scenario

Build your first scenario with WhoisFreaks

GoalWhen someone requests a new domain in another app, Make checks whether it is free with WhoisFreaks and looks up who holds it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. WhoisFreaks has no trigger, so start with the app where domain requests land, such as your form tool.

  2. 02

    Add the availability check

    Click the + on the right of that first module, search WhoisFreaks, pick Get a Domain Availability and click Create a connection if you have not linked your account yet.

  3. 03

    Map the domain

    In the module fields, map the requested domain from the first module. That value travels inside a bundle, the item that flows from one module to the next.

  4. 04

    Add the WHOIS lookup

    Click the + again, add Get a Live WHOIS Lookup and map the same domain, so the person who asked also learns who holds the name.

  5. 05

    Test with Run once

    Click Run once and open the bubble above each module to read the bundles it received. Each module run counts as one operation on your Make plan.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default for a new scenario), then switch the scenario on. It now runs without you.

Modules

What each WhoisFreaks module does

WhoisFreaks gives you 20 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

WhoisFreaks1

Get Dropped Domains in JSON

ActionIn the docs only

You get the list of dropped domains straight into your scenario, in JSON, so each name becomes data the following modules can sort, filter or store.

When to use it
a domain investor wants fresh dropped names written to a spreadsheet without opening the WhoisFreaks dashboard each time.
Watch out
the doc describes no filter for this module, so click Run once and read what comes back before you map anything.
WhoisFreaks2

Get Expired & Deleted Domains

ActionIn the docs only

Expired and deleted domains arrive in one step, ready to be compared with the names you care about, with no manual export.

When to use it
a reseller keeps a watch list in another app and wants to know when one of those names shows up among expired or deleted domains.
Watch out
this is an action, not a trigger. It never runs on its own; the scenario's schedule or another app's event decides when it fires.
WhoisFreaks3

Get Newly Registered Domains in JSON

ActionIn the docs only

This one hands you newly registered domains as plain JSON, the lightest version of the three modules on fresh registrations.

When to use it
you only need the names, for example to match them against your brand keywords before deciding whether any deserves a closer look.
Watch out
if you later split the list with an iterator, every module that runs on each domain costs one operation, so filter early.
WhoisFreaks4

Get Newly Registered Domains with DNS

ActionIn the docs only

Fresh registrations come back with their DNS records attached, so you see where each new domain points without a second lookup module.

When to use it
a brand protection team wants to know which lookalike domains already resolve somewhere, since those are the ones worth escalating first.
Watch out
pick one of the three newly registered modules per branch; stacking them repeats data you partly have and adds operations.
WhoisFreaks5

Get Newly Registered Domains with WHOIS

ActionIn the docs only

Here each fresh registration carries its WHOIS record, the ownership data of the domain, in the same bundle.

When to use it
a legal team reviewing suspicious names needs the registrant details right away to prepare a takedown request.
Watch out
the doc lists no fields for this module; run it once on real data and map only the values you actually saw in the output.
WhoisFreaks6

Get a Bulk Domains Availability

ActionIn the docs only

Checks a whole list of domain names at once and tells you which ones can still be registered.

When to use it
after a naming workshop, the shortlist sits in a sheet and you want every option checked in a single module instead of one by one.
Watch out
looping the single-domain module over the same list costs one operation per name; the bulk module keeps that count down.
WhoisFreaks7

Get a Bulk Domains Availability with TLDS

ActionIn the docs only

Going by its name, this variant of the bulk check brings TLDs, the extensions like .com or .fr, into the request, so one brand name can be tested across several endings.

When to use it
a company launching in several countries wants to see which extensions of its product name are still open.
Watch out
the doc gives no detail on its inputs, so test with Run once on a name you already know.
WhoisFreaks8

Get a Domain Availability

ActionIn the docs only

One domain in, one clear answer out: can this name still be registered or not.

When to use it
a client fills a request form with the domain they want, and the scenario checks it before anyone on your team replies.
Watch out
it handles a single domain per run, which is perfect for requests arriving one at a time and wasteful for a long list, where the bulk module fits better.
WhoisFreaks9

Get a Live SSL Lookup

ActionIn the docs only

Runs a live SSL lookup on a domain, so your scenario reads the certificate as it stands at the moment the module runs.

When to use it
an agency moves a client site to a new host and wants the certificate checked and reported in the team channel.
Watch out
live means live at run time only; how fresh the check stays depends on the scenario's schedule, every 15 minutes by default.
WhoisFreaks10

Get a Live WHOIS Lookup

ActionIn the docs only

Fetches the current WHOIS record of a domain, pulled when the module runs rather than from an old copy.

When to use it
a sales team receives a lead from a company website and wants the domain's registration details added to the CRM record.
Watch out
test it first on a domain you know well and compare with the WhoisFreaks dashboard, then map only the values you confirmed.
WhoisFreaks11

Get an ASN WHOIS Lookup

ActionIn the docs only

Returns the WHOIS record of an ASN, the number that identifies a network on the internet, so you learn who operates it.

When to use it
an IT team sees an unfamiliar network number in its logs and wants the operator's name added to the incident ticket.
Watch out
it expects an ASN, not a domain or an IP address; check that the value you map from the previous module really is a network number.
WhoisFreaks12

Get an IP WHOIS Lookup

ActionIn the docs only

Tells you who stands behind an IP address by reading its WHOIS record.

When to use it
your support team flags a burst of sign-ups from the same IP and wants to know which organization holds that address before blocking it.
Watch out
the answer describes who holds the address, not who sat behind the screen; treat it as a lead to check, not as proof.
WhoisFreaks13

List Historical WHOIS of a domain

SearchIn the docs only

Lays out the past WHOIS records of a domain, so you can see how its ownership changed over time.

When to use it
before buying a second-hand domain, you want to know who held it before and whether it changed hands often.
Watch out
it is a search, so it can return zero, one or several bundles; add an aggregator if you want one summary instead of one message per record.
WhoisFreaks14

Make an API Call

ActionIn the docs only

Opens the rest of the WhoisFreaks API to your scenario, using the connection you already created, for anything the other modules do not cover.

When to use it
the WhoisFreaks endpoint you need has no dedicated module among the 20 listed on this page.
Watch out
you write the request yourself, so keep the WhoisFreaks API documentation open and check the response with Run once before mapping it.
WhoisFreaks15

Search Bulk DNS of Domains

SearchIn the docs only

Reads the DNS records of a batch of domains in one search, so a full portfolio can be audited in a single module.

When to use it
your company switches email provider and you want to confirm that every domain you own now points to the new records.
Watch out
each result comes out as its own bundle, so place a filter before any alert module to avoid a flood of messages.
WhoisFreaks16

Search Historical DNS of a Domain

SearchIn the docs only

Digs up what a domain's DNS used to be, which is the part a live lookup cannot show you.

When to use it
during an incident review, the team wants to know where a domain pointed before a suspicious change was made.
Watch out
zero results is a valid answer for a search; plan for it so the next module does not send an empty report.
WhoisFreaks17

Search Reverse DNS

SearchIn the docs only

Works backwards from DNS data to the domain names tied to it, handy when you hold an address and want the names behind it.

When to use it
a hosting team wants to see which domains share a server with a client site that just got flagged.
Watch out
the answer can be a long list of bundles; every module placed after this one runs once per bundle and counts operations accordingly.
WhoisFreaks18

Search Reverse WHOIS

SearchIn the docs only

Finds the domains registered under a given owner detail, which turns one suspicious registrant into a full map of their names.

When to use it
a brand team discovers one impersonating domain and wants every other domain the same registrant holds.
Watch out
results can be numerous; collect them with an aggregator into a single row or report rather than one message each.
WhoisFreaks19

Search a Bulk WHOIS of Domains

SearchIn the docs only

Pulls WHOIS records for a whole batch of domains in one search, instead of chaining single lookups.

When to use it
a new client hands over their domain list at onboarding and you want owners and registration details in one table.
Watch out
a batch means several bundles; route them into one sheet module and check a few rows by hand the first time.
WhoisFreaks20

Search a Live DNS of a Domain

SearchIn the docs only

Shows how a domain resolves right now, with the DNS records read at the moment the scenario runs.

When to use it
after changing records for a site launch, you want confirmation before the announcement goes out, often paired with Get a Live SSL Lookup.
Watch out
as a search it may return several records as separate bundles; decide which one your next module really needs.
Need help

Need help automating WhoisFreaks with Make?

A person reads every message.

FAQ

Questions about WhoisFreaks and Make

01Is the WhoisFreaks Make integration free?
Yes on the Make side: WhoisFreaks is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. On the WhoisFreaks side, the doc requires an active account with purchased API credits or a subscription plan, so the lookups themselves depend on your WhoisFreaks account.
02What do you need to connect WhoisFreaks to Make?
An active WhoisFreaks account with purchased API credits or a subscription, and the API key shown on your WhoisFreaks dashboard. In Make, add any WhoisFreaks module, click Create a connection, give it a name if you like, then paste the key or follow the on-screen instructions. The connection is created once and every WhoisFreaks module in your scenarios reuses it, so you never paste the key twice. If the key changes on the WhoisFreaks side, update that one connection.
03Can WhoisFreaks start a Make scenario in real time?
No. WhoisFreaks has no trigger module in Make, neither scheduled nor instant, so it cannot wake a scenario on its own. You have two ways to start. Set a schedule on the first module of the scenario, every 15 minutes by default, or as often as every minute on a paid plan. Or open the scenario with a trigger from another app, such as a form or a CRM, and place the WhoisFreaks modules right after it.
04What if a WhoisFreaks module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the WhoisFreaks API with the connection you already have, so you are not limited to the 20 listed modules. You build the request from the WhoisFreaks API documentation and test it with Run once. Keep in mind that the Make doc page for WhoisFreaks is marked as AI-generated and may contain mistakes; when something does not match, check with WhoisFreaks directly.
05Should you use Make or n8n for WhoisFreaks?
It depends on where your team already builds. On Make, WhoisFreaks comes with 20 modules plus Make an API Call, a visual editor and the Free plan to test on. Many apps also exist as n8n nodes, so if your automations already live in n8n, check whether a WhoisFreaks node is available there before moving anything. Base the choice on the tool your team maintains every day, not on a single app.
Same platform

Other docs you might need on this stack.

Browse all integrations