Ver anime online.Aqui Puedes ver Naruto Shippuden Online,One Piece Online,Bleach Online entra y disfruta de NARUTO SHIPPUDEN 302 sub español,NARUTO SHIPPUDEN 302 , NARUTO SHIPPUDEN 302 online,descargar NARUTO SHIPPUDEN 302, naruto shippuden ...

buenanime.com
  • Domain Name
    buenanime.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #45668
  • Page Size
    43 KB
  • Ip Address
    184.154.209.106
  • Heading
    H1: 1, H2: 26, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 13 JPG, 2 PNG

Website Meta Analysis

  • Title
    NARUTO SHIPPUDEN 302 SUB ESPAÑOL , NARUTO MANGA 622
  • Meta Keyword
    anime,animes,anime online,ver anime online,naruto,naruto shippuden,ver naruto shippuden,NARUTO SHIPPUDEN 302 sub español, NARUTO SHIPPUDEN 302 , NARUTO SHIPPUDEN 302 online,descargar NARUTO SHIPPUDEN 302 , naruto shippuden manga 622 ,naruto manga 622
  • Meta Description
    Ver anime online.Aqui Puedes ver Naruto Shippuden Online,One Piece Online,Bleach Online entra y disfruta de NARUTO SHIPPUDEN 302 sub español,NARUTO SHIPPUDEN 302 , NARUTO SHIPPUDEN 302 online,descargar NARUTO SHIPPUDEN 302, naruto shippuden manga 622 ,naruto manga 622

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    184.154.209.106
  • Domain Age
    3 Years, 3 Months, 14 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 01 Mar 2013 17:59:49 GMT
  • server: Apache
  • x-powered-by: PHP/5.2.17
  • vary: Accept-Encoding,Cookie
  • cache-control: max-age=3, must-revalidate
  • wp-super-cache: Served supercache file from PHP
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for buenanime.com

DNS Analysis


DNS servers
ns1.dattabit.org [184.154.209.107]
ns2.dattabit.org [184.154.209.108]


DNS Records

Answer records
buenanime.com MX
preference: 0
exchange: buenanime.com
14400s
buenanime.com SOA
server: ns1.dattabit.org
email: banahost@live.com
serial: 2011090902
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
buenanime.com NS  ns2.dattabit.org 86400s
buenanime.com NS  ns1.dattabit.org 86400s
buenanime.com A 184.154.209.106 14400s

Authority records

Additional records
buenanime.com A 184.154.209.106 14400s
ns1.dattabit.org A 184.154.209.107 14400s
ns2.dattabit.org A 184.154.209.108 14400s

IP 184.154.209.106 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Chicago
  • Continent Code
    312
  • Latitude
    602
  • Longitude
    602
  • No whois ip data for 184.154.209.106

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 98 Errors
  • 24 Warnings
Ratio Text/Html
  • 0.7418227215980024
