improve How-to-Test page and exampleadultsite.com

While trying to figure out why OpenDNS was no longer working for me, I stumbled across https://support.opendns.com/entries/25897009-How-to-Test-for-Successful-OpenDNS-Configuration-

When I tested exampleadultsite.com, I got a fail - but at the time I thought it was a pass! This caused me to run around in circles for even longer. (Turns out I needed to run the Updater )

A few changes to the two web pages involved could make things clearer.

The exampleadultsite.com page is too upbeat; it looks like a success page because it has the OpenDNS orange icons on it and talks about filtering. It says nothing negative. It should have a big red X on it and clearly say something like "This website was NOT filtered. You are NOT yet using OpenDNS to filter out adult websites."

On the How-to-Test-for-Successful-OpenDNS-Configuration page, the fail column shows what will actually pop up, but the pass column does not. It would be better for the pass column to actually show what it is supposed to look like, with the large OpenDNS icon, the yellow triangle exclamation point, and the phrase "This domain is blocked due to content filtering"

Also on the How-to-Test-for-Successful-OpenDNS-Configuration page, the table could use some work. Perhaps it could be made less tall (on my small screen, when I scroll to the bottom to see the exampleadultsite row, I have lost the Incorrect / Correct heading. If the rows were shorter, maybe that wouldn't happen. It might be more intuitive to have fail to the left and pass to the right; presently it is the other way. Perhaps the exampleadultsite row could be right below the welcome.opendns row. Or break it into three tables to repeat the pass/fail header row three times.

The diagnostic page should also specifically mention the Updater as a possible solution.

It also surprises me that clicking on different diagnostic links is necessary. It seems like you should be able to have one page that calls others as subpages, processes what is found on the subpages, and reports overall status with checks and Xs - maybe even right down the list of filtering categories, rather than just three. With a little more CGI coding it might be possible to report whether the problem is that the Updater needs to be run (i.e. can you tell whether the network connection IP address used is one that is registered with OpenDNS?)