Estás en la mejor página de anime online de la red, no olvides recomendarnos! ...

todoanimes.com
  • Domain Name
    todoanimes.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #27407
  • Page Size
    135.4 KB
  • Ip Address
    108.162.196.211
  • Heading
    H1: 1, H2: 2, H3: 12, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 40 JPG, 1 PNG

Website Meta Analysis

  • Title
    Ver Anime Online Gratis @ TODOANIMES
  • Meta Keyword
    ver, anime, online, gratis
  • Meta Description
    Estás en la mejor página de anime online de la red, no olvides recomendarnos!

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.196.211
  • Domain Age
    4 Years, 5 Months, 24 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: cloudflare-nginx
  • date: Sat, 02 Feb 2013 05:32:30 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.3.19
  • cf-ray: 3a4fe6ed684018e
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: TODOANIMES.COM
Created on: 01-Sep-08
Expires on: 01-Sep-13
Last Updated on: 27-Jul-12

Registrant:
Luis Huapaya Farfan
Asent. H. Bella Aurora MzF Lt6
Lima, Lima 22
Peru

Administrative Contact:
Huapaya Farfan, Luis email
Asent. H. Bella Aurora MzF Lt6
Lima, Lima 22
Peru
+51.14224092 Fax -- +51.14224092

Technical Contact:
Huapaya Farfan, Luis email
Asent. H. Bella Aurora MzF Lt6
Lima, Lima 22
Peru
+51.14224092 Fax -- +51.14224092

Domain servers in listed order:
DAVE.NS.CLOUDFLARE.COM
UMA.NS.CLOUDFLARE.COM

DNS Analysis


DNS servers
dave.ns.cloudflare.com [173.245.59.109]
uma.ns.cloudflare.com [173.245.58.146]


DNS Records

Answer records
todoanimes.com NS  uma.ns.cloudflare.com 86400s
todoanimes.com A 108.162.196.211 300s
todoanimes.com 28 [16 bytes] 300s
todoanimes.com MX
preference: 0
exchange: dc-403b754b.todoanimes.com
300s
todoanimes.com A 108.162.197.211 300s
todoanimes.com NS  dave.ns.cloudflare.com 86400s
todoanimes.com 28 [16 bytes] 300s
todoanimes.com SOA
server: dave.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2013012804
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s

Authority records

Additional records
dc-403b754b.todoanimes.com A 72.55.168.138 300s

IP 108.162.196.211 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.196.211"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=108.162.196.211?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

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

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

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

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

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

    RTechHandle: ADMIN2521-ARIN
    RTechName: Admin
    RTechPhone: +1-650-319-8930
    RTechEmail: admin@cloudflare.com
    RTechRef: http://whois.arin.net/rest/poc/ADMIN2521-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
  • 76 Errors
  • 8 Warnings
Ratio Text/Html
  • 0.7330255374404848
