About PacketNebula
PacketNebula exists because most online tool sites are slow, ugly and a little nosy. You paste a JWT into some random page and immediately wonder where it just went. You open a subnet calculator and sit there while three ad networks load before the box even accepts a keystroke. I got tired of it. So this is the version I wanted for myself: tools that load instantly, keep your input on your machine, and tell you the answer before they tell you their life story.
What this site believes
- Your input is none of my business. Every tool that can run entirely in your browser does. When something genuinely needs a server (a DNS query, an SSL check), the page says so out loud, and nothing about your request gets logged.
- The answer comes first. Every guide opens with the command or the verdict. The background sits underneath, for when you actually want it, not as a tax you pay to get to the point.
- Numbers get sources. If there's a figure on a page, there's a link to where it came from. No vibes-based statistics.
- Free, and quietly so. No sign-up wall, no "enter your email to continue", no popup begging for a newsletter you didn't ask for.
Who's actually behind this
It says "we" in a few places, but honestly? It's one person. I'm Stéphane Cardon, a network & cybersecurity engineer. Day to day that's architecture, LAN and WLAN, a fair amount of system administration, more PowerShell than I'd have predicted ten years ago, and keeping the whole thing secure. Everything here comes out of work I actually do: the tools are ones I reach for, and the guides are the answers I've had to look up, get wrong, and look up again. If I haven't run into a problem myself, I try not to pretend I have.
You can check my background on LinkedIn. I'd rather you know there's a real person standing behind the numbers.
How the site is built
PacketNebula is a fully static site. Every page is plain HTML, built ahead of time and served as a file, which is why it loads the way it does. The interactive tools run as JavaScript in your browser, so your passwords, tokens and files never leave the tab. A small number of checks (DNS, SSL, HTTP headers) do reach a server I run, because they have to, and those requests aren't stored. If you're curious about the trade-offs of building a site this way instead of on WordPress, I wrote a whole piece on it: WordPress vs a static site.
What you'll find here
Two things, mostly. Tools: subnet math, password strength, JWT internals, cron schedules, hashing, DNS and SSL lookups, and a growing pile of small utilities that each do one job well. Guides: short, answer-first walkthroughs of the commands people actually search for, the kind where you just want the exact line to paste and a quick note on the gotcha. New ones land regularly.
Reusing the figures
Every chart and diagram here is mine. Reuse them for free, the only ask is a visible link back to the page they came from. That's the entire license, no form to fill in.
Found something wrong?
Good, tell me. A bug in a tool, a number that looks off, a command that's changed in a newer release: the contact page goes straight to me. Corrections make the site better for the next person who lands on it, and I read every one.