labor.mo.gov

This is the main page for the Missouri Department of Labor and Industrial Relations. The agencies operating with the Missouri Department of Labor and Industrial Relations are responsive to the workplace needs of ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    labor.mo.gov
  • Favicon
  • Alexa Rank
    #7825
  • Google Page Rank
    PR 6
  • Ip Address
    168.166.34.8
  • Page Size
    34 KB
  • Images
    0 GIF, 3 JPG, 14 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 2 16 3 0 0

Website Meta Analysis



  • Title
    Missouri Department of Labor & Industrial Relations
  • Meta Keyword
    employment, unemployment insurance, labor and industrial relations commission, discrimination, jobs, unemployment tax, Division of Labor Standards, labor & industrial relations commission, job, labor standards, workers compensation, public employee bargaining unit, industrial relations, labor department, workers' compensation, general workplace questions, labor, mediation, worker's compensation, state unemployment tax, department of labor, employment security, workers comp, employer, workers' comp, division of workers compensation, employers, worker's comp, division of worker's compensation, employment, work, State Board of Mediation, Missouri commission on human rights, job search, works, Division of Workers' Compensation, unemployment, working, job injury, unemployment check, human rights, Commission on Human Rights, unemployment benefits, work-related injury, Discrimination issues, job related injury, work related injury, work injury, unemployed, Unemployment Benefits
  • Meta Description
    This is the main page for the Missouri Department of Labor and Industrial Relations. The agencies operating with the Missouri Department of Labor and Industrial Relations are responsive to the workplace needs of employers and employees. Our mission is to strive to provide employees with safe and healthy workplaces and ensure economic security for all Missourians by promoting equal access to jobs, enforcing anti-discrimination laws and awarding payment of compensation to unemployed, injured workers and victims of crime. In addition, the Department strives to provide Missourians with equal employment opportunities while it also strives to prevent and eliminate unlawful discrimination. The Department provides educational information to Missourians regarding their rights and responsibilities under the labor laws.

Technical Analysis



  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    168.166.34.8
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 13 Sep 2013 18:34:41 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • ntcoent-length: 34466
  • content-type: text/html
  • cache-control: private
  • content-encoding: gzip
  • content-length: 10857
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% DOTGOV WHOIS Server ready
Domain Name: MO.GOV
Status: ACTIVE


>>> Last update of whois database: Fri, 31 Aug 2012 17:06:07 UTC

DNS Analysis


DNS servers
pubdns01.mo.gov
pubdnsdr02.mo.gov
services.mo.gov
pubdnsdr01.mo.gov


DNS Records

Answer records
labor.mo.gov MX
preference: 10
exchange: momail3.mo.gov
1800s
labor.mo.gov MX
preference: 10
exchange: momail2.mo.gov
1800s
labor.mo.gov MX
preference: 10
exchange: momail1.mo.gov
1800s
labor.mo.gov MX
preference: 10
exchange: momail4.mo.gov
1800s
labor.mo.gov NS  pubdns01.mo.gov 1800s
labor.mo.gov NS  pubdnsdr02.mo.gov 1800s
labor.mo.gov NS  services.mo.gov 1800s
labor.mo.gov NS  pubdnsdr01.mo.gov 1800s
labor.mo.gov SOA
server: pubdns01.mo.gov
email: oa@tsdnshelp.oa.mo.gov
serial: 64
refresh: 900
retry: 3600
expire: 2592000
minimum ttl: 900
1800s
labor.mo.gov A 168.166.34.8 900s

Authority records

Additional records

