meusresultados.com

Meus Resultados oferece resultados de futebol em directo e jogos em directo para mais de 500 ligas diferentes. Acompanha os jogos de futebol ao vivo e jogos ao vivo agora! Livescore! ...

meusresultados.com
Domain Name meusresultados.com
Favicon meusresultados.com
Google Page Rank 5
Alexa Rank #53588
Page Size 60 KB
Ip Address 188.92.41.197
Heading H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
Images 0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

Title Meus Resultados: Futebol em directo, jogos ao vivo e livescore
Meta Keyword Resultados ao vivo de futebol,  futebol ao vivo e em directo, resultados ao vivo, jogos em directo, jogos ao vivo, Futebol em directo, livescore
Meta Description Meus Resultados oferece resultados de futebol em directo e jogos em directo para mais de 500 ligas diferentes. Acompanha os jogos de futebol ao vivo e jogos ao vivo agora! Livescore!

Technical Analysis

Webserver Apache
Ip Address 188.92.41.197
Domain Age
Javascript Library jquery
Language used HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache
  • p3p: CP="CAO PSA OUR"
  • content-encoding: gzip
  • content-type: text/html
  • x-vname: VN-194
  • expires: Wed, 26 Jun 2013 23:54:05 GMT
  • cache-control: public
  • last-modified: Wed, 26 Jun 2013 23:49:05 GMT
  • x-ttlset: BEH
  • content-length: 13918
  • accept-ranges: bytes
  • date: Wed, 26 Jun 2013 23:52:24 GMT
  • age: 199
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

Registrant:
LiveSport Media Ltd email +356.21355711 +356.21355711
LiveSport Media Ltd
CMS House, First Floor, St. Peters Street
San Gwann,-,MT SGN 2310

Domain Name:meusresultados.com
Record last updated at 2012-01-09 05:18:42
Record created on 11/13/2007
Record expired on 11/13/2013

Domain servers in listed order:
ns1.edrive-hosting.cz ns2.edrive-hosting.cz

Administrator:
Name-- David Bruha
EMail-: ( email )
tel --: +420.277779500
fax: +420.277779555
org: 1st ART Studio s.r.o.
Konevova 101
Praha 3,-,CZ 130 00

Technical Contactor:
Name-- David Bruha
EMail-: ( email )
tel --: +420.277779500
fax: +420.277779555
org: 1st ART Studio s.r.o.
Konevova 101
Praha 3,-,CZ 130 00

Billing Contactor:
Name-- David Bruha
EMail-: ( email )
tel --: +420.277779500
fax: +420.277779555
org: 1st ART Studio s.r.o.
Konevova 101
Praha 3,-,CZ 130 00

Technical Analysis


DNS servers
ns1.edrive-hosting.cz [188.92.40.66]
ns2.edrive-hosting.cz [78.24.9.153]

DNS Records

Answer records
meusresultados.com SOA
server: ns1.edrive-hosting.cz
email: hostmaster@edrive-hosting.cz
serial: 2012072402
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s
meusresultados.com A 188.92.41.194 3600s
meusresultados.com A 188.92.41.195 3600s
meusresultados.com A 188.92.41.196 3600s
meusresultados.com A 188.92.41.197 3600s
meusresultados.com A 188.92.41.198 3600s
meusresultados.com A 188.92.41.199 3600s
meusresultados.com A 188.92.41.200 3600s
meusresultados.com MX
preference: 10
exchange: mailserver.edrive-hosting.cz
3600s
meusresultados.com MX
preference: 20
exchange: ns2.edrive-hosting.cz
3600s
meusresultados.com NS  ns1.edrive-hosting.cz 3600s
meusresultados.com NS  ns2.edrive-hosting.cz 3600s
meusresultados.com TXT meusresultados.com 3600s

Authority records

Additional records

IP 188.92.41.197 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 188.92.41.197

In Page Analysis

Traffic Analysis

Magestic Backlinks

Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

HTML Analysis

HTML validation
  • 41 Errors
  • 6 Warnings
Ratio Text/Html

0.6462304849658944

Message Error
  • Error Line 10, Column 16: there is no attribute "property"
    <meta property="og:image" content="http://www.meusresultados.com/res/_fs/image/…

    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 22, Column 213: there is no attribute "id"
    …content" id="lsadvert-top"><iframe id="lsadvert-zid-112-iframe" name="banx-top…

    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 22, Column 244: there is no attribute "name"
    …ame id="lsadvert-zid-112-iframe" name="banx-top" frameborder="0" scrolling="no…

    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 22, Column 267: there is no attribute "frameborder"
    …2-iframe" name="banx-top" frameborder="0" scrolling="no" style="width:728px; h…

    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 22, Column 281: there is no attribute "scrolling"
    …="banx-top" frameborder="0" scrolling="no" style="width:728px; height:90px"></…

    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 22, Column 292: there is no attribute "style"
    … frameborder="0" scrolling="no" style="width:728px; height:90px"></iframe></di…

    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 22, Column 318: element "iframe" undefined
    …="no" style="width:728px; height:90px"></iframe></div><div class="adsgraphvert…

    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 62, Column 487: element "iframe" undefined
    …"no" style="width:200px; height:630px"></iframe></div><div class="adsgraphhori…

    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 63, Column 72: required attribute "type" not specified
    …ntent-a" style="display: none;"><style>#box_over_content_44 { position: relati…

    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 63, Column 72: document type does not allow element "style" here
    …ntent-a" style="display: none;"><style>#box_over_content_44 { position: relati…

    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 63, Column 1617: there is no attribute "target"
    …a href="/promobox/44/?sport=1" target="_blank"><span class="gradient"></span><…

    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 63, Column 1704: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …="display: block; text-align: center;"><div style="display: inline-block;"><im…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 63, Column 1774: required attribute "alt" not specified
    …ck;"><img src="/res/data/001352.gif" /><em>100% de Bónus até 50€</em></div></d…

    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 63, Column 1956: required attribute "type" not specified
    …ntent-a" style="display: none;"><style>#box_over_content_630 { position: relat…

    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 63, Column 1956: document type does not allow element "style" here
    …ntent-a" style="display: none;"><style>#box_over_content_630 { position: relat…

    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 63, Column 3051: element "SPAN" undefined
    …ox/630/?sport=1" target="_blank"><SPAN>100% de Bónus até 50€</SPAN>, registe-s…

    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 63, Column 3187: required attribute "type" not specified
    …ntent-d" style="display: none;"><style>#box_over_content_bl { position: relati…

    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 63, Column 3187: document type does not allow element "style" here
    …ntent-d" style="display: none;"><style>#box_over_content_bl { position: relati…

    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 63, Column 4728: there is no attribute "onClick"
    …div class="close"><a href="#" onClick="close_caption_box('box_over_content_bl'…

    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 101, Column 355: element "iframe" undefined
    …="no" style="width:468px; height:60px"></iframe></div><div class="adsgraphhori…

    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 127, Column 359: element "iframe" undefined
    …"no" style="width:120px; height:300px"></iframe></div><div class="adsgraphhori…

    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 351, Column 26: document type does not allow element "span" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    <span id="mlc-4ck3s9wd8c"></span>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 352, Column 25: document type does not allow element "span" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    <span id="mlc-aks81bkdz"></span>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

Visitor Analysis

Daily Visitor

2.217 visits

Daily Visitor