We provide soccer results and predictions since 1999. Choose soccer league and you will find statistics, picks, tables and informations for all your betting needs. All football information on this site is free. ...

soccervista.com
  • Domain Name
    soccervista.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #10392
  • Page Size
    73.5 KB
  • Ip Address
    88.86.105.76
  • Heading
    H1: 1, H2: 1, H3: 1, H4: 1, H5: 0, H6: 0
  • Images
    2 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    SoccerVista - soccer results, predictions and betting picks
  • Meta Keyword
    , soccer, soccer betting, soccer predictions, soccer results, soccer tables
  • Meta Description
    We provide soccer results and predictions since 1999. Choose soccer league and you will find statistics, picks, tables and informations for all your betting needs. All football information on this site is free. You can choose football game by date or select league by country list. For detailed information about match click into score link.

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
    12 Years, 10 Months, 16 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from soccervista.com.

HTML Analysis

  • date: Sun, 04 Aug 2013 18:13:53 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: 11431
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: SOCCERVISTA.COM
Created on: 25-Sep-00
Expires on: 25-Sep-19
Last Updated on: 02-Sep-10

Registrant:
SoccerVista
Tyrsova541
Slatinany, 53821
Czech Republic

Administrative Contact:
Castka, Radek email
SoccerVista
Tyrsova541
Slatinany, 53821
Czech Republic
+420.776690687 Fax -- +420.776690687

Technical Contact:
Castka, Radek email
SoccerVista
Tyrsova541
Slatinany, 53821
Czech Republic
+420.776690687 Fax -- +420.776690687

Domain servers in listed order:
NS1.SUPERHOSTING.CZ
NS2.SUPERHOSTING.CZ

DNS Analysis


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

DNS Records

Answer records
soccervista.com SOA
server: ns1.superhosting.cz
email: dns@superhosting.cz
serial: 2012033006
refresh: 3600
retry: 3600
expire: 2592000
minimum ttl: 3600
3600s
soccervista.com NS  ns2.superhosting.cz 3600s
soccervista.com NS  ns1.superhosting.cz 3600s
soccervista.com A 88.86.105.76 3600s
soccervista.com MX
preference: 10
exchange: mail.superhosting.cz
3600s
soccervista.com TXT v=spf1 mx ip4:88.86.105.76 a:mail.superhosting.cz a:livescore.superhosting.cz a:smtp-relay.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
mail.superhosting.cz A 95.168.196.37 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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 14 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.7475662394581313
Message Error
  • Error Line 5, Column 16: there is no attribute "PROPERTY"
    <meta property="fb:admins" content="1049919137" >

    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 183, Column 468: there is no attribute "ALLOWTRANSPARENCY"
    …40px; height:21px;" allowTransparency="true"></iframe><br><br><div style="floa…

    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.

  • Warning Line 183, Column 652: NET-enabling start-tag requires SHORTTAG YES
    …a"  width="62" height="22" border="0" /></a></div> <div style="float: right;">…

    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 183, Column 652: required attribute "ALT" not specified
    …a"  width="62" height="22" border="0" /></a></div> <div style="float: right;">…

    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 183, Column 709: there is no attribute "HREF"
    …tyle="float: right;"><g:plusone  href="http://www.soccervista.com"  size="smal…

    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 183, Column 744: there is no attribute "SIZE"
    …ef="http://www.soccervista.com"  size="small" href="http://www.soccervista.com…

    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 183, Column 757: duplicate specification of attribute "HREF"
    …w.soccervista.com"  size="small" href="http://www.soccervista.com" ></g:pluson…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 183, Column 786: element "G:PLUSONE" undefined
    …ll" href="http://www.soccervista.com" ></g:plusone></div><br>  <ul id="navlist…

    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).
  • Warning Line 183, Column 2001: cannot generate system identifier for general entity "fr"
    …ww.soccervista.com/go/click.php?id=27&fr=38' target='_blank'><img src='http://…

    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 183, Column 2001: general entity "fr" not defined and no default entity
    …ww.soccervista.com/go/click.php?id=27&fr=38' target='_blank'><img src='http://…

    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 183, Column 2003: reference to entity "fr" for which no system identifier could be generated
    ….soccervista.com/go/click.php?id=27&fr=38' target='_blank'><img src='http://ff…

    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 183, Column 2000: entity was defined here
    …www.soccervista.com/go/click.php?id=27&fr=38' target='_blank'><img src='http:/…
  • Warning Line 183, Column 2100: cannot generate system identifier for general entity "placement"
    …rokes/selector/image?client=Ladbrokes&placement=Aff_Sbook_Generic_120x120_Gif'…

    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 183, Column 2100: general entity "placement" not defined and no default entity
    …rokes/selector/image?client=Ladbrokes&placement=Aff_Sbook_Generic_120x120_Gif'…

    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 183, Column 2109: reference to entity "placement" for which no system identifier could be generated
    …ector/image?client=Ladbrokes&placement=Aff_Sbook_Generic_120x120_Gif' width='1…

    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 183, Column 2099: entity was defined here
    …brokes/selector/image?client=Ladbrokes&placement=Aff_Sbook_Generic_120x120_Gif…
  • Error Line 183, Column 2218: ID "NAVLIST2" already defined
    …='bet at home' ></a></div><br><ul id='navlist2'><li><strong>Good Leagues</stro…

    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 183, Column 819: ID "NAVLIST2" first defined here
    …com" ></g:plusone></div><br>  <ul id="navlist2"><li><strong>Top Leagues</stron…
  • Error Line 184, Column 92: reference to entity "fr" for which no system identifier could be generated
    ….soccervista.com/go/click.php?id=21&fr=39' target='_blank'><img src='http://ww…

    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 183, Column 2000: entity was defined here
    …www.soccervista.com/go/click.php?id=27&fr=38' target='_blank'><img src='http:/…
  • Error Line 184, Column 259: ID "NAVLIST2" already defined
    …us from 10bet' ></a></div><br><ul id='navlist2'><li><strong>Others</strong></l…

    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 183, Column 819: ID "NAVLIST2" first defined here
    …com" ></g:plusone></div><br>  <ul id="navlist2"><li><strong>Top Leagues</stron…

Visitor Analysis

Daily Visitor
  • 7.350 visits