Have tested access to you site with fiddler, and see that when accessing to you domain in http, there is a 302 response (redirect). Not sure how your DNN is configured on IIS ...
Usually you would have 200 response (OK) exemple on www.dotnetnuke.com
Tested access to https://www.hishandsreader.org with fiddler too, and it well respond first then redirect to non https port. So with this configuration, i'm not sure you'll be able to get ssl running on pages of your site.
a last fiddler trace sample on the dotnetnuke Secure login page
So, i think you'll have to see with your hoster to make SSL work well on your dnn install.
After corrected configuration, to test SSL, create a page for that and don't test on your home or your login page.
You would be able to access the test page by http and https if SSL enable at site level and if the page is configured as secured and not enforced secure. (enforced secure don't allow to navigate to the page by http if secured)
HTH