Use TLS SNI to hide your servers (incl. Citrix) from IP-based mass exploitation
Comments on “Use TLS SNI to hide your servers (incl. Citrix) from IP-based mass exploitation”
3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked
A Hrih News story walks through hardening Citrix NetScaler TLS listeners against IP-based mass exploitation by using SNI enforcement. The author's lab tests on NetScaler CPX 13.0 and 14.1 show default vservers serve their certificate to clients with no or wrong SNI.
Why it ranked
No. 76 of 155 with a score of 0.60. The panel rated it highest on technical depth (0.93) and substantiated (0.81), lowest on audience breadth (0.36). The judges disagreed most on new information (spread 0.47), so the story is marked contested.
- AI judgeJudge 2claude-haiku-5-5
- Detailed, lab-tested hardening guide for Citrix NetScaler TLS/SNI configuration; practical for security and infrastructure admins, mostly tutorial with moderate evidence and limited broad significance.
- AI judgeJudge 3gpt-5.6-luna
- A detailed, lab-tested NetScaler hardening procedure with commands, test matrices, failure modes, and explicit limitations. It is highly actionable for security and infrastructure operators, though narrower in audience and not a substitute for patching.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.60total under rubric v2.2Contestedjudges differ by 0.47 on new information
- Significance0.49
- Reader interest0.68
- Audience breadth0.36
- Practical relevance0.79
- Substantiated0.81
- Technical depth0.93
- New information0.80
- Counts against: Promotional0.06
- Counts against: Overclaim0.27
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| Significance | 0.50 | 0.35 | 0.62 | 0.49 | 0.27 | +0.24 | +0.118 |
| Reader interest | 0.63 | 0.60 | 0.80 | 0.68 | 0.20 | +0.26 | +0.176 |
| Audience breadth | 0.24 | 0.50 | 0.35 | 0.36 | 0.26 | +0.13 | +0.047 |
| Practical relevance | 0.69 | 0.80 | 0.88 | 0.79 | 0.20 | +0.22 | +0.173 |
| Substantiated | 0.95 | 0.70 | 0.78 | 0.81 | 0.25 | +0.05 | +0.041 |
| Technical depth | 1.00 | 0.90 | 0.90 | 0.93 | 0.10 | +0.05 | +0.047 |
| New information | 0.93 | 0.50 | 0.97 | 0.80 | 0.47 , above the contested threshold | +0.05 | +0.040 |
| Promotional | 0.04 | 0.10 | 0.03 | 0.06 | 0.07 | −0.19 | −0.011 |
| Overclaim | 0.44 | 0.20 | 0.18 | 0.27 | 0.26 | −0.11 | −0.030 |
| Sum of contributions | +0.601 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.601 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-10-28/76/"><img src="https://rubric.hrih.si/badge/2026-10-28/76.svg" alt="Ranked #76 on Rubric, 28 Oct 2026" width="245" height="28"></a>Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 8 pts, not on front page
Recorded for context only, checked 28 Oct 2026, 06:47 UTC. It played no part in the ranking.