Sheas Cealer forges the SNI field through Chromium startup flags
Just Ceal It (can be used without a proxy for lawfully resisting network surveillance and conducting network research).
At a glance
- What is it?
- A WPF desktop tool that fakes the TLS SNI extension so destination hostnames stop appearing in plaintext, shipped as a Windows installer or a portable zip, with its rule set versioned in a separate repository.
- Who is it for?
- Sheas Cealer fits one narrow job on a Windows machine: keeping hostnames out of plaintext ClientHello messages for Chromium traffic, for research or for use against unauthorized monitoring. It is not a VPN, not a proxy and not encryption, so it should not be treated as a privacy layer on its own.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 173 days ago.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- SpaceTimee/Sheas-Cealer5,192 ★ · +35
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| SpaceTimee/Sheas-Cealer | 5.2k | 5.2k |
35 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The spoof rides on a Chromium launch flag, not on a network stack
Sheas Cealer introduces itself with the line Just Ceal It, and the self-description calls it a WPF (.Net8) desktop SNI spoofing tool. The mechanism fits in a single sentence: it exploits a property of Chromium startup parameters to forge the SNI extension mark. Everything technical sits outside this repository. The project links a written explanation on nicebowl.fun for the details, and the credit list names kit as the source of the entire principle foundation and NiceBowl for the detailed writeup. So what a reader installs is a Windows desktop front end that hands Chromium a parameter, not a network stack of its own. The code here is C# in Sheas-Cealer.csproj, which is what a GUI that launches a browser looks like, and not what a library another program links against would look like.
Two download shapes, plus a Scd build that carries its own runtime
Getting it onto a machine is two files and no build step. The preferred route is the Setup installer: download Sheas Cealer Setup.exe, run it, follow the prompts, and it installs. The second route skips the installer: download Sheas Cealer Zip.zip, extract it, and use the extracted copy as is. A third variant carries the name Scd and bundles the .Net runtime inside, so it starts on machines that have no .Net runtime installed. The stated price of that convenience is a larger file size and weaker cross-platform behavior, and the project says not to reach for Scd without a specific reason.
Sheas Cealer Setup.exe
Sheas Cealer Zip.zipWindows releases older than Win10 are pointed at the older 1.1.0 build instead of the current one.
An app update leaves your rules alone until you press the update button
The spoofing rules do not live in this repository. The built-in set is maintained in a companion project called Cealing Host, which is described as being updated continuously. Two behaviors follow from that split. First, updating Sheas Cealer itself never overwrites the rules already on disk, so a local rule set survives every app upgrade. Second, catching up with upstream becomes a deliberate act: press the update upstream rules button, or edit the override by hand when you want something the button does not produce. Two console tools sit alongside Cealing Host for that upkeep, Console-HostChecker as an automated checking script and Console-HostGenerator as an automated generation script. Skip the button and you keep whatever rules you had on the day you installed.
The tree shows a WPF shell with no command line anywhere in it
The top-level entries describe the program before you read a word of prose. App.xaml, App.xaml.cs and Pages/ are the standard WPF shell, Sheas-Cealer.sln and Sheas-Cealer.csproj are the build pair, and there is no command line entry point and no scripts directory.
App.config
App.xaml
App.xaml.cs
Consts/
Convs/
Exts/
Models/
Pages/
Preses/
Proces/
Props/
Rsces/
Utils/
Valids/
Wins/
Sheas-Cealer.csproj
Sheas-Cealer.slnWindows is the only desktop platform named as supported, with release 1.1.0 reserved for systems older than Win10. Everything else lives elsewhere: a cross-platform desktop build sits on the nix branch of this repository as Sheas Cealer Nix, and Sheas Cealer Droid covers Android.
It hides a hostname and leaves the rest of the session in plain sight
Read the mechanism narrowly and the limits follow from it. Sheas Cealer forges one field, the SNI extension in the ClientHello, through a Chromium launch parameter. Nothing in the description or the mechanism section claims a tunnel, a proxy or encryption, and the framing is resisting illegal network listening and doing network research without a proxy. The consequence for a reader is that the destination hostname stops being readable in plaintext while everything else about the session stays exactly as observable as it was: the address you connect to, the volume and timing of the traffic, and the fact that a connection was opened at all. The README does not document padding, cover traffic, or any fallback for destinations that need the real name, so treat it as one field being rewritten rather than as a privacy layer.
Newest tag is a December 2024 alpha while the branch kept moving
The published tags and the branch tell different stories, and the gap matters when you pin a version. The repository is not archived, and the last push to master landed on 26 May 2026. The newest release is 1.1.5-alpha from 30 December 2024, stacked on 1.1.4 from 22 December 2024 and 1.1.3 from 21 October 2024. So the newest downloadable build is an alpha, and nothing in the tag list tells you what currently sits on master. The README also says plainly that the project is still in development while trying to keep each formal release stable and usable. Distribution has narrowed as well: downloads come from the GitHub releases page, plus group files for people in the internal beta, and the earlier mirror on Lanzou cloud was withdrawn for reasons beyond the author's control.
Rules, docs and support all live outside the repository
Three external places carry what the repository does not. An agreement is linked first, as a privacy policy and a use agreement hosted on a team wiki, and readers are asked to read them before installing. Usage, terminology and build instructions sit in a separate docs site at docs.spacetimee.xyz, with the repository wiki open for community writing. Support runs through four QQ groups, a Telegram group named PixCealerChat, and an email address. Licensing is the weak point: the README carries a FOSSA scanning badge but names no license, so the redistribution terms are not stated in the README. Sibling projects push the same idea outward, with Sheas Dop handling DNS anti-pollution resolution and Sheas Nginx launching a Pixiv oriented Nginx.
Editorial conclusion
Sheas Cealer fits one narrow job on a Windows machine: keeping hostnames out of plaintext ClientHello messages for Chromium traffic, for research or for use against unauthorized monitoring. It is not a VPN, not a proxy and not encryption, so it should not be treated as a privacy layer on its own. Anyone adopting it should first read the two agreement documents it links, confirm that a rule set from Cealing Host matches the sites they actually visit, and accept that the newest downloadable build is still an alpha while master moves ahead of every published tag.
Frequently asked questions
What operating systems can Sheas Cealer run on?
Windows is the only platform named as supported, with pre-Win10 systems pointed at release 1.1.0. Other systems are covered by separate projects: a cross-platform desktop build on the nix branch as Sheas Cealer Nix, and Sheas Cealer Droid for Android.
Does Sheas Cealer need a proxy or VPN to hide what I visit?
No. The project presents itself as a way to resist illegal network listening and conduct network research without a proxy, and the mechanism is a forged SNI extension mark applied through Chromium startup parameters.
How do I update the spoofing rules in Sheas Cealer?
Updating Sheas Cealer itself never overwrites rules you already have. To sync with the upstream Cealing Host repository, press the update upstream rules button or edit the override by hand.
Where can I download Sheas Cealer from?
From the GitHub releases page, either the Setup installer or the Zip archive. People in the internal beta can also get builds from group files via the listed contact channels, and the former Lanzou cloud mirror was withdrawn.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/spacetimee-sheas-cealer)Star history chart for your README
[](https://hysenlabs.com/projects/spacetimee-sheas-cealer)Was this useful?