Divulgue Fácil é um site de divulgação de sites, autosurf e ptc, um site de publicidade onde que paga os membros para visitar sites de anunciantes, anuncie no site, autosurf grátis, troca de ...

divulguefacil.com
  • Domain Name
    divulguefacil.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #39164
  • Page Size
    55.6 KB
  • Ip Address
    184.82.87.50
  • Heading
    H1: 0, H2: 0, H3: 2, H4: 0, H5: 0, H6: 0
  • Images
    27 GIF, 6 JPG, 14 PNG

Website Meta Analysis

  • Title
    Divulgue Fácil - Seu Portal de Publicidade Online, Geração de Renda e Entretenimento
  • Meta Keyword
    divulgue seu site, auto surf, troca de visitas, paid to click, autosurf, hits, banners, links patrocinados, publicidade, visitas, cliques, ganhar dinheiro visitando sites, ganhe dinheiro com PTC, ganhar dinheiro clicando, ganhe dinheiro navegando, divulgue fácil, divulgue grátis, visitas garantidas, assinatura premium
  • Meta Description
    Divulgue Fácil é um site de divulgação de sites, autosurf e ptc, um site de publicidade onde que paga os membros para visitar sites de anunciantes, anuncie no site, autosurf grátis, troca de visitas, publicidade em banners, links patrocincados

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    184.82.87.50
  • Domain Age
    4 Years, 4 Months, 25 days.
  • Javascript Library
    jquery, prototype
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Mon, 04 Mar 2013 09:45:46 GMT
  • server: Apache
  • x-powered-by: PHP/5.4.10
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: DIVULGUEFACIL.COM

Registration Date: 31-Oct-2008
Expiration Date: 31-Oct-2013

Status:LOCKED



Name Servers:
ns1.mktdfm.net
ns2.mktdfm.net


Registrant Contact Details:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - Visit PrivacyProtect.org to contact the domain owner/operator
Nobby Beach
Queensland,QLD 4218
AU
Tel. +45.36946676

Administrative Contact Details:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - Visit PrivacyProtect.org to contact the domain owner/operator
Nobby Beach
Queensland,QLD 4218
AU
Tel. +45.36946676

Technical Contact Details:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - Visit PrivacyProtect.org to contact the domain owner/operator
Nobby Beach
Queensland,QLD 4218
AU
Tel. +45.36946676

Billing Contact Details:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - Visit PrivacyProtect.org to contact the domain owner/operator
Nobby Beach
Queensland,QLD 4218
AU
Tel. +45.36946676

DNS Analysis


DNS servers
ns1.mktdfm.net
ns2.mktdfm.net


DNS Records

Answer records
divulguefacil.com TXT v=spf1 +a +mx +ip4:184.82.87.50 ?all 14400s
divulguefacil.com MX
preference: 0
exchange: divulguefacil.com
14400s
divulguefacil.com SOA
server: ns1.mktdfm.net
email: dfm2501@gmail.com
serial: 2013013103
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
divulguefacil.com NS  ns2.mktdfm.net 86400s
divulguefacil.com NS  ns1.mktdfm.net 86400s
divulguefacil.com A 184.82.87.50 14400s

Authority records

Additional records
divulguefacil.com A 184.82.87.50 14400s
ns1.mktdfm.net A 184.82.87.50 14400s
ns2.mktdfm.net A 184.82.87.51 14400s

IP 184.82.87.50 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 178 Errors
  • 49 Warnings
Ratio Text/Html
  • 0.38406852849795503
