OrganizationsManage members, shared watchlists, alert scope, and destinations.Dark Web MonitoringWatch companies, vendors, domains, and brands for reviewable exposure alerts.SearchSearch companies, groups, source changes, and alert context.API and WebhooksRoute reviewed alert fields into customer tools and analyst workflows.

All SolutionsCompany exposure monitoring, API delivery, and review workflows.Dark Web MonitoringCompany and vendor alerts from watched exposure sources.Security MonitoringManaged detection from customer security logs, suspicious logins, and analyst evidence.Threat SearchOpen the public intelligence workspace for companies and groups.BrowserRegular and Tor browser runs with isolated capture, profiles, and queueing.

Trust CenterSecurity, DPA, SLA, subprocessors, and enterprise review path.StatusService health and current uptime.Service ChecksPermitted endpoint checks for URLs you control.Hash Exposure LookupCheck a SHA-1 hash through a prefix-only exposure lookup.CompanyProduct notes, ownership, and current Hanasand direction.

Support Go to Dashboard

Loading

Monitor company exposure, triage dark web alerts, and give analysts the context they need to open the right case.

monitoringalertscasesthreat intelligencebrowser sandbox

Product

Dark Web Monitoring Threat Intelligence Organizations Actor Overview

Solutions

All Solutions Browser API docs Pricing

Developers

Support Status Service Checks Hash Exposure Lookup

Company

About Trust Center Contact Pricing

Legal

Terms of use Privacy policy Cookie policy Cookie settings

Checking status

Terms of use Privacy policy Cookie policy Cookie settings© 2026 Hanasand

v1.6.7

Incident history

Core platform

API Health Interruption

API Health

OutageResolved

What happened

Unexpected public API contract response 503

Why it happened

Unexpected public API contract response 503

Timeline

investigating

Aug 2, 2026, 4:16 AM

Unexpected public API contract response 503

monitoring

Aug 2, 2026, 4:17 AM

Unexpected public API contract response 503

resolved

Aug 7, 2026, 6:17 AM

API health returned to normal.