Message Error
  • Error Line 13, Column 15: there is no attribute "content"
    <META content='ebd5cba53f95c05b' name='y_key'/>

    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 13, Column 39: there is no attribute "name"
    <META content='ebd5cba53f95c05b' name='y_key'/>

    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 13, Column 47: element "META" undefined
    <META content='ebd5cba53f95c05b' name='y_key'/>

    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 62, Column 42: there is no attribute "property"
    <meta content='100001154880661' property='fb:admins'/> 

    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 75, Column 170: required attribute "alt" not specified
    …/AAAAAAAACmQ/sSTHyNPfrhM/s1600/buenanime.png" width="350px" height="33px"/></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 81, Column 56: value of attribute "method" cannot be "GET"; must be one of "get", "post"
    <form action="http://www.google.com/search" method="GET">

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

  • Error Line 83, Column 46: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input value="UTF-8" name="ie" type="hidden"/>

    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 85, Column 46: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input value="UTF-8" name="oe" type="hidden"/>

    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 87, Column 84: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …lue="" name="q" size="30" type="text"/> <input value="Buscar" name="btnG" id="…

    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 87, Column 150: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …type="text"/> <input value="Buscar" name="btnG" id="search-btn" type="submit"/>

    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 89, Column 12: there is no attribute "size"
    <font size="-1">

    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 89, Column 16: element "font" undefined
    <font size="-1">

    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 93, Column 63: ID "search-box" already defined
    …h-box" type="hidden"/><br/><input id="search-box" type="hidden" checked value=…

    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 20: ID "search-box" first defined here
    name="domains" id="search-box" type="hidden"/><br/><input id="search-box" type=…
  • Error Line 93, Column 97: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …id="search-box" type="hidden" checked value="http://www.buenanime.com/" name="…

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 133, Column 76: document type does not allow element "ul" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …//www.buenanime.com/category/anime"><ul><li >VER ANTERIORES</li></ul></a></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 143, Column 77: document type does not allow element "ul" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …/www.buenanime.com/category/series"><ul><li >VER ANTERIORES</li></ul></a></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 153, Column 75: document type does not allow element "ul" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …://www.buenanime.com/category/2012"><ul><li >VER ANTERIORES</li></ul></a></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 164, Column 83: document type does not allow element "ul" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …uenanime.com/category/manga-online"><ul><li >VER ANTERIORES</li></ul></a></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 172, Column 11: there is no attribute "align"
    <h1 align="center">NARUTO SHIPPUDEN 302 SUB ESPAÑOL , NARUTO MANGA 622</h1>

    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 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 187, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 191, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 192, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 196, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 197, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 201, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 202, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 206, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 207, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 211, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 212, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 216, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 217, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 221, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 222, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 226, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 227, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 231, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 232, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 236, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 237, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 241, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 242, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 246, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 247, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 251, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 252, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 256, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 257, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 261, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 262, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 266, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 267, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 271, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 272, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 276, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 277, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 281, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 282, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 286, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 287, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 291, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 292, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 296, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 297, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 301, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 302, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 306, Column 40: "padding-left:30px" is not a member of a group specified for any attribute
    …h2 class="postTitle" padding-left:30px;><a href="http://www.buenanime.com/2013…
  • Error Line 307, Column 38: "padding-left:30px" is not a member of a group specified for any attribute
    <p class="postMeta" padding-left:30px;>Publicado en <a href="http://www.buenani…
  • Error Line 333, Column 26: there is no attribute "border"
    <img alt='Cerrar' border='0' onclick='closebar(); return false' src='http://i.i…

    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 339, Column 14: there is no attribute "TYPE"
    <SCRIPT TYPE="text/javascript" SRC="http://ad.xtendmedia.com/st?ad_type=ad&ad_s…

    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 339, Column 36: there is no attribute "SRC"
    <SCRIPT TYPE="text/javascript" SRC="http://ad.xtendmedia.com/st?ad_type=ad&ad_s…

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

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

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

  • Warning Line 339, Column 76: cannot generate system identifier for general entity "ad_size"
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=$…

    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 339, Column 76: general entity "ad_size" not defined and no default entity
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=$…

    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 339, Column 83: reference not terminated by REFC delimiter
    …d.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=${www.bu…

    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 339, Column 83: reference to external entity in attribute value
    …d.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=${www.bu…

    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 339, Column 83: reference to entity "ad_size" for which no system identifier could be generated
    …d.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=${www.bu…

    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 339, Column 75: entity was defined here
    …http://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=…
  • Warning Line 339, Column 91: cannot generate system identifier for general entity "section"
    …edia.com/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.…

    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 339, Column 91: general entity "section" not defined and no default entity
    …edia.com/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.…

    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 339, Column 98: reference not terminated by REFC delimiter
    …m/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.com}"><…

    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 339, Column 98: reference to external entity in attribute value
    …m/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.com}"><…

    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 339, Column 98: reference to entity "section" for which no system identifier could be generated
    …m/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.com}"><…

    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 339, Column 90: entity was defined here
    …media.com/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime…
  • Warning Line 339, Column 107: cannot generate system identifier for general entity "pub_url"
    …_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.com}"></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 339, Column 107: general entity "pub_url" not defined and no default entity
    …_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.com}"></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 339, Column 114: reference not terminated by REFC delimiter
    …_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.com}"></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 339, Column 114: reference to external entity in attribute value
    …_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.com}"></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 339, Column 114: reference to entity "pub_url" for which no system identifier could be generated
    …_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.com}"></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 339, Column 106: entity was defined here
    …_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.com}"></SCRIPT>
  • Error Line 339, Column 136: element "SCRIPT" undefined
    …_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.com}"></SCRIPT>

    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 350, Column 84: reference not terminated by REFC delimiter
    ….xtendmedia.com/st?ad_type=pop&ad_size=0x0&section=2869636&banned_pop_types=29…

    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 350, Column 84: reference to external entity in attribute value
    ….xtendmedia.com/st?ad_type=pop&ad_size=0x0&section=2869636&banned_pop_types=29…

    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 350, Column 84: reference to entity "ad_size" for which no system identifier could be generated
    ….xtendmedia.com/st?ad_type=pop&ad_size=0x0&section=2869636&banned_pop_types=29…

    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 339, Column 75: entity was defined here
    …http://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=…
  • Warning Line 350, Column 96: reference not terminated by REFC delimiter
    …com/st?ad_type=pop&ad_size=0x0&section=2869636&banned_pop_types=29&pop_times=1…

    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 350, Column 96: reference to external entity in attribute value
    …com/st?ad_type=pop&ad_size=0x0&section=2869636&banned_pop_types=29&pop_times=1…

    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 350, Column 96: reference to entity "section" for which no system identifier could be generated
    …com/st?ad_type=pop&ad_size=0x0&section=2869636&banned_pop_types=29&pop_times=1…

    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 339, Column 90: entity was defined here
    …media.com/st?ad_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime…
  • Warning Line 350, Column 105: cannot generate system identifier for general entity "banned_pop_types"
    …_type=pop&ad_size=0x0&section=2869636&banned_pop_types=29&pop_times=1&pop_freq…

    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 350, Column 105: general entity "banned_pop_types" not defined and no default entity
    …_type=pop&ad_size=0x0&section=2869636&banned_pop_types=29&pop_times=1&pop_freq…

    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 350, Column 121: reference not terminated by REFC delimiter
    …e=0x0&section=2869636&banned_pop_types=29&pop_times=1&pop_frequency=21600&pub_…

    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 350, Column 121: reference to external entity in attribute value
    …e=0x0&section=2869636&banned_pop_types=29&pop_times=1&pop_frequency=21600&pub_…

    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 350, Column 121: reference to entity "banned_pop_types" for which no system identifier could be generated
    …e=0x0&section=2869636&banned_pop_types=29&pop_times=1&pop_frequency=21600&pub_…

    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 350, Column 104: entity was defined here
    …d_type=pop&ad_size=0x0&section=2869636&banned_pop_types=29&pop_times=1&pop_fre…
  • Warning Line 350, Column 125: cannot generate system identifier for general entity "pop_times"
    …0&section=2869636&banned_pop_types=29&pop_times=1&pop_frequency=21600&pub_url=…

    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 350, Column 125: general entity "pop_times" not defined and no default entity
    …0&section=2869636&banned_pop_types=29&pop_times=1&pop_frequency=21600&pub_url=…

    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 350, Column 134: reference not terminated by REFC delimiter
    …=2869636&banned_pop_types=29&pop_times=1&pop_frequency=21600&pub_url=${www.bue…

    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 350, Column 134: reference to external entity in attribute value
    …=2869636&banned_pop_types=29&pop_times=1&pop_frequency=21600&pub_url=${www.bue…

    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 350, Column 134: reference to entity "pop_times" for which no system identifier could be generated
    …=2869636&banned_pop_types=29&pop_times=1&pop_frequency=21600&pub_url=${www.bue…

    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 350, Column 124: entity was defined here
    …x0&section=2869636&banned_pop_types=29&pop_times=1&pop_frequency=21600&pub_url…
  • Warning Line 350, Column 137: cannot generate system identifier for general entity "pop_frequency"
    …69636&banned_pop_types=29&pop_times=1&pop_frequency=21600&pub_url=${www.buenan…

    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 350, Column 137: general entity "pop_frequency" not defined and no default entity
    …69636&banned_pop_types=29&pop_times=1&pop_frequency=21600&pub_url=${www.buenan…

    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 350, Column 150: reference not terminated by REFC delimiter
    …pop_types=29&pop_times=1&pop_frequency=21600&pub_url=${www.buenanime.com}"></S…

    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 350, Column 150: reference to external entity in attribute value
    …pop_types=29&pop_times=1&pop_frequency=21600&pub_url=${www.buenanime.com}"></S…

    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 350, Column 150: reference to entity "pop_frequency" for which no system identifier could be generated
    …pop_types=29&pop_times=1&pop_frequency=21600&pub_url=${www.buenanime.com}"></S…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 350, Column 136: entity was defined here
    …869636&banned_pop_types=29&pop_times=1&pop_frequency=21600&pub_url=${www.buena…
  • Warning Line 350, Column 164: reference not terminated by REFC delimiter
    …ypes=29&pop_times=1&pop_frequency=21600&pub_url=${www.buenanime.com}"></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 350, Column 164: reference to external entity in attribute value
    …ypes=29&pop_times=1&pop_frequency=21600&pub_url=${www.buenanime.com}"></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 350, Column 164: reference to entity "pub_url" for which no system identifier could be generated
    …ypes=29&pop_times=1&pop_frequency=21600&pub_url=${www.buenanime.com}"></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 339, Column 106: entity was defined here
    …_type=ad&ad_size=728x90&section=3031262&pub_url=${www.buenanime.com}"></SCRIPT>
  • Error Line 350, Column 186: element "SCRIPT" undefined
    …ypes=29&pop_times=1&pop_frequency=21600&pub_url=${www.buenanime.com}"></SCRIPT>

    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 357, Column 7: document type does not allow element "table" here; assuming missing "li" start-tag
    <table>
  • Error Line 425, Column 5: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
     <li>

    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 427, Column 7: document type does not allow element "table" here; assuming missing "li" start-tag
    <table>
  • Error Line 447, Column 6: end tag for "li" omitted, but OMITTAG NO was specified
     </ul>

    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 427, Column 1: start tag was here
    <table>
  • Error Line 455, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    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 357, Column 1: start tag was here
    <table>
  • Error Line 466, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li>

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

    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 463, Column 1: start tag was here
    <li>
  • Error Line 495, Column 255: end tag for element "h1" which is not open
    …SUB ESPAÑOL , NARUTO MANGA 622</a></h1> --  Powered by <a href="http://www.wor…

    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 499, Column 175: there is no attribute "target"
    …ef="http://www.buenmanga.com/" target="_blank">NARUTO SHIPPUDEN MANGA</a> | <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.

Visitor Analysis

Daily Visitor
  • 3.733 visits
Daily Visitor