ncesc1.com

ncesc1.com has Alexa Rank 34.765 and Google Page Rank is 6

Display Widget for this domain on your website. Click Here
This data was last updated from 17-09-2013 05:58:21  (update).

Overview Info

  • Domain Name
    ncesc1.com
  • Favicon
  • Alexa Rank
    #34765
  • Google Page Rank
    PR 6
  • Ip Address
    149.168.171.30
  • Page Size
    31.3 KB
  • Images
    5 GIF, 0 JPG, 2 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    NC DES Home
  • Meta Keyword

Technical Analysis



  • Webserver
    Microsoft-IIS/5.0
  • Ip Address
    149.168.171.30
  • Domain Age
    4 Years, 6 Months, 25 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from ncesc1.com.

HTML Analysis

  • server: Microsoft-IIS/5.0
  • date: Tue, 17 Sep 2013 17:55:11 GMT
  • x-powered-by: ASP.NET
  • content-length: 30848
  • content-type: text/html
  • expires: Tue, 25 Dec 2001 05:00:00 GMT
  • cache-control: private
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: ncesc1.com

Registrant Contact:
FirstName: WhoisGuard
LastName: Protected
JobTitle:
OrganizationName: WhoisGuard
Address1: 11400 W. Olympic Blvd. Suite 200
Address2: Los Angeles, CA 90064
City:
StateProvince:
PostalCode:
Country: US
Phone: +1.6613102107
PhoneExt:
Fax: +1.6613102107
FaxExt:
EmailAddress: email

Administrative Contact:
FirstName: WhoisGuard
LastName: Protected
JobTitle:
OrganizationName: WhoisGuard
Address1: 11400 W. Olympic Blvd. Suite 200
Address2: Los Angeles, CA 90064
City:
StateProvince:
PostalCode:
Country: US
Phone: +1.6613102107
PhoneExt:
Fax: +1.6613102107
FaxExt:
EmailAddress: email

Technical Contact:
FirstName: WhoisGuard
LastName: Protected
JobTitle:
OrganizationName: WhoisGuard
Address1: 11400 W. Olympic Blvd. Suite 200
Address2: Los Angeles, CA 90064
City:
StateProvince:
PostalCode:
Country: US
Phone: +1.6613102107
PhoneExt:
Fax: +1.6613102107
FaxExt:
EmailAddress: email

Billing Contact:
FirstName: WhoisGuard
LastName: Protected
JobTitle:
OrganizationName: WhoisGuard
Address1: 11400 W. Olympic Blvd. Suite 200
Address2: Los Angeles, CA 90064
City:
StateProvince:
PostalCode:
Country: US
Phone: +1.6613102107
PhoneExt:
Fax: +1.6613102107
FaxExt:
EmailAddress: email

Name Servers:


Creation date: 3/17/2009 1:49:55 PM
Expiration date: 3/17/2013 1:49:55 PM

DNS Analysis


DNS servers
ns1.domainname.com [184.173.112.218]
ns2.domainname.com [208.64.127.157]
ns3.domainname.com [50.7.230.29]


DNS Records

Answer records
ncesc1.com SOA
server: ns1.domainname.com
email: hostmaster@domainname.com
serial: 2012051800
refresh: 3600
retry: 1801
expire: 3601
minimum ttl: 3601
3601s
ncesc1.com NS  ns1.domainname.com 1800s
ncesc1.com A 149.168.171.30 10800s
ncesc1.com NS  ns3.domainname.com 1800s
ncesc1.com NS  ns2.domainname.com 1800s

Authority records

Additional records
ns3.domainname.com A 50.7.230.29 1800s
ns1.domainname.com A 184.173.112.218 1800s
ns2.domainname.com A 208.64.127.157 1800s

IP 149.168.171.30 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 76 Errors
  • 43 Warnings
Ratio Text/Html
  • 0.6083369789388163
Message Error
  • Error Line 92, Column 80: there is no attribute "autocomplete"
    …name="Form1" method="post" action="default.aspx" id="Form1" autocomplete="off">

    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.

  • Warning Line 261, Column 402: character "&" is the first character of a delimiter but occurred as data
    …='#' class='basic' title="Customer ID & Hours of Availability"><img src="image…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 279, Column 102: character "&" is the first character of a delimiter but occurred as data
    …='#' class='basic' title="Customer ID & Hours of Availability">Hours of Availa…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 294, Column 170: cannot generate system identifier for general entity "size"
    …n.com/getseal?host_name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&l…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 294, Column 170: general entity "size" not defined and no default entity
    …n.com/getseal?host_name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&l…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 294, Column 174: reference not terminated by REFC delimiter
    …m/getseal?host_name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 294, Column 174: reference to external entity in attribute value
    …m/getseal?host_name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 294, Column 174: reference to entity "size" for which no system identifier could be generated
    …m/getseal?host_name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 294, Column 169: entity was defined here
    …gn.com/getseal?host_name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&…
  • Warning Line 294, Column 177: cannot generate system identifier for general entity "use_flash"
    …etseal?host_name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en"…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 294, Column 177: general entity "use_flash" not defined and no default entity
    …etseal?host_name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en"…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 294, Column 186: reference not terminated by REFC delimiter
    …st_name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en"></script…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 294, Column 186: reference to external entity in attribute value
    …st_name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en"></script…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 294, Column 186: reference to entity "use_flash" for which no system identifier could be generated
    …st_name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en"></script…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 294, Column 176: entity was defined here
    …getseal?host_name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en…
  • Warning Line 294, Column 190: cannot generate system identifier for general entity "use_transparent"
    …ame=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en"></script><br…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 294, Column 190: general entity "use_transparent" not defined and no default entity
    …ame=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en"></script><br…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 294, Column 205: reference not terminated by REFC delimiter
    …e=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en"></script><br />

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 294, Column 205: reference to external entity in attribute value
    …e=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en"></script><br />

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 294, Column 205: reference to entity "use_transparent" for which no system identifier could be generated
    …e=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en"></script><br />

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 294, Column 189: entity was defined here
    …name=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en"></script><b…
  • Warning Line 294, Column 213: reference not terminated by REFC delimiter
    …e=www.ncesc.com&size=S&use_flash=NO&use_transparent=NO&lang=en"></script><br />

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 327, Column 220: end tag for "br" omitted, but OMITTAG NO was specified
    …ty (DES). DES is now part of the North Carolina Department of Commerce.</p><br>

    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 327, Column 216: start tag was here
    …ty (DES). DES is now part of the North Carolina Department of Commerce.</p><br>
  • Error Line 333, Column 69: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …                          <p class="headline"> <p class="date">Jan 30, 2013</p>

    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 334, Column 52: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …                   <p class="headline">North Carolina’s December County and Ar…

    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 335, Column 35: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                                    <p>RALEIGH — Unemployment rates increased in 97…

    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 336, Column 48: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …                       <p class="more"><a href="http://www.ncesc1.com/PMI/Rate…

    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 338, Column 26: end tag for "p" omitted, but OMITTAG NO was specified
                        </div> 

    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 333, Column 33: start tag was here
                                    <p class="headline"> <p class="date">Jan 30, 20…
  • Error Line 376, Column 46: end tag for "div" omitted, but OMITTAG NO was specified
                    <!-- END Right Column --></td>

    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 358, Column 14: start tag was here
    	            <div id="systemMessages">	            
  • Warning Line 394, Column 98: character "&" is the first character of a delimiter but occurred as data
    …ww.ncesc1.com/browserInfo/browserInfoMain.asp">Browser Settings & Info</a></li>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.

Visitor Analysis

Daily Visitor
  • 4.783 visits

In Page Analysis