Sboxr DOM Documentation
  • Introduction
  • Getting Started
    • Prerequisites
    • Download Sboxr
    • Launch Sboxr
    • Register for Trial Access
    • Activate Subscription
    • Analyzing a Site
  • Finding Issues
  • Viewing Issues
    • Code Execution Issues
      • JSON Source
      • Non-JSON Source
      • Open Execution Details
      • Execution Flow Details
      • Verification and Remediation Advice
      • Duplicate Tainted Sources
    • Cryptographic Issues
    • JS Code Issues
      • View Cross-Origin Code
      • View Same-Origin Code
      • View All Code
      • View Code by Origin
    • Communication Issues
      • Cross-window Messaging Broadcasts
      • Cross-site Communications
      • Same-Origin Communications
      • All Communications
    • Data Leakage Issues
      • Sensitive Data Leakage
      • Non-sensitive Data Leakage
      • Non-sensitive Data leaked via Referrer header
      • All Data Leakage
      • All Data Leaked via Referrer header
    • Data Storage Issues
      • Sensitive Data Stored
      • Non-sensitive Data Stored
      • All Data Stored
  • View Live Event Stream
  • Event Location Details
    • Code Details
    • Window Details
  • Save/Reload Session Data
  • Troubleshooting FAQ
Powered by GitBook
On this page

Was this helpful?

  1. Viewing Issues

Communication Issues

PreviousView Code by OriginNextCross-window Messaging Broadcasts

Last updated 5 years ago

Was this helpful?

Sboxr captures all the DOM Communication performed by an application. It monitors the following communication channels:

  • Ajax calls, this includes XMLHttpRequest and fetch API use

  • Cross-windows messages sent via postMessage API

  • WebSocket communication

The following options exist for viewing these communication information:

Cross-Window messages broadcast
Cross-site Communications
Same-site Communications
All Communications