putariabrasileira.com

putariabrasileira.com has Alexa Rank 10.976 and Google Page Rank is 1

Display Widget for this domain on your website. Click Here
This data was last updated from 18-01-2013 07:24:12  (update).

Overview Info

  • Domain Name
    putariabrasileira.com
  • Favicon
  • Alexa Rank
    #10976
  • Google Page Rank
    PR 1
  • Ip Address
    89.185.229.127
  • Page Size
    220.3 KB
  • Images
    3 GIF, 65 JPG, 283 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 59 0 0 0 0

Technical Analysis



  • Webserver
    nginx admin
  • Ip Address
    89.185.229.127
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx admin
  • date: Fri, 18 Jan 2013 07:24:12 GMT
  • content-type: text/html;charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • cache-control: no-cache, must-revalidate, max-age=0
  • pragma: no-cache
  • expires: Wed, 11 Jan 1984 05:00:00 GMT
  • content-encoding-handler: default
  • last-modified: Thu, 17 Jan 2013 23:28:55 GMT
  • x-ua-compatible: IE=Edge,chrome=1
  • x-cache: HIT from Backend
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: putariabrasileira.com

Registrant:
edgar c/o Dynadot Privacy
PO Box 701
San Mateo, CA 94401
United States

Administrative Contact:
edgar c/o Dynadot Privacy
PO Box 701
San Mateo, CA 94401
United States
email
1-650-585-4708

Technical Contact:
edgar c/o Dynadot Privacy
PO Box 701
San Mateo, CA 94401
United States
email
1-650-585-4708

Record expires on 2015/08/19 UTC
Record created on 2009/08/19 UTC

Domain servers in listed order:
ns55.updns.net
ns56.updns.net

DNS Analysis


DNS servers
ns55.updns.net
ns56.updns.net


DNS Records

Answer records
putariabrasileira.com MX
preference: 0
exchange: putariabrasileira.com
14400s
putariabrasileira.com SOA
server: ns55.updns.net
email: webmailtafc@gmail.com
serial: 2012101711
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
putariabrasileira.com NS  ns56.updns.net 86400s
putariabrasileira.com NS  ns55.updns.net 86400s
putariabrasileira.com A 89.185.229.127 14400s

Authority records

Additional records
putariabrasileira.com A 89.185.229.127 14400s

IP 89.185.229.127 Analysis

  • Country Code
    CZ
  • Country Code3
    CZE
  • Country Name
    Czech Republic
  • City
    H�sting
  • Continent Code
    EU
  • Latitude
    49.0167
  • Longitude
    15.9.
  • No whois ip data for 89.185.229.127

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 72 Errors
  • 21 Warnings
Ratio Text/Html
  • 0.8829676395348321
