anidragon.net

Inicio Foro Fansub Reproduce MP4 / MKV Reproduce Hi10P Proyectos Donaciones Buscar Chat / IRC Afíliate Contáctanos NO AL ACTA Enviado por GilBoy Jue, 18/07/2013 - 3:29pm Senki Zesshou Symphogear G - 03 ...

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

Overview Info

  • Domain Name
    anidragon.net
  • Favicon
  • Alexa Rank
    #739978
  • Google Page Rank
    PR 2
  • Ip Address
    66.7.219.130
  • Page Size
    60.3 KB
  • Images
    15 GIF, 3 JPG, 8 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 17 1 0 0 0

Website Meta Analysis



  • Title
    AniDragon
  • Meta Keyword
  • Meta Description
    Inicio Foro Fansub Reproduce MP4 / MKV Reproduce Hi10P Proyectos Donaciones Buscar Chat / IRC Afíliate Contáctanos NO AL ACTA Enviado por GilBoy Jue, 18/07/2013 - 3:29pm Senki Zesshou Symphogear G - 03 Senki Zesshou Symphogear G - 03 DESCARGA ...

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    66.7.219.130
  • Domain Age
    6 Years, 7 Months, 12 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 19 Jul 2013 12:01:40 GMT
  • server: Apache
  • x-powered-by: PHP/5.3.22
  • expires: Sun, 19 Nov 1978 05:00:00 GMT
  • last-modified: Fri, 19 Jul 2013 12:01:40 GMT
  • cache-control: store, no-cache, must-revalidate
  • connection: close
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for anidragon.net

IP 66.7.219.130 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Orlando
  • Continent Code
    32801
  • Latitude
    407
  • Longitude
    534
  • %rwhois V-1.5:0000a0:00 rwhois.dimenoc.com (by HostDime.com, Inc. v0.1)
    network:id:DIMENOC-217041
    network:ip-network:66.7.219.130/31
    network:network-name:DIMENOC-217041
    network:org-name:Guillermo Mercado Lozano
    network:street-address:440 West Kennedy Blvd Suite #1
    network:city:Orlando
    network:state:FL
    network:postal-code:32810
    network:country-code:US
    network:tech-contact:abuse@dimenoc.com
    network:updated:2013-03-07 18:23:04
    network:updated-by:network@dimenoc.com

    %ok

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 136 Errors
  • 8 Warnings
Ratio Text/Html
  • 0.6011660863227792
