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. Web & auth
  3. Source map exposure checker
Your files stay on your device

Source map exposure checker

Check whether a site's deployed bundles expose reachable source maps and whether those maps carry original source.

This tool is in beta

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

Report a problem

Fetch a page or paste its markup to check the deployed bundles.

A map reference and an exposed map are different findings. A comment pointing at a 404 is untidy but not a leak; a map that answers is a leak when it carries sourcesContent, because that is the original unminified source with comments. The remediation, in order of preference: stop deploying .map files, strip the sourceMappingURL comment too (a comment alone still tells attackers the maps existed), or upload maps to your error monitor at build time instead of the web server. This check is markup- and fetch-level only: scripts a tag manager injects at runtime are invisible, and nothing is executed.

Page

Input
http or https; fetched through the site proxy
More settings▾

Only first-party scripts are followed, up to 8 per run; third-party scripts are listed and skipped. Each proxied response is readable up to 4,096 characters, so a bundle's trailing sourceMappingURL comment is only visible when the whole bundle fits that window; otherwise the conventional script-plus-.map address is probed instead. Map files are inspected for source counts and the sourcesContent flag and nothing else: no map content is ever shown or kept.

More web & auth tools

  • Subresource integrity
  • CSP evaluator & builder
All web & auth tools

Was this tool useful?