**The main reason for including error codes is diagnosis. For instance, if an experienced user needs to know which particular error he is looking at, or if a beginning user is trying to get help from an experienced user, these codes would be important. So, including them in a visible but not prominent way can address this use case. This is similar to how Chrome and IE handle codes in network error warnings.
Is it * The network error pages should display the most useful* tools possible to link to a page with for the given input, but no more information about the problem? than five tools.* Should indication that the error is *<nowiki>*</nowiki>Most useful will be determined an inexact science of approximation of a "404best match," or "DNS Not Found" be provided in given the first screen? * How many alternatives should be showntools we have available. For instance, and how closely should those match user input? * What distinction should be drawn if a page is only one letter off from the user's perspective between 404 errors and input, it would have a higher "DNS Not Foundusefulness" errors? score than simply linking a failed subdirectory to the domain-level page* Which tools should *Non-current (cached, stored, etc) pages will be provided?displayed last
==The Official UI Design==
