Please turn on JavaScript. The North Carolina - Electronic Pre-Assessment Screening Service site uses JavaScript. Either your web browser does not support JavaScript or you have it turned off. Please use a JavaScript ...

epass.nc.gov
  • Domain Name
    epass.nc.gov
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #41836
  • Page Size
    2.6 KB
  • Ip Address
    204.211.245.132
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
  • Meta Keyword
  • Meta Description
    Please turn on JavaScript. The North Carolina - Electronic Pre-Assessment Screening Service site uses JavaScript. Either your web browser does not support JavaScript or you have it turned off. Please use a JavaScript enabled web browser. After ...

Technical Analysis

  • Webserver
    IBM_HTTP_Server
  • Ip Address
    204.211.245.132
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from epass.nc.gov.

HTML Analysis

  • date: Tue, 05 Mar 2013 03:21:16 GMT
  • server: IBM_HTTP_Server
  • content-length: 2573
  • expires: Thu, 01 Dec 1994 16:00:00 GMT
  • cache-control: no-cache="set-cookie, set-cookie2"
  • content-type: text/html; charset=UTF-8
  • content-language: en-US
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for epass.nc.gov

IP 204.211.245.132 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 204.211.245.132

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 15 Errors
  • 0 Warnings
Ratio Text/Html
  • 0.4735283228433913
Message Error
  • Error Line 3, Column 3: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
      <html><head><script type="text/javascript">

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 7, Column 25: document type does not allow element "noscript" here; assuming missing "object" start-tag
          </script><noscript><META CONTENT="0;URL=nojavascript.jsp" HTTP-EQUIV="Ref…
  • Error Line 7, Column 40: there is no attribute "CONTENT"
    …     </script><noscript><META CONTENT="0;URL=nojavascript.jsp" HTTP-EQUIV="Ref…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 7, Column 76: there is no attribute "HTTP-EQUIV"
    …T="0;URL=nojavascript.jsp" HTTP-EQUIV="Refresh"/></noscript><meta content="tex…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 7, Column 86: element "META" undefined
    …ojavascript.jsp" HTTP-EQUIV="Refresh"/></noscript><meta content="text/html; ch…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 7, Column 165: document type does not allow element "meta" here
    …t="text/html; charset=UTF-8" http-equiv="Content-Type"/><style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 7, Column 188: document type does not allow element "style" here
    …t="text/html; charset=UTF-8" http-equiv="Content-Type"/><style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 45, Column 17: end tag for "object" omitted, but OMITTAG NO was specified
    		</style></head><body class="logonBody" onload="autoSubmit()" style="visibilit…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 7, Column 16: start tag was here
          </script><noscript><META CONTENT="0;URL=nojavascript.jsp" HTTP-EQUIV="Ref…
  • Error Line 45, Column 17: end tag for "head" which is not finished
    		</style></head><body class="logonBody" onload="autoSubmit()" style="visibilit…

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 45, Column 159: there is no attribute "name"
    …ck" id="loginform" method="post" name="loginform"><input name="j_username" typ…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 45, Column 232: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …" type="hidden" value="publiccitizen"/><input name="j_password" type="hidden" …

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 45, Column 289: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …sword" type="hidden" value="password"/><input name="user_type" type="hidden" v…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 45, Column 345: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …_type" type="hidden" value="EXTERNAL"/></form><noscript><div class="cluster"><…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 45, Column 707: ID "welcome-text-2" already defined
    …Script enabled web browser.</p><p id="welcome-text-2">After you have enabled J…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 45, Column 470: ID "welcome-text-2" first defined here
    …>Please turn on JavaScript.</p><p id="welcome-text-2">The North Carolina - Ele…
  • Error Line 45, Column 924: there is no attribute "target"
    …="https://www.nccarelink.gov/" target="_new" title="Visit the North Carolina c…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

Visitor Analysis

Daily Visitor
  • 4.667 visits
Daily Visitor