HOME Top 100 Artists Top 100 Tracks Follow @mp3_li Top 50 artists: 1. Maroon 5 2. Richie Kotzen 3. Elli Kokkinou 4. Bellowhead 5. Motorhead 6. Paramore 7. Juli 8. Akon 9. Smokie ...

mp3.li
  • Domain Name
    mp3.li
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #27895
  • Page Size
    47.7 KB
  • Ip Address
    94.242.221.221
  • Heading
    H1: 3, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 3 PNG

Website Meta Analysis

  • Title
    Mp3.li - your music Library online. Download mp3's for free!
  • Meta Keyword
  • Meta Description
    HOME Top 100 Artists Top 100 Tracks Follow @mp3_li Top 50 artists: 1. Maroon 5 2. Richie Kotzen 3. Elli Kokkinou 4. Bellowhead 5. Motorhead 6. Paramore 7. Juli 8. Akon 9. Smokie 10. Bruno Mars 11. Sailor 12. Accept 13. Motley Crue 14. E-Type ...

Technical Analysis

  • Webserver
    ngx_openresty
  • Ip Address
    94.242.221.221
  • Domain Age
  • Javascript Library
    jquery, dojo
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from mp3.li.

HTML Analysis

  • server: ngx_openresty
  • date: Mon, 09 Sep 2013 14:10:36 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.3.25
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
whois: This information is subject to an Acceptable Use Policy.
See http://www.nic.ch/terms/aup.html


Domain name:
mp3.li

Holder of domain name:
Agnieszka Syslo
Agnieszka Syslo
Kreith 7
AT-6162 Mutters
Austria
Contractual Language: German

Technical contact:
Agnieszka Syslo
Agnieszka Syslo
Kreith 7
AT-6162 Mutters
Austria

DNSSEC:N

Name servers:
dns1.webdrive.ru
dns2.webdrive.ru

DNS Analysis


DNS servers
dns1.webdrive.ru [176.74.216.129]
dns2.webdrive.ru [159.253.133.210]


DNS Records

Answer records
mp3.li NS  dns2.webdrive.ru 86400s
mp3.li SOA
server: dns1.webdrive.ru
email: admin@webdrive.ru
serial: 1359018450
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
86400s
mp3.li NS  dns1.webdrive.ru 86400s
mp3.li A 94.242.221.153 86400s

Authority records

Additional records

