Finds out what this browser and this network will actually let us do, so the file bridge gets designed around real constraints instead of assumed ones. Nothing is stored and nothing leaves this page except the report you copy out yourself.
Run on load. No interaction needed.
The three ways a browser can obtain local bytes. If all three fail, binaries can only leave this machine as text.
The text-out path is only as wide as the largest paste that arrives intact. DLP tooling often truncates large pastes silently, so every payload carries numbered lines and an end sentinel - if it gets cut, we can say exactly where.
The in-direction depends entirely on this. Confirm each one actually lands in your Downloads folder at the stated size.
This is the fork in the road. If a shell runs, binaries can leave this machine properly via a small uploader script and none of the base64 paste awkwardness is needed. If not, binaries cannot leave through a browser at all.
PowerShell [Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes("PROBE"))
cmd + certutil echo PROBE> p.txt && certutil -encode p.txt p.b64 && type p.b64
macOS / Linux printf PROBE | base64
Getting this off the machine is itself the text-out test. If you can copy it into an email or a chat, mode 2 works.