Montagem de Fotos, e geradores diversos, para Orkut, Hi5, MySpace, etc. Molduras para Fotos, Criador de Glitters animados... ...

scrapee.net
  • Domain Name
    scrapee.net
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #36793
  • Page Size
    35 KB
  • Ip Address
    108.162.199.77
  • Heading
    H1: 0, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    3 GIF, 7 JPG, 33 PNG

Website Meta Analysis

  • Title
    Montagem de Fotos para Orkut, Hi5, Facebook, e outras redes sociais.
  • Meta Keyword
    montagem de fotos, molduras, glitters, criador, efeitos, fotos, fotomontajes, fotomontagens, efeitos especiais, etc
  • Meta Description
    Montagem de Fotos, e geradores diversos, para Orkut, Hi5, MySpace, etc. Molduras para Fotos, Criador de Glitters animados...

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.199.77
  • Domain Age
    4 Years, 8 Months, 9 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from scrapee.net.

HTML Analysis

  • server: cloudflare-nginx
  • date: Wed, 22 May 2013 00:17:22 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.3.8
  • vary: Accept-Encoding
  • cf-ray: 72552b2958e043d
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for scrapee.net

DNS Analysis


DNS servers
alex.ns.cloudflare.com [173.245.59.100]
uma.ns.cloudflare.com [173.245.58.146]


DNS Records

Answer records
scrapee.net SOA
server: alex.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2013013015
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s
scrapee.net A 108.162.199.77 300s
scrapee.net TXT v=spf1 ip4:174.36.108.130 ip4:74.86.168.224 a mx ?all 300s
scrapee.net A 108.162.198.77 300s
scrapee.net NS  uma.ns.cloudflare.com 86400s
scrapee.net NS  alex.ns.cloudflare.com 86400s
scrapee.net MX
preference: 0
exchange: dc-6bbd42e9.scrapee.net
300s

Authority records

Additional records
dc-6bbd42e9.scrapee.net A 174.36.108.130 300s

IP 108.162.199.77 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 108.162.199.77"
    #
    # Use "?" to get help.
    #

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

    NetRange: 108.162.192.0 - 108.162.255.255
    CIDR: 108.162.192.0/18
    OriginAS: AS13335
    NetName: CLOUDFLARENET
    NetHandle: NET-108-162-192-0-1
    Parent: NET-108-0-0-0-0
    NetType: Direct Assignment
    Comment: http://www.cloudflare.com
    RegDate: 2011-10-28
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-108-162-192-0-1

    OrgName: CloudFlare, Inc.
    OrgId: CLOUD14
    Address: 665 Third Street #207
    City: San Francisco
    StateProv: CA
    PostalCode: 94107
    Country: US
    RegDate: 2010-07-09
    Updated: 2013-01-04
    Comment: http://www.cloudflare.com/
    Ref: http://whois.arin.net/rest/org/CLOUD14

    OrgNOCHandle: NOC11962-ARIN
    OrgNOCName: NOC
    OrgNOCPhone: +1-650-319-8930
    OrgNOCEmail:
    OrgNOCRef: http://whois.arin.net/rest/poc/NOC11962-ARIN

    OrgTechHandle: ADMIN2521-ARIN
    OrgTechName: Admin
    OrgTechPhone: +1-650-319-8930
    OrgTechEmail:
    OrgTechRef: http://whois.arin.net/rest/poc/ADMIN2521-ARIN

    OrgAbuseHandle: ABUSE2916-ARIN
    OrgAbuseName: Abuse
    OrgAbusePhone: +1-650-319-8930
    OrgAbuseEmail:
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE2916-ARIN

    RTechHandle: ADMIN2521-ARIN
    RTechName: Admin
    RTechPhone: +1-650-319-8930
    RTechEmail:
    RTechRef: http://whois.arin.net/rest/poc/ADMIN2521-ARIN

    RNOCHandle: NOC11962-ARIN
    RNOCName: NOC
    RNOCPhone: +1-650-319-8930
    RNOCEmail:
    RNOCRef: http://whois.arin.net/rest/poc/NOC11962-ARIN

    RAbuseHandle: ABUSE2916-ARIN
    RAbuseName: Abuse
    RAbusePhone: +1-650-319-8930
    RAbuseEmail:
    RAbuseRef: http://whois.arin.net/rest/poc/ABUSE2916-ARIN

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 64 Errors
  • 12 Warnings
Ratio Text/Html
  • 0.6279296875
