Automation platforms

Check links, domain age and website contacts in Make

Screen the website address a lead submits before a Make scenario writes it anywhere, and keep reported malicious domains out of your records.

Why the data matters in Make

A scenario moves bundles from module to module, so a link that arrives in a form submission gets stored, enriched and often clicked by a sales rep within minutes. In a scenario that fans out to several apps, one bad address lands in all of them.

What LookValid checks

LookValid checks for Make
Product	What it does here	Credits
Link Safety Check	Checks the domain of a URL against a public list of reported malicious domains and returns listed or not listed. It checks the domain, not the page, and an unlisted domain is not proof of safety.	1 credit per URL checked (a check that cannot run is free)
Domain Age	Returns registration and expiry dates and age in days from the registry, which helps spot a domain registered last week.	2 credits per registered domain (unregistered domains are free)
Website Contacts Scraper	Reads a domain's public pages and returns the email addresses, phone numbers and social links they publish.	10 credits per domain with contacts found

Connect it in four steps

Create a LookValid account and an API key from the dashboard, which a person does once.
In the Make a request module pick the API key authentication type and put the key in a keychain through the Credentials field, rather than typing it into the Headers field, so one stored key serves every scenario.
Set the method to POST, the body content type to application/JSON, and Parse response to Yes, then send the submitted URL to the link-safety endpoint; on found false send the bundle to a review route, and on an error response stop the run and read the code and fix.
Use the verdict in a router so listed domains go to a quarantine route, and map the host value into the record field your scenario saves.

The Make a request module of the HTTP app, placed between the module that receives the form bundle and the modules that store it. The call is POST https://YOUR_API_HOST/v1/link-safety and costs 1 credit per URL checked (a check that cannot run is free).

HTTP request step

1POST https://YOUR_API_HOST/v1/link-safety
2Authorization: Bearer {{LOOKVALID_API_KEY}}
3Content-Type: application/json
4
5{
6  "url": "{{value}}"
7}

Where to read each value in the LookValid response
Response field	Goes into
data.verdict	Link verdict
data.host	Link host

The recipe returns nothing when the lookup finds nothing, and stops with the error code and fix on a failed request.

Without code

Make has no LookValid module and needs none. The HTTP app's Make a request module sends the POST shown above and, with Parse response on, turns the JSON answer into fields you can map, so a router right after your trigger can branch on the verdict. The same pattern works for any scenario that receives a web address.

REST and MCPOne shared credit balance

Questions

What does a check cost in credits?

The pricing page lists the credits for the link-safety product. A scenario that checks one link per bundle uses one check per run.

What does the link check not do?

It compares the domain with a list of domains already reported as malicious. It does not open the page, and a new bad domain may not be listed yet.

Where does the key go in a scenario?

In a keychain chosen through the Credentials field of the Make a request module, using the API key authentication type.

Sources

HTTP app documentation (Make) https://apps.make.com/http, read 2026-10-18
LookValid API reference: Link Safety Check https://lookvalid.com/docs/api/link-safety, read 2026-10-18

LookValid is run by Meralume Labs. It is not connected to, endorsed by or a partner of any company or product named on this page, and every product name belongs to its owner.

LookValid bills every lookup in credits from one shared balance, so the same key works for each check above.

See Link Safety Check