Conheça o Clube do Ricardo e aproveite ofertas com até 90% de desconto! ...

clubedoricardo.com.br
  • Domain Name
    clubedoricardo.com.br
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #39927
  • Page Size
    28.5 KB
  • Ip Address
    64.94.136.5
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 16 JPG, 21 PNG

Website Meta Analysis

  • Title
    ClubeDoRicardo.com.br - Desconto é tudo!
  • Meta Keyword
  • Meta Description
    Conheça o Clube do Ricardo e aproveite ofertas com até 90% de desconto!

Technical Analysis

  • Webserver
    WEB 7
  • Ip Address
    64.94.136.5
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Mon, 11 Feb 2013 08:09:02 GMT
  • server: WEB 7
  • html-cache: HIT from FIREFOX - 15.0.1
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-length: 5435
  • content-type: text/html; charset=ISO-8859-1
  • age: 22
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)

% Copyright (c) Nic.br
% The use of the data below is only permitted as described in
% full by the terms of use (http://registro.br/termo/en.html),
% being prohibited its distribution, comercialization or
% reproduction, in particular, to use it for advertising or
% any similar purpose.
% 2012-11-12 11:19:54 (BRST -02:00)

domain: clubedoricardo.com.br
owner: Ricardo Eletro Divinópolis Ltda
ownerid: 064.282.601/0001-17
responsible: Ricardo Rodrigues Nunes
country: BR
owner-c: RRN93
admin-c: RRN93
tech-c: RRN93
billing-c: RRN93
nserver: ns1.maquinadevendas.com.br
nsstat: 20121108 AA
nslastaa: 20121108
nserver: ns2.maquinadevendas.com.br
nsstat: 20121108 AA
nslastaa: 20121108
nserver: ns3.maquinadevendas.com.br
nsstat: 20121108 AA
nslastaa: 20121108
nserver: ns4.maquinadevendas.com.br
nsstat: 20121108 AA
nslastaa: 20121108
nserver: ns5.maquinadevendas.com.br
nsstat: 20121108 AA
nslastaa: 20121108
saci: yes
created: 20110722 #8612264
expires: 20160722
changed: 20110806
status: published

nic-hdl-br: RRN93
person: Ricardo Rodrigues Nunes
e-mail: email
created: 20051112
changed: 20110512

% Security and mail abuse issues should also be addressed to
% cert.br, http://www.cert.br/, respectivelly to email
% and email
%
% whois.registro.br accepts only direct match queries. Types
% of queries are: domain (.br), ticket, provider, ID, CIDR
% block, IP and ASN.

DNS Analysis


DNS servers
ns1.maquinadevendas.com.br [64.94.136.11]
ns2.maquinadevendas.com.br [64.237.45.34]
ns3.maquinadevendas.com.br [64.94.136.13]
ns4.maquinadevendas.com.br
ns5.maquinadevendas.com.br


DNS Records

Answer records
clubedoricardo.com.br NS  dns3.nettica.com 86400s
clubedoricardo.com.br NS  dns4.nettica.com 86400s
clubedoricardo.com.br NS  dns5.nettica.com 86400s
clubedoricardo.com.br SOA
server: dns1.nettica.com
email: hostmaster@nettica.com
serial: 112
refresh: 21600
retry: 7200
expire: 604800
minimum ttl: 3600
3600s
clubedoricardo.com.br TXT v=spf1 include:spf1.clubedoricardo.com.br include:spf2.clubedoricardo.com.br ip4:75.126.58.10 ip4:209.59.225.0/24 ip4:177.136.16.0/21 ip4:69.72.160.26 ip4:69.72.186.0/24 ip4:65.98.101.0/24 ip4:50.61.243.0/24 ip4:50.61.242.0/24 ip4:177.136.16.0/21 ~all 3600s
clubedoricardo.com.br A 64.94.136.5 3600s
clubedoricardo.com.br MX
preference: 5
exchange: mailserver.ricardoeletro.com.br
3600s
clubedoricardo.com.br NS  dns1.nettica.com 86400s

Authority records

Additional records

IP 64.94.136.5 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Lawrenceville
  • Continent Code
    30044
  • Latitude
    770
  • Longitude
    524
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 64.94.136.5"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=64.94.136.5?showDetails=true&showARIN=false&ext=netref2
    #

    Internap Network Services Corporation PNAP-05-2000 (NET-64-94-0-0-1) 64.94.0.0 - 64.95.255.255
    Nettica INAP-SEF-NETTICA-15838 (NET-64-94-136-0-1) 64.94.136.0 - 64.94.136.255


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 50 Errors
  • 10 Warnings
Ratio Text/Html
  • 0.5391981876844923
Message Error
  • Error Line 12, Column 16: there is no attribute "property"
    <meta property="og:title" content="ClubeDoRicardo.com.br - Desconto &eacute; tu…

    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 15, Column 229: cannot generate system identifier for general entity "h"
    …jb20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=c09047201618f1e1d4ba56adf03f3d0d" rel=…

    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 15, Column 229: general entity "h" not defined and no default entity
    …jb20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=c09047201618f1e1d4ba56adf03f3d0d" rel=…

    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.

  • Warning Line 15, Column 230: reference not terminated by REFC delimiter
    …b20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=c09047201618f1e1d4ba56adf03f3d0d" rel="…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 15, Column 230: reference to external entity in attribute value
    …b20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=c09047201618f1e1d4ba56adf03f3d0d" rel="…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 15, Column 230: reference to entity "h" for which no system identifier could be generated
    …b20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=c09047201618f1e1d4ba56adf03f3d0d" rel="…

    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 15, Column 228: entity was defined here
    …5jb20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=c09047201618f1e1d4ba56adf03f3d0d" rel…
  • Warning Line 15, Column 443: reference not terminated by REFC delimiter
    …b20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=68899926f8b071bd1274dca9b6d0f923" type=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 15, Column 443: reference to external entity in attribute value
    …b20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=68899926f8b071bd1274dca9b6d0f923" type=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 15, Column 443: reference to entity "h" for which no system identifier could be generated
    …b20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=68899926f8b071bd1274dca9b6d0f923" type=…

    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 15, Column 228: entity was defined here
    …5jb20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=c09047201618f1e1d4ba56adf03f3d0d" rel…
  • Warning Line 17, Column 175: reference not terminated by REFC delimiter
    …b20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=c09047201618f1e1d4ba56adf03f3d0d" type=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 17, Column 175: reference to external entity in attribute value
    …b20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=c09047201618f1e1d4ba56adf03f3d0d" type=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 17, Column 175: reference to entity "h" for which no system identifier could be generated
    …b20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=c09047201618f1e1d4ba56adf03f3d0d" type=…

    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 15, Column 228: entity was defined here
    …5jb20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=c09047201618f1e1d4ba56adf03f3d0d" rel…
  • Warning Line 19, Column 173: reference not terminated by REFC delimiter
    …b20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=db3e6215001e1a972b305427b1c31599" type=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 19, Column 173: reference to external entity in attribute value
    …b20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=db3e6215001e1a972b305427b1c31599" type=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 19, Column 173: reference to entity "h" for which no system identifier could be generated
    …b20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=db3e6215001e1a972b305427b1c31599" type=…

    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 15, Column 228: entity was defined here
    …5jb20uYnImcGF0aD1jciZzaXRlX3BhdGg9Y3I=&h=c09047201618f1e1d4ba56adf03f3d0d" rel…
  • Error Line 24, Column 8: required attribute "type" not specified
    <script>

    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 31, Column 105: document type does not allow element "a" here
    …br/Cliente/Sair/1' title='Não é você?'>não é você?</a> /  <a href='https://www…

    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 31, Column 196: document type does not allow element "a" here
    …f='https://www.clubedoricardo.com.br/Cliente/Sair/2' title='Sair'>sair</a> )");

    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 33, Column 99: document type does not allow element "a" here
    …https://www.clubedoricardo.com.br/Cliente/Login' title='Entrar'>Entrar</a> )");

    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 61, Column 28: character ";" not allowed in attribute specification list
    	for(i=0; i<qtdProdCarrinho; i++) {
  • Error Line 61, Column 28: element "qtdProdCarrinho" undefined
    	for(i=0; i<qtdProdCarrinho; i++) {

    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 85, Column 9: end tag for "qtdProdCarrinho" omitted, but OMITTAG NO was specified
    </script>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 61, Column 12: start tag was here
    	for(i=0; i<qtdProdCarrinho; i++) {
  • Error Line 93, Column 8: required attribute "type" not specified
    <script>

    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 127, Column 7: required attribute "type" not specified
    <style>

    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 127, Column 7: document type does not allow element "style" here
    <style>

    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 174, Column 104: required attribute "alt" not specified
    …ges.maquinadevendas.com.br/220x220/produto/210528_481710_20120402174319.jpg" />

    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 195, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
    					<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 195, Column 6: start tag was here
    					<br>
  • Error Line 204, Column 102: required attribute "alt" not specified
    …ages.maquinadevendas.com.br/68x50/produto/283755_1476958_20120928094549.jpg" />

    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 221, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 200, Column 2: start tag was here
    	<div class="conteudo">
  • Error Line 227, Column 99: required attribute "alt" not specified
    …/images.maquinadevendas.com.br/68x50/produto/32345_88154_20101011095324.jpg" />

    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 244, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 223, Column 2: start tag was here
    	<div class="conteudo">
  • Error Line 250, Column 99: required attribute "alt" not specified
    …/images.maquinadevendas.com.br/68x50/produto/35077_88409_20101011135358.jpg" />

    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 267, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 246, Column 2: start tag was here
    	<div class="conteudo">
  • Error Line 273, Column 99: required attribute "alt" not specified
    …/images.maquinadevendas.com.br/68x50/produto/29001_80106_20100915091938.jpg" />

    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 290, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 269, Column 2: start tag was here
    	<div class="conteudo">
  • Error Line 296, Column 102: required attribute "alt" not specified
    …ages.maquinadevendas.com.br/68x50/produto/301693_1541600_20121011104535.jpg" />

    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 313, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 292, Column 2: start tag was here
    	<div class="conteudo">
  • Error Line 319, Column 102: required attribute "alt" not specified
    …ages.maquinadevendas.com.br/68x50/produto/307768_1608923_20121105111543.jpg" />

    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 336, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 315, Column 2: start tag was here
    	<div class="conteudo">
  • Error Line 342, Column 102: required attribute "alt" not specified
    …ages.maquinadevendas.com.br/68x50/produto/249805_1152538_20120611173240.jpg" />

    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 359, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 338, Column 2: start tag was here
    	<div class="conteudo">
  • Error Line 365, Column 101: required attribute "alt" not specified
    …mages.maquinadevendas.com.br/68x50/produto/31428_1830504_20130204102925.jpg" />

    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 382, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 361, Column 2: start tag was here
    	<div class="conteudo">
  • Error Line 388, Column 100: required attribute "alt" not specified
    …images.maquinadevendas.com.br/68x50/produto/9449_1830510_20130204103819.jpg" />

    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 405, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 384, Column 2: start tag was here
    	<div class="conteudo">
  • Error Line 411, Column 102: required attribute "alt" not specified
    …ages.maquinadevendas.com.br/68x50/produto/283202_1437768_20120914113123.jpg" />

    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 428, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </li>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 407, Column 2: start tag was here
    	<div class="conteudo">
  • Error Line 439, Column 106: required attribute "alt" not specified
    …mages.maquinadevendas.com.br/90x65/produto/102655_371162_20120216083906.jpg" />

    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 445, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    									<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 445, Column 10: start tag was here
    									<br>
  • Error Line 451, Column 125: required attribute "alt" not specified
    …adevendas.com.br/site/cr/esgotado.png" width="97" height="19"/></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 461, Column 23: required attribute "type" not specified
                    <style>

    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 461, Column 23: document type does not allow element "style" here
                    <style>

    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 493, Column 18: there is no attribute "target"
    							<a target="_blank" href="http://twitter.com/#!/clubedoricardo">

    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 494, Column 137: required attribute "alt" not specified
    …quinadevendas.com.br/site/cr/buttons/bt_twitter.jpg" width="224" height="252"/>

    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 499, Column 135: required attribute "alt" not specified
    …uinadevendas.com.br/site/cr/buttons/bt_facebook.jpg" width="253" height="252"/>

    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 505, Column 15: required attribute "type" not specified
    			   	<script>

    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 530, Column 119: there is no attribute "link"
    …o.com.br/Cliente/modal_cadastro" link="http://www.clubedoricardo.com.br">meus …

    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 545, Column 101: required attribute "alt" not specified
    …/a248.e.akamai.net/f/248/52872/0s/img.ebit.com.br/ebitBR/selo/img_17613.png" />

    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 602, Column 8: required attribute "type" not specified
    <script>

    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.917 visits
Daily Visitor