Regardless, the point of neverssl.com is that a non-technical user can learn "if I'm on a new wifi network and I see errors when I try to visit pages I can enter neverssl.com and get to the wifi login". Adding ssl + a redirect is much easier and more effective than trying to retrain everybody to manually type http.
It probably should have been named wifilogin.com or something. But renaming it has the same retraining issue.
I type into the address bar: `http://example.com` and it corrects it to the HTTPS version. Even when I try to change the URL back to the `http://` it goes to the HTTPS version. When I try the same with curl as in `curl -v http://example.com` I can see the HTTP traffic coming through correctly i.e. the site still supports HTTP.
Note that I have configured "Don't enable HTTPS-Only Mode" in the Firefox settings. I use some addons although none to specifically redirect my requests to HTTPS...
Enable the web developer tools (Menu->More Tools->Web Developer Tools), visit the site again, and see if it is directly visiting the site or getting a redirect.
I additionally tested with my own site: http://masysma.net/31/web_main.xhtml. It is configured to not redirect to HTTPS except for the root node (http://masysma.net). It is not configured to behave any differently for user agents and hence the redirection (or no redirection) behaviour can also be checked by the commandline tools that print the course of the redirection (like curl, wget).