Skip to content
SPECIFICTION
Get listed

Canarytokens vs Heralding

Canarytokens

canarytokens.org

Heralding

github.com

Side by side

FigureCanarytokensHeralding
Price fromFreeFree
Free planYesYes
Free trial——
Open source——
WebYes—
WindowsYes—
Linux—Yes
iOSYes—
AndroidYes—
Self-hostedYesYes
Plans published11
Spec score · Honeypot Software8.2 (#1)7.5 (#12)
PurposeCanarytokens are decoy tokens placed in networks, computers, and cloud environments to alert when accessed.Heralding is a simple honeypot that collects credentials.

Plans

Canarytokens

  • Canarytokens hosted serviceFree

Canarytokens pricing →

Heralding

  • HeraldingFree

Heralding pricing →

In their own words

Canarytokens

Canarytokens are decoy tokens placed in networks, computers, and cloud environments to alert users when accessed. The hosted service lets users create tokens without installing software; they can provide an email address to receive an alert when a token is triggered. Some token types also accept a webhook address. Documented examples include HTTP, DNS, Windows directory, AWS API key, Kubernetes configuration, and WireGuard tokens. The Fake IdP SAML App token has setup instructions for Microsoft Entra ID and Okta. Fake App is a Progressive Web App that alerts when opened and can include device location if location access is allowed; it currently supports Safari and Google Chrome. Sensitive Command monitors execution of a specified command on Windows and requires importing its registry file with administrator permissions. The Slack API Token is deprecated, and new tokens cannot be created, though existing ones continue to work. Use of the hosted service through canarytokens.org costs nothing. The maker also publishes the server as open-source software and recommends Docker for self-hosting.

Visit canarytokens.org

Heralding

Heralding is a free, self-hosted network honeypot that collects credentials. It runs on Linux and supports FTP, Telnet, SSH, HTTP, HTTPS, POP3, POP3S, IMAP, IMAPS, SMTP, VNC, PostgreSQL and SOCKS5. When a protocol makes them available, its authentication log records usernames and plaintext passwords. It also writes authentication attempts, session summaries and full session data to CSV and JSON Lines files. Session details can include timestamps, duration, source and destination IP addresses and ports, protocol, authentication attempts and protocol-specific auxiliary data. Session log entries are written after sessions end; authentication entries appear once a password has been transmitted. The README describes pip installation on Debian-based systems and Docker deployment using port mapping. Python 3.7.0 or higher is required. For separate packet captures per session, the README points to Curisoum and says it must be enabled in Heralding.yml. GitHub identifies the project as GPL-3.0 licensed.

Visit github.com