This page has moved. The new page is located at /css/default.asp! You will be transported there in 5 seconds -- please update your bookmarks! ...

leg.mt.gov
  • Domain Name
    leg.mt.gov
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #18441
  • Page Size
    383 B
  • Ip Address
    161.7.19.169
  • 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
    This page has moved. The new page is located at /css/default.asp! You will be transported there in 5 seconds -- please update your bookmarks!

Technical Analysis

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

Hyper Text Transfer Protocol (HTTP) header show data header response from leg.mt.gov.

HTML Analysis

  • cache-control: private
  • content-length: 326
  • content-type: text/html
  • server: Microsoft-IIS/8.0
  • x-powered-by: ASP.NET
  • date: Fri, 30 Aug 2013 15:10:54 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% DOTGOV WHOIS Server ready
Domain Name: MT.GOV
Status: ACTIVE


>>> Last update of whois database: Sat, 28 Jul 2012 05:05:14 UTC

DNS Analysis


DNS servers
mtdnspri.mt.gov [161.7.38.10]
mtdnssec.mt.gov [161.7.38.11]
mtdnstri.mt.gov [161.7.129.10]


DNS Records

Answer records
leg.mt.gov A 161.7.19.171 86400s

Authority records

Additional records

IP 161.7.19.169 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 5 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.5639686684073106
Message Error
  • Error Line 1, Column 1: no document type declaration; will parse without validation
    <header><META HTTP-EQUIV="refresh" content="0; url=/css/default.asp"></header>

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Warning Line 2, Column 58: NET-enabling start-tag requires SHORTTAG YES
    <link rel="stylesheet" type="text/css" href="screen.css" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 2, Column 58: document type does not allow element "LINK" here
    <link rel="stylesheet" type="text/css" href="screen.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 3, Column 80: character data is not allowed here
    …d. The new page is located at <A HREF="/css/default.asp">/css/default.asp</A>! 

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 3, Column 98: end tag for element "A" which is not open
    …d. The new page is located at <A HREF="/css/default.asp">/css/default.asp</A>! 

    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 4, Column 81: end tag for element "P" which is not open
    …You will be transported there in 5 seconds -- please update your bookmarks!</p>

    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
  • 9.800 visits