ver peliculas online y descargar peliculas gratis ...

veocine.es
  • Domain Name
    veocine.es
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #21043
  • Page Size
    101.5 KB
  • Ip Address
    91.192.110.166
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 5, H5: 0, H6: 0
  • Images
    0 GIF, 90 JPG, 9 PNG

Website Meta Analysis

  • Title
    VeoCine.es - ver peliculas online, descargar peliculas, estrenos online
  • Meta Keyword
    peliculas, peliculas online, peliculas gratis, estrenos de cine, descargar peliculas
  • Meta Description
    ver peliculas online y descargar peliculas gratis

Technical Analysis

  • Webserver
    Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/0.9.8o PHP/5.2.17
  • Ip Address
    91.192.110.166
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from veocine.es.

HTML Analysis

  • date: Thu, 25 Jul 2013 08:04:22 GMT
  • server: Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/0.9.8o PHP/5.2.17
  • x-powered-by: PHP/5.2.17
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for veocine.es

DNS Analysis


DNS servers
dns2.hispalisdns.com [67.18.244.114]
dns3.hispalisdns.com [213.186.47.218]
dns1.hispalisdns.com [195.78.228.199]


DNS Records

Answer records
veocine.es SOA
server: dns1.hispalisdns.com
email: admin@furanet.com
serial: 2011052502
refresh: 3200
retry: 1600
expire: 604800
minimum ttl: 3600
3600s
veocine.es MX
preference: 10
exchange: mail.veocine.es
3600s
veocine.es NS  dns1.hispalisdns.com 3600s
veocine.es NS  dns2.hispalisdns.com 3600s
veocine.es NS  dns3.hispalisdns.com 3600s
veocine.es TXT v=spf1 a mx a:mail.veocine.es ip4:195.78.228.0/22 ip4:91.192.108.0/22 ?all 3600s
veocine.es A 91.192.110.166 3600s
veocine.es 28 [16 bytes] 3600s

Authority records

Additional records
mail.veocine.es A 91.192.110.166 3600s
dns1.hispalisdns.com A 195.78.228.199 3600s
dns2.hispalisdns.com A 67.18.244.114 3600s
dns3.hispalisdns.com A 213.186.47.218 3600s