Message Error
  • Error Line 30, Column 104: end tag for "link" omitted, but OMITTAG NO was specified
    ….googleapis.com/css?family=Yanone+Kaffeesatz' rel='stylesheet' type='text/css'>

    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 30, Column 1: start tag was here
    <link href='http://fonts.googleapis.com/css?family=Yanone+Kaffeesatz' rel='styl…
  • Error Line 31, Column 94: end tag for "link" omitted, but OMITTAG NO was specified
    …tp://fonts.googleapis.com/css?family=PT+Sans' rel='stylesheet' type='text/css'>

    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 31, Column 1: start tag was here
    <link href='http://fonts.googleapis.com/css?family=PT+Sans' rel='stylesheet' ty…
  • Warning Line 62, Column 31: character "&" is the first character of a delimiter but occurred as data
    			var parts = url.replace(/[?&]+([^=&]+)=([^&]*)/gi, function(m,key,value)

    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 62, Column 38: character "&" is the first character of a delimiter but occurred as data
    			var parts = url.replace(/[?&]+([^=&]+)=([^&]*)/gi, function(m,key,value)

    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 62, Column 46: character "&" is the first character of a delimiter but occurred as data
    			var parts = url.replace(/[?&]+([^=&]+)=([^&]*)/gi, function(m,key,value)

    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 87, Column 139: there is no attribute "onClick"
    … -10px 0 0; padding:2px 4px;" onClick="$('.sharer-icons').fadeOut(500);">X</di…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 92, Column 112: end tag for "img" omitted, but OMITTAG NO was specified
    …rasileira.com/wp-content/themes/pb2/images/logo-sharer-buttons.png" alt="Blog">

    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 92, Column 4: start tag was here
       <img src="http://www.putariabrasileira.com/wp-content/themes/pb2/images/logo…
  • Error Line 96, Column 21: there is no attribute "size"
        <g:plusone size="tall" href="http://www.putariabrasileira.com"></g:plusone>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 96, Column 33: there is no attribute "href"
        <g:plusone size="tall" href="http://www.putariabrasileira.com"></g:plusone>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 96, Column 67: element "g:plusone" undefined
        <g:plusone size="tall" href="http://www.putariabrasileira.com"></g:plusone>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 99, Column 36: there is no attribute "data-href"
        <div class="fb-like" data-href="http://www.putariabrasileira.com" data-send…

    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 99, Column 81: there is no attribute "data-send"
    …/www.putariabrasileira.com" data-send="false" data-layout="box_count" data-wid…

    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 99, Column 101: there is no attribute "data-layout"
    …ra.com" data-send="false" data-layout="box_count" data-width="70" data-show-fa…

    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 99, Column 124: there is no attribute "data-width"
    …d="false" data-layout="box_count" data-width="70" data-show-faces="true"></div>

    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 99, Column 145: there is no attribute "data-show-faces"
    …d="false" data-layout="box_count" data-width="70" data-show-faces="true"></div>

    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 103, Column 78: there is no attribute "data-url"
    …class="twitter-share-button" data-url="http://www.putariabrasileira.com" data-…

    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 103, Column 123: there is no attribute "data-text"
    …/www.putariabrasileira.com" data-text="Julia &#8211; As Panteras: Encontros Ar…

    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 103, Column 217: there is no attribute "data-count"
    …os Ardentes - http://www.putariabrasileira.com" data-count="vertical">Tweet</a>

    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 115, Column 28: value of attribute "id" invalid: "1" cannot start a name
        <ul class="catnav" id="1">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 143, Column 332: required attribute "alt" not specified
    …je!!" src='http://www.originalafiliados.com/banners/bp-175x175.jpg' /></a></li>

    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 145, Column 289: required attribute "alt" not specified
    …ão Paulo"src='http://www.megapotencia.com/publicidadesplove1751.gif'/></a></li>

    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 147, Column 290: required attribute "alt" not specified
    …ente"src='http://www.putariabrasileira.com/galerias/mega-bomba.jpg' /></a></li>

    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 148, Column 272: required attribute "alt" not specified
    …='http://protectorlink.info/capas/putaria_175x175.jpg' /></a></li>        </ul>

    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 157, Column 85: cannot generate system identifier for general entity "r_orderby"
    …iabrasileira.com/?r_sortby=most_rated&r_orderby=desc"><span class="left"></spa…

    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 157, Column 85: general entity "r_orderby" not defined and no default entity
    …iabrasileira.com/?r_sortby=most_rated&r_orderby=desc"><span class="left"></spa…

    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 157, Column 94: reference not terminated by REFC delimiter
    …ira.com/?r_sortby=most_rated&r_orderby=desc"><span class="left"></span><span 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 157, Column 94: reference to external entity in attribute value
    …ira.com/?r_sortby=most_rated&r_orderby=desc"><span class="left"></span><span 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 157, Column 94: reference to entity "r_orderby" for which no system identifier could be generated
    …ira.com/?r_sortby=most_rated&r_orderby=desc"><span class="left"></span><span 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 157, Column 84: entity was defined here
    …riabrasileira.com/?r_sortby=most_rated&r_orderby=desc"><span class="left"></sp…
  • Warning Line 158, Column 80: cannot generate system identifier for general entity "v_orderby"
    …putariabrasileira.com/?v_sortby=views&v_orderby=desc"><span class="left"></spa…

    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 158, Column 80: general entity "v_orderby" not defined and no default entity
    …putariabrasileira.com/?v_sortby=views&v_orderby=desc"><span class="left"></spa…

    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 158, Column 89: reference not terminated by REFC delimiter
    …asileira.com/?v_sortby=views&v_orderby=desc"><span class="left"></span><span 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 158, Column 89: reference to external entity in attribute value
    …asileira.com/?v_sortby=views&v_orderby=desc"><span class="left"></span><span 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 158, Column 89: reference to entity "v_orderby" for which no system identifier could be generated
    …asileira.com/?v_sortby=views&v_orderby=desc"><span class="left"></span><span 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 158, Column 79: entity was defined here
    ….putariabrasileira.com/?v_sortby=views&v_orderby=desc"><span class="left"></sp…
  • Error Line 184, Column 233: there is no attribute "onerror"
    …Panteras: Encontros Ardentes" onerror="this.onerror=null; this.src='http://www…

    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 1441, Column 97: there is no attribute "onClick"
    …usca..." name="s"  size="10"  onClick="if (this.value == 'Digite sua busca...'…

    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 1441, Column 168: there is no attribute "onBlur"
    …sca...') { this.value = ''; }" onBlur="if (this.value == '') { this.value = 'D…

    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 1459, Column 276: NET-enabling start-tag not immediately followed by null end-tag
    …o Vivo"src='http://www.putariabrasileira.com/galerias/telefone-disk.jpg'/ ></a>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 1459, Column 276: required attribute "alt" not specified
    …o Vivo"src='http://www.putariabrasileira.com/galerias/telefone-disk.jpg'/ ></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 1459, Column 276: end tag for "img" omitted, but OMITTAG NO was specified
    …o Vivo"src='http://www.putariabrasileira.com/galerias/telefone-disk.jpg'/ ></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 1459, Column 185: start tag was here
    …', 'Zoo', 'putariabrasileira-L1']);" ><img title="Sexo ao Vivo"src='http://www…
  • Error Line 1461, Column 286: required attribute "alt" not specified
    …do AGORA!" src="http://www.originalafiliados.com/banners/da-300x250.gif" ></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 1461, Column 290: end tag for "img" omitted, but OMITTAG NO was specified
    …do AGORA!" src="http://www.originalafiliados.com/banners/da-300x250.gif" ></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 1461, Column 174: start tag was here
    …ou', 'Download', 'Slider Rodape']);" ><img title="Descubra se está sendo traíd…
  • Error Line 1464, Column 326: required attribute "alt" not specified
    …ot.com/-DymSetWlglY/T1t45bZ7mqI/AAAAAAAAAHc/iYnhQ5xRVtI/s320/496777.jpg' /></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 1466, Column 301: NET-enabling start-tag not immediately followed by null end-tag
    …nte Hoje!!"src='http://www.originalafiliados.com/banners/bp-300x250.jpg'/ ></a>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 1466, Column 301: required attribute "alt" not specified
    …nte Hoje!!"src='http://www.originalafiliados.com/banners/bp-300x250.jpg'/ ></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 1466, Column 301: end tag for "img" omitted, but OMITTAG NO was specified
    …nte Hoje!!"src='http://www.originalafiliados.com/banners/bp-300x250.jpg'/ ></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 1466, Column 172: start tag was here
    …', 'Zoo', 'putariabrasileira-L1']);" ><img title="Aumente Seu Pénis Agora, Ent…
  • Error Line 1471, Column 264: required attribute "alt" not specified
    …www.originalafiliados.com/banners/vr-300x250.jpg" width="300" height="250"></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 1471, Column 268: end tag for "img" omitted, but OMITTAG NO was specified
    …www.originalafiliados.com/banners/vr-300x250.jpg" width="300" height="250"></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 1471, Column 173: start tag was here
    …', 'Zoo', 'putariabrasileira-L1']);" ><img src="http://www.originalafiliados.c…
  • Error Line 1474, Column 322: required attribute "alt" not specified
    …com/-iV-NnV-ea2c/T1ttq8-uD0I/AAAAAAAAAFM/aw3zAMr2nAk/s320/splovelat.png' /></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 1482, Column 260: NET-enabling start-tag not immediately followed by null end-tag
    …onecas de Luxo"src='http://protectorlink.info/capas/putaria_300x250.jpg'/ ></a>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 1482, Column 260: required attribute "alt" not specified
    …onecas de Luxo"src='http://protectorlink.info/capas/putaria_300x250.jpg'/ ></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 1482, Column 260: end tag for "img" omitted, but OMITTAG NO was specified
    …onecas de Luxo"src='http://protectorlink.info/capas/putaria_300x250.jpg'/ ></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 1482, Column 174: start tag was here
    …', 'Zoo', 'putariabrasileira-L1']);" ><img title="Bonecas de Luxo"src='http://…
  • Error Line 1486, Column 278: NET-enabling start-tag not immediately followed by null end-tag
    …s Mulheres"src='http://www.originalafiliados.com/banners/pm-300x250.jpg'/ ></a>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 1486, Column 278: required attribute "alt" not specified
    …s Mulheres"src='http://www.originalafiliados.com/banners/pm-300x250.jpg'/ ></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 1486, Column 278: end tag for "img" omitted, but OMITTAG NO was specified
    …s Mulheres"src='http://www.originalafiliados.com/banners/pm-300x250.jpg'/ ></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 1486, Column 180: start tag was here
    …', 'Zoo', 'putariabrasileira-L1']);" ><img title="Conquiste Mais Mulheres"src=…
  • Error Line 1513, Column 9: character "%" is not allowed in the value of attribute "id"
    <li id="%1$s" class="widget %2$s">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1534, Column 9: character "%" is not allowed in the value of attribute "id"
    <li id="%1$s" class="widget %2$s">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1534, Column 9: ID "%1$s" already defined
    <li id="%1$s" class="widget %2$s">

    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 1513, Column 9: ID "%1$s" first defined here
    <li id="%1$s" class="widget %2$s">
  • Error Line 1555, Column 9: character "%" is not allowed in the value of attribute "id"
    <li id="%1$s" class="widget %2$s">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1555, Column 9: ID "%1$s" already defined
    <li id="%1$s" class="widget %2$s">

    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 1513, Column 9: ID "%1$s" first defined here
    <li id="%1$s" class="widget %2$s">
  • Error Line 1586, Column 9: character "%" is not allowed in the value of attribute "id"
    <li id="%1$s" class="widget %2$s">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1586, Column 9: ID "%1$s" already defined
    <li id="%1$s" class="widget %2$s">

    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 1513, Column 9: ID "%1$s" first defined here
    <li id="%1$s" class="widget %2$s">
  • Error Line 1711, Column 336: duplicate specification of attribute "rel"
    …tag" title="Filmes Porno" target="_blank" rel="nofollow" >Filmes Porno</a></li>

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

  • Error Line 1757, Column 275: NET-enabling start-tag not immediately followed by null end-tag
    … title="Sexo Virtual"src='http://protectorlink.info/capas/camera300.gif'/ ></a>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 1757, Column 275: required attribute "alt" not specified
    … title="Sexo Virtual"src='http://protectorlink.info/capas/camera300.gif'/ ></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 1757, Column 275: end tag for "img" omitted, but OMITTAG NO was specified
    … title="Sexo Virtual"src='http://protectorlink.info/capas/camera300.gif'/ ></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 1757, Column 198: start tag was here
    …eralove', 'putariabrasileira-L1']);" ><img title="Sexo Virtual"src='http://pro…
  • Error Line 1763, Column 131: required attribute "alt" not specified
    …www.putariabrasileira.com/wp-content/uploads/botao.png"></a></center>    </div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1763, Column 135: end tag for "img" omitted, but OMITTAG NO was specified
    …www.putariabrasileira.com/wp-content/uploads/botao.png"></a></center>    </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 1763, Column 59: start tag was here
    …p://www.putariabrasileira.com/email/"><img src="http://www.putariabrasileira.c…
  • Warning Line 1793, Column 67: cannot generate system identifier for general entity "name"
    …mcam.com.br/publicidade/ad.aspx?c=126&name=yesporno&m=du" type="text/javascrip…

    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 1793, Column 67: general entity "name" not defined and no default entity
    …mcam.com.br/publicidade/ad.aspx?c=126&name=yesporno&m=du" type="text/javascrip…

    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 1793, Column 71: reference not terminated by REFC delimiter
    ….com.br/publicidade/ad.aspx?c=126&name=yesporno&m=du" type="text/javascript" l…

    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 1793, Column 71: reference to external entity in attribute value
    ….com.br/publicidade/ad.aspx?c=126&name=yesporno&m=du" type="text/javascript" l…

    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 1793, Column 71: reference to entity "name" for which no system identifier could be generated
    ….com.br/publicidade/ad.aspx?c=126&name=yesporno&m=du" type="text/javascript" l…

    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 1793, Column 66: entity was defined here
    …amcam.com.br/publicidade/ad.aspx?c=126&name=yesporno&m=du" type="text/javascri…
  • Warning Line 1793, Column 81: cannot generate system identifier for general entity "m"
    …blicidade/ad.aspx?c=126&name=yesporno&m=du" type="text/javascript" language="j…

    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 1793, Column 81: general entity "m" not defined and no default entity
    …blicidade/ad.aspx?c=126&name=yesporno&m=du" type="text/javascript" language="j…

    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 1793, Column 82: reference not terminated by REFC delimiter
    …licidade/ad.aspx?c=126&name=yesporno&m=du" type="text/javascript" language="ja…

    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 1793, Column 82: reference to external entity in attribute value
    …licidade/ad.aspx?c=126&name=yesporno&m=du" type="text/javascript" language="ja…

    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 1793, Column 82: reference to entity "m" for which no system identifier could be generated
    …licidade/ad.aspx?c=126&name=yesporno&m=du" type="text/javascript" language="ja…

    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 1793, Column 80: entity was defined here
    …ublicidade/ad.aspx?c=126&name=yesporno&m=du" type="text/javascript" language="…
  • Error Line 1795, Column 30: required attribute "type" not specified
    <script language="javascript">

    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 1808, Column 10: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <noscript><a href="http://www.histats.com" target="_blank"><img  src="http://ss…

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

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

  • Warning Line 1808, Column 111: character "&" is the first character of a delimiter but occurred as data
    …tp://sstatic1.histats.com/0.gif?837729&101" alt="web counter" border="0"></a><…

    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 1808, Column 149: end tag for "img" omitted, but OMITTAG NO was specified
    …tic1.histats.com/0.gif?837729&101" alt="web counter" border="0"></a></noscript>

    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 1808, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/0…
  • Error Line 1846, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 1850, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=200067443413588";

    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 1850, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=200067443413588";

    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 1850, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=200067443413588";

    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.

  • Error Line 1850, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=200067443413588";

    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 1850, Column 56: entity was defined here
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=200067443413588";
  • Warning Line 1867, Column 100: cannot generate system identifier for general entity "campanha"
    …//ads01.originalafiliados.com/campanhas.php?afiliado=4938&campanha=1"></script>

    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 1867, Column 100: general entity "campanha" not defined and no default entity
    …//ads01.originalafiliados.com/campanhas.php?afiliado=4938&campanha=1"></script>

    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 1867, Column 108: reference not terminated by REFC delimiter
    …//ads01.originalafiliados.com/campanhas.php?afiliado=4938&campanha=1"></script>

    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 1867, Column 108: reference to external entity in attribute value
    …//ads01.originalafiliados.com/campanhas.php?afiliado=4938&campanha=1"></script>

    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 1867, Column 108: reference to entity "campanha" for which no system identifier could be generated
    …//ads01.originalafiliados.com/campanhas.php?afiliado=4938&campanha=1"></script>

    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 1867, Column 99: entity was defined here
    …//ads01.originalafiliados.com/campanhas.php?afiliado=4938&campanha=1"></script>
  • Error Line 1869, Column 30: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div id="original_campanha_1"></div>

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

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

  • Error Line 1871, Column 7: end tag for "a" omitted, but OMITTAG NO was specified
    </body>

    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 1804, Column 1: start tag was here
    <a href="http://www.histats.com" target="_blank" title="web counter"><script ty…

Visitor Analysis

Daily Visitor
  • 17.267 visits
Daily Visitor

In Page Analysis