A verification workflow is the repeatable sequence a business uses to confirm a domain, email server, IP, or partner is legitimate and operationally healthy. This guide walks through designing one your team can run on autopilot.
Start from a real business event your team handles — onboarding a vendor, approving a new sending domain, or qualifying a partner integration. Write the checks down in the order you'd run them, then save that sequence as a named workflow you can resume in one click.
Run through these steps in order. Each step links to the right diagnostic tool.
Save the workflow
From the dashboard, save the sequence so the next incident or onboarding resumes in one click.
Open Operational dashboardA named, repeatable sequence of checks — typically domain, DNS, SSL, blacklist, and reputation — that confirms an external party or your own infrastructure is trustworthy.
Onboarding events run once; ongoing trust monitoring runs on a daily or weekly schedule. Critical assets like sending IPs and payment domains belong on the shortest interval.
Operations or IT typically owns the workflow; compliance, security, and deliverability teams consume the output. Saved workflows make ownership transferable.
Verification is a point-in-time confirmation. Monitoring is verification on a schedule with alerts on state change. Mature teams pair the two.
Run the rest of the checks
DNS, SSL, headers, blacklists and WHOIS all run free in the browser — no account, nothing stored.