How to report a Roblox script listing?#
Email report@redzhub.dev with the listing URL, your concern and the change you want. We fetch loaders as text and never run them, so a status is not proof a script works.
- Identify the listing. Include its redzhub.dev URL and the displayed script or hub name. A page can contain several entries, so check that the name identifies the one you mean.
- Describe the issue. Say whether you found a broken destination, suspect malicious behavior, noticed inaccurate attribution or want an author takedown. Separate what you observed from what you suspect.
- Attach relevant evidence. Include the destination URL, error text or a redacted image where useful. Do not run a script to gather evidence or send passwords, session cookies or access tokens.
- State the requested change. Specify a correction, review or removal. For multiple listings, pair each URL with its own reason so we can assess each concern separately.
Choose supporting details from the report types below.
Evidence for broken links and suspected harm#
A broken destination needs an error report; suspected malicious content needs evidence of the concern. An error message shows an availability problem. A claim about harmful behavior needs the specific text or behavior that raised your concern and where you found it.
| Report type | Useful supporting detail |
|---|---|
| Broken destination | Listing URL, destination URL, error text and when observed |
| Suspected malicious content | Listing URL, suspicious text or behavior, and where the evidence came from |
| Incorrect attribution | Listing URL, disputed credit and a source supporting the correction |
| Author takedown | Listing URL, material at issue and proof connecting the requester to its authorship |
The screening methodology explains what our text checks cover. Describe the issue directly: quote the error or identify the suspicious passage rather than relying on a listing label. For an authorship dispute, also show your connection to the material.
What should an author include for copyright removal?#
An author requesting copyright removal should identify the listing, explain which material is theirs and include proof of authorship. A project page or repository history can help show the original material and connect you to it.
A script takedown request should distinguish our listing from the externally hosted source. Explain whether the concern involves copied text, attribution or the inclusion of a link. A matching display name alone may leave the authorship connection unclear; explain how your reference supports the request.
redzhub.dev is an independent index, not the Redz Hub developers’ site. The about page explains who we are. Point us to the specific redzhub.dev content you want reviewed.
Review, copy restrictions and removal#
We disable copying for the reported listing, review the evidence and remove the listing when warranted. Disabling copy is a precaution during review; it does not establish that an allegation is true.
Our review covers content indexed by redzhub.dev. We promise neither a response deadline nor a particular outcome. Use the script directory to locate any other entries you want to report, and give evidence for each. A report about one listing does not establish a problem with others. Roblox incidents need a separate platform report.
Reporting content on Roblox#
Roblox rule violations belong in Roblox’s Report Abuse tools. Roblox’s reporting guidance asks you to report the specific chat, message, experience or other content involved. Emailing redzhub.dev does not submit a Roblox report.
Roblox states that exploiting violates its Terms of Use and can result in account deletion in its cheating and exploiting guidance. Our text-only checks cannot establish runtime behavior or account safety. We never run loaders, and a status does not prove a script works. To report a Roblox script listing here, email its URL and the evidence above to report@redzhub.dev.