livescore.cz

Livescore - Place where you can find live soccer results. All is real time. Football leagues from all over the world. ...

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

Overview Info

  • Domain Name
    livescore.cz
  • Favicon
  • Alexa Rank
    #54015
  • Google Page Rank
    PR 4
  • Ip Address
    88.86.105.76
  • Page Size
    19.8 KB
  • Images
    1 GIF, 1 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 0 0 0 0

Website Meta Analysis



  • Title
    Livescore.cz - Soccer results
  • Meta Keyword
    livescore,soccer,football,livescores
  • Meta Description
    Livescore - Place where you can find live soccer results. All is real time. Football leagues from all over the world.

Technical Analysis



  • Webserver
    Apache/2.2.16 (Debian) PHP/5.3.3-7+squeeze14 with Suhosin-Patch mod_ssl/2.2.16 OpenSSL/0.9.8o
  • Ip Address
    88.86.105.76
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from livescore.cz.

HTML Analysis

  • date: Mon, 08 Jul 2013 14:08:05 GMT
  • server: Apache/2.2.16 (Debian) PHP/5.3.3-7+squeeze14 with Suhosin-Patch mod_ssl/2.2.16 OpenSSL/0.9.8o
  • x-powered-by: PHP/5.3.3-7+squeeze14
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 3682
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for livescore.cz

DNS Analysis


DNS servers
ns1.superhosting.cz [93.99.200.2]
ns2.superhosting.cz [88.86.116.42]


DNS Records

Answer records
livescore.cz SOA
server: ns1.superhosting.cz
email: dns@superhosting.cz
serial: 2012033002
refresh: 3600
retry: 3600
expire: 2592000
minimum ttl: 3600
3600s
livescore.cz NS  ns2.superhosting.cz 3600s
livescore.cz NS  ns1.superhosting.cz 3600s
livescore.cz A 88.86.105.76 3600s
livescore.cz MX
preference: 10
exchange: vip-mail.superhosting.cz
3600s
livescore.cz TXT v=spf1 a:smtp-relay.superhosting.cz mx mx:livescore.superhosting.cz -all 3600s

Authority records

Additional records
ns1.superhosting.cz A 93.99.200.2 3600s
ns1.superhosting.cz 28 [16 bytes] 3600s
ns2.superhosting.cz A 88.86.116.42 3600s
ns2.superhosting.cz 28 [16 bytes] 3600s
vip-mail.superhosting.cz A 95.168.196.56 3600s