IP 168.166.34.8 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Jefferson City
  • Continent Code
    65101
  • Latitude
    573
  • Longitude
    604
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 168.166.34.8"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=168.166.34.8?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 168.166.0.0 - 168.166.255.255
    CIDR: 168.166.0.0/16
    OriginAS:
    NetName: SHOWMEINFO
    NetHandle: NET-168-166-0-0-1
    Parent: NET-168-0-0-0-0
    NetType: Direct Assignment
    RegDate: 1994-09-27
    Updated: 2011-12-13
    Ref: http://whois.arin.net/rest/net/NET-168-166-0-0-1

    OrgName: State of Missouri Office of Administration
    OrgId: SMOA-Z
    Address: Information Technology Systems Division, Suite 280
    Address: 301 W. High Street
    City: Jefferson City
    StateProv: MO
    PostalCode: 65101
    Country: US
    RegDate: 2011-10-24
    Updated: 2011-10-24
    Ref: http://whois.arin.net/rest/org/SMOA-Z

    OrgAbuseHandle: NEELY4-ARIN
    OrgAbuseName: Neely, Nate
    OrgAbusePhone: +1-573-522-6946
    OrgAbuseEmail: nate.neely@oa.mo.gov
    OrgAbuseRef: http://whois.arin.net/rest/poc/NEELY4-ARIN

    OrgAbuseHandle: NEWMA11-ARIN
    OrgAbuseName: Newman, Doug
    OrgAbusePhone: +1-573-526-3663
    OrgAbuseEmail: doug.newman@oa.mo.gov
    OrgAbuseRef: http://whois.arin.net/rest/poc/NEWMA11-ARIN

    OrgTechHandle: SEO1-ARIN
    OrgTechName: Owens, Stephen E
    OrgTechPhone: +1-573-751-3299
    OrgTechEmail: steve.owens@oa.mo.gov
    OrgTechRef: http://whois.arin.net/rest/poc/SEO1-ARIN

    OrgTechHandle: NEELY4-ARIN
    OrgTechName: Neely, Nate
    OrgTechPhone: +1-573-522-6946
    OrgTechEmail: nate.neely@oa.mo.gov
    OrgTechRef: http://whois.arin.net/rest/poc/NEELY4-ARIN

    OrgAbuseHandle: SEO1-ARIN
    OrgAbuseName: Owens, Stephen E
    OrgAbusePhone: +1-573-751-3299
    OrgAbuseEmail: steve.owens@oa.mo.gov
    OrgAbuseRef: http://whois.arin.net/rest/poc/SEO1-ARIN

    OrgTechHandle: NEWMA11-ARIN
    OrgTechName: Newman, Doug
    OrgTechPhone: +1-573-526-3663
    OrgTechEmail: doug.newman@oa.mo.gov
    OrgTechRef: http://whois.arin.net/rest/poc/NEWMA11-ARIN

    RTechHandle: SEO1-ARIN
    RTechName: Owens, Stephen E
    RTechPhone: +1-573-751-3299
    RTechEmail: steve.owens@oa.mo.gov
    RTechRef: http://whois.arin.net/rest/poc/SEO1-ARIN

    RTechHandle: JB2875-ARIN
    RTechName: Brenneke, Joe
    RTechPhone: +1-573-751-3299
    RTechEmail: joe.brenneke@oa.mo.gov
    RTechRef: http://whois.arin.net/rest/poc/JB2875-ARIN

    RAbuseHandle: POSTM21-ARIN
    RAbuseName: Postmaster
    RAbusePhone: +1-573-751-2201
    RAbuseEmail: postmaster@mo.gov
    RAbuseRef: http://whois.arin.net/rest/poc/POSTM21-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 27 Errors
  • 0 Warnings
Ratio Text/Html
  • 0.701456519865552
