PSYCHPSYO.COM!

List of Tests

• ageXmlHeader.php
• metaAdult.html
• metaGeneral.html
• metaMature.html
• metaRtaLabel.html
• metaRtaLabelCaseSensitive.html
• preferSafe.php

Results

These are the results for all configurations I've tested so far. If a test is not listed for a configuration, that test has not been run for that configuration yet. You can also download these results as a JSON file: download results.json

Note that pretty much every setup passes metaGeneral.html, since that one requires not getting blocked.
I also don't consider passing preferSafe.php to be desirable, since it unnecessarily exposes the fact that parental controls are enabled to every website that a child might visit.

If you are the developer of any of these parental control systems and believe that the information for your system is incorrect or outdated, don't hesitate to contact me. I will gladly rerun the tests and update any findings.

Interpreting the Results

When interpreting these results, please keep in mind that, while they may look somewhat dire, most parental control systems on this list do manage to block a decent amount of adult content, based on other heuristics such as a page's URL or its contents. This is great for users of these systems, but not so much for developers of adult sites, who do not want their content shown to children. For a developer, it would be nice if there were a universally supported way of marking one's content as unfit for children. That way, developers can be certain that their content is getting blocked, and might be able to set up more granular blocking for various parts of a site.

One example of more granular blocking that this might enable is X (formerly known as Twitter), which does include one of the meta tags for adult content on user profiles that are marked as NSFW. Most parental control systems that I have tested either block the entirety of x.com, or nothing at all, both of which are suboptimal.