Why do iframes fail to embed?
Browsers refuse to frame pages that send X-Frame-Options: DENY/SAMEORIGIN or a restrictive Content-Security-Policy frame-ancestors directive. Mixed content (HTTPS parent embedding HTTP) also blanks the frame. SSO, OAuth widgets, and payment embeds hit these rules constantly.
This workbench loads a candidate URL in a controllable iframe, probes public framing headers via a short-lived proxy, simulates HTML sandbox permissions, and logs window.postMessage traffic so you can validate cross-origin contracts safely.
How to use this tool
- Paste a URL (or pick a preset), click Load / Audit headers, and read the embed verdict.
- Toggle sandbox flags and viewport size to mimic production embed constraints.
- Use the postMessage terminal to send JSON/string payloads and inspect inbound events from the frame.
Frequently asked questions
Can you probe localhost headers?
No — the server header probe blocks private hosts. You can still load http://localhost in the iframe from your browser for local widget testing.
Is framed content uploaded to stbox?
The live preview runs in your browser. Header audits fetch only framing-related response headers for public URLs and do not store bodies.
Why warn about allow-scripts + allow-same-origin?
Together they can let same-origin framed content remove the sandbox attribute, defeating the isolation model for untrusted embeds.