You may be trying to access this site from a secured browser on the server. Please enable scripts and reload this page. Turn on more accessible mode Turn off more accessible mode Skip ...

labor.ky.gov
  • Domain Name
    labor.ky.gov
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #17492
  • Page Size
    86.2 KB
  • Ip Address
    205.204.187.206
  • Heading
    H1: 1, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 2 JPG, 9 PNG

Website Meta Analysis

  • Title
    Kentucky Labor Cabinet
  • Meta Keyword
  • Meta Description
    You may be trying to access this site from a secured browser on the server. Please enable scripts and reload this page. Turn on more accessible mode Turn off more accessible mode Skip Ribbon Commands Skip to main content This page location ...

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    205.204.187.206
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from labor.ky.gov.

HTML Analysis

  • cache-control: private, max-age=0
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • expires: Wed, 20 Feb 2013 22:29:20 GMT
  • last-modified: Thu, 07 Mar 2013 22:29:20 GMT
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • sprequestguid: 8418c70a-27a0-49bb-88c5-a1619ec58939
  • x-sharepointhealthscore: 0
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • date: Thu, 07 Mar 2013 22:29:20 GMT
  • content-length: 25574
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for labor.ky.gov

IP 205.204.187.206 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 69 Errors
  • 0 Warnings
Ratio Text/Html
  • 0.4655961224859576
Message Error
  • Error Line 4, Column 72: there is no attribute "__expr-val-dir"
    …hemas-microsoft-com:office:office" __expr-val-dir="ltr" lang="en-us" dir="ltr">

    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 4, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html xmlns:o="urn:schemas-microsoft-com:office:office" __expr-val-dir="ltr" la…

    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 34, Column 33: document type does not allow element "span" here; assuming missing "object" start-tag
    <span id="ctl00_ctl15_iprRibbon"><span></span></span>
  • Error Line 35, Column 96: document type does not allow element "link" here
    …ut icon" href="/_layouts/images/favicon.ico" type="image/vnd.microsoft.icon" />

    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 37, Column 24: document type does not allow element "style" here
    	<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 448, Column 79: document type does not allow element "link" here
    <link rel="stylesheet" href="/Labor Assets/tinydropdown.css" 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).

Visitor Analysis

Daily Visitor
  • 10.617 visits
Daily Visitor