IP 88.86.105.76 Analysis

  • Country Code
    CZ
  • Country Code3
    CZE
  • Country Name
    Czech Republic
  • City
    EU
  • Continent Code
    49°75' North
  • Latitude
    15.5.
  • Longitude
  • No whois ip data for 88.86.105.76

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 21 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.7971851851851852
Message Error
  • Error Line 1, Column 135: there is no attribute "PROPERTY"
    … Soccer results</title><meta property="og:title" content="Livescore.cz - Footb…

    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 38, Column 145: required attribute "ALT" not specified
    …tp://www.livescore.cz/sb125.gif"  width='125' height='125'  border='0'></a><br>

    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 39, Column 89: NET-enabling start-tag requires SHORTTAG YES
    …et are now offering their &pound;100 free bet offer to all new customers!<br />

    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 43, Column 55: cannot generate system identifier for general entity "fr"
    …//www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at Sp…

    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 43, Column 55: general entity "fr" not defined and no default entity
    …//www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at Sp…

    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 43, Column 57: reference to entity "fr" for which no system identifier could be generated
    …www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at Spor…

    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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 58, Column 56: reference to entity "fr" for which no system identifier could be generated
    …/www.livescore.cz/go/click.php?id=9&fr=5' target='_blank'>get &euro;30 bonus</…

    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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 66, Column 54: reference to entity "fr" for which no system identifier could be generated
    …/www.livescore.cz/go/click.php?id=3&fr=5' target='_blank'>Get your Free &pound…

    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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Warning Line 96, Column 100: NET-enabling start-tag requires SHORTTAG YES
    …lue="http://imstore.bet365affiliates.com/grm_2761-508-199-2-149-1-3319.aspx" />

    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 97, Column 36: NET-enabling start-tag requires SHORTTAG YES
    <param name="quality" value="high" />

    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 98, Column 41: NET-enabling start-tag requires SHORTTAG YES
    <param name="wmode" value="transparent" />

    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 99, Column 48: NET-enabling start-tag requires SHORTTAG YES
    <param name="allowScriptAccess" value="always" />

    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 100, Column 48: NET-enabling start-tag requires SHORTTAG YES
    <param name="allowNetworking" value="external" />

    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 102, Column 164: end tag for element "IMG" which is not open
    …=199&amp;TID=1&amp;PID=149&amp;LNG=1" style="border:0;" alt="bet365"></img></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 110, Column 397: there is no attribute "ALLOWTRANSPARENCY"
    …00px; height:80px;" allowTransparency="true"></iframe><div align="center"><g:p…

    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 110, Column 449: there is no attribute "SIZE"
    …e><div align="center"><g:plusone size="medium"  href="http://www.livescore.cz"…

    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 110, Column 464: there is no attribute "HREF"
    …enter"><g:plusone size="medium"  href="http://www.livescore.cz" ></g:plusone>&…

    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 110, Column 490: element "G:PLUSONE" undefined
    …e size="medium"  href="http://www.livescore.cz" ></g:plusone>&nbsp;&nbsp;&nbsp;

    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 111, Column 110: required attribute "ALT" not specified
    …g src="http://topsites.limso.net/button.php?u=lIVESCORE" border="0" ></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>.

  • Error Line 126, Column 54: reference to entity "fr" for which no system identifier could be generated
    …/www.livescore.cz/go/click.php?id=2&fr=3"><img src="http://www.livescore.cz/ba…

    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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 126, Column 137: required attribute "ALT" not specified
    …src="http://www.livescore.cz/bah125.gif" width="124" height="124" border=0></a>

    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 133, Column 59: reference to entity "fr" for which no system identifier could be generated
    …><a href="http://www.livescore.cz/go/click.php?id=2&fr=2">: Bet at Home</a><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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 135, Column 58: reference to entity "fr" for which no system identifier could be generated
        <a href="http://www.livescore.cz/go/click.php?id=3&fr=2">: Bet365</a><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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 137, Column 59: reference to entity "fr" for which no system identifier could be generated
    …  <a href="http://www.livescore.cz/go/click.php?id=20&fr=2">: Betfair</a><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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 139, Column 58: reference to entity "fr" for which no system identifier could be generated
        <a href="http://www.livescore.cz/go/click.php?id=4&fr=2">: Bwin</a><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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 141, Column 58: reference to entity "fr" for which no system identifier could be generated
    …<a href="http://www.livescore.cz/go/click.php?id=9&fr=2">: Gamebookers</a><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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 143, Column 59: reference to entity "fr" for which no system identifier could be generated
    …<a href="http://www.livescore.cz/go/click.php?id=21&fr=2">: SportingBet</a><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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 145, Column 59: reference to entity "fr" for which no system identifier could be generated
    …<a href="http://www.livescore.cz/go/click.php?id=19&fr=2">: Interwetten</a><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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 147, Column 59: reference to entity "fr" for which no system identifier could be generated
    …  <a href="http://www.livescore.cz/go/click.php?id=27&fr=2">: Ladbrokes</a><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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 149, Column 59: reference to entity "fr" for which no system identifier could be generated
        <a href="http://www.livescore.cz/go/click.php?id=10&fr=2">: Pinnacle</a><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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 151, Column 60: reference to entity "fr" for which no system identifier could be generated
    …<a href="http://www.livescore.cz/go/click.php?id=24&fr=2">: Paddy Power</a><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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 153, Column 61: reference to entity "fr" for which no system identifier could be generated
    …a href="http://www.livescore.cz/go/click.php?id=28&fr=2">: William Hill</a><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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 158, Column 59: reference to entity "fr" for which no system identifier could be generated
    …www.livescore.cz/go/click.php?id=10&fr=3"><img src="ps_eng_125x125_soc_gen4.gi…

    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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 158, Column 137: required attribute "ALT" not specified
    …ps_eng_125x125_soc_gen4.gif" width="124" height="124" border="0"></A><br> <br> 

    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 160, Column 62: reference to entity "fr" for which no system identifier could be generated
    …/www.livescore.cz/go/click.php?id=3&fr=3"><img src="bet125.gif" width="124" he…

    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 43, Column 54: entity was defined here
    …://www.livescore.cz/go/click.php?id=21&fr=5" target="_blank">Open account at S…
  • Error Line 160, Column 123: required attribute "ALT" not specified
    …k.php?id=3&fr=3"><img src="bet125.gif" width="124" height="199" border="0"></A>

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

Visitor Analysis

Daily Visitor
  • 2.800 visits

In Page Analysis