# Rules.sonarsource.com not reachable anymore

**URL:** <https://community.sonarsource.com/t/rules-sonarsource-com-not-reachable-anymore/177316>\
**Category:** SonarQube Server / Community Build\
**Tags:** sonarqube\
**Created:** [February 6, 2026, 9:25am UTC](https://community.sonarsource.com/t/rules-sonarsource-com-not-reachable-anymore/177316 "2026-02-06T09:25:20Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![karlhorky](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/karlhorky/32/77560_2.png) [@karlhorky](https://community.sonarsource.com/u/karlhorky)\
**Post date:** [September 19, 2026, 5:08pm UTC](https://community.sonarsource.com/t/rules-sonarsource-com-not-reachable-anymore/177316/16 "2026-09-19T17:08:02Z")

</div>

Oh wow, I ended up here while digging into the related RSPEC documentation removal.

The endpoint I originally found broken is the separate `sonarsource.github.io/rspec` site, but I see from the official statement above that both the rules site and RSPEC repo were affected.

The scale of the broken references is pretty surprising. `rules.sonarsource.com` is now `NXDOMAIN`, while GitHub code search reports about 13,760 files referencing it in total. Only 20 of those are in the SonarSource org.

On the RSPEC side I found a similar situation: 923 occurrences across 626 committed files in SonarJS, plus about 420 files outside SonarJS referencing the public RSPEC site.

I posted the detailed RSPEC findings and one possible alternative here:

> [@Rspec github repository is gone/private?](https://community.sonarsource.com/t/rspec-github-repository-is-gone-private/177308/7):
>
> I ended up here after finding the downstream effects of making the RSPEC repository/site private. The SonarSource/SonarJS repo still contains many public links to sonarsource.github.io/rspec, which now redirect users through GitHub authentication instead of showing the rule documentation: I signed up for this Discourse to figure out what happened to these public docs. I count 923 sonarsource.github.io/rspec occurrences across 626 committed files in SonarJS alone. GitHub code search also…

And the `eslint-plugin-sonarjs`-related breakage here:

> [@Eslint-plugin-sonar Links to rule docs broken on GitHub page](https://community.sonarsource.com/t/eslint-plugin-sonar-links-to-rule-docs-broken-on-github-page/178145/7):
>
> Victor, hey waving_hand nice to see you again on the SonarSource message boards. I came here because I’m still seeing many broken rule documentation links in the SonarSource/SonarJS repo: I signed up for this Discourse to find out why the public docs are now missing. I checked the change you made after this report. It looks like it removed the broken RSPEC links from two generated tables, but the main ## Rules table still contains 295 of them. And it seems to go quite a bit further t…

---

_[View the full topic](https://community.sonarsource.com/t/rules-sonarsource-com-not-reachable-anymore/177316)._
