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 fast, 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 those requests are not 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. What isn't confirmed is written as unconfirmed.
Free, and quiet about it. No sign-up wall, no "enter your email to continue", no popup begging for a newsletter. There is one cookie banner, and nothing from Google loads until you answer it. Nothing from Google loads on the tool pages at all.
Who's actually behind this
It says "we" in a few places, but? 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. The tools are the ones I reach for, and the guides are the answers I've had to look up, get wrong, and look up again.
You can check my background on LinkedIn. I'd rather you know there's a real person answerable for the numbers. How the work is done, including where AI assistance fits in, is written down on the editorial policy page.
How the site is built
PacketNebula runs on WordPress, on a small virtual server that I rent and administer myself. It started as a hand-built static site, and in September 2026 I moved it to WordPress, the platform I maintain every day, because adding guides and reference pages is simply faster there. The trade-offs of that choice are in WordPress vs a static site.
The interactive tools are plain JavaScript running in your browser, so your passwords, tokens and files never leave the tab. A small number of checks (DNS, SSL, HTTP headers, WHOIS and RDAP, IP geolocation) do reach a server I run, because a browser cannot open those connections itself. Those requests are processed and discarded, not logged.
What you'll find here
News. Announcements from the AI and infrastructure world, read against their primary sources, newest first, with a plain statement of what is confirmed and what is only claimed. The reference trackers keep the prices, licences, retirement dates and deals in one place.
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. There are 24 of them.
Guides. Short, answer-first walkthroughs of the commands people actually search for: the exact line to paste, and a note on the gotcha that usually goes with it.
Reusing the figures and images
Every chart and diagram we draw is ours. 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. The photos and announcement images that open each news piece belong to their sources and are credited under the image; they aren't covered by that offer.
Found something wrong?
Good, tell me. A bug in a tool, a number that looks off, a command that 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 they are noted on the page when they change something that matters.