What this site is
An independent, English-language reference for Roblox executors on PC. Each of the 19 profiles is built from traceable records: tracker entries, repository descriptions, sandbox scores, domain scans, and forum threads. Where a record exists, the page cites it. Where no record exists, the page says so.
The site is not a download directory. It does not host executables. The Download buttons on profile pages are placeholders until a verified source is inserted. The site is not affiliated with Roblox Corporation or with any executor developer. It does not sell placement, accept payment for a profile, or rank executors by commercial relationship.
What this site is not
- It is not a malware analysis lab. The site does not execute the files it describes. It compares public records. A sandbox score or a domain scan is a record, not an audit performed by this site.
- It is not a ranking service. There is no "best executor" list, no safety score, and no stars or ratings. The site does not have a basis for those claims, and it does not make them.
- It is not a news site. It does not publish announcements, rumors, or "breaking" updates. It records what is already public and dated.
- It is not a community forum. It does not host user comments, reviews, or testimonials. The comments cited on some profile pages come from third-party sites, and they are cited as third-party comments, not endorsed.
- It is not affiliated with Roblox Corporation. Roblox's Terms of Use prohibit exploiting, and this site does not encourage or facilitate it. The site documents what public records say about software that violates those terms.
How sources are selected
The site uses four kinds of sources, in descending order of weight: tracker measurements, independent behavioral signals, project-controlled claims, and domain reputation scans. The Research Notes page explains each kind in detail. The short version: a tracker that runs the sUNC suite is a stronger source than a website that claims a score, and a sandbox that ran the file is a stronger source than a website that describes the file.
No source is treated as definitive. A tracker entry can be outdated. A sandbox can only describe what it observed. A domain scan describes a website, not a binary. A project-controlled page describes what the project says about itself. The site keeps the sources separate because they answer different questions, and combining them into a single verdict would hide which question is being answered.
When two sources conflict, the site records the conflict rather than picking a winner. Velocity's two domains, SirHurt's four measurements, and Volcano's changelog-versus-phishing-flag are examples. In each case, the page explains what each source says and does not merge them into a resolution that the records do not support.
Why no author is named
Every profile on this site is built from records that a reader can open and check. The value of the page is not in who wrote it; it is in whether the records support what the page says. Naming an author would not change whether a ScriptBunker entry says 100% sUNC or whether a Bitdefender report describes a fake installer. It would add a credential without adding a check.
Some sites name authors to establish expertise. This site does not claim expertise in malware analysis, reverse engineering, or executor development. It claims that the records it cites exist and say what it says they say. That claim is checkable without knowing who assembled it. If a page says a tracker recorded 59% sUNC, you can open the tracker and see the 59%. The author's identity is not required for that verification.
If a future version of this site adds an author byline, it will be because the site is doing something that requires one: original testing, a credential, or a claim that depends on the author's identity. Until then, the byline is the records.
How corrections work
If a claim on this site is wrong and you can point to a better source, the claim should change. A correction is not a comment or a counter-claim. It is a source that contradicts what the page says. If the source is stronger than the one the page used — a tracker measurement that contradicts a website claim, a sandbox report that contradicts a description, a dated record that contradicts an undated one — the page will be updated.
The correction route is a single channel: the contact address published in the site's metadata and on the legal pages. There is no comment form, no community thread, and no public argument about whether a page is right. A correction is a source, sent to the site, evaluated against the source the page used, and applied if the source is stronger.
When a correction is applied, the change is recorded in the Changelog with the date and the source that justified it. A page that is corrected without a changelog entry is a gap in the record. The site's goal is to log corrections as they happen, and to describe the gaps when they are noticed.
What "Unknown" means in this site's voice
On this site, Unknown is not a synonym for "bad," "unsafe," or "nonexistent." It is a description of the evidence state. A profile that says Unknown in every field is a profile where no public record was found. A profile that says Unknown in one field is a profile where the record exists but does not cover that field.
The site uses Unknown instead of guessing because a guess would make the page look more complete and would make the record less useful. A reader who wants to know what is known about an executor can see, at a glance, where the record stops. That is the point of the format. It is also the reason some pages are short and one page is almost empty.
Editorial questions
Who runs this site?
The site does not name an individual or a team. It publishes records and cites them. If a future version adds an author byline, it will be because the site is doing something that requires one: original testing, a credential, or a claim that depends on the author's identity.
How is the site funded?
No funding relationship is disclosed on this site because no funding relationship affects the content. There is no paid placement, no affiliate link, and no sponsored profile. If that changes, it will be disclosed on the page where it applies.
Does the site accept guest posts or sponsored content?
No. The profiles are built from records, not from submissions. A developer cannot pay to have a profile written, changed, or removed.
How can I contact the site?
The contact address is published in the site's metadata and on the legal pages. Corrections are the primary reason to use it. A correction is a source, not a comment. If the source is stronger than the one the page used, the page will be updated and the change will be logged in the Changelog.
Why is there no "About the author" section?
Because the value of the page is in the records, not in the author. A reader can open a tracker entry and check the score. A reader can open a Bitdefender report and check the description. The author's identity is not required for that verification. If that changes, the byline will be added.
Does the site take a position on whether exploiting is right or wrong?
No. The site documents what public records say about software that violates Roblox's Terms of Use. It does not encourage exploiting, and it does not moralize about it. It also does not claim that any executor is safe, because the records it cites do not support that claim.