Message Error
  • Error Line 11, Column 71: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="viewport" content="width=device-width, initial-scale=1.0">

    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 11, Column 1: start tag was here
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
  • Error Line 44, Column 35: document type does not allow element "div" here
    	$j('#cycle').after('<div id="nav">').cycle({ 

    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 54, Column 9: end tag for "div" omitted, but OMITTAG NO was specified
    </script>

    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 44, Column 22: start tag was here
    	$j('#cycle').after('<div id="nav">').cycle({ 
  • Error Line 68, Column 8: required attribute "type" not specified
    <script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 70, Column 44: document type does not allow element "div" here
      $j('#youtube ul').after('<div id="vidNav">').cycle({

    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 78, Column 9: end tag for "div" omitted, but OMITTAG NO was specified
    </script>

    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 70, Column 28: start tag was here
      $j('#youtube ul').after('<div id="vidNav">').cycle({
  • Error Line 81, Column 78: required attribute "type" not specified
    …src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 84, Column 8: required attribute "type" not specified
    <script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 167, Column 25: there is no attribute "role"
      <div id="search" role="search" class="noprint">

    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 290, Column 57: document type does not allow element "ul" here; assuming missing "li" start-tag
    … newsFade'><ul class='grid_9 newsFade'><li><a href='/News_Center/rss.xml'>Visi…
  • Error Line 290, Column 149: end tag for "li" omitted, but OMITTAG NO was specified
    …/News_Center/rss.xml'>Visit the Department of Labor RSS Site</a></li></ul></ul>

    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 290, Column 30: start tag was here
    	<ul class='grid_9 newsFade'><ul class='grid_9 newsFade'><li><a href='/News_Cen…
  • Error Line 310, Column 35: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    <form id="formFinder" method="POST" name="MyForm" action="/formsfinder/index.as…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 310, Column 42: there is no attribute "name"
    …rm id="formFinder" method="POST" name="MyForm" action="/formsfinder/index.asp?…

    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 321, Column 76: end tag for "input" omitted, but OMITTAG NO was specified
    …rch" size="18" id="formName" value=""><input type="submit" value="Search" name…

    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 321, Column 7: start tag was here
          <input type="text" name="txtSearch" size="18" id="formName" value=""><inp…
  • Error Line 321, Column 130: end tag for "input" omitted, but OMITTAG NO was specified
    …" id="formName" value=""><input type="submit" value="Search" name="cmdSearch" >

    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 321, Column 76: start tag was here
    …rch" size="18" id="formName" value=""><input type="submit" value="Search" name…
  • Error Line 350, Column 16: value of attribute "id" invalid: "1" cannot start a name
          <div id="1099" class="mobile-hide"><a href="/offthebooks/"><img src="img/…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 355, Column 15: there is no attribute "width"
    <iframe width="300" height="250" src="http://www.youtube.com/embed/aHbjheZMIKE?…

    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 355, Column 28: there is no attribute "height"
    <iframe width="300" height="250" src="http://www.youtube.com/embed/aHbjheZMIKE?…

    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 355, Column 38: there is no attribute "src"
    <iframe width="300" height="250" src="http://www.youtube.com/embed/aHbjheZMIKE?…

    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 355, Column 99: there is no attribute "frameborder"
    ….youtube.com/embed/aHbjheZMIKE?rel=0" frameborder="0" allowfullscreen></iframe>

    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 355, Column 118: "allowfullscreen" is not a member of a group specified for any attribute
    ….youtube.com/embed/aHbjheZMIKE?rel=0" frameborder="0" allowfullscreen></iframe>
  • Error Line 355, Column 118: element "iframe" undefined
    ….youtube.com/embed/aHbjheZMIKE?rel=0" frameborder="0" allowfullscreen></iframe>

    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 359, Column 19: invalid comment declaration: found name start character outside comment but inside comment declaration
          <!--<h4> <--style="line-height:1.4em;color:#333">-><a style="font-size:12…
  • Info Line 359, Column 7: comment declaration started here
          <!--<h4> <--style="line-height:1.4em;color:#333">-><a style="font-size:12…
  • Error Line 359, Column 183: end tag for element "h4" which is not open
    …:#333;" href="http://youtu.be/Mea4eE7qXA0">Working During the Holidays</a></h4>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 360, Column 125: "allowfullscreen" is not a member of a group specified for any attribute
    …el=0" frameborder="0" allowfullscreen style="border: 3px dotted #cc3333;"></if…
  • Error Line 360, Column 131: there is no attribute "style"
    …frameborder="0" allowfullscreen style="border: 3px dotted #cc3333;"></iframe>-…

    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 360, Column 160: element "iframe" undefined
    …rameborder="0" allowfullscreen style="border: 3px dotted #cc3333;"></iframe>-->

    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 498, Column 13: ID "border" already defined
        <li id="border"><a href="http://www.mo.gov/my-government/online-services/" …

    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 497, Column 13: ID "border" first defined here
        <li id="border"><a href="http://www.mo.gov/my-government/state-agencies/" t…
  • Error Line 499, Column 10: ID "border" already defined
    	<li id="border"><a href="http://www.mo.gov/accessibility/" title="State of Mis…

    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 497, Column 13: ID "border" first defined here
        <li id="border"><a href="http://www.mo.gov/my-government/state-agencies/" t…
  • Error Line 500, Column 10: ID "border" already defined
    	<li id="border"><a href="http://www.mo.gov/privacy-policy/" title="State of Mi…

    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 497, Column 13: ID "border" first defined here
        <li id="border"><a href="http://www.mo.gov/my-government/state-agencies/" t…
  • Error Line 525, Column 6: end tag for element "div" which is not open
    </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

Visitor Analysis

Daily Visitor
  • 14.000 visits

In Page Analysis