Nutter Tools
Nutter Tools

A free toolbox that runs in your browser. A tool for every job.

Your files never leave your device

Images

  • Convert images
  • Compress images
  • Resize images
  • Crop
  • Watermark

PDF & files

  • Merge PDFs
  • Split a PDF
  • Images to PDF
  • PDF to images
  • Remove photo location

Video & audio

  • Compress video
  • Convert video
  • Video to GIF
  • Convert audio
  • Trim audio

Everyday

  • QR codes
  • Passwords
  • Time zones
  • Unit converter
  • Word count
  • Webcam test

Developer

  • JSON formatter
  • Base64
  • Regex tester
  • Hashes
  • JWT decoder

Site

  • About
  • Contact
  • Settings
  • Privacy
  • Terms
  • Site map
  • llms.txt

Everyday

  • Images
  • Video
  • Audio
  • PDF & files
  • Text
  • QR codes
  • Units & math
  • Time & dates
  • Color
  • Passwords & IDs
  • Device tests
  • Sun & moon

For developers

  • JSON
  • Encoding
  • Regex & cron
  • Web & auth
  • Hashing & encryption
  • Config files
  • Network
  • Browser
  • AI
  • Fake data
© Nutter Toolsnutter.tools
  1. Home
  2. Network
  3. COOP checker
Your files stay on your device

COOP checker

Fetches a page's Cross-Origin-Opener-Policy header through the proxy and rules what it isolates the page from across unsafe-none, same-origin-allow-popups and same-origin, flagging unrecognized values.

This tool is in beta

Still being tested. If a result looks wrong, tell us.

Report a problem

Press the button to read the headers

Nothing leaves this page until you do. The report grades the Cross-Origin-Opener-Policy header against its three real values, flags values browsers would silently ignore, and names which popup flows break under each policy.

COOP answers one question: when another document opens this page, or this page opens another, do the two windows get to see each other? Without it, the opener keeps window.opener and can navigate your tab after a user has logged in, the classic reverse tabnabbing setup. The safe default is same-origin, with one known exception: OAuth and payment providers need their popup to talk back, so those routes carry same-origin-allow-popups and keep the inbound protection. Two traps are worth checking for. A misspelled value looks configured while browsers silently treat it as unsafe-none, and a Report-Only header rehearses the policy without isolating anything. COOP is per response, so tightening it route by route is a valid rollout.

Target

The main document whose response headers are read

What leaves your browser

The one document fetch goes through this project's capped proxy server (GET only, public hosts only, size and time caps, rate-limited), because a browser page cannot read cross-origin response headers itself. The proxy never follows redirects. This page leaves your browser only when you press the button; never on load, never in the background. Nothing is sent anywhere else. Google Analytics still measures the visit to this page, and it never receives what you run through this tool.

Was this tool useful?