Skip to content

Viewing Detections

The Detections page is your central hub for monitoring all threat events captured by WebDecoy. Every decoy trigger, bot scanner alert, and endpoint interaction is recorded here.

  1. Click Detections in the sidebar
  2. View the detections table
  3. Use filters and search to find specific events
ColumnDescription
TimestampWhen the detection occurred
SourceWhat triggered it (decoy_link, endpoint, bot_scanner, etc.)
MITRE TacticATT&CK tactic classification
IP AddressVisitor’s IP
Bot Score0-100 bot likelihood
ActionWhat action was taken (logged, blocked)
MenuView details, block IP, etc.
SourceIconDescription
decoy_link🔗Hidden honeypot link accessed
endpoint📡API honeypot triggered
bot_scanner🤖JavaScript scanner detection
wordpress_plugin📝WordPress plugin detection
sdk🔧Server-side SDK detection

Use filters to narrow down detections to specific criteria.

Select one or more detection sources:

  • Decoy Links
  • Endpoints
  • Bot Scanner
  • WordPress Plugin
  • SDK

Choose a time period:

  • Presets: Last 24 hours, Last 7 days, Last 30 days
  • Custom: Select specific start and end dates

Set minimum and maximum bot scores:

  • Slider from 0 to 100
  • Example: 70-100 to see only high-confidence bots

Filter by visitor location:

  • Multi-select countries
  • Based on GeoIP data

Toggle specific risk flags:

  • Is Proxy
  • Is VPN
  • Is TOR

Filter by what happened:

  • Logged (recorded only)
  • Blocked (access denied)
  • Challenged (CAPTCHA shown)

For endpoint detections:

  • GET, POST, PUT, DELETE, PATCH
  1. Click Filters to expand the filter panel
  2. Select your criteria
  3. Filters apply automatically
  4. Click Clear All to reset

Currently, filter settings are not saved between sessions. Clear your filters before navigating away if you want a fresh view.


The search box allows you to find detections by:

  • IP Address: 192.168.1.100
  • User Agent: Mozilla or Googlebot
  • Decoy Name: Search by the decoy that was triggered
  • Detection ID: Exact ID match

Search is debounced (300ms delay) for performance.

Sort ByDescription
Most RecentNewest detections first (default)
Oldest FirstHistorical view
Threat ScoreHighest threats first
Bot ScoreMost bot-like first
  • Descending (default): Highest/newest first
  • Ascending: Lowest/oldest first
  • Default: 50 detections per page
  • Use page navigation at bottom
  • Total count shown above table

Click any detection row to open the detail panel showing comprehensive information about that event.

The detail panel is organized into collapsible sections:

┌─────────────────────────────────┐
│ Detection Details │
├─────────────────────────────────┤
│ ▼ General Information │
│ ▼ Threat Scoring │
│ ▼ MITRE ATT&CK │
│ ▼ IP Intelligence │
│ ▼ Geographic Data │
│ ▼ Request Details │
│ ▼ Endpoint Data (if applicable)│
│ ▼ Rule Enforcement │
└─────────────────────────────────┘

FieldDescription
Detection IDUnique identifier (det_xxx)
TimestampExact date/time (UTC)
SourceDetection source type
PropertyWhich property caught this
FieldDescription
IP AddressClient IP
User AgentBrowser/bot identifier
URLRequested path
RefererWhere they came from
HTTP MethodGET, POST, etc.
ProtocolHTTP/1.1, HTTP/2

Key headers displayed:

  • Accept
  • Accept-Language
  • Accept-Encoding
  • Connection
  • Cache-Control

FieldDescription
CountryCountry name and flag
CityCity if available
RegionState/province
Postal CodeZIP/postal code
TimezoneVisitor’s timezone
CoordinatesLatitude/Longitude
FieldDescription
ASNAutonomous System Number
ISPInternet Service Provider
OrganizationNetwork owner
IndicatorMeaning
🔴 TORTraffic from TOR exit node
🟠 VPNUsing VPN service
🟡 ProxyBehind proxy server
🟣 HostingDatacenter/hosting IP
AnonymousKnown anonymizer
🔵 High-RiskKnown malicious

Shows the hostname associated with the IP:

Hostname: ec2-192-168-1-100.compute-1.amazonaws.com

If enabled, detections include data from AbuseIPDB.

FieldDescription
Abuse Score0-100 confidence of abuse
Total ReportsNumber of abuse reports
Last ReportedMost recent report date
CategoriesTypes of abuse reported
ScoreRisk LevelMeaning
0-10Very LowClean or minimal reports
11-25LowSome suspicious activity
26-50MediumMultiple reports
51-75HighSignificant abuse history
76-100CriticalKnown malicious IP
  • Port Scan
  • Brute Force
  • Web Spam
  • SQL Injection
  • Hacking
  • Fraud
  • DDoS Attack

For detections from endpoint decoys, additional information is shown.

FieldDescription
Request MethodPOST, PUT, DELETE, PATCH
Content-Typeapplication/json, etc.
Body SizeRequest body size in bytes
Has Auth HeaderAuthorization header present

If body capture is enabled:

{
"username": "admin",
"password": "test123",
"remember": true
}
SignatureConfidenceLocation
SQL InjectionHighbody.password
XSSMediumbody.comment
Path TraversalHighurl

Shows what automated actions were taken.

StatusMeaning
PendingRules not yet evaluated
EnforcedRules executed successfully
FailedRule execution failed
SkippedNo applicable rules
FieldDescription
IntegrationCloudflare, AWS WAF, etc.
ActionBlock, notify, etc.
TimestampWhen action was taken
ErrorError message if failed

From the detection detail panel or table menu:

ActionDescription
View DetailsOpen detail panel
Block in CloudflareManual IP block
Copy IPCopy IP to clipboard
Copy Detection IDCopy ID for reference
ExportDownload detection data
  1. Open detection details
  2. Click Block in Cloudflare (if configured)
  3. Confirm the block
  4. IP is added to Cloudflare WAF

  1. Check the checkbox on detection rows
  2. Select action from bulk actions menu
  3. Confirm the operation
  • Export Selected - Download as CSV/JSON
  • Block All IPs - Block all selected IPs