Know what is exposed.
Discover domains, subdomains, IPs and the services behind them.
Cyber threat intelligence. External attack surface. Digital risk. One operational perspective for the security teams connecting the dots.
AI-powered intelligence. Built around your external exposure.
Connect an internet-facing asset to its DNS, certificate and service evidence. Understand what changed before deciding what to investigate.
Interactive illustration · Sample data
Discover domains, subdomains, IPs and the services behind them.
Bring account, content, brand and threat findings into organizational context.
Review evidence, triage alerts and hand findings to your security workflows.
External risk crosses boundaries. Your investigation should be able to follow it.
Tetharion brings CTI, external attack surface management and digital risk monitoring into a shared workspace. Move from the overview to the affected asset, account or record without losing the context.
Domains · DNS · IPs · TLS · Services · Findings
Global IOCs · Threat sources · Dark web findings
Account leaks · Content matches · Lookalike domains
Explore the capabilities that connect discovery, context and operational review.
Capabilities are described from the supplied product documentation. Data availability depends on the record and configured monitoring scope.
A unified view of alarms, assets, leaked accounts, vulnerability exposure, brand signals and dark web findings connects the overview to individual investigations.
Review domains, subdomains, IP addresses and DNS records alongside certificate, WAF/CDN and infrastructure context. Track supported discovery and change events.
Follow host and service evidence: port, protocol, product/version, banner, scan time and L4/L7 findings. Examine new, closed or changed services in technical context.
Review finding severity, the affected host or service and available technical details. CVE/CPE references are provided when available in the record.
Review employee, customer and third-party records by category, associated URL and date. Support identity investigations with sensitive-data access controls.
Assess algorithmic similarity and typosquatting signals together with reachability, available registration data and corporate asset relationships. Similarity is an investigation signal.
Review domains, IP:port records, URLs and file hashes. Filter the global repository by threat type, malware family, confidence, tags and timestamps.
Filter organization-related records by keyword, URL, discovery date and available metadata to investigate brand and data exposure signals.
Review mentions, files and archive references, with details and raw content where accessible. Content acquisition can involve request, approval, queue and processing stages.
Review new discoveries and changes by alert type, severity and time. Configure notifications and carry evidence into existing investigation and response processes.
Define domains, hostnames, IPs and keywords. Manage scanner operations, module permissions, sensitive account access, VIP monitoring scope and delivery configuration.
Follow an external finding from discovery to an informed handoff.
Bring together asset, account, brand, vulnerability and threat findings.
Review signals alongside organizational assets and technical evidence.
Assess alert type, severity, timing and investigation priority.
Notify, track and hand evidence to response teams and security leaders.
A common source of context. A different perspective for each team.
Bring alarm triage, IOC research, account exposure and dark web findings into a common investigation workflow.
Carry the findings into existing processes, with delivery options and access controls that support enterprise workflows.
UDP, TCP and TLS transport. Formats include RFC 5424, RFC 3164, CEF, LEEF and JSON.
Account and content data, with client scopes, IP allowlists and request limits.
Email rules by user, severity, alert type and subject. Active delivery services and recipients must be configured.
Module permissions and separate controls for sensitive account data, alongside tenant-based workspaces.
Product details you can share with your security team.
Internet-facing assets, DNS and certificates, services and vulnerability findings, account leak records, organization-related content, lookalike domains, dark web findings and global threat indicators. The configured scope determines what is monitored.
No. A leak record is evidence for an identity investigation. It does not, by itself, prove that the account is currently compromised. Similarly, an IOC in the global repository does not mean an incident has been detected in your environment.
Tetharion includes alert workflows, configurable email notifications, syslog delivery, scoped account/content API access and user permissions. Available delivery depends on active services and your configuration.
Start with your organizational domains and the scenarios you want to investigate: external asset exposure, account leaks, brand impersonation or organization-related content. The demo can focus on that monitoring scope.
Use Workspace login and enter your assigned tenant ID. You will be redirected to your dedicated workspace at app.tetharion.com.
Tell us what your team needs to investigate. Plan a walkthrough around your domains and priority scenarios.