Message Error
  • Error Line 106, Column 16: there is no attribute "color"
    <p><font color="red"><b>Les pedimos que nos ayuden descargado diario un video d…

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

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

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

  • Error Line 106, Column 21: element "font" undefined
    <p><font color="red"><b>Les pedimos que nos ayuden descargado diario un video d…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 108, Column 17: element "center" undefined
    <p><br /><center><a href="http://www.anidragon.net/node/4539"><img src="http://…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 108, Column 125: there is no attribute "border"
    …rc="http://www.anidragondd.net/img/news/mas.png" border="0" /></a></center></p>

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

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

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

  • Error Line 108, Column 130: required attribute "alt" not specified
    …rc="http://www.anidragondd.net/img/news/mas.png" border="0" /></a></center></p>

    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 128, Column 16: element "center" undefined
    					<p><center><b>Vividred Operation - 09</b><br /><iframe frameborder="0" scr…

    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 128, Column 73: there is no attribute "frameborder"
    …ion - 09</b><br /><iframe frameborder="0" scrolling="no" src="http://www.anidr…

    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 128, Column 87: there is no attribute "scrolling"
    …r /><iframe frameborder="0" scrolling="no" src="http://www.anidragondd.net/vid…

    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 128, Column 96: there is no attribute "src"
    …me frameborder="0" scrolling="no" src="http://www.anidragondd.net/video/0313vi…

    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 128, Column 177: there is no attribute "width"
    …ideo.php?vid=[AD]VividredOP_09" width="550" height="309"></iframe><br /><b>DES…

    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 128, Column 190: there is no attribute "height"
    …[AD]VividredOP_09" width="550" height="309"></iframe><br /><b>DESCARGA (RAW SD…

    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 128, Column 195: element "iframe" undefined
    …ividredOP_09" width="550" height="309"></iframe><br /><b>DESCARGA (RAW SD): <a…

    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 128, Column 304: there is no attribute "target"
    …les/3284230175/AD_VvOp_09.zip" target="_blank">Rapidshare</a> | <a href="http:…

    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 147, Column 16: element "center" undefined
    					<p><center><b>Sasami-san@Ganbaranai - 09</b><br /><iframe frameborder="0" …

    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 147, Column 198: element "iframe" undefined
    …asami-san_09" width="550" height="309"></iframe><br /><b>DESCARGA (RAW SD): <a…

    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 166, Column 16: element "center" undefined
    					<p><center><b>Robotics;Notes - 20</b><br /><iframe frameborder="0" scrolli…

    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 166, Column 194: element "iframe" undefined
    …ticsNotes_20" width="550" height="309"></iframe><br /><b>DESCARGA (RAW SD): <a…

    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 185, Column 16: element "center" undefined
    					<p><center><b>PSYCHO-PASS - 20</b><br /><iframe frameborder="0" scrolling=…

    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 185, Column 188: element "iframe" undefined
    …sychoPass_20" width="550" height="309"></iframe><br /><b>DESCARGA (RAW SD): <a…

    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 204, Column 16: element "center" undefined
    					<p><center><b>Puchimas! Petit iDOLM@STER - 49</b><br /><iframe frameborder…

    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 204, Column 201: element "iframe" undefined
    …]Puchimas_49" width="550" height="309"></iframe><br /><b>DESCARGA (RAW SD): <a…

    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 223, Column 16: element "center" undefined
    					<p><center><b><s>Star Wars Episode VII</s> Gintama 262 (ESP)</b><br /><ifr…

    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 223, Column 22: element "s" undefined
    					<p><center><b><s>Star Wars Episode VII</s> Gintama 262 (ESP)</b><br /><ifr…

    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 223, Column 216: element "iframe" undefined
    …]Gintama_262" width="550" height="309"></iframe><br /><b>DESCARGA (RAW SD + SU…

    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 242, Column 16: element "center" undefined
    					<p><center><b>Pokemon Best Wishes! Season 2 - 32</b><br /><iframe framebor…

    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 242, Column 201: element "iframe" undefined
    …[AD]PBWS2_32" width="550" height="309"></iframe><br /><b>DESCARGA (RAW SD): <a…

    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 261, Column 16: element "center" undefined
    					<p><center><b>GJ-bu - 09</b><br /><iframe frameborder="0" scrolling="no" s…

    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 261, Column 174: element "iframe" undefined
    …id=[AD]GJ_09" width="550" height="309"></iframe><br /><b>DESCARGA (RAW SD): <a…

    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 280, Column 16: element "center" undefined
    					<p><center><b>Mangirl! - 10</b><br /><iframe frameborder="0" scrolling="no…

    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 280, Column 182: element "iframe" undefined
    …D]Mangirl_10" width="550" height="309"></iframe><br /><b>DESCARGA (RAW SD): <a…

    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 313, Column 41: there is no attribute "language"
    <script type='text/javascript' 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 327, Column 37: element "center" undefined
    	    <div class="content"><p><center><iframe frameborder="0" scrolling="no" src…

    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 327, Column 153: element "iframe" undefined
    …ragondd.net/script/gif/img.php" width="140" height="130"></iframe></center></p>

    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 350, Column 7: required attribute "type" not specified
    <style>

    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 350, Column 7: document type does not allow element "style" here
    <style>

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

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

  • Error Line 616, Column 88: "if" is not a reserved name
    …enui0" href="#series"><span>Transmitiéndose</span><![if gt IE 6]></a><![endif]>
  • Error Line 616, Column 107: "endif" is not a reserved name
    …enui0" href="#series"><span>Transmitiéndose</span><![if gt IE 6]></a><![endif]>
  • Error Line 655, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 655, Column 1: start tag was here
    <br>
  • Error Line 656, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 656, Column 1: start tag was here
    <br>
  • Error Line 657, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 657, Column 1: start tag was here
    <br>
  • Error Line 661, Column 87: "if" is not a reserved name
    …Menui0" href="#temporadas"><span>Temporadas</span><![if gt IE 6]></a><![endif]>
  • Error Line 661, Column 106: "endif" is not a reserved name
    …Menui0" href="#temporadas"><span>Temporadas</span><![if gt IE 6]></a><![endif]>
  • Error Line 677, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 677, Column 1: start tag was here
    <br>
  • Error Line 678, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 678, Column 1: start tag was here
    <br>
  • Error Line 679, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 679, Column 1: start tag was here
    <br>
  • Error Line 681, Column 109: there is no attribute "onChange"
    …font-size:11px; width:144px" onChange='document.location.href=this.options[thi…

    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 802, Column 51: character "&" is the first character of a delimiter but occurred as data
    …n value='/anime/Panty_%2526_Stocking'>Panty & Stocking with Garterbelt</option>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 866, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 866, Column 1: start tag was here
    <br>
  • Error Line 871, Column 34: element "center" undefined
    	    <div class="content"><center><form action="https://www.paypal.com/cgi-bin/…

    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 871, Column 109: there is no attribute "target"
    …/cgi-bin/webscr" method="post" target="_Blank"><input type="hidden" name="cmd"…

    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 871, Column 167: 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
    …="hidden" name="cmd" value="_s-xclick"><input type="hidden" name="hosted_butto…

    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 871, Column 168: end tag for "input" omitted, but OMITTAG NO was specified
    …"hidden" name="cmd" value="_s-xclick"><input type="hidden" name="hosted_button…

    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 871, Column 118: start tag was here
    …webscr" method="post" target="_Blank"><input type="hidden" name="cmd" value="_…
  • Error Line 871, Column 234: 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
    …osted_button_id" value="2SX73LR393X54"><input type="image" src="http://anidrag…

    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 871, Column 235: end tag for "input" omitted, but OMITTAG NO was specified
    …sted_button_id" value="2SX73LR393X54"><input type="image" src="http://anidrago…

    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 871, Column 168: start tag was here
    …"hidden" name="cmd" value="_s-xclick"><input type="hidden" name="hosted_button…
  • Error Line 871, Column 316: there is no attribute "border"
    ….net/script/donate/donate.gif" border="0" name="submit" alt="PayPal"><img alt=…

    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 871, Column 346: 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
    … border="0" name="submit" alt="PayPal"><img alt="" border="0" src="https://www…

    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 871, Column 347: end tag for "input" omitted, but OMITTAG NO was specified
    …border="0" name="submit" alt="PayPal"><img alt="" border="0" src="https://www.…

    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 871, Column 235: start tag was here
    …sted_button_id" value="2SX73LR393X54"><input type="image" src="http://anidrago…
  • Error Line 871, Column 448: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    ….paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1"></form></center>

    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 871, Column 455: end tag for "img" omitted, but OMITTAG NO was specified
    ….paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1"></form></center>

    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 871, Column 347: start tag was here
    …border="0" name="submit" alt="PayPal"><img alt="" border="0" src="https://www.…
  • Error Line 872, Column 8: element "center" undefined
    <center>Tus donaciones servirán para pagar el servidor</center></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 876, Column 39: there is no attribute "align"
    	    <div class="content"> <div align="center"> 

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

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

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

  • Error Line 880, Column 19: there is no attribute "Behavior"
    <Marquee Behavior="Scroll" scrollAmount="2" onMouseOver="this.stop()" onMouseOu…

    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 880, Column 41: there is no attribute "scrollAmount"
    …arquee Behavior="Scroll" scrollAmount="2" onMouseOver="this.stop()" onMouseOut…

    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 880, Column 57: there is no attribute "onMouseOver"
    …"Scroll" scrollAmount="2" onMouseOver="this.stop()" onMouseOut="this.start()">…

    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 880, Column 82: there is no attribute "onMouseOut"
    … onMouseOver="this.stop()" onMouseOut="this.start()"><br /> <a href="http://ya…

    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 880, Column 96: element "Marquee" undefined
    …this.stop()" onMouseOut="this.start()"><br /> <a href="http://yaminofansub.wor…

    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 880, Column 542: document type does not allow element "a" here; missing one of "object", "ins", "del", "span", "bdo", "tt", "i", "b", "big", "small", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label" start-tag
    …="http://digisoul.net" target="_blank"><img src="http://digisoul.net/images/ba…

    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 880, Column 610: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …/images/banners/digisoul8.jpg" border=0 width=88 height=31></a> <a href="http:…
  • Error Line 880, Column 618: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …banners/digisoul8.jpg" border=0 width=88 height=31></a> <a href="http://digizo…
  • Error Line 880, Column 628: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …gisoul8.jpg" border=0 width=88 height=31></a> <a href="http://digizone.foroarg…
  • Error Line 880, Column 630: required attribute "alt" not specified
    …soul8.jpg" border=0 width=88 height=31></a> <a href="http://digizone.foroargen…

    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 880, Column 634: end tag for "img" omitted, but OMITTAG NO was specified
    …8.jpg" border=0 width=88 height=31></a> <a href="http://digizone.foroargentina…

    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 880, Column 543: start tag was here
    …"http://digisoul.net" target="_blank"><img src="http://digisoul.net/images/ban…
  • Error Line 880, Column 696: document type does not allow element "a" here; missing one of "object", "ins", "del", "span", "bdo", "tt", "i", "b", "big", "small", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label" start-tag
    …ne.foroargentina.net/" target="_blank"><img alt="DigiZone" src="http://i238.ph…

    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 880, Column 858: document type does not allow element "a" here; missing one of "object", "ins", "del", "span", "bdo", "tt", "i", "b", "big", "small", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label" start-tag
    …pkfenix.servermh.com/" target="_blank"><img src="http://i290.photobucket.com/a…

    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 880, Column 1203: end tag for element "MARQUEE" which is not open
    …/botonam.jpg" border="0" title="Algo Mas" alt="Algo Mas" /></a></MARQUEE></div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 880, Column 1209: end tag for "Marquee" omitted, but OMITTAG NO was specified
    …/botonam.jpg" border="0" title="Algo Mas" alt="Algo Mas" /></a></MARQUEE></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 880, Column 1: start tag was here
    <Marquee Behavior="Scroll" scrollAmount="2" onMouseOver="this.stop()" onMouseOu…
  • Error Line 882, Column 10: there is no attribute "align"
    <p align="center"> <a href="http://www.anidragon.net/afiliate"><strong>AFILIATE…

    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 882, Column 97: end tag for "br" omitted, but OMITTAG NO was specified
    …ate"><strong>AFILIATE</strong></a><br> <a href="http://www.anidragon.net" targ…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 882, Column 93: start tag was here
    …filiate"><strong>AFILIATE</strong></a><br> <a href="http://www.anidragon.net" …
  • Error Line 882, Column 264: end tag for "img" omitted, but OMITTAG NO was specified
    …img/anidragon/anidragon.gif" width="88" height="31" alt="AniDragon"></a> </p>  

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 882, Column 149: start tag was here
    …://www.anidragon.net" target="_blank"><img border="0" src="http://anidragondd.…
  • Error Line 887, Column 43: end tag for "br" omitted, but OMITTAG NO was specified
    	    <div class="content">Noticias RSS<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 887, Column 39: start tag was here
    	    <div class="content">Noticias RSS<br>
  • Error Line 889, Column 12: end tag for "br" omitted, but OMITTAG NO was specified
    Twitter<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 889, Column 8: start tag was here
    Twitter<br>
  • Error Line 890, Column 163: end tag for "img" omitted, but OMITTAG NO was specified
    …net/anidragon/siguenos_img/twitter.png" border="0" alt="Twitter AniDragon"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 890, Column 56: start tag was here
    …witter.com/AniDragon" target="_blank"><img src="http://anidragondd.net/anidrag…
  • Error Line 891, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 891, Column 1: start tag was here
    <br>
  • Error Line 892, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    Facebook<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 892, Column 9: start tag was here
    Facebook<br>
  • Error Line 893, Column 172: end tag for "img" omitted, but OMITTAG NO was specified
    …t/anidragon/siguenos_img/facebook.png" border="0" alt="Facebook AniDragon"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 893, Column 63: start tag was here
    …book.com/AniDragon02" target="_blank"><img src="http://anidragondd.net/anidrag…
  • Error Line 894, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 894, Column 1: start tag was here
    <br>
  • Error Line 895, Column 12: end tag for "br" omitted, but OMITTAG NO was specified
    iGoogle<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 895, Column 8: start tag was here
    iGoogle<br>
  • Warning Line 896, Column 51: cannot generate system identifier for general entity "feedurl"
    …p://fusion.google.com/add?source=atgs&feedurl=http%3A//www.anidragon.net/rss.x…

    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 896, Column 51: general entity "feedurl" not defined and no default entity
    …p://fusion.google.com/add?source=atgs&feedurl=http%3A//www.anidragon.net/rss.x…

    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 896, Column 58: reference not terminated by REFC delimiter
    …ion.google.com/add?source=atgs&feedurl=http%3A//www.anidragon.net/rss.xml" tar…

    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 896, Column 58: reference to external entity in attribute value
    …ion.google.com/add?source=atgs&feedurl=http%3A//www.anidragon.net/rss.xml" tar…

    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 896, Column 58: reference to entity "feedurl" for which no system identifier could be generated
    …ion.google.com/add?source=atgs&feedurl=http%3A//www.anidragon.net/rss.xml" tar…

    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 896, Column 50: entity was defined here
    …tp://fusion.google.com/add?source=atgs&feedurl=http%3A//www.anidragon.net/rss.…
  • Error Line 896, Column 204: end tag for "img" omitted, but OMITTAG NO was specified
    …ules.com/ig/images/plus_google.gif" border="0" alt="Añadir a Google"></a></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 896, Column 111: start tag was here
    …nidragon.net/rss.xml" target="_blank"><img src="http://gmodules.com/ig/images/…
  • Error Line 913, Column 35: element "center" undefined
          <div class="content"><center><a href="http://www.ademails.com/estadistica…

    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 920, Column 19: document type does not allow element "noscript" here; missing one of "object", "ins", "del", "map", "button" start-tag
    </script><noscript><img src=http://www.ademails.com/cgi-bin/contador.cgi?ID=105…

    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 920, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    </script><noscript><img src=http://www.ademails.com/cgi-bin/contador.cgi?ID=105…
  • Error Line 920, Column 35: NET-enabling start-tag not immediately followed by null end-tag
    </script><noscript><img src=http://www.ademails.com/cgi-bin/contador.cgi?ID=105…

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

  • Error Line 920, Column 35: required attribute "alt" not specified
    </script><noscript><img src=http://www.ademails.com/cgi-bin/contador.cgi?ID=105…

    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 920, Column 35: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    </script><noscript><img src=http://www.ademails.com/cgi-bin/contador.cgi?ID=105…

    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 920, Column 35: end tag for "img" omitted, but OMITTAG NO was specified
    </script><noscript><img src=http://www.ademails.com/cgi-bin/contador.cgi?ID=105…

    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 920, Column 20: start tag was here
    </script><noscript><img src=http://www.ademails.com/cgi-bin/contador.cgi?ID=105…
  • Error Line 920, Column 35: character data is not allowed here
    </script><noscript><img src=http://www.ademails.com/cgi-bin/contador.cgi?ID=105…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 921, Column 27: there is no attribute "allowscriptaccess"
    <object allowscriptaccess="always" type="application/x-shockwave-flash" data="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.

  • Warning Line 921, Column 134: cannot generate system identifier for general entity "ln"
    …container.info/mp4player.swf?id=46548&ln=es" width="1" height="1" wmode="trans…

    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 921, Column 134: general entity "ln" not defined and no default entity
    …container.info/mp4player.swf?id=46548&ln=es" width="1" height="1" wmode="trans…

    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 921, Column 136: reference not terminated by REFC delimiter
    …ntainer.info/mp4player.swf?id=46548&ln=es" width="1" height="1" wmode="transpa…

    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 921, Column 136: reference to external entity in attribute value
    …ntainer.info/mp4player.swf?id=46548&ln=es" width="1" height="1" wmode="transpa…

    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 921, Column 136: reference to entity "ln" for which no system identifier could be generated
    …ntainer.info/mp4player.swf?id=46548&ln=es" width="1" height="1" wmode="transpa…

    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 921, Column 133: entity was defined here
    …-container.info/mp4player.swf?id=46548&ln=es" width="1" height="1" wmode="tran…
  • Error Line 921, Column 168: there is no attribute "wmode"
    …548&ln=es" width="1" height="1" wmode="transparent"><param name="allowscriptac…

    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 921, Column 315: reference not terminated by REFC delimiter
    …ntainer.info/mp4player.swf?id=46548&ln=es" /><param name="wmode" value="transp…

    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 921, Column 315: reference to external entity in attribute value
    …ntainer.info/mp4player.swf?id=46548&ln=es" /><param name="wmode" value="transp…

    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 921, Column 315: reference to entity "ln" for which no system identifier could be generated
    …ntainer.info/mp4player.swf?id=46548&ln=es" /><param name="wmode" value="transp…

    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 921, Column 133: entity was defined here
    …-container.info/mp4player.swf?id=46548&ln=es" width="1" height="1" wmode="tran…
  • Error Line 921, Column 375: there is no attribute "src"
    …ode" value="transparent" /><embed src="http://xml.flash-container.info/mp4play…

    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 921, Column 433: reference not terminated by REFC delimiter
    …ntainer.info/mp4player.swf?id=46548&ln=es" type="application/x-shockwave-flash…

    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 921, Column 433: reference to external entity in attribute value
    …ntainer.info/mp4player.swf?id=46548&ln=es" type="application/x-shockwave-flash…

    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 921, Column 433: reference to entity "ln" for which no system identifier could be generated
    …ntainer.info/mp4player.swf?id=46548&ln=es" type="application/x-shockwave-flash…

    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 921, Column 133: entity was defined here
    …-container.info/mp4player.swf?id=46548&ln=es" width="1" height="1" wmode="tran…
  • Error Line 921, Column 443: there is no attribute "type"
    …fo/mp4player.swf?id=46548&ln=es" type="application/x-shockwave-flash" allowscr…

    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 921, Column 493: there is no attribute "allowscriptaccess"
    …/x-shockwave-flash" allowscriptaccess="always" wmode="transparent" width="1" 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 921, Column 508: there is no attribute "wmode"
    …ash" allowscriptaccess="always" wmode="transparent" width="1" height="1" /><vi…

    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 921, Column 528: there is no attribute "width"
    …ss="always" wmode="transparent" width="1" height="1" /><video width="1" height…

    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 921, Column 539: there is no attribute "height"
    … wmode="transparent" width="1" height="1" /><video width="1" height="1"></vide…

    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 921, Column 544: element "embed" undefined
    …e="transparent" width="1" height="1" /><video width="1" height="1"></video></o…

    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 921, Column 558: there is no attribute "width"
    …ansparent" width="1" height="1" /><video width="1" height="1"></video></object>

    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 921, Column 569: there is no attribute "height"
    …ansparent" width="1" height="1" /><video width="1" height="1"></video></object>

    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 921, Column 572: element "video" undefined
    …ansparent" width="1" height="1" /><video width="1" height="1"></video></object>

    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 936, Column 127: end tag for "br" omitted, but OMITTAG NO was specified
    …gos, compañías, etc. son propiedad de sus respectivos dueños y autores.<br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 936, Column 123: start tag was here
    …gos, compañías, etc. son propiedad de sus respectivos dueños y autores.<br><br>
  • Error Line 936, Column 131: end tag for "br" omitted, but OMITTAG NO was specified
    …gos, compañías, etc. son propiedad de sus respectivos dueños y autores.<br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 936, Column 127: start tag was here
    …gos, compañías, etc. son propiedad de sus respectivos dueños y autores.<br><br>
  • Error Line 937, Column 152: required attribute "alt" not specified
    …k"><img src="http://anidragondd.net/anidragon/img/cc2.png"></a> versión 3.4<br>

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

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

  • Error Line 937, Column 156: end tag for "img" omitted, but OMITTAG NO was specified
    …k"><img src="http://anidragondd.net/anidragon/img/cc2.png"></a> versión 3.4<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 937, Column 97: start tag was here
    …nc-sa/3.0/deed.es_MX" target="_Blank"><img src="http://anidragondd.net/anidrag…
  • Error Line 937, Column 173: end tag for "br" omitted, but OMITTAG NO was specified
    …k"><img src="http://anidragondd.net/anidragon/img/cc2.png"></a> versión 3.4<br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 937, Column 169: start tag was here
    …k"><img src="http://anidragondd.net/anidragon/img/cc2.png"></a> versión 3.4<br>
  • Error Line 939, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 939, Column 1: start tag was here
    <br> 
  • Error Line 943, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 40, Column 1: start tag was here
    <div id="pagewidthHead">

Visitor Analysis

Daily Visitor
  • 68 visits

In Page Analysis