Resources · Make integration

ViewDNS Make integrationAutomate ViewDNS with Make.

Tired of pasting domains into lookup tools one at a time? The ViewDNS Make integration puts 11 action modules in your scenarios, from DNS records to port scans. It suits admins, agencies and SEO teams, and this page takes you from the connection to a first scenario that runs alone.

Try the ViewDNS integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ViewDNS Make integration do for you?

The ViewDNS Make integration lets a Make scenario (the automation you build, a chain of bricks called modules) ask ViewDNS about a domain, an IP address or a MAC address, then pass the answer to your other tools. Every one of its 11 modules is an action: it runs when the scenario reaches it, never on its own.

A DNS change you can confirm without refreshing a tool. After a migration, chain Lookup DNS Records and Check DNS Propagation, then send the result to the channel where your team tracks the switch.

A cleaner abuse report. When a suspicious IP shows up in a form or a log, Lookup Abuse Contact and Lookup Domain / IP Whois gather who to write to, so the ticket starts with a name instead of a blank field.

A quick map of a server. For a site audit, Lookup Reverse IP lists what else lives on the same address, and Scan Ports adds what the host exposes.

What the page cannot promise: Make's documentation for ViewDNS is marked as limited, with no list of fields and no connection steps of its own, so each note below reads the module from its name and tells you to confirm the output with a test. There is also no trigger and no universal API call module, so a scenario always starts from another app or from a schedule. The Make troubleshooting guide helps when a run fails, and Make training covers the editor basics. If you are still choosing a platform, n8n vs Make lays out the criteria.

Connect

How do you connect ViewDNS to Make?

  1. 01

    Add a ViewDNS module

    In your scenario, click the +, search for ViewDNS and pick any of its modules, for example Lookup DNS Records. Then click Create a connection. A connection is your ViewDNS account linked to Make once and reused by every ViewDNS module.

  2. 02

    Name it and authorize

    Give the connection a name if you like, such as "ViewDNS main", which helps once you have several. Then follow what the window asks: either an authorization page from ViewDNS or a field where you paste the key ViewDNS gives you.

  3. 03

    Save and check the module

    Click Save. The connection now appears in the module, and you can fill its fields. From this point, any other ViewDNS module in any scenario can pick the same connection from the list.

First scenario

Your first scenario with ViewDNS

GoalWhen the scenario runs on its schedule, Make reads the DNS records of a domain with ViewDNS, then checks whether the change has spread.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor. This first bubble will hold your first module.

  2. 02

    Add Lookup DNS Records

    Search for ViewDNS, choose Lookup DNS Records and click Create a connection as shown above. Fill the module fields with the domain you want to watch after a migration.

  3. 03

    Chain Check DNS Propagation

    Click the + on the right of the first module and add Check DNS Propagation. Map the domain from the previous module so both lookups work on the same name.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received (a bundle is one item passed along, here one answer). Read them to learn what ViewDNS returns.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Keep it or adjust it, then switch the scenario on.

Modules

What the 11 ViewDNS modules do

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

ViewDNS1

Check Chinese Firewall

ActionIn the docs only

Here you find out whether a site seems reachable from inside China, judging by the module name, without asking a contact there to test it for you.

When to use it
before a launch aimed at Chinese visitors, or when a partner there reports that your pages never load.
Watch out
the documentation does not describe the result. Read the bundle after Run once before you build a rule on it.
ViewDNS2

Check DNS Propagation

ActionIn the docs only

This one tells you whether a DNS change has spread, so you stop refreshing an online checker after moving a domain to a new host.

When to use it
right after Lookup DNS Records in a migration scenario, to confirm the new records are visible before you announce the switch.
Watch out
each check counts as an operation, one execution Make bills on your plan, so avoid scheduling it far more often than you need.
ViewDNS3

Lookup Abuse Contact

ActionIn the docs only

You get the address to report abuse for a domain or IP, which turns a vague complaint into a message that reaches the right network owner.

When to use it
when a form spam wave or a suspicious login comes from one address and your support tool needs someone to notify.
Watch out
some owners publish no abuse contact, so plan a fallback path in the scenario for an empty answer.
ViewDNS4

Lookup DNS Records

ActionIn the docs only

With it, the records of a domain land in your scenario as data, ready to be compared, logged or sent to a teammate without opening a terminal.

When to use it
for a client audit, or as the first step before Check DNS Propagation when you move email or a website.
Watch out
Make lists no fields for this module, so map the output only after one test run has shown you its structure.
ViewDNS5

Lookup Domain / IP Whois