Message Error
  • Error Line 19, Column 16: there is no attribute "property"
    <meta property="og:title" content="Anime Online @ TodoAnimes"/>

    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 25, Column 18: document type does not allow element "div" here; assuming missing "object" start-tag
    <div id="fb-root"></div>
  • Error Line 26, 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 30, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/es_LA/all.js#xfbml=1&appId=188737447912424";

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

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

    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 30, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/es_LA/all.js#xfbml=1&appId=188737447912424";

    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 30, Column 56: entity was defined here
      js.src = "//connect.facebook.net/es_LA/all.js#xfbml=1&appId=188737447912424";
  • Error Line 33, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

    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 25, Column 1: start tag was here
    <div id="fb-root"></div>
  • Error Line 44, Column 96: required attribute "alt" not specified
    …odoanimes.com/"><img src="http://img.todoanimes.com/logo.png" border="0" /></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 47, Column 18: there is no attribute "language"
    <SCRIPT language="Javascript">

    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 47, Column 30: element "SCRIPT" undefined
    <SCRIPT language="Javascript">

    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 50, Column 23: an attribute specification must start with a name or name token
    document.writeln("<SCR"+"IPT language='Javascript' src='http://server.cpmstar.c…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 50, Column 23: element "SCR" undefined
    document.writeln("<SCR"+"IPT language='Javascript' src='http://server.cpmstar.c…

    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).
  • Warning Line 50, Column 116: cannot generate system identifier for general entity "script"
    ….com/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IP…

    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 50, Column 116: general entity "script" not defined and no default entity
    ….com/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IP…

    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 50, Column 122: reference not terminated by REFC delimiter
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

    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 50, Column 122: reference to entity "script" for which no system identifier could be generated
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

    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 50, Column 115: entity was defined here
    …r.com/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"I…
  • Warning Line 50, Column 125: cannot generate system identifier for general entity "rnd"
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

    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 50, Column 125: general entity "rnd" not defined and no default entity
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

    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 50, Column 128: reference not terminated by REFC delimiter
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

    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 50, Column 128: reference to entity "rnd" for which no system identifier could be generated
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

    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 50, Column 124: entity was defined here
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");
  • Error Line 50, Column 151: delimiter """ invalid: only S separators and TAGC allowed here
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");
  • Error Line 146, Column 108: required attribute "alt" not specified
    …es.com/roboticsnotes.jpg"  width="60" height="90" class="thumb" align="left" />

    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 153, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 152, Column 51: start tag was here
    <span><a href="roboticsnotes/15/">Ver Episodio</a><span>
  • Error Line 153, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 152, Column 1: start tag was here
    <span><a href="roboticsnotes/15/">Ver Episodio</a><span>
  • Error Line 156, Column 111: required attribute "alt" not specified
    …com/maoyu-mao-yuusha.jpg"  width="60" height="90" class="thumb" align="left" />

    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 163, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 162, Column 53: start tag was here
    <span><a href="maoyu-mao-yuusha/5/">Ver Episodio</a><span>
  • Error Line 163, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 162, Column 1: start tag was here
    <span><a href="maoyu-mao-yuusha/5/">Ver Episodio</a><span>
  • Error Line 166, Column 91: required attribute "alt" not specified
    …tp://img.todoanimes.com/"  width="60" height="90" class="thumb" align="left" />

    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 173, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 172, Column 76: start tag was here
    …pan><a href="pokemon-best-wishes-kyurem-vs-seikenshi/1/">Ver Episodio</a><span>
  • Error Line 173, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 172, Column 1: start tag was here
    <span><a href="pokemon-best-wishes-kyurem-vs-seikenshi/1/">Ver Episodio</a><spa…
  • Error Line 176, Column 113: required attribute "alt" not specified
    …m/vividred-operation.jpg"  width="60" height="90" class="thumb" align="left" />

    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 183, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 182, Column 55: start tag was here
    <span><a href="vividred-operation/4/">Ver Episodio</a><span>
  • Error Line 183, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 182, Column 1: start tag was here
    <span><a href="vividred-operation/4/">Ver Episodio</a><span>
  • Error Line 186, Column 110: required attribute "alt" not specified
    ….com/ginga-e-kickoff.jpg"  width="60" height="90" class="thumb" align="left" />

    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 193, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 192, Column 53: start tag was here
    <span><a href="ginga-e-kickoff/34/">Ver Episodio</a><span>
  • Error Line 193, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 192, Column 1: start tag was here
    <span><a href="ginga-e-kickoff/34/">Ver Episodio</a><span>
  • Error Line 196, Column 91: required attribute "alt" not specified
    …tp://img.todoanimes.com/"  width="60" height="90" class="thumb" align="left" />

    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 203, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 202, Column 60: start tag was here
    <span><a href="kuroko-no-basket-ng-shu/2/">Ver Episodio</a><span>
  • Error Line 203, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 202, Column 1: start tag was here
    <span><a href="kuroko-no-basket-ng-shu/2/">Ver Episodio</a><span>
  • Error Line 206, Column 113: required attribute "alt" not specified
    …m/zetsuen-no-tempest.jpg"  width="60" height="90" class="thumb" align="left" />

    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 213, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 212, Column 56: start tag was here
    <span><a href="zetsuen-no-tempest/16/">Ver Episodio</a><span>
  • Error Line 213, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 212, Column 1: start tag was here
    <span><a href="zetsuen-no-tempest/16/">Ver Episodio</a><span>
  • Error Line 216, Column 128: required attribute "alt" not specified
    …achi-ga-sukunai-next.jpg"  width="60" height="90" class="thumb" align="left" />

    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 223, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 222, Column 70: start tag was here
    <span><a href="boku-wa-tomodachi-ga-sukunai-next/4/">Ver Episodio</a><span>
  • Error Line 223, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 222, Column 1: start tag was here
    <span><a href="boku-wa-tomodachi-ga-sukunai-next/4/">Ver Episodio</a><span>
  • Error Line 226, Column 100: required attribute "alt" not specified
    …todoanimes.com/gj-bu.jpg"  width="60" height="90" class="thumb" align="left" />

    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 233, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 232, Column 42: start tag was here
    <span><a href="gj-bu/4/">Ver Episodio</a><span>
  • Error Line 233, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 232, Column 1: start tag was here
    <span><a href="gj-bu/4/">Ver Episodio</a><span>
  • Error Line 236, Column 106: required attribute "alt" not specified
    …imes.com/kotoura-san.jpg"  width="60" height="90" class="thumb" align="left" />

    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 243, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 242, Column 48: start tag was here
    <span><a href="kotoura-san/4/">Ver Episodio</a><span>
  • Error Line 243, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 242, Column 1: start tag was here
    <span><a href="kotoura-san/4/">Ver Episodio</a><span>
  • Error Line 246, Column 116: required attribute "alt" not specified
    …okemon-best-wishes-2.jpg"  width="60" height="90" class="thumb" align="left" />

    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 253, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 252, Column 59: start tag was here
    <span><a href="pokemon-best-wishes-2/26/">Ver Episodio</a><span>
  • Error Line 253, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 252, Column 1: start tag was here
    <span><a href="pokemon-best-wishes-2/26/">Ver Episodio</a><span>
  • Error Line 256, Column 104: required attribute "alt" not specified
    …animes.com/ai-mai-mi.jpg"  width="60" height="90" class="thumb" align="left" />

    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 263, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 262, Column 46: start tag was here
    <span><a href="ai-mai-mi/5/">Ver Episodio</a><span>
  • Error Line 263, Column 6: end tag for "span" omitted, but OMITTAG NO was specified
    </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 262, Column 1: start tag was here
    <span><a href="ai-mai-mi/5/">Ver Episodio</a><span>
  • Error Line 280, Column 41: there is no attribute "FRAMEBORDER"
    …iv align="center"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…

    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 280, Column 41: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …iv align="center"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 280, Column 55: there is no attribute "MARGINWIDTH"
    …er"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …

    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 280, Column 55: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …er"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …
  • Error Line 280, Column 70: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…

    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 280, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 280, Column 82: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 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 280, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://www.…
  • Error Line 280, Column 91: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://www.todoanime…

    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 280, Column 91: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://www.todoanime…
  • Error Line 280, Column 102: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://www.todoanimes.com/ads/c…

    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 280, Column 102: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://www.todoanimes.com/ads/c…
  • Error Line 280, Column 110: there is no attribute "SRC"
    …SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://www.todoanimes.com/ads/cpmstar.h…

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

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

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

  • Error Line 280, Column 154: element "IFRAME" undefined
    …300 HEIGHT=250 SRC="http://www.todoanimes.com/ads/cpmstar.html"></IFRAME></div>

    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 283, Column 41: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …iv align="center"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 283, Column 55: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …er"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …
  • Error Line 283, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 283, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://www.…
  • Error Line 283, Column 91: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://www.todoanime…
  • Error Line 283, Column 102: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://www.todoanimes.com/ads/c…
  • Error Line 283, Column 154: element "IFRAME" undefined
    …300 HEIGHT=250 SRC="http://www.todoanimes.com/ads/cpmstar.html"></IFRAME></div>

    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 1415, 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.

  • Warning Line 1447, Column 125: reference not terminated by REFC delimiter
    …aspx?poolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3c/scri…

    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 1447, Column 125: reference to entity "script" for which no system identifier could be generated
    …aspx?poolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3c/scri…

    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 50, Column 115: entity was defined here
    …r.com/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"I…
  • Warning Line 1447, Column 131: reference not terminated by REFC delimiter
    …oolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3c/script\x3e…

    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 1447, Column 131: reference to entity "rnd" for which no system identifier could be generated
    …oolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3c/script\x3e…

    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 50, Column 124: entity was defined here
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

Visitor Analysis

Daily Visitor
  • 7.000 visits
Daily Visitor