DigitalOcean Referral Badge
cloud1
cloud2
cloud3
cloud4
cloud5
cloud6
← Back to catalog
code proto

Protocol anomaly

Syndu annotates all incoming traffic and extracts behavioral signals that help explain intent. This page defines the proto signal — what it means, how to interpret it, and how it will later connect to live evidence across IPs, subnets, organizations, ISPs, countries, and cities.

Signal gist Request structure or protocol-level signals deviate from typical browser HTTP traffic.
Read the definition → View live signal sections →

Definition

Canonical reference for proto behavior.
Catalog code
proto
Display name
Protocol anomaly
How to read this signal
This annotator represents a behavioral pattern, not a claim of identity. It’s designed to help you understand why certain traffic looks suspicious, automated, probing, or exploit-oriented — and to support consistent reporting across the Syndu system.
Explanation
Flags anomalies at the HTTP/protocol layer such as malformed request structure, unusual header formatting/order, invalid versions, or other indicators that the client is not a standard web browser. Useful for spotting scanners, fuzzers, and custom tooling, and for explaining “nonstandard client behavior” in reports.

Live sections

These panels will be wired to real metrics, enrichment context, and drill-down links.
Signal footprint over time
Rolling volume, bursts, first/last seen, and time-window slices (e.g. last hour/day/week). This will help separate chronic background noise from active campaigns.
Coming next: time series + burst markers
Top affected entities
Links to the entities where proto is most present: IPs, subnets, organizations/ASNs, ISPs, and geographies — with “why” context.
Coming next: entity leaderboards + drill-down
Enrichment context
How enrichment affects interpretation: known crawlers, monitored ranges, trusted scanners, or policy exceptions. This is where “benign but noisy” gets separated from “unknown and risky.”
Coming next: enrichment flags + allowlist context