ActionIn the docs only

Registration details for a domain or an IP arrive straight in the scenario, which saves a trip to a Whois site each time a new name comes up.

When to use it
when a lead fills a form with a company domain and your sales team wants to know who holds it before calling.
Watch out
privacy services often hide the owner, so treat missing names as normal rather than as an error.
ViewDNS6

Lookup IP History

ActionIn the docs only

Past addresses of a domain become visible, which helps you understand where a site was hosted before and spot an old server still in use.

When to use it
during a takeover of a client site, or when an investigation needs to know whether a domain changed hosts recently.
Watch out
an address can return several entries, so add a step that handles each one instead of only the first.
ViewDNS7

Lookup IP Location

ActionIn the docs only

An IP address turns into a place, so a raw number in a log becomes a country or city your team can read at a glance.

When to use it
to enrich a signup or an order with the visitor's likely location before it reaches your CRM or your fraud review.
Watch out
a location tied to an IP is an estimate, and a VPN points elsewhere, so do not block anyone on this alone.
ViewDNS8

Lookup MAC Address

ActionIn the docs only

From a MAC address, this module finds who made the network device, handy when an inventory lists hardware only by its identifier.

When to use it
when your network tool exports unknown devices to a sheet and IT wants a vendor name next to each line.
Watch out
it works on the hardware address, not on an IP, so check that the mapped value really is a MAC before running it.
ViewDNS9

Lookup Reverse DNS

ActionIn the docs only

Give it an IP and it tries to return the hostname behind it, a quick way to put a name on a server that appears in your logs.

When to use it
when checking where outgoing email is sent from, or when a monitoring alert shows only an address.
Watch out
many addresses have no reverse name set, so an empty result says nothing bad about the host.
ViewDNS10

Lookup Reverse IP

ActionIn the docs only

Other domains hosted on the same address show up, which reveals the neighbors of a site on shared hosting in one step.

When to use it
in an SEO or security audit, to see whether a client shares a server with unrelated or doubtful sites.
Watch out
the answer can be a long list, so add a filter, or an aggregator (a Make module that groups bundles into one), before sending it on.
ViewDNS11

Scan Ports

ActionIn the docs only

Scan Ports checks which ports of a host answer, giving a first view of what a server exposes to the internet without installing a scanner.

When to use it
after a deployment, to confirm that only the services you meant to open are reachable.
Watch out
scan only hosts you own or have permission to test, since probing someone else's server can be read as hostile.
Need help

Need help automating ViewDNS with Make?

A person reads every message.

FAQ

ViewDNS and Make: common questions

01Is the ViewDNS Make integration free?
Yes, on the Make side. ViewDNS is a standard app, available from the Free plan like the 3,000+ standard apps. The Free plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Each ViewDNS lookup counts as one operation on your plan. Whatever ViewDNS itself charges is set by ViewDNS, not by Make.
02What do you need to connect ViewDNS to Make?
A ViewDNS account and a Make account. Make's documentation for ViewDNS lists no prerequisite and no dedicated steps, so the generic flow applies: add a ViewDNS module, click Create a connection, name it if you want, authorize Make on the ViewDNS page or paste the key ViewDNS provides, then click Save. The connection is created once and reused by all 11 modules. If the window asks for a key you cannot find, check your ViewDNS account before contacting support.
03Does the ViewDNS Make integration have a trigger?
No. All 11 ViewDNS modules are actions, so nothing in ViewDNS can start a scenario by itself. You have two ways to launch one anyway. The first is a schedule: the clock on the first module runs the scenario every 15 minutes by default, and you can change that interval. The second is to begin with another app, such as a form tool or a spreadsheet, whose trigger passes a domain or an IP to the ViewDNS module placed right after it.
04What if a ViewDNS module is missing in Make?
It depends on what you need. ViewDNS has no Make an API Call module in Make, so you cannot reach an endpoint that the 11 modules do not cover from inside this app. Make also marks its ViewDNS documentation as limited, which means fields and limits are not described. Two options remain: look for another app in Make that covers the same lookup, or ask the team for help designing a workaround that fits your scenario.
05Should you use Make or n8n for ViewDNS?
It depends on your criteria, not on a ranking. In Make, ViewDNS gives you 11 ready action modules and a visual editor where each lookup is a bubble you drag into place, which suits a team that wants to test quickly with Run once. The same app often exists as an n8n node too, so check what that node offers before deciding. Compare the modules you actually need, how your team likes to build, and which platform already runs your other automations.
Same platform

Other docs you might need on this stack.

Browse all integrations