Introducing SirHurt's exploit status checker! List your exploit for FREE!

@prochanell3345 all rep is given as anonymous to prevent people attacking eachother over negative reps

@acexx bad spelling mistake

LOL, ice u getting dumbed each release 

1) SirHurt is trash

2) You're a pedo

Interesting release, I like the idea of a non-biased system which allows any exeucutor to be listed regardless of popularity.

I agree. Services should not be biased. Good job on this one.

@Ballistic i know it was to late for me to not type wrong

you ripped this off of what exploits are online..
babyhamsta wont stay too calm about this
also Misako > SirHurt
https://cdn.discordapp.com/attachments/924722337981530135/1005797035783495690/MISAKO_SHOWCASE.mp4

@59576 I would like to remind you the weareexploits.online api is public and the reason we utilize it is so we can display the update status of executors which have not gone through our registration/application process yet. Regardless of his opinion, it's an open source endpoint made with the intention of being used in other places besides the direct website, whether it be a lua script processing the json or an actual website. SirHurt makes no money or income off this status page and thus it's fair use of a tool made for public use. The SirHurt status page was made to inform consumers of the update status of not only SirHurt V4, but other executors as well. This endpoint is utilized because it has already existing data on exploits that haven't directly gone through us yet to be displayed there. Any executors that register directly with us will depend all on local resources rather than a third-party.

pov: https://whatexploitsare.online/

No thanks, don't fancy using a service made by a known pedophile. Also would appreciate if you take my software off your website.

@FluxusDevelopment Done and done.

@mrk0 I'm glad you agree! All exploit users should have a right to check on the status of there favorite products. We're glad to see new executors registering for this! A status page should be a free place of knowledge to inform the community and we believe any functioning executor should be allowed to list there service, regardless of size. Popular opinion should not be the main ground for determining if a executor should or should not be listed, because again, we here at SirHurt understand that such information should be free to all. Our intention is not to drive whatexploitsare.online out of business, but rather have an alternate source/place that both exploit developers and community members can go to if there products are rejected or not listed by WHAO.  I'm glad some exploits aren't like Fluxus and see the potential in having a secondary place to depend on exploit status for all. The issue with WHAO being the only place of it's kind give's the owner more power to influence and sway the community in his favor. If you got declined on WHAO for whatever reason, what would you do? nothing. You would of no longer had a third party source you could of used to list your exploits status information. Considering WHAO also listed product purchase information or download information on site it could give the owner grounds of determining which products should get traffic and which shouldn't which could lead to a degree of market manipulation by forcing it's users to abide by a chosen list of exploits. I don't like or support these odds, and because I've seen worthy executors myself be declined I will not stand to let one individual or one community to have that kind power and I've decided to take it in my own hands to limit this power by offering a second place for developers and consumers to get there information. We will approve every application as long as we deem the executor as functional, safe, will work with our api, and abiding by our own TOS. The difference between SirHurt's status page and WHAO is that we will accept all as long as you have an active & functional executor with a level of demand, even if it's not the popular demand. As a informative place should be.

LOL how are you going to talk trash on my service then use it's API for your website?

@HamstaGang I think you took the wrong impression by my comments. Your service itself is fine and works as intended and the only issue with it is current management and how it runs. SirHurt's status page was created with the intention to not 'overthrow' or 'crap talk' your service but to provide a secondary place to supply exploit update information for exploits you and your community refuse to add to your own service. You and your communities refusal to add support for not only SirHurt but smaller products has made me see that a second place to check exploit statuses needs to exist. I've noticed multiple script developers use your API directly in there lua scripts to fetch information behind specific exploits supported by your API making your service used in more ways than one. The issue with your service not adding support for small executors or sirhurt could also lead to a lack of compatability for those products not supported by you if the developer only has your API to depend on fetching certain information about certain exploits. By not adding support for a executor you do not only remove one source a person can use to get information on there chosen roblox cheats but it may also cause compatability issues with lua developers who depend on a specific API to get the information they need on the exploit executing their code because they aren't configured to work with that API. I created SirHurt's status service not only as a way to allow smaller exploits (and sirhurt) to provide information about there product while giving lua developers who depend on accurate information from an API a secondary method to get that information about the executor that it requires if the 1st one fails. The only part of weareexploits.online that SirHurt adapted was the live JSON api file (which is public and free to use) to supply information on the additional exploits such as Synapse that haven't directly gone through sirhurt's application process yet. I wasn't aware that you wanted to be credited when your API bc I saw no where on site where it said credit had to be added for use of the service. I'm more than happy to add a small credits list on the page if that's what you really desire ^_^