What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether most knocking bots run on already-compromised servers and why one hosting provider dominates.From this comment
- Whether attacks began immediately at server startup or took time to ramp up.From this comment
- Whether the site publishes its list of attacking IP addresses anywhere.From this comment
- Whether SSH passwords seen come from leaks or are generated from usernames.From this comment
- Whether using fail2ban reduces the hits or they still appear in logs.From this comment
What they doubted or pushed back on our summary
- The page is cut off and cannot be scrolled sideways on the reader's screen.From this comment
- Hammering port 22 with common credentials seems pointless since password-accepting servers are long compromised.From this comment
- A more responsible hosting provider actively blocks abusive machines, so why does this one not.From this comment
- Existing monitoring and visualization tooling may already cover much of what this site shows.From this comment
What the maker answered our summary
31 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Most knocks come from compromised servers, and one large provider likely leads even when measured per registered IP.From this comment
- Attempts started almost immediately, then accelerated from under one to over eight knocks per minute.From this comment
- Attackers commonly append simple suffixes to usernames, and the trivia pane highlights that pattern.From this comment
- Setting up fail2ban would reduce the noise but would remove the traffic worth visualizing.From this comment
What a builder can take from it: Exposing any server publicly invites constant automated break-in attempts, so designers should expect noise early and plan safety as well as observability. our reading
The title, taken apart our calculation
This post got 224 points; the median for all 1442 posts is 112.
When it was posted our calculation
Sunday at 17:00 UTC. Of 3,019 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 109 (3.6%) reached 50 points; on Sundays it was 3.4% of 5,343. The average over all hours is 2.9%. One post's time does not explain its result; the full table of hours is on the Show HN hub.
Check your title our calculation
Type the title you plan to post. It is compared with 1,442 Show HN posts that reached 50 or more points: its length, its shape, and how posts of that length and shape did. Nothing is sent anywhere.
Type a title above to see where it sits.
Draft my Show HN post
Paste your site address and get title options and a first comment for your own Show HN post, written from what your site says and checked against the numbers above. Nothing is posted for you.
Free to try and no account needed. FoxPlug is for people who ship several projects and keep stalling on telling anyone: it turns what you ship into posts you approve before anything goes out. See what each plan includes.
More teardowns
Points, comments, titles and times are Hacker News's own numbers, read from the post itself, last updated Nov 2026. Summaries of what people said are ours, written in our own words, and each one links to the comment it came from. Percentages and medians marked "our calculation" are computed from the posts counted on the page: they describe what happened, not what will happen to your post. FoxPlug posts nothing for you. Plans and limits are on the pricing page. Questions: support.
After the launch post: a changelog your users read
A launch brings visitors once. FoxPlug turns what you ship afterwards into a public changelog and ready posts, so the next visitor finds something new.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with