Dark Web MonitoringCompany and vendor alerts from watched exposure sources.Security MonitoringFind suspicious logins and other security events.Security ScannerSafe validation scans for approved Hanasand assets.Threat SearchSearch companies, groups, source changes, and alert context.BrowserOpen suspicious sites in isolated browsers and save the results.OrganizationsManage members, shared watchlists, alert scope, and destinations.

API overviewGet started with the Hanasand API.API keys and onboardingCreate an organization, get a key, and make your first request.API referenceBrowse endpoints, access requirements, and key scopes.TypeScript clientGenerate types and connect your application.OpenAPI JSONDownload the API specification.

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.About HanasandProduct notes, ownership, and current Hanasand direction.

Support DashboardGo to Dashboard

Loading

Monitor company exposure and review dark web alerts with the details your team needs.

Product

Dark Web Monitoring Threat Intelligence Organizations Actor Overview

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

Monitoring unavailable

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

v1.6.7

Incident history

Dark web monitoring

Resolved

Latest Activity Interruption

Affected component: Latest Activity
First detected: 19 Sept 2026, 11:58 UTC
Recovered: 19 Sept 2026, 11:59 UTC

Impact

The activity feed was delayed.

Cause

Cause unknown.

Updates

2 updates, newest first

Recovered
19 Sept 2026, 11:59 UTC
Recovered. No repair recorded.
Check result
Sources checked successfully. No new activity. 3382 saved records.
Issue detected
19 Sept 2026, 11:58 UTC
The activity feed was unavailable or empty (HTTP 503).