# WhoisFreaks integrations: WHOIS records

> Run a reverse WHOIS search and run a reverse DNS lookup in WhoisFreaks. Connect WhoisFreaks to the rest of your data and analytics stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/whoisfreaks-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

WhoisFreaks is a domain and IP intelligence service offering WHOIS, DNS, SSL, IP geolocation and domain reputation lookups, including historical and reverse searches. Tray.ai connects to WhoisFreaks through the HTTP Connector, so your workflows can call the WhoisFreaks API alongside the rest of your stack.

## Use cases

### WHOIS records

Read and create whois records in WhoisFreaks from any Tray.ai workflow. The WhoisFreaks API covers calls such as look up live WHOIS data and get WHOIS history.

- Look up live WHOIS data
- Get WHOIS history
- Run a reverse WHOIS search

### DNS records

Read and create dns records in WhoisFreaks from any Tray.ai workflow. The WhoisFreaks API covers calls such as look up live DNS records and get historical DNS records.

- Look up live DNS records
- Get historical DNS records
- Run a reverse DNS lookup

### IP addresses

Read ip addresses in WhoisFreaks from any Tray.ai workflow. The WhoisFreaks API covers calls such as look up IP geolocation and check IP reputation.

- Look up IP geolocation
- Check IP reputation
- Look up IP WHOIS

### Domains

Read domains in WhoisFreaks from any Tray.ai workflow. The WhoisFreaks API covers calls such as check domain availability and check domain reputation.

- Check domain availability
- Check domain reputation
- Find typosquatting domains

## Challenges Tray.ai solves

### Keeping WhoisFreaks credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store WhoisFreaks credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the WhoisFreaks API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the WhoisFreaks API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to WhoisFreaks?

Yes. Tray.ai connects to WhoisFreaks through the HTTP Connector, which calls the WhoisFreaks API directly. Any call the WhoisFreaks API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with WhoisFreaks?

The WhoisFreaks API uses an API key in the query string. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated WhoisFreaks connector?

WhoisFreaks runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated WhoisFreaks connector from the WhoisFreaks API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/
