Field notes
Notes
Short, original notes from running Codynet — what changed and why, the network quirks worth writing down, and how the site itself is built and kept honest. Less formal than the guides, but the same rule applies: no filler.
These notes are the working log behind Codynet: short, original write-ups of the network behavior worth remembering and the decisions that shape the site. Many come straight out of building and running the tools — why two resolvers disagree about the same record, how the site avoids retaining what you look up, or what changed in a given month and the reasoning behind it.
Where the guides explain a protocol from the ground up, the notes are field observations and product updates — closer to a lab notebook than a textbook. They exist because the small, specific findings are usually the ones that are hardest to find written down anywhere else.
I Found Out Why an HTTP Header Check Took 16 Seconds and Fixed It
One unusual hostname made the HTTP Header Tool wait twice as long as necessary and return a confusing error. I traced the problem, removed the unnecessary retry, and made the result clearer.
Read noteWhat Changed on Codynet — June 2026
A short, honest log of what we deepened across the tools and guides this month, and the principle behind every change: show the protocol's real answer.
Read noteWhy Two DNS Resolvers Give You Different Answers
Cloudflare says one thing, Google says another, and your laptop says a third. A field note on why that happens, when it is normal, and when it means something is actually broken.
Read noteHow Codynet Avoids Query Retention
Codynet resolves your lookups server-side, so honesty matters: here is exactly what leaves your browser, what we do and do not store, and where your history actually lives.
Read note