Message Error
  • Error Line 9, Column 117: end tag for "meta" omitted, but OMITTAG NO was specified
    …e seu site grátis Auto Surf e PTC Ganhe Dinheiro Visitando sites" name="title">

    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 9, Column 1: start tag was here
    <meta content="Divulgue Fácil Divulgue seu site grátis Auto Surf e PTC Ganhe Di…
  • Error Line 246, 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>.

  • Warning Line 414, Column 39: character "&" is the first character of a delimiter but occurred as data
    				if (stickytooltip.rightclickstick && $(e.target).parents().andSelf().filter…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 414, Column 40: character "&" is the first character of a delimiter but occurred as data
    …			if (stickytooltip.rightclickstick && $(e.target).parents().andSelf().filter…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 451, Column 88: character "&" is the first character of a delimiter but occurred as data
    …|http|https):\/\/(\w+:{0,1}\w*@)?(\S+)(:[0-9]+)?(\/|\/([\w#!:.?+=&%@!\-\/]))?/;

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 507, Column 17: there is no attribute "topmargin"
    <body topmargin=0 rightmargin=0 leftmargin=0 >

    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 507, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <body topmargin=0 rightmargin=0 leftmargin=0 >
  • Error Line 507, Column 31: there is no attribute "rightmargin"
    <body topmargin=0 rightmargin=0 leftmargin=0 >

    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 507, Column 31: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <body topmargin=0 rightmargin=0 leftmargin=0 >
  • Error Line 507, Column 44: there is no attribute "leftmargin"
    <body topmargin=0 rightmargin=0 leftmargin=0 >

    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 507, Column 44: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <body topmargin=0 rightmargin=0 leftmargin=0 >
  • Error Line 539, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    			<td align=left  width="middle"><a href="index.php?r="><img src="logo5.png" a…
  • Error Line 540, Column 23: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                <td align=right  width="730px"><div class="bannerheader"><div align…
  • Error Line 540, Column 81: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …><div class="bannerheader"><div align=center><a href="" onclick="window.open('…
  • Warning Line 540, Column 161: cannot generate system identifier for general entity "cod"
    …tp://divulguefacil.com/clk.php?ad=352&cod=caa1e60db3ebf8f9348df8e90107a6b5','d…

    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 540, Column 161: general entity "cod" not defined and no default entity
    …tp://divulguefacil.com/clk.php?ad=352&cod=caa1e60db3ebf8f9348df8e90107a6b5','d…

    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 540, Column 164: reference not terminated by REFC delimiter
    …//divulguefacil.com/clk.php?ad=352&cod=caa1e60db3ebf8f9348df8e90107a6b5','dd')…

    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 540, Column 164: reference to external entity in attribute value
    …//divulguefacil.com/clk.php?ad=352&cod=caa1e60db3ebf8f9348df8e90107a6b5','dd')…

    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 540, Column 164: reference to entity "cod" for which no system identifier could be generated
    …//divulguefacil.com/clk.php?ad=352&cod=caa1e60db3ebf8f9348df8e90107a6b5','dd')…

    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 540, Column 160: entity was defined here
    …ttp://divulguefacil.com/clk.php?ad=352&cod=caa1e60db3ebf8f9348df8e90107a6b5','…
  • Error Line 540, Column 341: required attribute "alt" not specified
    …ng" width="728" height="90" border="0"></a></div><div style="font-family:Arial…

    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 540, Column 345: end tag for "img" omitted, but OMITTAG NO was specified
    …width="728" height="90" border="0"></a></div><div style="font-family:Arial; fo…

    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 540, Column 221: start tag was here
    …8df8e90107a6b5','dd'); return false;"><img src="http://divulguefacil.com/banne…
  • Warning Line 553, Column 37: cannot generate system identifier for general entity "r"
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               

    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 553, Column 37: general entity "r" not defined and no default entity
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               

    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 553, Column 38: reference not terminated by REFC delimiter
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               

    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 553, Column 38: reference to external entity in attribute value
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               

    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 553, Column 38: reference to entity "r" for which no system identifier could be generated
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Warning Line 554, Column 40: reference not terminated by REFC delimiter
                    <li><a href="?act=ads&r=">Anúncios</a></li>

    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 554, Column 40: reference to external entity in attribute value
                    <li><a href="?act=ads&r=">Anúncios</a></li>

    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 554, Column 40: reference to entity "r" for which no system identifier could be generated
                    <li><a href="?act=ads&r=">Anúncios</a></li>

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Warning Line 558, Column 28: reference not terminated by REFC delimiter
    				<li><a href="?act=faq&r=">FAQ</a></li>

    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 558, Column 28: reference to external entity in attribute value
    				<li><a href="?act=faq&r=">FAQ</a></li>

    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 558, Column 28: reference to entity "r" for which no system identifier could be generated
    				<li><a href="?act=faq&r=">FAQ</a></li>

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Warning Line 559, Column 34: reference not terminated by REFC delimiter
    				<li><a href="?act=advertise&r=">Anunciar</a></li>

    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 559, Column 34: reference to external entity in attribute value
    				<li><a href="?act=advertise&r=">Anunciar</a></li>

    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 559, Column 34: reference to entity "r" for which no system identifier could be generated
    				<li><a href="?act=advertise&r=">Anunciar</a></li>

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Warning Line 560, Column 30: reference not terminated by REFC delimiter
    				<li><a href="?act=prova&r=">Comprovando</a></li>

    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 560, Column 30: reference to external entity in attribute value
    				<li><a href="?act=prova&r=">Comprovando</a></li>

    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 560, Column 30: reference to entity "r" for which no system identifier could be generated
    				<li><a href="?act=prova&r=">Comprovando</a></li>

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Warning Line 562, Column 35: reference not terminated by REFC delimiter
        <li><a href="?act=depoimento&r=">Depoimentos</a></li><!--

    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 562, Column 35: reference to external entity in attribute value
        <li><a href="?act=depoimento&r=">Depoimentos</a></li><!--

    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 562, Column 35: reference to entity "r" for which no system identifier could be generated
        <li><a href="?act=depoimento&r=">Depoimentos</a></li><!--

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Warning Line 568, Column 32: reference not terminated by REFC delimiter
    				<li><a href="?act=contact&r=">Contato</a></li>

    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 568, Column 32: reference to external entity in attribute value
    				<li><a href="?act=contact&r=">Contato</a></li>

    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 568, Column 32: reference to entity "r" for which no system identifier could be generated
    				<li><a href="?act=contact&r=">Contato</a></li>

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Error Line 581, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    						<td width="200" valign=top>
  • Error Line 583, Column 64: invalid comment declaration: found name character outside comment but inside comment declaration
                            <!-- ########## MENU LATERAL ESQUERA --->
  • Info Line 583, Column 25: comment declaration started here
                            <!-- ########## MENU LATERAL ESQUERA --->
  • Error Line 586, Column 5: 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 586, Column 1: start tag was here
    <br>
  • Error Line 588, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>Clique no botão abaixo para realizar seu Cadastro.

    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 588, Column 1: start tag was here
    <br>Clique no botão abaixo para realizar seu Cadastro.
  • Warning Line 592, Column 119: reference not terminated by REFC delimiter
    …name="B1" class="fieldbutton" onclick="location.href='?act=register&r='"/></td>

    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 592, Column 119: reference to external entity in attribute value
    …name="B1" class="fieldbutton" onclick="location.href='?act=register&r='"/></td>

    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 592, Column 119: reference to entity "r" for which no system identifier could be generated
    …name="B1" class="fieldbutton" onclick="location.href='?act=register&r='"/></td>

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Error Line 597, Column 5: 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 597, Column 1: start tag was here
    <br>
  • Error Line 602, Column 25: value of attribute "method" cannot be "POST"; must be one of "get", "post"
          <form method="POST" action="logar.php"><tr>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 602, Column 45: document type does not allow element "form" here
          <form method="POST" action="logar.php"><tr>

    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 602, Column 49: document type does not allow element "tr" here; assuming missing "table" start-tag
          <form method="POST" action="logar.php"><tr>
  • Error Line 604, Column 76: end tag for "input" omitted, but OMITTAG NO was specified
            <td width="middle"><input type="text" name="username" size="8"></td>

    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 604, Column 28: start tag was here
            <td width="middle"><input type="text" name="username" size="8"></td>
  • Error Line 608, Column 80: end tag for "input" omitted, but OMITTAG NO was specified
            <td width="middle"><input type="password" name="password" size="8"></td>

    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 608, Column 28: start tag was here
            <td width="middle"><input type="password" name="password" size="8"></td>
  • Warning Line 615, Column 75: reference not terminated by REFC delimiter
    …e" colspan="2"><a href="index.php?act=recoverpwd&r=">Recuperar Acesso!</a></td>

    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 615, Column 75: reference to external entity in attribute value
    …e" colspan="2"><a href="index.php?act=recoverpwd&r=">Recuperar Acesso!</a></td>

    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 615, Column 75: reference to entity "r" for which no system identifier could be generated
    …e" colspan="2"><a href="index.php?act=recoverpwd&r=">Recuperar Acesso!</a></td>

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Error Line 616, Column 20: end tag for "table" omitted, but OMITTAG NO was specified
            </tr></form>

    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 602, Column 46: start tag was here
          <form method="POST" action="logar.php"><tr>
  • Error Line 617, Column 12: end tag for "table" which is not finished
        </table>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 621, Column 5: 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 621, Column 1: start tag was here
    <br>
  • Error Line 623, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>Clique no botão abaixo para acompanhar as estatísticas de seu anúncio.

    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 623, Column 1: start tag was here
    <br>Clique no botão abaixo para acompanhar as estatísticas de seu anúncio.
  • Error Line 625, Column 25: value of attribute "method" cannot be "POST"; must be one of "get", "post"
          <form method="POST" action="?act=anunciante&r=">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 625, Column 52: reference not terminated by REFC delimiter
          <form method="POST" action="?act=anunciante&r=">

    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 625, Column 52: reference to external entity in attribute value
          <form method="POST" action="?act=anunciante&r=">

    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 625, Column 52: reference to entity "r" for which no system identifier could be generated
          <form method="POST" action="?act=anunciante&r=">

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Error Line 625, Column 54: document type does not allow element "form" here
          <form method="POST" action="?act=anunciante&r=">

    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 626, Column 10: document type does not allow element "tr" here; assuming missing "table" start-tag
          <tr>
  • Error Line 629, Column 18: end tag for "table" omitted, but OMITTAG NO was specified
          </tr></form>

    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 626, Column 7: start tag was here
          <tr>
  • Error Line 630, Column 12: end tag for "table" which is not finished
        </table>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 632, Column 5: 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 632, Column 1: start tag was here
    <br>
  • Error Line 639, Column 18: document type does not allow element "tr" here
              <tr><tr><td><div style="font-family: Aria, Tahoma, Verdana; font-size…

    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 639, Column 313: document type does not allow element "tr" here
    …astre já.</a></div></div></td></tr><tr><td><div style="font-family: Aria, Taho…

    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 639, Column 669: end tag for "a" omitted, but OMITTAG NO was specified
    …as promoções, tudo gratuitamen...</div></td></tr><tr><td><div style="font-fami…

    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 639, Column 404: start tag was here
    …font-size: 12px;"><div align="center"><a href="" onclick="window.open('viewads…
  • Error Line 639, Column 674: end tag for "div" omitted, but OMITTAG NO was specified
    …omoções, tudo gratuitamen...</div></td></tr><tr><td><div style="font-family: A…

    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 639, Column 318: start tag was here
    … já.</a></div></div></td></tr><tr><td><div style="font-family: Aria, Tahoma, V…
  • Error Line 639, Column 683: document type does not allow element "tr" here
    …tudo gratuitamen...</div></td></tr><tr><td><div style="font-family: Aria, Taho…

    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 639, Column 1039: end tag for "a" omitted, but OMITTAG NO was specified
    …derno e ágil. Não deixe de par...</div></td></tr><tr><td><div style="font-fami…

    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 639, Column 774: start tag was here
    …font-size: 12px;"><div align="center"><a href="" onclick="window.open('viewads…
  • Error Line 639, Column 1044: end tag for "div" omitted, but OMITTAG NO was specified
    … e ágil. Não deixe de par...</div></td></tr><tr><td><div style="font-family: A…

    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 639, Column 688: start tag was here
    …gratuitamen...</div></td></tr><tr><td><div style="font-family: Aria, Tahoma, V…
  • Error Line 639, Column 1053: document type does not allow element "tr" here
    …Não deixe de par...</div></td></tr><tr><td><div style="font-family: Aria, Taho…

    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 640, Column 20: document type does not allow element "tr" here
    </div></td></tr><tr><td><div style="font-family: Aria, Tahoma, Verdana; font-si…

    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 640, Column 381: document type does not allow element "tr" here
    …M CENTAVO</a></div></div></td></tr><tr><td><div style="font-family: Aria, Taho…

    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 640, Column 736: end tag for "a" omitted, but OMITTAG NO was specified
    …lucros são só seus venderá por...</div></td></tr><tr><td><div style="font-fami…

    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 640, Column 472: start tag was here
    …font-size: 12px;"><div align="center"><a href="" onclick="window.open('viewads…
  • Error Line 640, Column 741: end tag for "div" omitted, but OMITTAG NO was specified
    …s são só seus venderá por...</div></td></tr><tr><td><div style="font-family: A…

    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 640, Column 386: start tag was here
    …TAVO</a></div></div></td></tr><tr><td><div style="font-family: Aria, Tahoma, V…
  • Error Line 640, Column 750: document type does not allow element "tr" here
    …seus venderá por...</div></td></tr><tr><td><div style="font-family: Aria, Taho…

    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 640, Column 1102: document type does not allow element "tr" here
    …r do MMN.</a></div></div></td></tr><tr><td><div style="font-family: Aria, Taho…

    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 640, Column 1342: document type does not allow element "tr" here
    … Dinheiro</a></div></div></td></tr><tr><td><div style="font-family: Aria, Taho…

    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 640, Column 1698: end tag for "a" omitted, but OMITTAG NO was specified
    …o)! Trabalhe em casa como Digi...</div></td></tr><tr><td><div style="font-fami…

    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 640, Column 1433: start tag was here
    …font-size: 12px;"><div align="center"><a href="" onclick="window.open('viewads…
  • Error Line 640, Column 1703: end tag for "div" omitted, but OMITTAG NO was specified
    …rabalhe em casa como Digi...</div></td></tr><tr><td><div style="font-family: A…

    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 640, Column 1347: start tag was here
    …eiro</a></div></div></td></tr><tr><td><div style="font-family: Aria, Tahoma, V…
  • Error Line 640, Column 1712: document type does not allow element "tr" here
    …m casa como Digi...</div></td></tr><tr><td><div style="font-family: Aria, Taho…

    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 640, Column 2068: end tag for "a" omitted, but OMITTAG NO was specified
    …E MUITOS BENEFICIOS MAIS INFORMAÇÕES CLIQUE AQUI E TE DA...</div></td></tr><tr>

    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 640, Column 1803: start tag was here
    …font-size: 12px;"><div align="center"><a href="" onclick="window.open('viewads…
  • Error Line 640, Column 2073: end tag for "div" omitted, but OMITTAG NO was specified
    …E MUITOS BENEFICIOS MAIS INFORMAÇÕES CLIQUE AQUI E TE DA...</div></td></tr><tr>

    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 640, Column 1717: start tag was here
    …a como Digi...</div></td></tr><tr><td><div style="font-family: Aria, Tahoma, V…
  • Error Line 640, Column 2082: document type does not allow element "tr" here
    …E MUITOS BENEFICIOS MAIS INFORMAÇÕES CLIQUE AQUI E TE DA...</div></td></tr><tr>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 642, Column 50: reference not terminated by REFC delimiter
    …ign="center"><a href="?act=advertise&r=&tipo=link">Seu Link Aqui</a></div></td…

    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 642, Column 50: reference to external entity in attribute value
    …ign="center"><a href="?act=advertise&r=&tipo=link">Seu Link Aqui</a></div></td…

    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 642, Column 50: reference to entity "r" for which no system identifier could be generated
    …ign="center"><a href="?act=advertise&r=&tipo=link">Seu Link Aqui</a></div></td…

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Warning Line 642, Column 52: cannot generate system identifier for general entity "tipo"
    …ign="center"><a href="?act=advertise&r=&tipo=link">Seu Link Aqui</a></div></td>

    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 642, Column 52: general entity "tipo" not defined and no default entity
    …ign="center"><a href="?act=advertise&r=&tipo=link">Seu Link Aqui</a></div></td>

    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 642, Column 56: reference not terminated by REFC delimiter
    …ign="center"><a href="?act=advertise&r=&tipo=link">Seu Link Aqui</a></div></td>

    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 642, Column 56: reference to external entity in attribute value
    …ign="center"><a href="?act=advertise&r=&tipo=link">Seu Link Aqui</a></div></td>

    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 642, Column 56: reference to entity "tipo" for which no system identifier could be generated
    …ign="center"><a href="?act=advertise&r=&tipo=link">Seu Link Aqui</a></div></td>

    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 642, Column 51: entity was defined here
    …ign="center"><a href="?act=advertise&r=&tipo=link">Seu Link Aqui</a></div></td>
  • Error Line 643, Column 13: "tr" not finished but containing element ended
    </tr></table></div>
  • Error Line 643, Column 13: end tag for "tr" omitted, but OMITTAG NO was specified
    </tr></table></div>

    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 639, Column 11: start tag was here
              <tr><tr><td><div style="font-family: Aria, Tahoma, Verdana; font-size…
  • Error Line 643, Column 19: end tag for "center" omitted, but OMITTAG NO was specified
    </tr></table></div>

    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 637, Column 9: start tag was here
            <center>
  • Error Line 647, Column 40: invalid comment declaration: found name character outside comment but inside comment declaration
    <!-- ########## MENU LATERAL ESQUERA --->
  • Info Line 647, Column 1: comment declaration started here
    <!-- ########## MENU LATERAL ESQUERA --->
  • Error Line 649, Column 29: end tag for "div" omitted, but OMITTAG NO was specified
                            </td>

    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 585, Column 1: start tag was here
    <div align="center" id="menu">
  • Error Line 650, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    						<td valign=top><div align="center">
  • Error Line 653, Column 221: required attribute "alt" not specified
    …if" width="468" height="60" border="0"></a><div style="font-family:Arial; font…

    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 653, Column 225: end tag for "img" omitted, but OMITTAG NO was specified
    …width="468" height="60" border="0"></a><div style="font-family:Arial; font-siz…

    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 653, Column 125: start tag was here
    …0e59c4e32a9bf6','dd'); return false;"><img src="http://visitasgratis.rp5.com.b…
  • Warning Line 653, Column 381: reference not terminated by REFC delimiter
    …vulgueFácil: <a href="?act=advertise&r=" style="text-decoration: underline;">c…

    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 653, Column 381: reference to external entity in attribute value
    …vulgueFácil: <a href="?act=advertise&r=" style="text-decoration: underline;">c…

    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 653, Column 381: reference to entity "r" for which no system identifier could be generated
    …vulgueFácil: <a href="?act=advertise&r=" style="text-decoration: underline;">c…

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Error Line 659, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    			<td class="tabela"><div align=left><div align="center">
  • Error Line 661, Column 113: there is no attribute "bordercolor"
    …ding="0" style="width: middle; border-collapse:collapse" bordercolor="#111111">

    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 673, Column 34: end tag for "br" omitted, but OMITTAG NO was specified
                <td width="100%"><br><font face="Verdana" size="2"><b>CADASTRE-SE G…

    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 673, Column 30: start tag was here
                <td width="100%"><br><font face="Verdana" size="2"><b>CADASTRE-SE G…
  • Error Line 676, Column 64: end tag for "br" omitted, but OMITTAG NO was specified
                <td width="100%"><font face="Verdana" size="2"><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 676, Column 60: start tag was here
                <td width="100%"><font face="Verdana" size="2"><br>
  • Error Line 678, Column 48: end tag for "br" omitted, but OMITTAG NO was specified
                visitarem sites de anunciantes.<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 678, Column 44: start tag was here
                visitarem sites de anunciantes.<br>
  • Error Line 680, Column 31: end tag for "br" omitted, but OMITTAG NO was specified
                visitar sites.<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 680, Column 27: start tag was here
                visitar sites.<br>
  • Error Line 682, Column 61: end tag for "br" omitted, but OMITTAG NO was specified
                para visitar os sites de nossos anunciantes.<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 682, Column 57: start tag was here
                para visitar os sites de nossos anunciantes.<br>
  • Warning Line 685, Column 42: reference not terminated by REFC delimiter
    …         <a href="?act=como-funciona&r=">Clique aqui</a></font><font face="Ver…

    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 685, Column 42: reference to external entity in attribute value
    …         <a href="?act=como-funciona&r=">Clique aqui</a></font><font face="Ver…

    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 685, Column 42: reference to entity "r" for which no system identifier could be generated
    …         <a href="?act=como-funciona&r=">Clique aqui</a></font><font face="Ver…

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Error Line 690, Column 38: end tag for "br" omitted, but OMITTAG NO was specified
                você precisará fazer:<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 690, Column 34: start tag was here
                você precisará fazer:<br>
  • Error Line 691, Column 18: end tag for "p" omitted, but OMITTAG NO was specified
    &nbsp;</font></td>

    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 689, Column 13: start tag was here
                <p><font face="Verdana" size="2">Veja abaixo uma simulação do que 
  • Error Line 701, Column 42: there is no attribute "height"
    …ble id="Tabela_01" width="782" height="563" border="0" cellpadding="0" cellspa…

    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 704, Column 75: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/registro_01.png" width="817" height="111" alt=""></td>

    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 704, Column 4: start tag was here
    			<img src="imagens/registro_01.png" width="817" height="111" alt=""></td>
  • Error Line 706, Column 68: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="111" alt=""></td>

    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 706, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="111" alt=""></td>
  • Error Line 710, Column 74: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/registro_02.png" width="262" height="45" alt=""></td>

    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 710, Column 4: start tag was here
    			<img src="imagens/registro_02.png" width="262" height="45" alt=""></td>
  • Error Line 725, Column 74: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/registro_04.png" width="288" height="49" alt=""></td>

    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 725, Column 4: start tag was here
    			<img src="imagens/registro_04.png" width="288" height="49" alt=""></td>
  • Error Line 727, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="45" alt=""></td>

    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 727, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="45" alt=""></td>
  • Error Line 745, Column 66: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="4" alt=""></td>

    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 745, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="4" alt=""></td>
  • Error Line 763, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="40" alt=""></td>

    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 763, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="40" alt=""></td>
  • Error Line 769, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="39" alt=""></td>

    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 769, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="39" alt=""></td>
  • Error Line 773, Column 75: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/registro_08.png" width="262" height="324" alt=""></td>

    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 773, Column 4: start tag was here
    			<img src="imagens/registro_08.png" width="262" height="324" alt=""></td>
  • Error Line 775, Column 66: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="7" alt=""></td>

    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 775, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="7" alt=""></td>
  • Error Line 779, Column 75: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/registro_09.png" width="288" height="317" alt=""></td>

    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 779, Column 4: start tag was here
    			<img src="imagens/registro_09.png" width="288" height="317" alt=""></td>
  • Error Line 781, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="11" alt=""></td>

    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 781, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="11" alt=""></td>
  • Warning Line 789, Column 37: reference not terminated by REFC delimiter
                <a href="?act=register&r=">Cadastre-se!</a></font></b></div></td>

    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 789, Column 37: reference to external entity in attribute value
                <a href="?act=register&r=">Cadastre-se!</a></font></b></div></td>

    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 789, Column 37: reference to entity "r" for which no system identifier could be generated
                <a href="?act=register&r=">Cadastre-se!</a></font></b></div></td>

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Error Line 793, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="35" alt=""></td>

    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 793, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="35" alt=""></td>
  • Error Line 799, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="43" alt=""></td>

    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 799, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="43" alt=""></td>
  • Error Line 817, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="98" alt=""></td>

    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 817, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="98" alt=""></td>
  • Error Line 821, Column 75: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/registro_15.png" width="267" height="130" alt=""></td>

    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 821, Column 4: start tag was here
    			<img src="imagens/registro_15.png" width="267" height="130" alt=""></td>
  • Error Line 823, Column 68: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="130" alt=""></td>

    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 823, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="130" alt=""></td>
  • Error Line 839, Column 12: ID "Tabela_01" already defined
    <table id="Tabela_01" width="695" height="563" border="0" cellpadding="0" cells…

    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 701, Column 12: ID "Tabela_01" first defined here
    <table id="Tabela_01" width="782" height="563" border="0" cellpadding="0" cells…
  • Error Line 852, Column 40: end tag for "br" omitted, but OMITTAG NO was specified
                      <td width="100%"><br><font face="Verdana" size="2">O site 

    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 852, Column 36: start tag was here
                      <td width="100%"><br><font face="Verdana" size="2">O site 
  • Error Line 865, Column 70: end tag for "p" omitted, but OMITTAG NO was specified
                      O PROCESSO DE ANÚNCIOS EM NOSSO SITE</font></b></td>

    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 864, Column 19: start tag was here
                      <p><b><font face="Verdana" size="2">VEJA ABAIXO COMO FUNCIONA 
  • Error Line 876, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/anunciante_01.png" width="817" height="111" alt=""></td>

    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 876, Column 4: start tag was here
    			<img src="imagens/anunciante_01.png" width="817" height="111" alt=""></td>
  • Error Line 878, Column 68: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="111" alt=""></td>

    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 878, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="111" alt=""></td>
  • Error Line 882, Column 76: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/anunciante_02.png" width="262" height="45" alt=""></td>

    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 882, Column 4: start tag was here
    			<img src="imagens/anunciante_02.png" width="262" height="45" alt=""></td>
  • Error Line 891, Column 89: end tag for "p" omitted, but OMITTAG NO was specified
    …        necessidades e o DivulgueFácil publica seu anúncio no site.</font></td>

    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 889, Column 19: start tag was here
                      <p align="left"><font face="Verdana" style="font-size: 9pt">
  • Error Line 898, Column 76: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/anunciante_04.png" width="288" height="49" alt=""></td>

    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 898, Column 4: start tag was here
    			<img src="imagens/anunciante_04.png" width="288" height="49" alt=""></td>
  • Error Line 900, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="45" alt=""></td>

    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 900, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="45" alt=""></td>
  • Error Line 918, Column 66: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="4" alt=""></td>

    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 918, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="4" alt=""></td>
  • Error Line 936, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="40" alt=""></td>

    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 936, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="40" alt=""></td>
  • Error Line 942, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="39" alt=""></td>

    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 942, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="39" alt=""></td>
  • Error Line 946, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/anunciante_08.png" width="262" height="324" alt=""></td>

    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 946, Column 4: start tag was here
    			<img src="imagens/anunciante_08.png" width="262" height="324" alt=""></td>
  • Error Line 948, Column 66: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="7" alt=""></td>

    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 948, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="7" alt=""></td>
  • Error Line 952, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/anunciante_09.png" width="288" height="317" alt=""></td>

    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 952, Column 4: start tag was here
    			<img src="imagens/anunciante_09.png" width="288" height="317" alt=""></td>
  • Error Line 954, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="11" alt=""></td>

    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 954, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="11" alt=""></td>
  • Warning Line 960, Column 49: reference not terminated by REFC delimiter
    …ign="center"><a href="?act=advertise&r=            "><b><font size="3" face="V…

    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 960, Column 49: reference to external entity in attribute value
    …ign="center"><a href="?act=advertise&r=            "><b><font size="3" face="V…

    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 960, Column 49: reference to entity "r" for which no system identifier could be generated
    …ign="center"><a href="?act=advertise&r=            "><b><font size="3" face="V…

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Error Line 964, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="35" alt=""></td>

    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 964, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="35" alt=""></td>
  • Error Line 970, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="43" alt=""></td>

    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 970, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="43" alt=""></td>
  • Error Line 988, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="98" alt=""></td>

    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 988, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="98" alt=""></td>
  • Error Line 992, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/anunciante_15.png" width="267" height="130" alt=""></td>

    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 992, Column 4: start tag was here
    			<img src="imagens/anunciante_15.png" width="267" height="130" alt=""></td>
  • Error Line 994, Column 68: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="imagens/spacer.gif" width="1" height="130" alt=""></td>

    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 994, Column 4: start tag was here
    			<img src="imagens/spacer.gif" width="1" height="130" alt=""></td>
  • Error Line 1010, Column 14: there is no attribute "widht"
    			<td widht="728px" class="bannerheader"><div align="center">

    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 1012, Column 208: required attribute "alt" not specified
    …5reais.com/banner/728x90.jpg" width="729" height="90" border="0"></a></td></tr>

    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 1012, Column 212: end tag for "img" omitted, but OMITTAG NO was specified
    …5reais.com/banner/728x90.jpg" width="729" height="90" border="0"></a></td></tr>

    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 1012, Column 116: start tag was here
    …4c9c24ef777e4a','dd'); return false;"><img src="http://www.revenda5reais.com/b…
  • Error Line 1019, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    						<td width="200" valign=top>
  • Error Line 1021, Column 25: ID "menu" already defined
    <div align="center" id="menu">

    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 585, Column 25: ID "menu" first defined here
    <div align="center" id="menu">
  • Error Line 1022, Column 5: 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 1022, Column 1: start tag was here
    <br>
  • Error Line 1024, Column 24: end tag for "br" omitted, but OMITTAG NO was specified
    <b>Estatísticas</b><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 1024, Column 20: start tag was here
    <b>Estatísticas</b><br>
  • Error Line 1028, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td align=left><font face="Tahoma" style="font-size:10px;font-weight: bold;">To…
  • Error Line 1029, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td align=left><font face="Tahoma" style="font-size:10px;font-weight: bold;colo…
  • Error Line 1032, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td align=left><font face="Tahoma" style="font-size:10px;font-weight: bold;">Us…
  • Error Line 1033, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td align=left><font face="Tahoma" style="font-size:10px;font-weight: bold;colo…
  • Error Line 1036, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td align=left><font face="Tahoma" style="font-size:10px;font-weight: bold;">Pa…
  • Error Line 1037, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td align=left><font face="Tahoma" style="font-size:10px;font-weight: bold;colo…
  • Error Line 1040, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td align=left><font face="Tahoma" style="font-size:10px;font-weight: bold;">To…
  • Error Line 1041, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <td align=left><font face="Tahoma" style="font-size:10px;font-weight: bold;colo…
  • Error Line 1049, Column 5: 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 1049, Column 1: start tag was here
    <br>
  • Error Line 1051, Column 23: end tag for "br" omitted, but OMITTAG NO was specified
    <b>Publicidade</b><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 1051, Column 19: start tag was here
    <b>Publicidade</b><br>
  • Error Line 1056, Column 235: required attribute "alt" not specified
    …com-ebooks.jpg" width="120" border="0"></a></td></tr><tr><td width="100%" alig…

    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 1056, Column 239: end tag for "img" omitted, but OMITTAG NO was specified
    …ebooks.jpg" width="120" border="0"></a></td></tr><tr><td width="100%" align="c…

    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 1056, Column 141: start tag was here
    …7680f132e9d5ed','dd'); return false;"><img src="http://como-ganhar.net/images/…
  • Error Line 1056, Column 468: required attribute "alt" not specified
    …banner/125.jpg" width="120" border="0"></a></td></tr><tr><td width="100%" alig…

    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 1056, Column 472: end tag for "img" omitted, but OMITTAG NO was specified
    …er/125.jpg" width="120" border="0"></a></td></tr><tr><td width="100%" align="c…

    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 1056, Column 390: start tag was here
    …2e3520d80c4210','dd'); return false;"><img src="http://www.rotadodinheiro.com/…
  • Error Line 1056, Column 744: required attribute "alt" not specified
    …om-revenda.png" width="120" border="0"></a></td></tr><tr><td width="100%" alig…

    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 1056, Column 748: end tag for "img" omitted, but OMITTAG NO was specified
    …evenda.png" width="120" border="0"></a></td></tr><tr><td width="100%" align="c…

    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 1056, Column 623: start tag was here
    …69278a91bc85d1','dd'); return false;"><img src="http://www.fazeromeusite.com/w…
  • Error Line 1056, Column 1001: required attribute "alt" not specified
    …if" width="120" height="60" border="0"></a></td></tr><tr><td width="100%" alig…

    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 1056, Column 1005: end tag for "img" omitted, but OMITTAG NO was specified
    …width="120" height="60" border="0"></a></td></tr><tr><td width="100%" align="c…

    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 1056, Column 899: start tag was here
    …ee958f9a4b6af6','dd'); return false;"><img src="http://www.kitpilotoautomatico…
  • Error Line 1056, Column 1250: required attribute "alt" not specified
    …heiro.com.br/banners/banne_300x250.jpg" width="120" border="0"></a></td></tr>  

    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 1056, Column 1254: end tag for "img" omitted, but OMITTAG NO was specified
    …heiro.com.br/banners/banne_300x250.jpg" width="120" border="0"></a></td></tr>  

    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 1056, Column 1156: start tag was here
    …f24c74ee04bf91','dd'); return false;"><img src="http://www.internetdinheiro.co…
  • Error Line 1058, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div align=center><a href="http://www.recargaplus.com.br/13" _cke_saved_href="h…
  • Error Line 1058, Column 78: there is no attribute "_cke_saved_href"
    …ecargaplus.com.br/13" _cke_saved_href="http://www.recargaplus.com.br/13"> <img…

    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 1058, Column 202: there is no attribute "_cke_saved_src"
    …ges/banner1120x60.gif" _cke_saved_src="http://recargaplus.com.br/images/banner…

    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 1058, Column 278: required attribute "alt" not specified
    …ttp://recargaplus.com.br/images/banner1120x60.gif" width="120" height="60"></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 1058, Column 282: end tag for "img" omitted, but OMITTAG NO was specified
    …ttp://recargaplus.com.br/images/banner1120x60.gif" width="120" height="60"></a>

    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 1058, Column 114: start tag was here
    …f="http://www.recargaplus.com.br/13"> <img border="0" src="http://recargaplus.…
  • Warning Line 1059, Column 32: reference not terminated by REFC delimiter
    <br /><a href="?act=advertise&r=&tipo=banner120x60"><img src="images/anuncieaqu…

    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 1059, Column 32: reference to external entity in attribute value
    <br /><a href="?act=advertise&r=&tipo=banner120x60"><img src="images/anuncieaqu…

    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 1059, Column 32: reference to entity "r" for which no system identifier could be generated
    <br /><a href="?act=advertise&r=&tipo=banner120x60"><img src="images/anuncieaqu…

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               
  • Warning Line 1059, Column 38: reference not terminated by REFC delimiter
    <br /><a href="?act=advertise&r=&tipo=banner120x60"><img src="images/anuncieaqu…

    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 1059, Column 38: reference to external entity in attribute value
    <br /><a href="?act=advertise&r=&tipo=banner120x60"><img src="images/anuncieaqu…

    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 1059, Column 38: reference to entity "tipo" for which no system identifier could be generated
    <br /><a href="?act=advertise&r=&tipo=banner120x60"><img src="images/anuncieaqu…

    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 642, Column 51: entity was defined here
    …ign="center"><a href="?act=advertise&r=&tipo=link">Seu Link Aqui</a></div></td>
  • Error Line 1059, Column 246: end tag for "br" omitted, but OMITTAG NO was specified
    …ácil, ganhe dinheiro visitando sites, Auto Surf e PTC Divulgue Fácil"/></a><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 1059, Column 242: start tag was here
    …ácil, ganhe dinheiro visitando sites, Auto Surf e PTC Divulgue Fácil"/></a><br>
  • Error Line 1060, Column 79: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rt/show?url=divulguefacil.com" target=_blank><img src="http://divulguefacil.co…
  • Error Line 1060, Column 196: end tag for "br" omitted, but OMITTAG NO was specified
    …com/seguro.jpg" width="120" height="60" border="0"  alt="Site Seguro"/></a><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 1060, Column 192: start tag was here
    …com/seguro.jpg" width="120" height="60" border="0"  alt="Site Seguro"/></a><br>
  • Error Line 1062, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <tr><td align=center>
  • Error Line 1065, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
    <div align="center"><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 1065, Column 21: start tag was here
    <div align="center"><br> 
  • Error Line 1066, Column 168: required attribute "alt" not specified
    …'600' src='http://www.frpromotora.com/images123/4448banner120x600.gif'></a></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 1066, Column 172: end tag for "img" omitted, but OMITTAG NO was specified
    …'600' src='http://www.frpromotora.com/images123/4448banner120x600.gif'></a></a>

    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 1066, Column 63: start tag was here
    …omotora.com/44595842' target='_blank'><img border='0' width='160' height='600'…
  • Error Line 1066, Column 176: end tag for element "a" which is not open
    …'600' src='http://www.frpromotora.com/images123/4448banner120x600.gif'></a></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 1089, Column 19: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    			<td><div align=center><center><b><font size="2" color="#ffff00"><i>* Este si…
  • Error Line 1089, Column 196: end tag for "br" omitted, but OMITTAG NO was specified
    …><font size="2" color="ffffff"><i><br><b>Atenção! </b>Os anúncios publicados n…

    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 1089, Column 192: start tag was here
    …></b><font size="2" color="ffffff"><i><br><b>Atenção! </b>Os anúncios publicad…
  • Error Line 1090, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><b>&copy; Copyright 2011 - 2013</b> by <a style="color: #CCFFFF;" href="ind…

    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 1090, Column 1: start tag was here
    <br><b>&copy; Copyright 2011 - 2013</b> by <a style="color: #CCFFFF;" href="ind…
  • Warning Line 1090, Column 204: cannot generate system identifier for general entity "cad"
    …;" href="javascript:abrir('tos.php?r=&cad=20130220');">Termo de Uso</a> | <a s…

    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 1090, Column 204: general entity "cad" not defined and no default entity
    …;" href="javascript:abrir('tos.php?r=&cad=20130220');">Termo de Uso</a> | <a s…

    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 1090, Column 207: reference not terminated by REFC delimiter
    …href="javascript:abrir('tos.php?r=&cad=20130220');">Termo de Uso</a> | <a styl…

    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 1090, Column 207: reference to external entity in attribute value
    …href="javascript:abrir('tos.php?r=&cad=20130220');">Termo de Uso</a> | <a styl…

    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 1090, Column 207: reference to entity "cad" for which no system identifier could be generated
    …href="javascript:abrir('tos.php?r=&cad=20130220');">Termo de Uso</a> | <a styl…

    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 1090, Column 203: entity was defined here
    …F;" href="javascript:abrir('tos.php?r=&cad=20130220');">Termo de Uso</a> | <a …
  • Warning Line 1090, Column 287: reference not terminated by REFC delimiter
    …"color: #CCFFFF;" href="?act=privacy&r=">Política De Privacidade</a></font></c…

    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 1090, Column 287: reference to external entity in attribute value
    …"color: #CCFFFF;" href="?act=privacy&r=">Política De Privacidade</a></font></c…

    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 1090, Column 287: reference to entity "r" for which no system identifier could be generated
    …"color: #CCFFFF;" href="?act=privacy&r=">Política De Privacidade</a></font></c…

    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 553, Column 36: entity was defined here
    				<li><a href="?act=como-funciona&r=">Como Funciona</a></li>               

Visitor Analysis

Daily Visitor
  • 3.150 visits
Daily Visitor