IP 94.242.221.221 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 110 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.6388417067430676
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 3, Column 68: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="content-type" content="text/html; charset=UTF-8" />

    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 3, Column 69: character data is not allowed here
    <meta http-equiv="content-type" content="text/html; charset=UTF-8" />

    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.
  • Warning Line 4, Column 50: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="content-language" content="en" />

    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.

  • Warning Line 5, Column 58: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="content-style-type" content="text/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.

  • Warning Line 7, Column 85: NET-enabling start-tag requires SHORTTAG YES
    …el="stylesheet" href="http://mp3.li/themes/default/main.css" type="text/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 14, Column 7: end tag for element "HEAD" which is not open
    </head>

    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 15, Column 17: "ITEMSCOPE" is not a member of a group specified for any attribute
    <body itemscope itemtype="http://schema.org/WebPage">
  • Error Line 15, Column 26: there is no attribute "ITEMTYPE"
    <body itemscope itemtype="http://schema.org/WebPage">

    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 15, Column 53: document type does not allow element "BODY" here
    <body itemscope itemtype="http://schema.org/WebPage">

    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).

  • Warning Line 20, Column 115: NET-enabling start-tag requires SHORTTAG YES
    …mg id="logo_img" src="http://mp3.li/themes/default/images/logo.png"/></a></div>

    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 20, Column 115: required attribute "ALT" not specified
    …mg id="logo_img" src="http://mp3.li/themes/default/images/logo.png"/></a></div>

    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>.

  • Warning Line 24, Column 59: cannot generate system identifier for general entity "count"
    …f="http://mp3.li/top.php?kind=artists&count=100" class="mainlevel-nav" >Top 10…

    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 24, Column 59: general entity "count" not defined and no default entity
    …f="http://mp3.li/top.php?kind=artists&count=100" class="mainlevel-nav" >Top 10…

    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.

  • Error Line 24, Column 64: reference to entity "count" for which no system identifier could be generated
    …tp://mp3.li/top.php?kind=artists&count=100" class="mainlevel-nav" >Top 100 Art…

    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 24, Column 58: entity was defined here
    …ef="http://mp3.li/top.php?kind=artists&count=100" class="mainlevel-nav" >Top 1…
  • Error Line 25, Column 63: reference to entity "count" for which no system identifier could be generated
    …ttp://mp3.li/top.php?kind=tracks&count=100" class="mainlevel-nav" >Top 100 Tra…

    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 24, Column 58: entity was defined here
    …ef="http://mp3.li/top.php?kind=artists&count=100" class="mainlevel-nav" >Top 1…
  • Warning Line 31, Column 55: NET-enabling start-tag requires SHORTTAG YES
              <input type="text" class="inputbox" name="q"/>  

    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.

  • Warning Line 32, Column 55: NET-enabling start-tag requires SHORTTAG YES
              <input type="submit" class="button" value=""/>  

    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 118, Column 58: reference to entity "count" for which no system identifier could be generated
    …<a href="http://mp3.li/top.php?kind=artists&count=100">Show top 100 artists</a>

    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 24, Column 58: entity was defined here
    …ef="http://mp3.li/top.php?kind=artists&count=100" class="mainlevel-nav" >Top 1…
  • Warning Line 152, Column 166: cannot generate system identifier for general entity "M"
    ….php?q=Rihanna%20-%20S%26M" title="Rihanna - S&M">Rihanna - S&M</a></div></div>

    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 152, Column 166: general entity "M" not defined and no default entity
    ….php?q=Rihanna%20-%20S%26M" title="Rihanna - S&M">Rihanna - S&M</a></div></div>

    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.

  • Error Line 152, Column 167: reference to entity "M" for which no system identifier could be generated
    ….php?q=Rihanna%20-%20S%26M" title="Rihanna - S&M">Rihanna - S&M</a></div></div>

    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 152, Column 165: entity was defined here
    ….php?q=Rihanna%20-%20S%26M" title="Rihanna - S&M">Rihanna - S&M</a></div></div>
  • Error Line 152, Column 182: reference to entity "M" for which no system identifier could be generated
    ….php?q=Rihanna%20-%20S%26M" title="Rihanna - S&M">Rihanna - S&M</a></div></div>

    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 152, Column 165: entity was defined here
    ….php?q=Rihanna%20-%20S%26M" title="Rihanna - S&M">Rihanna - S&M</a></div></div>
  • Error Line 175, Column 57: reference to entity "count" for which no system identifier could be generated
    …  <a href="http://mp3.li/top.php?kind=tracks&count=100">Show top 100 tracks</a>

    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 24, Column 58: entity was defined here
    …ef="http://mp3.li/top.php?kind=artists&count=100" class="mainlevel-nav" >Top 1…
  • Error Line 223, Column 58: reference to entity "count" for which no system identifier could be generated
    …http://mp3.li/top.php?kind=artists&count=100">Top 100 Artists</a><span>|</span>

    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 24, Column 58: entity was defined here
    …ef="http://mp3.li/top.php?kind=artists&count=100" class="mainlevel-nav" >Top 1…
  • Error Line 224, Column 57: reference to entity "count" for which no system identifier could be generated
            <a href="http://mp3.li/top.php?kind=tracks&count=100">Top 100 Tracks</a>

    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 24, Column 58: entity was defined here
    …ef="http://mp3.li/top.php?kind=artists&count=100" class="mainlevel-nav" >Top 1…

Visitor Analysis

Daily Visitor
  • 4.900 visits