I'm so angry I'm shaking while typing this. Many others and I have reported this one alone, and it's still here! It looks like it's gotten more tabs to try to hide.
Please. Ban this filth. This is NOT okay.
There is no valid reason for children to be made on a generator that allows NSFW. And some of the tabs are filthy when I think of them in the context of CP.
It shouldn't be possible to make CSAM on Perchance, even if generator authors have combinations of dropdowns which combine age keywords with NSFW keywords. If there are combinations of keywords that produce CSAM, then that's a bug with the text-to-image-plugin that should be reported (you can DM me here). Reporting generators that are clearly designed to generate CSAM is helpful, but less so - it's more whack-a-mole, rather than solving the underlying issue.
If your concern is that people are generating non-CSAM pictures of children, and are possibly being sexually gratified by them (e.g. child beauty pageant pictures or similar), then it's quite hard to prevent that at the text-to-image-plugin level, since it's about the mind of the observer rather than the image itself. There's a surprisingly long tail of things in this category that even extend to semi-nude children in non-sexual situations - e.g. cherubs / renaissance paintings, tribal settings, swimsuits, and even semi-nude children with semi-nude adults in the same picture - e.g. breastfeeding, childbirth.
That said, there is certainly still a lot of room for improvement on the current CSAM-prevention system. Taking it to the next level is unfortunately more like a research project (mainly becasue of how cheap I need to run it) than simply flipping a "enable stronger CSAM filtering" switch, so I don't have a clear ETA at this point, but in the meantime it's helpful if people can report loopholes in the current system.