IP 91.192.110.166 Analysis

  • Country Code
    ES
  • Country Code3
    ESP
  • Country Name
    Spain
  • City
    EU
  • Continent Code
    40° North
  • Latitude
    4.
  • Longitude
  • No whois ip data for 91.192.110.166

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 53 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.8135816729232842
Message Error
  • Error Line 5, Column 18: there is no attribute "HTTP-EQUIV"
    <META HTTP-EQUIV="Cache-Control" CONTENT ="no-cache">

    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 5, Column 43: there is no attribute "CONTENT"
    <META HTTP-EQUIV="Cache-Control" CONTENT ="no-cache">

    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 5, Column 53: element "META" undefined
    <META HTTP-EQUIV="Cache-Control" CONTENT ="no-cache">

    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 6, Column 12: there is no attribute "NAME"
    <META NAME="Keywords" CONTENT="peliculas,Peliculas Online, veocine, cine gratis…

    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 6, Column 173: element "META" undefined
    … gratis, peliculas online estrenos, ver peliculas online, pagina de peliculas">

    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 7, Column 133: element "META" undefined
    …veocine.es disfruta de estrenos y peliculas gratis, peliculas para ver gratis">

    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 8, Column 60: element "META" undefined
    <META NAME="Title" CONTENT="Peliculas Online en VeoCine.es">

    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 9, Column 63: element "META" undefined
    <META NAME="Subject" CONTENT="Peliculas Online en VeoCine.es ">

    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 13, Column 46: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="shortcut icon" href="favicon.ico">

    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 13, Column 1: start tag was here
    <link rel="shortcut icon" href="favicon.ico">
  • Error Line 16, Column 27: required attribute "type" not specified
    <script src="ajax/ajax.js"></script>

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

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

  • Error Line 17, Column 26: required attribute "type" not specified
    <script src="ajax/log.js"></script>

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

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

  • Error Line 19, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 9, Column 1: start tag was here
    <META NAME="Subject" CONTENT="Peliculas Online en VeoCine.es ">
  • Error Line 19, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 8, Column 1: start tag was here
    <META NAME="Title" CONTENT="Peliculas Online en VeoCine.es">
  • Error Line 19, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 7, Column 1: start tag was here
    <META NAME="Description" CONTENT="peliculas online en veocine.es disfruta de es…
  • Error Line 19, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 6, Column 1: start tag was here
    <META NAME="Keywords" CONTENT="peliculas,Peliculas Online, veocine, cine gratis…
  • Error Line 19, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 5, Column 1: start tag was here
    <META HTTP-EQUIV="Cache-Control" CONTENT ="no-cache">
  • Error Line 19, Column 7: end tag for "head" which is not finished
    </head>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 21, Column 51: there is no attribute "leftmargin"
    …r="#FFFFFF" text="#000000" leftmargin="0" topmargin="0" marginwidth="0" margin…

    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 21, Column 65: there is no attribute "topmargin"
    …" text="#000000" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">

    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 21, Column 81: there is no attribute "marginwidth"
    …" text="#000000" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">

    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 21, Column 98: there is no attribute "marginheight"
    …" text="#000000" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">

    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 23, Column 43: document type does not allow element "style" here
                        <style type="text/css">

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

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

  • Warning Line 48, Column 91: cannot generate system identifier for general entity "width"
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 48, Column 91: general entity "width" not defined and no default entity
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>

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

  • Warning Line 48, Column 96: reference not terminated by REFC delimiter
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 48, Column 96: reference to external entity in attribute value
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 48, Column 96: reference to entity "width" for which no system identifier could be generated
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>

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

  • Info Line 48, Column 90: entity was defined here
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>
  • Warning Line 48, Column 101: cannot generate system identifier for general entity "height"
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 48, Column 101: general entity "height" not defined and no default entity
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>

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

  • Warning Line 48, Column 107: reference not terminated by REFC delimiter
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 48, Column 107: reference to external entity in attribute value
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 48, Column 107: reference to entity "height" for which no system identifier could be generated
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>

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

  • Info Line 48, Column 100: entity was defined here
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>
  • Error Line 48, Column 111: required attribute "type" not specified
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>

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

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

  • Error Line 61, Column 89: document type does not allow element "form" here
    …              <form id="form1" name="form1" method="get" action="buscador.php">

    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 62, Column 30: document type does not allow element "tr" here; assuming missing "table" start-tag
                              <tr>
  • Error Line 66, Column 31: end tag for "table" omitted, but OMITTAG NO was specified
                            </form>

    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 62, Column 27: start tag was here
                              <tr>
  • Error Line 67, Column 28: end tag for "table" which is not finished
                        </table></td>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 72, Column 125: required attribute "alt" not specified
    …="top"><img src="veoestrenos/cabecera/raya.png" width="960" height="10" /></td>

    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 105, Column 130: end tag for "br" omitted, but OMITTAG NO was specified
    …0' border='0' alt='Coriolanus online' /><br>Coriolanus               </a> </td>

    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 105, Column 126: start tag was here
    …0' border='0' alt='Coriolanus online' /><br>Coriolanus               </a> </td>
  • Error Line 107, Column 124: end tag for "br" omitted, but OMITTAG NO was specified
    …ht='150' border='0' alt='Lincoln online' /><br>Lincoln               </a> </td>

    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 107, Column 120: start tag was here
    …ht='150' border='0' alt='Lincoln online' /><br>Lincoln               </a> </td>
  • Error Line 109, Column 154: end tag for "br" omitted, but OMITTAG NO was specified
    …' Django desencadenado  online' /><br> Django desencadenado                </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 109, Column 150: start tag was here
    …alt=' Django desencadenado  online' /><br> Django desencadenado               …
  • Error Line 111, Column 134: end tag for "br" omitted, but OMITTAG NO was specified
    …order='0' alt='Jack Reacher online' /><br>Jack Reacher               </a> </td>

    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 111, Column 130: start tag was here
    …order='0' alt='Jack Reacher online' /><br>Jack Reacher               </a> </td…
  • Error Line 113, Column 191: end tag for "br" omitted, but OMITTAG NO was specified
    …ura (Zero dark thirty)  online' /><br> La noche más oscura (Zero dark thirty) …

    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 113, Column 187: start tag was here
    … oscura (Zero dark thirty)  online' /><br> La noche más oscura (Zero dark thir…
  • Error Line 115, Column 160: end tag for "br" omitted, but OMITTAG NO was specified
    …l Hombre De Las Sombras online' /><br> El Hombre De Las Sombras               …

    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 115, Column 156: start tag was here
    …=' El Hombre De Las Sombras online' /><br> El Hombre De Las Sombras           …
  • Error Line 117, Column 136: end tag for "br" omitted, but OMITTAG NO was specified
    …der='0' alt='Lo Imposible  online' /><br>Lo Imposible                </a> </td>

    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 117, Column 132: start tag was here
    …rder='0' alt='Lo Imposible  online' /><br>Lo Imposible                </a> </t…
  • Error Line 119, Column 168: end tag for "br" omitted, but OMITTAG NO was specified
    …cinante mundo de Norman online' /><br>El alucinante mundo de Norman           …

    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 119, Column 164: start tag was here
    … alucinante mundo de Norman online' /><br>El alucinante mundo de Norman       …
  • Error Line 121, Column 137: end tag for "br" omitted, but OMITTAG NO was specified
    …der='0' alt='¡Rompe Ralph! online' /><br>¡Rompe Ralph!               </a> </td>

    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 121, Column 133: start tag was here
    …rder='0' alt='¡Rompe Ralph! online' /><br>¡Rompe Ralph!               </a> </t…
  • Error Line 132, Column 104: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"
    …dth="0" marginheight="0" scrolling="No" class="iframe300" src="http://www.veoc…

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

  • Warning Line 133, Column 126: reference not terminated by REFC delimiter
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 133, Column 126: reference to external entity in attribute value
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 133, Column 126: reference to entity "width" for which no system identifier could be generated
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

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

  • Info Line 48, Column 90: entity was defined here
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>
  • Warning Line 133, Column 137: reference not terminated by REFC delimiter
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 133, Column 137: reference to external entity in attribute value
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 133, Column 137: reference to entity "height" for which no system identifier could be generated
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

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

  • Info Line 48, Column 100: entity was defined here
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>
  • Error Line 133, Column 142: required attribute "type" not specified
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

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

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

  • Error Line 137, Column 58: document type does not allow element "h2" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …             <span class="titulo_video"> <h2>Peliculas Online</h2></span><br />

    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 139, Column 57: document type does not allow element "td" here; assuming missing "tr" start-tag
                                      <td class="celdalibre">
  • Error Line 202, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 202, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 213, Column 328: end tag for "br" omitted, but OMITTAG NO was specified
    …os dentro del arcade.<span class='lucida12'></span><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 213, Column 324: start tag was here
    …os dentro del arcade.<span class='lucida12'></span><br>                        
  • Error Line 224, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 224, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 235, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 235, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 246, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 246, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 249, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <tr><td colspan=2><table width="100%" border="0" cellspacing="0" cellpadding="0…
  • Error Line 249, Column 175: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"
    …dth='0' marginheight='0' scrolling='No' class='iframe300' src="http://www.veoc…

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

  • Error Line 258, Column 429: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 258, Column 425: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 269, Column 396: end tag for "br" omitted, but OMITTAG NO was specified
    …de una de las chicas.<span class='lucida12'></span><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 269, Column 392: start tag was here
    …de una de las chicas.<span class='lucida12'></span><br>                        
  • Error Line 280, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 280, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 291, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 291, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 302, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 302, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 315, Column 267: end tag for "br" omitted, but OMITTAG NO was specified
    …e;pata Rusty Nail... <span class='lucida12'></span><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 315, Column 263: start tag was here
    …e;pata Rusty Nail... <span class='lucida12'></span><br>                        
  • Error Line 327, Column 365: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 327, Column 361: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 330, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <tr><td colspan=2><table width="100%" border="0" cellspacing="0" cellpadding="0…
  • Error Line 330, Column 175: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"
    …dth='0' marginheight='0' scrolling='No' class='iframe300' src="http://www.veoc…

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

  • Error Line 338, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 338, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 349, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 349, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 360, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 360, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Warning Line 371, Column 378: cannot generate system identifier for general entity "aacut..."
    …ctantes como inesperadas: que tiene c&aacut... <font color='#777777'>Entra en …

    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 371, Column 378: general entity "aacut..." not defined and no default entity
    …ctantes como inesperadas: que tiene c&aacut... <font color='#777777'>Entra en …

    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 371, Column 386: reference not terminated by REFC delimiter
    …como inesperadas: que tiene c&aacut... <font color='#777777'>Entra en la peli …

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 371, Column 386: reference to entity "aacut..." for which no system identifier could be generated
    …como inesperadas: que tiene c&aacut... <font color='#777777'>Entra en la peli …

    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 371, Column 377: entity was defined here
    …actantes como inesperadas: que tiene c&aacut... <font color='#777777'>Entra en…
  • Error Line 371, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 371, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 382, Column 402: end tag for "br" omitted, but OMITTAG NO was specified
    …nciosa c&aacute;rcel.<span class='lucida12'></span><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 382, Column 398: start tag was here
    …nciosa c&aacute;rcel.<span class='lucida12'></span><br>                        
  • Error Line 393, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 393, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 396, Column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <tr><td colspan=2><table width="100%" border="0" cellspacing="0" cellpadding="0…
  • Error Line 396, Column 175: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"
    …dth='0' marginheight='0' scrolling='No' class='iframe300' src="http://www.veoc…

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

  • Error Line 404, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 404, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Warning Line 409, Column 193: character "&" is the first character of a delimiter but occurred as data
    ….jpg' width='100' height='143' border='0' alt='Beowulf & Grendel online' /></a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 413, Column 33: character "&" is the first character of a delimiter but occurred as data
                            Beowulf & Grendel                        </a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 417, Column 374: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 417, Column 370: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 428, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 428, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 439, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 439, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 450, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 450, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 463, Column 284: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 463, Column 280: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 474, Column 403: end tag for "br" omitted, but OMITTAG NO was specified
    …e una lecci&oacute;n.<span class='lucida12'></span><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 474, Column 399: start tag was here
    …e una lecci&oacute;n.<span class='lucida12'></span><br>                        
  • Error Line 485, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 485, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 496, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 496, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 507, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 507, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 518, Column 333: end tag for "br" omitted, but OMITTAG NO was specified
    …;sica de su escuela. <span class='lucida12'></span><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 518, Column 329: start tag was here
    …;sica de su escuela. <span class='lucida12'></span><br>                        
  • Error Line 529, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 529, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 540, Column 67: end tag for "br" omitted, but OMITTAG NO was specified
    …             <br />  <span class='lucida12'></span><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 540, Column 63: start tag was here
    …             <br />  <span class='lucida12'></span><br>                        
  • Error Line 551, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 551, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 562, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 562, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 573, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 573, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 584, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 584, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 595, Column 345: end tag for "br" omitted, but OMITTAG NO was specified
    …o estaba embarazada. <span class='lucida12'></span><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 595, Column 341: start tag was here
    …o estaba embarazada. <span class='lucida12'></span><br>                        
  • Error Line 606, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 606, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 617, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 617, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 628, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 628, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 641, Column 402: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 641, Column 398: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 652, Column 340: end tag for "br" omitted, but OMITTAG NO was specified
    … los j&oacute;venes. <span class='lucida12'></span><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 652, Column 336: start tag was here
    … los j&oacute;venes. <span class='lucida12'></span><br>                        
  • Error Line 663, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 663, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 674, Column 355: end tag for "br" omitted, but OMITTAG NO was specified
    …vertido y trepidante.<span class='lucida12'></span><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 674, Column 351: start tag was here
    …vertido y trepidante.<span class='lucida12'></span><br>                        
  • Error Line 685, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 685, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 696, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 696, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 707, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 707, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 718, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 718, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Error Line 729, Column 480: end tag for "br" omitted, but OMITTAG NO was specified
    … para ver mas!</font><span class='lucida12'></span><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 729, Column 476: start tag was here
    … para ver mas!</font><span class='lucida12'></span><br>                        
  • Warning Line 762, Column 119: reference not terminated by REFC delimiter
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 762, Column 119: reference to external entity in attribute value
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 762, Column 119: reference to entity "width" for which no system identifier could be generated
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

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

  • Info Line 48, Column 90: entity was defined here
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>
  • Warning Line 762, Column 130: reference not terminated by REFC delimiter
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 762, Column 130: reference to external entity in attribute value
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 762, Column 130: reference to entity "height" for which no system identifier could be generated
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

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

  • Info Line 48, Column 100: entity was defined here
    …h.net/src/js/min/adbooth_ajax.js?section=3221764&width=728&height=90"></script>
  • Error Line 762, Column 135: required attribute "type" not specified
    ….net/src/js/min/adbooth_ajax.js?section=3221765&width=300&height=250"></script>

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

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

  • Error Line 772, Column 53: document type does not allow element "style" here
                                  <style type="text/css">

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

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

  • Error Line 831, Column 11: element "B" undefined
            <B>A</B><br>        <b><a target="_blank" href="http://a-camara-super-l…

    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 831, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>A</B><br>        <b><a target="_blank" href="http://a-camara-super-l…

    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 831, Column 17: start tag was here
            <B>A</B><br>        <b><a target="_blank" href="http://a-camara-super-l…
  • Error Line 1039, Column 11: element "B" undefined
            <B>B</B><br>        <b><a target="_blank" href="http://baby-boom.series…

    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 1039, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>B</B><br>        <b><a target="_blank" href="http://baby-boom.series…

    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 1039, Column 17: start tag was here
            <B>B</B><br>        <b><a target="_blank" href="http://baby-boom.series…
  • Error Line 1245, Column 11: element "B" undefined
            <B>C</B><br>        <b><a target="_blank" href="http://caillou.seriespe…

    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 1245, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>C</B><br>        <b><a target="_blank" href="http://caillou.seriespe…

    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 1245, Column 17: start tag was here
            <B>C</B><br>        <b><a target="_blank" href="http://caillou.seriespe…
  • Error Line 1463, Column 11: element "B" undefined
            <B>D</B><br>        <b><a target="_blank" href="http://d-artacan-y-los-…

    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 1463, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>D</B><br>        <b><a target="_blank" href="http://d-artacan-y-los-…

    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 1463, Column 17: start tag was here
            <B>D</B><br>        <b><a target="_blank" href="http://d-artacan-y-los-…
  • Error Line 1617, Column 11: element "B" undefined
            <B>E</B><br>        <b><a target="_blank" href="http://eagleheart.serie…

    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 1617, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>E</B><br>        <b><a target="_blank" href="http://eagleheart.serie…

    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 1617, Column 17: start tag was here
            <B>E</B><br>        <b><a target="_blank" href="http://eagleheart.serie…
  • Error Line 1859, Column 11: element "B" undefined
            <B>F</B><br>        <b><a target="_blank" href="http://faemino-y-cansad…

    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 1859, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>F</B><br>        <b><a target="_blank" href="http://faemino-y-cansad…

    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 1859, Column 17: start tag was here
            <B>F</B><br>        <b><a target="_blank" href="http://faemino-y-cansad…
  • Error Line 1945, Column 11: element "B" undefined
            <B>G</B><br>        <b><a target="_blank" href="http://gabriel-amor-inm…

    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 1945, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>G</B><br>        <b><a target="_blank" href="http://gabriel-amor-inm…

    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 1945, Column 17: start tag was here
            <B>G</B><br>        <b><a target="_blank" href="http://gabriel-amor-inm…
  • Error Line 2029, Column 11: element "B" undefined
            <B>H</B><br>        <b><a target="_blank" href="http://h2o.seriespepito…

    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 2029, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>H</B><br>        <b><a target="_blank" href="http://h2o.seriespepito…

    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 2029, Column 17: start tag was here
            <B>H</B><br>        <b><a target="_blank" href="http://h2o.seriespepito…
  • Warning Line 2110, Column 15: character "&" is the first character of a delimiter but occurred as data
              Him & Her          </a></b><br />

    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 2167, Column 11: element "B" undefined
            <B>I</B><br>        <b><a target="_blank" href="http://i-get-that-a-lot…

    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 2167, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>I</B><br>        <b><a target="_blank" href="http://i-get-that-a-lot…

    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 2167, Column 17: start tag was here
            <B>I</B><br>        <b><a target="_blank" href="http://i-get-that-a-lot…
  • Error Line 2219, Column 11: element "B" undefined
            <B>J</B><br>        <b><a target="_blank" href="http://jack-and-bobby.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 2219, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>J</B><br>        <b><a target="_blank" href="http://jack-and-bobby.s…

    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 2219, Column 17: start tag was here
            <B>J</B><br>        <b><a target="_blank" href="http://jack-and-bobby.s…
  • Warning Line 2226, Column 16: character "&" is the first character of a delimiter but occurred as data
              Jake & Blake          </a></b><br />

    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 2261, Column 11: element "B" undefined
            <B>K</B><br>        <b><a target="_blank" href="http://kacho-oji.series…

    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 2261, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>K</B><br>        <b><a target="_blank" href="http://kacho-oji.series…

    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 2261, Column 17: start tag was here
            <B>K</B><br>        <b><a target="_blank" href="http://kacho-oji.series…
  • Error Line 2305, Column 11: element "B" undefined
            <B>L</B><br>        <b><a target="_blank" href="http://la-alqueria-blan…

    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 2305, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>L</B><br>        <b><a target="_blank" href="http://la-alqueria-blan…

    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 2305, Column 17: start tag was here
            <B>L</B><br>        <b><a target="_blank" href="http://la-alqueria-blan…
  • Error Line 2615, Column 11: element "B" undefined
            <B>M</B><br>        <b><a target="_blank" href="http://macgyver.seriesp…

    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 2615, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>M</B><br>        <b><a target="_blank" href="http://macgyver.seriesp…

    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 2615, Column 17: start tag was here
            <B>M</B><br>        <b><a target="_blank" href="http://macgyver.seriesp…
  • Warning Line 2704, Column 19: character "&" is the first character of a delimiter but occurred as data
              Melissa & Joey           </a></b><br />

    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 2849, Column 11: element "B" undefined
            <B>N</B><br>        <b><a target="_blank" href="http://naruto.seriespep…

    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 2849, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>N</B><br>        <b><a target="_blank" href="http://naruto.seriespep…

    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 2849, Column 17: start tag was here
            <B>N</B><br>        <b><a target="_blank" href="http://naruto.seriespep…
  • Error Line 2903, Column 11: element "B" undefined
            <B>O</B><br>        <b><a target="_blank" href="http://october-road.ser…

    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 2903, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>O</B><br>        <b><a target="_blank" href="http://october-road.ser…

    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 2903, Column 17: start tag was here
            <B>O</B><br>        <b><a target="_blank" href="http://october-road.ser…
  • Error Line 2943, Column 11: element "B" undefined
            <B>P</B><br>        <b><a target="_blank" href="http://pablo-escobar-el…

    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 2943, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>P</B><br>        <b><a target="_blank" href="http://pablo-escobar-el…

    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 2943, Column 17: start tag was here
            <B>P</B><br>        <b><a target="_blank" href="http://pablo-escobar-el…
  • Error Line 3117, Column 11: element "B" undefined
            <B>Q</B><br>        <b><a target="_blank" href="http://que-fue-de-jorge…

    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 3117, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>Q</B><br>        <b><a target="_blank" href="http://que-fue-de-jorge…

    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 3117, Column 17: start tag was here
            <B>Q</B><br>        <b><a target="_blank" href="http://que-fue-de-jorge…
  • Error Line 3129, Column 11: element "B" undefined
            <B>R</B><br>        <b><a target="_blank" href="http://raices.seriespep…

    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 3129, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>R</B><br>        <b><a target="_blank" href="http://raices.seriespep…

    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 3129, Column 17: start tag was here
            <B>R</B><br>        <b><a target="_blank" href="http://raices.seriespep…
  • Warning Line 3214, Column 20: character "&" is the first character of a delimiter but occurred as data
              Rosemary & Thyme          </a></b><br />

    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 3233, Column 11: element "B" undefined
            <B>S</B><br>        <b><a target="_blank" href="http://s-o-s-sexo-y-otr…

    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 3233, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>S</B><br>        <b><a target="_blank" href="http://s-o-s-sexo-y-otr…

    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 3233, Column 17: start tag was here
            <B>S</B><br>        <b><a target="_blank" href="http://s-o-s-sexo-y-otr…
  • Warning Line 3384, Column 18: character "&" is the first character of a delimiter but occurred as data
              Snooki & Jwoww          </a></b><br />

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 3456, Column 20: character "&" is the first character of a delimiter but occurred as data
              Sullivan & Son          </a></b><br />

    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 3495, Column 11: element "B" undefined
            <B>T</B><br>        <b><a target="_blank" href="http://tacones-armados.…

    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 3495, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>T</B><br>        <b><a target="_blank" href="http://tacones-armados.…

    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 3495, Column 17: start tag was here
            <B>T</B><br>        <b><a target="_blank" href="http://tacones-armados.…
  • Error Line 3799, Column 11: element "B" undefined
            <B>U</B><br>        <b><a target="_blank" href="http://ugly-americans.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 3799, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>U</B><br>        <b><a target="_blank" href="http://ugly-americans.s…

    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 3799, Column 17: start tag was here
            <B>U</B><br>        <b><a target="_blank" href="http://ugly-americans.s…
  • Error Line 3845, Column 11: element "B" undefined
            <B>V</B><br>        <b><a target="_blank" href="http://v-2009.seriespep…

    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 3845, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>V</B><br>        <b><a target="_blank" href="http://v-2009.seriespep…

    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 3845, Column 17: start tag was here
            <B>V</B><br>        <b><a target="_blank" href="http://v-2009.seriespep…
  • Error Line 3885, Column 11: element "B" undefined
            <B>W</B><br>        <b><a target="_blank" href="http://wakfu.seriespepi…

    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 3885, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>W</B><br>        <b><a target="_blank" href="http://wakfu.seriespepi…

    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 3885, Column 17: start tag was here
            <B>W</B><br>        <b><a target="_blank" href="http://wakfu.seriespepi…
  • Error Line 3943, Column 11: element "B" undefined
            <B>X</B><br>        <b><a target="_blank" href="http://x-men.seriespepi…

    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 3943, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>X</B><br>        <b><a target="_blank" href="http://x-men.seriespepi…

    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 3943, Column 17: start tag was here
            <B>X</B><br>        <b><a target="_blank" href="http://x-men.seriespepi…
  • Error Line 3953, Column 11: element "B" undefined
            <B>Y</B><br>        <b><a target="_blank" href="http://y-el-mundo-cambi…

    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 3953, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>Y</B><br>        <b><a target="_blank" href="http://y-el-mundo-cambi…

    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 3953, Column 17: start tag was here
            <B>Y</B><br>        <b><a target="_blank" href="http://y-el-mundo-cambi…
  • Error Line 3975, Column 11: element "B" undefined
            <B>Z</B><br>        <b><a target="_blank" href="http://zack-y-cody-todo…

    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 3975, Column 21: end tag for "br" omitted, but OMITTAG NO was specified
            <B>Z</B><br>        <b><a target="_blank" href="http://zack-y-cody-todo…

    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 3975, Column 17: start tag was here
            <B>Z</B><br>        <b><a target="_blank" href="http://zack-y-cody-todo…
  • Error Line 4003, Column 8: document type does not allow element "br" here; missing one of "th", "td" start-tag
      <br /></tr>

    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 4006, Column 23: end tag for element "td" which is not open
                      </td>

    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 4008, Column 27: end tag for element "tr" which is not open
                          </tr>

    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 4009, Column 28: end tag for element "table" which is not open
                        </table>

    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 4038, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 4059, Column 85: "s" is not a member of a group specified for any attribute
    …<table width="960" border="0" align="center" cellpadding="0" cellspacing="3" s>
  • Error Line 4098, Column 341: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"
    …ebsite counter" width="80" height="15" border="0" align="absmiddle" /></a></td>

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

Visitor Analysis

Daily Visitor
  • 5.600 visits