Run it, read it, keep it.

Every script here is meant to be piped straight into a shell on a server you administer. Each one states plainly whether it changes anything. The default is: it doesn't — read-only checks, printed as a short, clear report.

Before you run a one-liner against a production box, open view source on it first. That's the whole trust model — no obfuscation, no hidden steps.

On the run command: it uses curl -Ls, not -k. The -k flag skips TLS certificate verification, which would let anyone on the network path swap in a different script. Leave it off.

Verify before you run. Every script has a published SHA-256. Download first, check the hash, then run:

curl -Ls -o netcheck.sh orynium.com/scripts/netcheck.sh
sha256sum netcheck.sh
# compare with SHA256SUMS, then:  bash netcheck.sh

All hashes: SHA256SUMS

available scripts

netcheck.sh

read-only Ubuntu / Debian RHEL / CentOS v2.0

Linux network audit: NIC + MTU, routing, primary-IP vs gateway subnet, DNS, firewall state, VPN/tunnel/proxy detection (names the product), public-IP geo check, repo reachability, and per-domain DNS/TLS/route-trace when a site looks down. Read-only.

linux ~ bash

bash <(curl -Ls orynium.com/scripts/netcheck.sh)

view full script →sha256 eba785ec71db23d4…

netcheck.ps1

read-only Windows Server Windows VPS v2.0

Windows equivalent (PowerShell): adapters + MTU, routing, primary-IP vs gateway subnet, DNS, Windows Firewall state, VPN detection, public-IP geo check, and per-domain DNS/TLS/route-trace. Run it with the .bat launcher below — no execution-policy fight. Read-only.

windows ~ powershell

irm orynium.com/scripts/netcheck.ps1 | iex

view .ps1 →.bat launcher →

coming next

more scripts land here as they're written