Message Error
  • Error Line 1, Column 121: DTD did not contain element declaration for document type name
    ….0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

    A DOCTYPE declares the version of the language used, as well as what the root (top) element of your document will be. For example, if the top element of your document is <html>, the DOCTYPE declaration will look like: "<!DOCTYPE html".

    In most cases, it is safer not to type or edit the DOCTYPE declaration at all, and preferable to let a tool include it, or copy and paste it from a trusted list of DTDs.

  • Error Line 2, Column 99: document type does not allow element "html" here
    …www.w3.org/1999/xhtml" lang="pt" xml:lang="pt" xmlns:fb="http://ogp.me/ns/fb#">

    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 5, Column 16: there is no attribute "property"
    <meta property="fb:app_id" content="131880306936663" />

    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 9, Column 53: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Language" content="pt-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 9, Column 1: start tag was here
    <meta http-equiv="Content-Language" content="pt-br">
  • Error Line 10, Column 161: end tag for "meta" omitted, but OMITTAG NO was specified
    …rkut, Hi5, MySpace, etc. Molduras para Fotos, Criador de Glitters animados...">

    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 10, Column 1: start tag was here
    <meta name="description" content="Montagem de Fotos, e geradores diversos, para…
  • Warning Line 17, Column 34: cannot generate system identifier for general entity "ver"
    <script src="/scripts.js?lang=pt&ver=3" type="text/javascript"></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 17, Column 34: general entity "ver" not defined and no default entity
    <script src="/scripts.js?lang=pt&ver=3" type="text/javascript"></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 17, Column 37: reference not terminated by REFC delimiter
    <script src="/scripts.js?lang=pt&ver=3" type="text/javascript"></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 17, Column 37: reference to external entity in attribute value
    <script src="/scripts.js?lang=pt&ver=3" type="text/javascript"></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 17, Column 37: reference to entity "ver" for which no system identifier could be generated
    <script src="/scripts.js?lang=pt&ver=3" type="text/javascript"></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 17, Column 33: entity was defined here
    <script src="/scripts.js?lang=pt&ver=3" type="text/javascript"></script>
  • Error Line 25, 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 38, Column 4: "if" is not a reserved name
    <![if !lt IE 7]>
  • Error Line 39, 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 45, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=131880306936663";

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

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

    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 45, 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=131880306936663";

    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 45, Column 56: entity was defined here
      js.src = "//connect.facebook.net/pt_BR/all.js#xfbml=1&appId=131880306936663";
  • Error Line 68, Column 4: "endif" is not a reserved name
    <![endif]>
  • Error Line 85, Column 23: document type does not allow element "style" here
    <style type="text/css">

    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 97, Column 137: end tag for "img" omitted, but OMITTAG NO was specified
    …/www.scrapee.net/logos/logoscrapee2.png" alt="montagem de fotos e efeitos"></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 97, Column 43: start tag was here
    …  <a href="http://www.scrapee.net/pt"><img src="http://www.scrapee.net/logos/l…
  • Error Line 105, Column 383: there is no attribute "allowTransparency"
    …rflow:hidden; width:60px; height:63px;" allowTransparency="true"></iframe></td>

    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 106, Column 41: there is no attribute "size"
              <td width="2"><g:plusone size="tall"></g:plusone></td>

    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 106, Column 47: element "g:plusone" undefined
              <td width="2"><g:plusone size="tall"></g:plusone></td>

    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 108, Column 136: there is no attribute "data-count"
    …ass="twitter-share-button" data-count="vertical" data-via="scrapee_net" rel="m…

    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 108, Column 156: there is no attribute "data-via"
    …r-share-button" data-count="vertical" data-via="scrapee_net" rel="me">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 134, Column 99: document type does not allow element "form" here; missing one of "object", "applet", "map", "iframe", "ins", "del" start-tag
    …"http://www.scrapee.net/buscar.htm" id="cse-search-box" style="display:inline">

    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 149, Column 123: end tag for "span" omitted, but OMITTAG NO was specified
    …://www.google.com.br/cse/brand?form=cse-search-box&amp;lang=pt"></script></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 132, Column 23: start tag was here
      Recados  </a></span><span class="style3"> |
  • Error Line 168, Column 30: end tag for "br" omitted, but OMITTAG NO was specified
      Escrever em Fotos  </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 168, Column 26: start tag was here
      Escrever em Fotos  </a><br>
  • Error Line 169, Column 6: end tag for element "a" which is not open
      </a></span> </div>

    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 175, Column 201: required attribute "alt" not specified
    …arget="_blank"><img src="/adtelexfree.png" width="728" height="57" /></a></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 176, Column 6: "if" is not a reserved name
      <![if !lt IE 7]>
  • Error Line 180, Column 235: required attribute "alt" not specified
    …ight="164" onmouseover="espandebuscape();"  style="cursor:pointer;"/></a></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 181, Column 109: required attribute "alt" not specified
    …style="display:none"> <img src="/shopping.png" style="cursor:pointer;"/> </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 182, Column 110: there is no attribute "onmouseout"
    …ht="262" frameborder="0" scrolling="no"  onmouseout="closebuscape();"></iframe>

    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 186, Column 4: "endif" is not a reserved name
    <![endif]>
  • Error Line 187, Column 10: ID "listasites" already defined
    <div id="listasites"></div>

    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 93, Column 10: ID "listasites" first defined here
    <div id="listasites">
  • Error Line 188, Column 10: ID "listasites" already defined
    <div id="listasites">

    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 93, Column 10: ID "listasites" first defined here
    <div id="listasites">
  • Error Line 195, Column 10: ID "listasites" already defined
    <div id="listasites">

    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 93, Column 10: ID "listasites" first defined here
    <div id="listasites">
  • Error Line 203, Column 158: required attribute "alt" not specified
    …llow"><img title="ver todas as molduras" src="/images/vertodas.png"/></a></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 208, Column 10: ID "listasites" already defined
    <div id="listasites">

    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 93, Column 10: ID "listasites" first defined here
    <div id="listasites">
  • Error Line 211, Column 34: there is no attribute "name"
          <div id="HOTWordsTxt" name="HOTWordsTxt">

    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 218, Column 49: required attribute "alt" not specified
                        <img src="/icones/novo.gif"/>

    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 228, Column 14: end tag for element "a" which is not open
              </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 232, Column 44: required attribute "alt" not specified
              </a> <img src="/icones/novo.gif"/><br />

    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 291, Column 73: required attribute "alt" not specified
              Criador de Tirinhas          </a> <img src="/icones/novo.gif"/><br />

    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 343, Column 12: ID "listasites" already defined
      <div id="listasites">

    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 93, Column 10: ID "listasites" first defined here
    <div id="listasites">
  • Error Line 345, Column 16: ID "scriptIcons2" already defined
          <div id="scriptIcons2" style="padding-top:10px; padding-left:0px;">

    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 197, Column 14: ID "scriptIcons2" first defined here
        <div id="scriptIcons2" style="padding-top:0px; padding-left:0px;">
  • Error Line 356, Column 6: end tag for element "div" which is not open
    </div>

    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 357, Column 10: ID "listasites" already defined
    <div id="listasites">

    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 93, Column 10: ID "listasites" first defined here
    <div id="listasites">
  • Warning Line 359, Column 5: character "<" is the first character of a delimiter but occurred as data
        <!– google_ad_section_start –>

    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 370, Column 6: end tag for element "div" which is not open
    </div>

    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 371, Column 6: end tag for element "div" which is not open
    </div>

    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 390, Column 4: "if" is not a reserved name
    <![if !lt IE 7]>
  • Warning Line 396, Column 112: character "&" is the first character of a delimiter but occurred as data
    …ttp://sstatic1.histats.com/0.gif?1618832&101" alt="" border="0"></a></noscript>

    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 396, Column 139: end tag for "img" omitted, but OMITTAG NO was specified
    …ttp://sstatic1.histats.com/0.gif?1618832&101" alt="" 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 396, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/0…
  • Error Line 397, Column 4: "endif" is not a reserved name
    <![endif]>
  • Warning Line 420, Column 1: character "<" is the first character of a delimiter but occurred as data
    <!- Cache - 6666cd76f96956469e7be39d750cc7d9?d41d8cd98f00b204e9800998ecf8427e -…

    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 420, Column 1: character data is not allowed here
    <!- Cache - 6666cd76f96956469e7be39d750cc7d9?d41d8cd98f00b204e9800998ecf8427e -…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 420, Column 104: end tag for "html" omitted, but OMITTAG NO was specified
    …56469e7be39d750cc7d9?d41d8cd98f00b204e9800998ecf8427e - 11:29:55, 15-02-2013 ->

    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 2, Column 1: start tag was here
    <html xmlns="http://www.w3.org/1999/xhtml" lang="pt" xml:lang="pt" xmlns:fb="ht…
  • Error Line 420, Column 104: no document element
    …56469e7be39d750cc7d9?d41d8cd98f00b204e9800998ecf8427e - 11:29:55, 15-02-2013 ->

Visitor Analysis

Daily Visitor
  • 2.917 visits
Daily Visitor