zonasports.me Website: ZonaSports.me - Programacion - Los mejores eventos deportivos en calidad HD!

zonasports.me

Transmitimos los mejores eventos deportivos en calidad HD en internet. ...

Domain Name

zonasports.me
Favicon
Google Page Rank

2
Alexa Rank

#73799
Page Size

40.5 KB
Ip Address

141.101.116.146
Heading

H1: 0, H2: 0, H3: 2, H4: 0, H5: 0, H6: 0
Images

2 GIF, 2 JPG, 8 PNG

Website Meta Analysis

Title

ZonaSports.me - Programacion - Los mejores eventos deportivos en calidad HD!
Meta Keyword
Meta Description

Transmitimos los mejores eventos deportivos en calidad HD en internet.

Technical Analysis

Webserver

nginx
Ip Address

141.101.116.146
Domain Age
Javascript Library
Language used

HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from zonasports.me.

HTML Analysis

server: nginx
date: Tue, 05 Mar 2013 03:33:25 GMT
content-type: text/html
connection: keep-alive
vary: Accept-Encoding
x-powered-by: PHP/5.3.20
x-cacheable: YES
x-varnish: 1008407249
via: 1.1 varnish
age: 0
x-cache: MISS
expires: Wed, 06 Mar 2013 03:33:25 GMT
cache-control: max-age=86400
content-encoding: gzip
x-google-cache-control: remote-fetch

No data whois for zonasports.me

IP 141.101.116.146 Analysis

Country Code

EU
Country Code3

EU
Country Name

Europe
City

EU
Continent Code

47° North
Latitude

8.
Longitude

No whois ip data for 141.101.116.146

In Page Analysis

Outbound Links

zonasports.me has 9 outlinks. The relation of external links to inner links influences the distribution of the site's weight in general. To grow the amount of indexed pages, there should be more inner links than external links.

Outbound Links

Traffic Analysis

Magestic Backlinks

Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

HTML validation

323 Errors
89 Warnings

Ratio Text/Html

0.6413951243060585

Message Error

Line 3, Column 52: document type does not allow element "meta" here; assuming missing "head" start-tag
```
<meta http-equiv="Content-Language" content="en-us">
```
Line 3, Column 53: end tag for "meta" omitted, but OMITTAG NO was specified
```
<meta http-equiv="Content-Language" content="en-us">
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 3, Column 1: start tag was here

<meta http-equiv="Content-Language" content="en-us">

Line 4, Column 6: document type does not allow element "head" here
```
<head>
```
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).
Line 6, Column 75: end tag for "meta" omitted, but OMITTAG NO was specified
```
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 6, Column 1: start tag was here

<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">

Line 7, Column 40: end tag for "meta" omitted, but OMITTAG NO was specified
```
<meta http-equiv="Expires" content="0">
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 7, Column 1: start tag was here
```
<meta http-equiv="Expires" content="0">
```
Line 9, Column 34: duplicate specification of attribute "content"
```
<meta content="keywords" content="Ver Barcelona vs Real Madrid En Vivo, eventos…
```
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 16, Column 73: end tag for "link" omitted, but OMITTAG NO was specified
```
<link rel="shortcut icon" href="images/favicon.ico" type="image/x-icon">
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 16, Column 1: start tag was here

<link rel="shortcut icon" href="images/favicon.ico" type="image/x-icon">

Line 20, Column 56: end tag for "link" omitted, but OMITTAG NO was specified
```
<link rel="canonical" href="http://www.zonasports.me/">
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 20, Column 1: start tag was here

<link rel="canonical" href="http://www.zonasports.me/">

Line 33, Column 8: required attribute "type" not specified
```
<script>
```
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Line 49, Column 43: character "&" is the first character of a delimiter but occurred as data
```
(document.layers||(document.getElementById&&!document.all)) {
```
This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 49, Column 44: character "&" is the first character of a delimiter but occurred as data
```
(document.layers||(document.getElementById&&!document.all)) {
```
This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 64, Column 33: required attribute "type" not specified
```
<script language="JavaScript1.2">
```
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>.

Line 78, Column 46: character "|" not allowed in attribute specification list

….window.outerHeight<screen.availHeight||top.window.outerWidth<screen.availWidt…

Line 78, Column 46: element "screen.availHeight" undefined
```
….window.outerHeight<screen.availHeight||top.window.outerWidth<screen.availWidt…
```
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).

Line 78, Column 87: character ")" not allowed in attribute specification list

…indow.outerHeight<screen.availHeight||top.window.outerWidth<screen.availWidth){

Line 78, Column 87: element "screen.availWidth" undefined
```
…indow.outerHeight<screen.availHeight||top.window.outerWidth<screen.availWidth){
```
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).
Line 90, Column 9: end tag for "screen.availWidth" omitted, but OMITTAG NO was specified
```
</script>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 78, Column 69: start tag was here

…indow.outerHeight<screen.availHeight||top.window.outerWidth<screen.availWidth){

Line 90, Column 9: end tag for "screen.availHeight" omitted, but OMITTAG NO was specified
```
</script>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 78, Column 27: start tag was here

if (top.window.outerHeight<screen.availHeight||top.window.outerWidth<screen.ava…

Line 113, Column 20: document type does not allow element "div" here; assuming missing "object" start-tag
```
<div align="center">
```
Line 117, Column 90: required attribute "alt" not specified
```
…na1023.com/wp-content/themes/latina/images/facebookl.png" border="0"></a></div>
```
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Line 117, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
```
…na1023.com/wp-content/themes/latina/images/facebookl.png" border="0"></a></div>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 117, Column 1: start tag was here

<img src="http://latina1023.com/wp-content/themes/latina/images/facebookl.png" …

Line 117, Column 100: end tag for "font" omitted, but OMITTAG NO was specified
```
…na1023.com/wp-content/themes/latina/images/facebookl.png" border="0"></a></div>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 115, Column 1: start tag was here
```
<font face="Tahoma">
```
Line 118, Column 22: document type does not allow element "base" here
```
<base target="_blank">
```
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).
Line 118, Column 23: end tag for "base" omitted, but OMITTAG NO was specified
```
<base target="_blank">
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 118, Column 1: start tag was here
```
<base target="_blank">
```
Line 119, Column 7: end tag for element "font" which is not open
```
</font><font face="Tahoma">
```
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.
Line 120, Column 7: end tag for "font" 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 ">".
Line 119, Column 8: start tag was here
```
</font><font face="Tahoma">
```
Line 120, Column 7: end tag for "div" 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 ">".
Line 113, Column 1: start tag was here
```
<div align="center">
```
Line 120, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
```
</head>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 113, Column 1: start tag was here
```
<div align="center">
```
Line 120, 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.
Line 121, Column 8: required attribute "type" not specified
```
<script> 
```
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Line 121, Column 8: document type does not allow element "script" here; assuming missing "body" start-tag
```
<script> 
```
Line 181, Column 10: character "<" is the first character of a delimiter but occurred as data
```
if (year < 2000) year = year + 1900; 
```
This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 189, Column 19: character "<" is the first character of a delimiter but occurred as data
```
for (var i = 0; i < len; i++) this[i] = null; 
```
This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 196, Column 7: required attribute "type" not specified
```
<style><!--
```
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Line 196, Column 7: document type does not allow element "style" here
```
<style><!--
```
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 199, Column 7: end tag for element "head" which is not open
```
</head>
```
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.
Line 200, Column 7: end tag for element "font" which is not open
```
</font>
```
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.
Line 201, Column 68: document type does not allow element "body" here
```
<body link="#006699" vlink="#5493B4" onload="guardaHorario();dT();">
```
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).
Line 224, Column 7: end tag for element "head" which is not open
```
</head>
```
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.
Line 226, Column 33: ID "navbar" already defined
```
<div class="navbar section" id="navbar">
```
An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 202, Column 33: ID "navbar" first defined here
```
<div class="navbar section" id="navbar">
```
Line 227, Column 32: ID "Navbar1" already defined
```
<div class="widget Navbar" id="Navbar1">
```
An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 203, Column 32: ID "Navbar1" first defined here
```
<div class="widget Navbar" id="Navbar1">
```
Line 230, Column 7: end tag for element "font" which is not open
```
</font>
```
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.
Line 237, Column 60: there is no attribute "height"
```
<table cellspacing="0" cellpadding="0" width="1105" height="41">
```
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.
Line 245, Column 86: end tag for "br" omitted, but OMITTAG NO was specified
```
…f="/">Programacion de ZonaSports.me</a></font></strong><font face="Tahoma"><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 ">".

Line 245, Column 82: start tag was here

…f="/">Programacion de ZonaSports.me</a></font></strong><font face="Tahoma"><br>

Line 252, Column 66: end tag for element "span" which is not open
```
Advertencia legal</a></font><font size="2" color="#00FFFF"></span>
```
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.
Line 286, Column 99: there is no attribute "bordercolorlight"
```
…height: 230px" border="1" bordercolorlight="#00BDC4" bordercolordark="#00BDC4">
```
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.
Line 286, Column 125: there is no attribute "bordercolordark"
```
…height: 230px" border="1" bordercolorlight="#00BDC4" bordercolordark="#00BDC4">
```
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.
Line 286, Column 134: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
…height: 230px" border="1" bordercolorlight="#00BDC4" bordercolordark="#00BDC4">
```
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>").
Line 288, Column 46: document type does not allow element "font" here; missing one of "th", "td" start-tag
```
<font color="#00bdc4" size="4" face="Verdana">
```
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>").
Line 289, Column 19: document type does not allow element "td" here
```
<td align="center">
```
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).
Line 303, Column 4: document type does not allow element "hr" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
<hr><b>Elige tu
```
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>").
Line 303, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
```
<hr><b>Elige tu
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 303, Column 1: start tag was here
```
<hr><b>Elige tu
```
Line 306, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
```
<br>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 306, Column 1: start tag was here
```
<br>
```
Line 356, Column 23: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
<div class="post-body">
```
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>").
Line 365, Column 373: end tag for "br" omitted, but OMITTAG NO was specified
```
…smitiendo en tiempo real."/></a></span></font></strong><font face="Tahoma"><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 ">".

Line 365, Column 369: start tag was here

…smitiendo en tiempo real."/></a></span></font></strong><font face="Tahoma"><br>

Line 366, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
```
<br>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 366, Column 1: start tag was here
```
<br>
```
Line 367, Column 59: cannot generate system identifier for general entity "ad_size"
```
…ad.yieldmanager.com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url=…
```
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&" (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 æ 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.
Line 367, Column 59: general entity "ad_size" not defined and no default entity
```
…ad.yieldmanager.com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url=…
```
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 367, Column 66: reference not terminated by REFC delimiter
```
…dmanager.com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventos…
```
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.
Line 367, Column 66: reference to external entity in attribute value
```
…dmanager.com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventos…
```
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 '&'.
Line 367, Column 66: reference to entity "ad_size" for which no system identifier could be generated
```
…dmanager.com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventos…
```
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.

Line 367, Column 58: entity was defined here

…/ad.yieldmanager.com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url…

Line 367, Column 75: cannot generate system identifier for general entity "section"
```
…com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventosppv.com" …
```
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 "&" (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 æ 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.
Line 367, Column 75: general entity "section" not defined and no default entity
```
…com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventosppv.com" …
```
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 367, Column 82: reference not terminated by REFC delimiter
```
…ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventosppv.com" width="…
```
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.
Line 367, Column 82: reference to external entity in attribute value
```
…ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventosppv.com" width="…
```
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 '&'.
Line 367, Column 82: reference to entity "section" for which no system identifier could be generated
```
…ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventosppv.com" width="…
```
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.

Line 367, Column 74: entity was defined here

….com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventosppv.com"…

Line 367, Column 91: cannot generate system identifier for general entity "pub_url"
```
…frame&ad_size=160x600&section=3607391&pub_url=eventosppv.com" width="160" heig…
```
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 "&" (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 æ 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.
Line 367, Column 91: general entity "pub_url" not defined and no default entity
```
…frame&ad_size=160x600&section=3607391&pub_url=eventosppv.com" width="160" heig…
```
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.
Line 367, Column 98: reference not terminated by REFC delimiter
```
…d_size=160x600&section=3607391&pub_url=eventosppv.com" width="160" height="600…
```
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.
Line 367, Column 98: reference to external entity in attribute value
```
…d_size=160x600&section=3607391&pub_url=eventosppv.com" width="160" height="600…
```
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 '&'.
Line 367, Column 98: reference to entity "pub_url" for which no system identifier could be generated
```
…d_size=160x600&section=3607391&pub_url=eventosppv.com" width="160" height="600…
```
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.

Line 367, Column 90: entity was defined here

…iframe&ad_size=160x600&section=3607391&pub_url=eventosppv.com" width="160" hei…

Line 371, Column 57: there is no attribute "bordercolor"
```
<td width="650" align="center" valign="top" bordercolor="#C0C0C0">
```
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.
Line 375, Column 62: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
<table border="0" cellpadding="0" cellspacing="6" width="456">
```
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>").
Line 380, Column 30: required attribute "type" not specified
```
<script language="JavaScript">
```
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Line 399, Column 7: end tag for "span" omitted, but OMITTAG NO was specified
```
</font>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 373, Column 1: start tag was here
```
<span style="letter-spacing: normal">
```
Line 399, Column 7: end tag for "strong" omitted, but OMITTAG NO was specified
```
</font>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 372, Column 1: start tag was here
```
<strong>
```
Line 399, Column 7: end tag for "td" omitted, but OMITTAG NO was specified
```
</font>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 371, Column 1: start tag was here

<td width="650" align="center" valign="top" bordercolor="#C0C0C0">

Line 399, Column 7: end tag for "tr" omitted, but OMITTAG NO was specified
```
</font>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 358, Column 1: start tag was here
```
<tr>
```
Line 399, Column 7: end tag for "table" omitted, but OMITTAG NO was specified
```
</font>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 357, Column 1: start tag was here

<table border="0" width="100%" style="border-collapse: collapse">

Line 399, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
```
</font>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 356, Column 1: start tag was here
```
<div class="post-body">
```
Line 401, Column 63: there is no attribute "bordercolor"
```
…r="1" cellpadding="5" cellspacing="0" bordercolor="#DDDDDD" width="650" height>
```
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

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

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 401, Column 91: "height" is not a member of a group specified for any attribute
```
…r="1" cellpadding="5" cellspacing="0" bordercolor="#DDDDDD" width="650" height>
```
Line 401, Column 91: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
…r="1" cellpadding="5" cellspacing="0" bordercolor="#DDDDDD" width="650" height>
```
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>").
Line 408, Column 18: end tag for "b" omitted, but OMITTAG NO was specified
```
Hora</font></font></b></font></p>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 406, Column 1: start tag was here
```
<b>
```
Line 408, Column 22: end tag for element "b" which is not open
```
Hora</font></font></b></font></p>
```
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.
Line 408, Column 29: end tag for "p" omitted, but OMITTAG NO was specified
```
Hora</font></font></b></font></p>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 404, Column 1: start tag was here
```
<p align="center">
```
Line 408, Column 29: end tag for "td" omitted, but OMITTAG NO was specified
```
Hora</font></font></b></font></p>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 403, Column 1: start tag was here
```
<td align="center" width="60">
```
Line 408, Column 29: end tag for "tr" omitted, but OMITTAG NO was specified
```
Hora</font></font></b></font></p>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 402, Column 1: start tag was here
```
<tr>
```
Line 408, Column 29: end tag for "table" omitted, but OMITTAG NO was specified
```
Hora</font></font></b></font></p>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 401, Column 1: start tag was here

<table border="1" cellpadding="5" cellspacing="0" bordercolor="#DDDDDD" width="…

Line 408, Column 33: end tag for element "p" which is not open
```
Hora</font></font></b></font></p>
```
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.
Line 409, Column 5: end tag for "strong" omitted, but OMITTAG NO was specified
```
</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 ">".
Line 291, Column 1: start tag was here
```
<strong>
```
Line 409, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
```
</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 ">".
Line 290, Column 1: start tag was here
```
<div class="post-body">
```
Line 410, Column 46: document type does not allow element "td" here
```
<td height="13px" width="26px" align="center">
```
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).
Line 415, Column 17: document type does not allow element "td" here
```
<td align="left">
```
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).
Line 422, Column 5: end tag for "font" omitted, but OMITTAG NO was specified
```
</tr>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 288, Column 1: start tag was here

<font color="#00bdc4" size="4" face="Verdana">

Line 422, Column 5: end tag for "tr" which is not finished
```
</tr>
```
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.
Line 424, Column 18: document type does not allow element "td" here; assuming missing "tr" start-tag
```
<td align="right">
```
Line 428, Column 60: required attribute "alt" not specified
```
<img src="imagenes/espndeportes.png" width="31" height="11"></font></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>.
Line 428, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
```
<img src="imagenes/espndeportes.png" width="31" height="11"></font></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 ">".

Line 428, Column 1: start tag was here

<img src="imagenes/espndeportes.png" width="31" height="11"></font></td>

Line 447, Column 73: required attribute "alt" not specified
```
…rc="http://s3.fuel.tv/fsb/fox_deportes.png" width="33" height="12"></font></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>.
Line 447, Column 80: end tag for "img" omitted, but OMITTAG NO was specified
```
…rc="http://s3.fuel.tv/fsb/fox_deportes.png" width="33" height="12"></font></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 ">".

Line 447, Column 1: start tag was here

<img src="http://s3.fuel.tv/fsb/fox_deportes.png" width="33" height="12"></font…

Line 465, Column 124: required attribute "alt" not specified
```
…wI/AAAAAAAAEe8/_WjV9jOBx18/s400/GolTV1.JPG" width="31" height="13"></font></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>.
Line 465, Column 131: end tag for "img" omitted, but OMITTAG NO was specified
```
…wI/AAAAAAAAEe8/_WjV9jOBx18/s400/GolTV1.JPG" width="31" height="13"></font></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 ">".

Line 465, Column 1: start tag was here

<img src="http://4.bp.blogspot.com/_wSFnp8s92ew/THlGw-ugjwI/AAAAAAAAEe8/_WjV9jO…

Line 481, Column 84: required attribute "alt" not specified
```
…="13" width="26">&nbsp;<img height="10" src="imagenes/en.png" width="13"/></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>.
Line 488, Column 84: required attribute "alt" not specified
```
…="13" width="26">&nbsp;<img height="10" src="imagenes/es.png" width="13"/></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>.
Line 494, Column 85: required attribute "alt" not specified
```
…"13" width="26">&nbsp;<img height="10" src="imagenes/wwe.png" width="13"/></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>.
Line 495, Column 46: end tag for element "b" which is not open
```
<td align="left">WWE Monday Raw en español</b><b> (<a href="canal-1.php">canal
```
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.
Line 500, Column 85: required attribute "alt" not specified
```
…"13" width="26">&nbsp;<img height="13" src="imagenes/bkb.png" width="13"/></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>.
Line 506, Column 85: required attribute "alt" not specified
```
…"13" width="26">&nbsp;<img height="13" src="imagenes/bkb.png" width="13"/></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>.
Line 512, Column 7: end tag for element "font" which is not open
```
</font>
```
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.
Line 520, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
```
anterior.<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 ">".
Line 520, Column 10: start tag was here
```
anterior.<br>
```
Line 528, Column 63: end tag for "br" omitted, but OMITTAG NO was specified
```
tarde.</font><font color="#00FFFF" size="2" face="Tahoma"><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 ">".

Line 528, Column 59: start tag was here

tarde.</font><font color="#00FFFF" size="2" face="Tahoma"><br>

Line 533, Column 97: there is no attribute "onClick"
```
…alue="Actualizar Programacion" onClick="document.location.reload(true)"></font>
```
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.
Line 533, Column 136: end tag for "input" omitted, but OMITTAG NO was specified
```
…alue="Actualizar Programacion" onClick="document.location.reload(true)"></font>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 533, Column 36: start tag was here

&nbsp;<font face="Tahoma" size="2"><input type="button" value="Actualizar Progr…

Line 534, Column 20: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
<div align="center">
```
The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 537, Column 111: end tag for "hr" omitted, but OMITTAG NO was specified
```
…nter"><b><font color="#FF0000" size="3" face="Tahoma">IMPORTANTE</font></b><hr>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 537, Column 107: start tag was here

…nter"><b><font color="#FF0000" size="3" face="Tahoma">IMPORTANTE</font></b><hr>

Line 538, Column 239: end tag for "br" omitted, but OMITTAG NO was specified
```
…ick al partido de tu preferencia, seras dirigido al canal donde se pondra. <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 ">".

Line 538, Column 235: start tag was here

…ick al partido de tu preferencia, seras dirigido al canal donde se pondra. <br>

Line 539, Column 106: end tag for "br" omitted, but OMITTAG NO was specified
```
…e cambia automaticamente segun tupais; el horario mostrado es el correcto. <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 ">".

Line 539, Column 102: start tag was here

…e cambia automaticamente segun tupais; el horario mostrado es el correcto. <br>

Line 540, Column 79: end tag for "br" omitted, but OMITTAG NO was specified
```
- Si no te muestra el horario correcto, actualiza la hora en tu ordenador.<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 ">".

Line 540, Column 75: start tag was here

- Si no te muestra el horario correcto, actualiza la hora en tu ordenador.<br>

Line 541, Column 62: end tag for "br" omitted, but OMITTAG NO was specified
```
- La programacion puede ser modificada sin previo aviso. <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 ">".

Line 541, Column 58: start tag was here

- La programacion puede ser modificada sin previo aviso. <br>

Line 542, Column 86: end tag for "br" omitted, but OMITTAG NO was specified
```
…señales de los eventos se colocan de 30 a 5 minutos antes de que comienzen.<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 ">".

Line 542, Column 82: start tag was here

…señales de los eventos se colocan de 30 a 5 minutos antes de que comienzen.<br>

Line 547, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
```
</font>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 534, Column 1: start tag was here
```
<div align="center">
```
Line 549, Column 7: end tag for element "span" which is not open
```
</span>
```
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.
Line 554, Column 30: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
<table border="0" width="78%">
```
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>").
Line 557, Column 136: cannot generate system identifier for general entity "send"
```
…3A%2F%2Fwww.facebook.com%2FEventosPPV&send=false&layout=button_count&locale=es…
```
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 "&" (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 æ 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.
Line 557, Column 136: general entity "send" not defined and no default entity
```
…3A%2F%2Fwww.facebook.com%2FEventosPPV&send=false&layout=button_count&locale=es…
```
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.
Line 557, Column 140: reference not terminated by REFC delimiter
```
…F%2Fwww.facebook.com%2FEventosPPV&send=false&layout=button_count&locale=es_ES&…
```
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.
Line 557, Column 140: reference to external entity in attribute value
```
…F%2Fwww.facebook.com%2FEventosPPV&send=false&layout=button_count&locale=es_ES&…
```
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 '&'.
Line 557, Column 140: reference to entity "send" for which no system identifier could be generated
```
…F%2Fwww.facebook.com%2FEventosPPV&send=false&layout=button_count&locale=es_ES&…
```
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.

Line 557, Column 135: entity was defined here

…%3A%2F%2Fwww.facebook.com%2FEventosPPV&send=false&layout=button_count&locale=e…

Line 557, Column 147: cannot generate system identifier for general entity "layout"
```
….facebook.com%2FEventosPPV&send=false&layout=button_count&locale=es_ES&width=4…
```
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 "&" (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 æ 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.
Line 557, Column 147: general entity "layout" not defined and no default entity
```
….facebook.com%2FEventosPPV&send=false&layout=button_count&locale=es_ES&width=4…
```
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.
Line 557, Column 153: reference not terminated by REFC delimiter
```
…ook.com%2FEventosPPV&send=false&layout=button_count&locale=es_ES&width=450&sho…
```
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.
Line 557, Column 153: reference to external entity in attribute value
```
…ook.com%2FEventosPPV&send=false&layout=button_count&locale=es_ES&width=450&sho…
```
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 '&'.
Line 557, Column 153: reference to entity "layout" for which no system identifier could be generated
```
…ook.com%2FEventosPPV&send=false&layout=button_count&locale=es_ES&width=450&sho…
```
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.

Line 557, Column 146: entity was defined here

…w.facebook.com%2FEventosPPV&send=false&layout=button_count&locale=es_ES&width=…

Line 557, Column 167: cannot generate system identifier for general entity "locale"
```
…tosPPV&send=false&layout=button_count&locale=es_ES&width=450&show_faces=false&…
```
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 "&" (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 æ 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.
Line 557, Column 167: general entity "locale" not defined and no default entity
```
…tosPPV&send=false&layout=button_count&locale=es_ES&width=450&show_faces=false&…
```
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.
Line 557, Column 173: reference not terminated by REFC delimiter
```
…&send=false&layout=button_count&locale=es_ES&width=450&show_faces=false&action…
```
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.
Line 557, Column 173: reference to external entity in attribute value
```
…&send=false&layout=button_count&locale=es_ES&width=450&show_faces=false&action…
```
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 '&'.
Line 557, Column 173: reference to entity "locale" for which no system identifier could be generated
```
…&send=false&layout=button_count&locale=es_ES&width=450&show_faces=false&action…
```
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.

Line 557, Column 166: entity was defined here

…ntosPPV&send=false&layout=button_count&locale=es_ES&width=450&show_faces=false…

Line 557, Column 180: cannot generate system identifier for general entity "width"
```
…alse&layout=button_count&locale=es_ES&width=450&show_faces=false&action=like&c…
```
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 "&" (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 æ 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.
Line 557, Column 180: general entity "width" not defined and no default entity
```
…alse&layout=button_count&locale=es_ES&width=450&show_faces=false&action=like&c…
```
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.
Line 557, Column 185: reference not terminated by REFC delimiter
```
…layout=button_count&locale=es_ES&width=450&show_faces=false&action=like&colors…
```
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.
Line 557, Column 185: reference to external entity in attribute value
```
…layout=button_count&locale=es_ES&width=450&show_faces=false&action=like&colors…
```
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 '&'.
Line 557, Column 185: reference to entity "width" for which no system identifier could be generated
```
…layout=button_count&locale=es_ES&width=450&show_faces=false&action=like&colors…
```
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.

Line 557, Column 179: entity was defined here

…false&layout=button_count&locale=es_ES&width=450&show_faces=false&action=like&…

Line 557, Column 190: cannot generate system identifier for general entity "show_faces"
```
…t=button_count&locale=es_ES&width=450&show_faces=false&action=like&colorscheme…
```
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 "&" (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 æ 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.
Line 557, Column 190: general entity "show_faces" not defined and no default entity
```
…t=button_count&locale=es_ES&width=450&show_faces=false&action=like&colorscheme…
```
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.
Line 557, Column 200: reference not terminated by REFC delimiter
```
…ount&locale=es_ES&width=450&show_faces=false&action=like&colorscheme=dark&font…
```
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.
Line 557, Column 200: reference to external entity in attribute value
```
…ount&locale=es_ES&width=450&show_faces=false&action=like&colorscheme=dark&font…
```
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 '&'.
Line 557, Column 200: reference to entity "show_faces" for which no system identifier could be generated
```
…ount&locale=es_ES&width=450&show_faces=false&action=like&colorscheme=dark&font…
```
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.

Line 557, Column 189: entity was defined here

…ut=button_count&locale=es_ES&width=450&show_faces=false&action=like&colorschem…

Line 557, Column 207: cannot generate system identifier for general entity "action"
```
…cale=es_ES&width=450&show_faces=false&action=like&colorscheme=dark&font=arial&…
```
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 "&" (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 æ 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.
Line 557, Column 207: general entity "action" not defined and no default entity
```
…cale=es_ES&width=450&show_faces=false&action=like&colorscheme=dark&font=arial&…
```
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.
Line 557, Column 213: reference not terminated by REFC delimiter
```
…s_ES&width=450&show_faces=false&action=like&colorscheme=dark&font=arial&height…
```
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.
Line 557, Column 213: reference to external entity in attribute value
```
…s_ES&width=450&show_faces=false&action=like&colorscheme=dark&font=arial&height…
```
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 '&'.
Line 557, Column 213: reference to entity "action" for which no system identifier could be generated
```
…s_ES&width=450&show_faces=false&action=like&colorscheme=dark&font=arial&height…
```
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.

Line 557, Column 206: entity was defined here

…ocale=es_ES&width=450&show_faces=false&action=like&colorscheme=dark&font=arial…

Line 557, Column 219: cannot generate system identifier for general entity "colorscheme"
```
…idth=450&show_faces=false&action=like&colorscheme=dark&font=arial&height=21&ap…
```
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 "&" (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 æ 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.
Line 557, Column 219: general entity "colorscheme" not defined and no default entity
```
…idth=450&show_faces=false&action=like&colorscheme=dark&font=arial&height=21&ap…
```
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.
Line 557, Column 230: reference not terminated by REFC delimiter
```
…ow_faces=false&action=like&colorscheme=dark&font=arial&height=21&appId=1813093…
```
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.
Line 557, Column 230: reference to external entity in attribute value
```
…ow_faces=false&action=like&colorscheme=dark&font=arial&height=21&appId=1813093…
```
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 '&'.
Line 557, Column 230: reference to entity "colorscheme" for which no system identifier could be generated
```
…ow_faces=false&action=like&colorscheme=dark&font=arial&height=21&appId=1813093…
```
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.

Line 557, Column 218: entity was defined here

…width=450&show_faces=false&action=like&colorscheme=dark&font=arial&height=21&a…

Line 557, Column 236: cannot generate system identifier for general entity "font"
```
…es=false&action=like&colorscheme=dark&font=arial&height=21&appId=1813093485550…
```
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 "&" (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 æ 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.
Line 557, Column 236: general entity "font" not defined and no default entity
```
…es=false&action=like&colorscheme=dark&font=arial&height=21&appId=1813093485550…
```
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.
Line 557, Column 240: reference not terminated by REFC delimiter
```
…alse&action=like&colorscheme=dark&font=arial&height=21&appId=181309348555036" …
```
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.
Line 557, Column 240: reference to external entity in attribute value
```
…alse&action=like&colorscheme=dark&font=arial&height=21&appId=181309348555036" …
```
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 '&'.
Line 557, Column 240: reference to entity "font" for which no system identifier could be generated
```
…alse&action=like&colorscheme=dark&font=arial&height=21&appId=181309348555036" …
```
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.

Line 557, Column 235: entity was defined here

…ces=false&action=like&colorscheme=dark&font=arial&height=21&appId=181309348555…

Line 557, Column 247: cannot generate system identifier for general entity "height"
```
…tion=like&colorscheme=dark&font=arial&height=21&appId=181309348555036" scrolli…
```
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 "&" (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 æ 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.
Line 557, Column 247: general entity "height" not defined and no default entity
```
…tion=like&colorscheme=dark&font=arial&height=21&appId=181309348555036" scrolli…
```
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.
Line 557, Column 253: reference not terminated by REFC delimiter
```
…ike&colorscheme=dark&font=arial&height=21&appId=181309348555036" scrolling="no…
```
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.
Line 557, Column 253: reference to external entity in attribute value
```
…ike&colorscheme=dark&font=arial&height=21&appId=181309348555036" scrolling="no…
```
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 '&'.
Line 557, Column 253: reference to entity "height" for which no system identifier could be generated
```
…ike&colorscheme=dark&font=arial&height=21&appId=181309348555036" scrolling="no…
```
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.

Line 557, Column 246: entity was defined here

…ction=like&colorscheme=dark&font=arial&height=21&appId=181309348555036" scroll…

Line 557, Column 257: cannot generate system identifier for general entity "appId"
```
…colorscheme=dark&font=arial&height=21&appId=181309348555036" scrolling="no" fr…
```
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 "&" (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 æ 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.
Line 557, Column 257: general entity "appId" not defined and no default entity
```
…colorscheme=dark&font=arial&height=21&appId=181309348555036" scrolling="no" fr…
```
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.
Line 557, Column 262: reference not terminated by REFC delimiter
```
…scheme=dark&font=arial&height=21&appId=181309348555036" scrolling="no" framebo…
```
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.
Line 557, Column 262: reference to external entity in attribute value
```
…scheme=dark&font=arial&height=21&appId=181309348555036" scrolling="no" framebo…
```
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 '&'.
Line 557, Column 262: reference to entity "appId" for which no system identifier could be generated
```
…scheme=dark&font=arial&height=21&appId=181309348555036" scrolling="no" framebo…
```
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.

Line 557, Column 256: entity was defined here

…&colorscheme=dark&font=arial&height=21&appId=181309348555036" scrolling="no" f…

Line 557, Column 399: there is no attribute "allowtransparency"
```
…119px; height:22px" allowtransparency="true"></iframe><a href="https://twitter…
```
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.
Line 557, Column 504: there is no attribute "data-show-count"
```
…witter-follow-button" data-show-count="true" data-lang="es" data-show-screen-n…
```
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.
Line 557, Column 521: there is no attribute "data-lang"
```
…ton" data-show-count="true" data-lang="es" data-show-screen-name="false">Segui…
```
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.
Line 557, Column 548: there is no attribute "data-show-screen-name"
```
…unt="true" data-lang="es" data-show-screen-name="false">Segui @zonasportshd</a>
```
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

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

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 558, Column 8: required attribute "type" not specified
```
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…
```
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>.
Line 558, Column 252: end tag for "br" omitted, but OMITTAG NO was specified
```
…rentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script><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 ">".

Line 558, Column 248: start tag was here

…rentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script><br>

Line 563, Column 6: end tag for "font" omitted, but OMITTAG NO was specified
```
</div>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 553, Column 1: start tag was here

<font face="Verdana" color="#00bdc4" size="4">

Line 563, Column 6: end tag for "font" omitted, but OMITTAG NO was specified
```
</div>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 552, Column 1: start tag was here
```
<font class="Apple-style-span">
```
Line 563, Column 6: end tag for "font" omitted, but OMITTAG NO was specified
```
</div>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 551, Column 1: start tag was here

<font class="Apple-style-span" face="Verdana">

Line 563, Column 6: end tag for "strong" omitted, but OMITTAG NO was specified
```
</div>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 550, Column 1: start tag was here
```
<strong>
```
Line 565, Column 8: end tag for "table" which is not finished
```
</table>
```
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.
Line 570, Column 53: required attribute "type" not specified
```
<script src="http://widgets.twimg.com/j/2/widget.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>.
Line 571, Column 8: required attribute "type" not specified
```
<script>
```
The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
Line 646, Column 118: "allowtransparency" is not a member of a group specified for any attribute
```
…ne" frameborder="0" allowtransparency scrolling="no" src="http://www.facebook.…
```
Line 646, Column 242: reference not terminated by REFC delimiter
```
…facebook.com%2Foficialzonasports&width=300&colorscheme=dark&show_faces=true&st…
```
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.
Line 646, Column 242: reference to external entity in attribute value
```
…facebook.com%2Foficialzonasports&width=300&colorscheme=dark&show_faces=true&st…
```
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 '&'.
Line 646, Column 242: reference to entity "width" for which no system identifier could be generated
```
…facebook.com%2Foficialzonasports&width=300&colorscheme=dark&show_faces=true&st…
```
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.

Line 557, Column 179: entity was defined here

…false&layout=button_count&locale=es_ES&width=450&show_faces=false&action=like&…

Line 646, Column 258: reference not terminated by REFC delimiter
```
…ficialzonasports&width=300&colorscheme=dark&show_faces=true&stream=true&header…
```
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.
Line 646, Column 258: reference to external entity in attribute value
```
…ficialzonasports&width=300&colorscheme=dark&show_faces=true&stream=true&header…
```
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 '&'.
Line 646, Column 258: reference to entity "colorscheme" for which no system identifier could be generated
```
…ficialzonasports&width=300&colorscheme=dark&show_faces=true&stream=true&header…
```
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.

Line 557, Column 218: entity was defined here

…width=450&show_faces=false&action=like&colorscheme=dark&font=arial&height=21&a…

Line 646, Column 274: reference not terminated by REFC delimiter
```
…&width=300&colorscheme=dark&show_faces=true&stream=true&header=false&height=39…
```
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.
Line 646, Column 274: reference to external entity in attribute value
```
…&width=300&colorscheme=dark&show_faces=true&stream=true&header=false&height=39…
```
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 '&'.
Line 646, Column 274: reference to entity "show_faces" for which no system identifier could be generated
```
…&width=300&colorscheme=dark&show_faces=true&stream=true&header=false&height=39…
```
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.

Line 557, Column 189: entity was defined here

…ut=button_count&locale=es_ES&width=450&show_faces=false&action=like&colorschem…

Line 646, Column 280: cannot generate system identifier for general entity "stream"
```
…=300&colorscheme=dark&show_faces=true&stream=true&header=false&height=395" nam…
```
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 "&" (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 æ 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.
Line 646, Column 280: general entity "stream" not defined and no default entity
```
…=300&colorscheme=dark&show_faces=true&stream=true&header=false&height=395" nam…
```
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.
Line 646, Column 286: reference not terminated by REFC delimiter
```
…olorscheme=dark&show_faces=true&stream=true&header=false&height=395" name="I19…
```
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.
Line 646, Column 286: reference to external entity in attribute value
```
…olorscheme=dark&show_faces=true&stream=true&header=false&height=395" name="I19…
```
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 '&'.
Line 646, Column 286: reference to entity "stream" for which no system identifier could be generated
```
…olorscheme=dark&show_faces=true&stream=true&header=false&height=395" name="I19…
```
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.

Line 646, Column 279: entity was defined here

…h=300&colorscheme=dark&show_faces=true&stream=true&header=false&height=395" na…

Line 646, Column 292: cannot generate system identifier for general entity "header"
```
…lorscheme=dark&show_faces=true&stream=true&header=false&height=395" name="I19">
```
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 "&" (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 æ 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.
Line 646, Column 292: general entity "header" not defined and no default entity
```
…lorscheme=dark&show_faces=true&stream=true&header=false&height=395" name="I19">
```
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.
Line 646, Column 298: reference not terminated by REFC delimiter
```
…lorscheme=dark&show_faces=true&stream=true&header=false&height=395" name="I19">
```
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.
Line 646, Column 298: reference to external entity in attribute value
```
…lorscheme=dark&show_faces=true&stream=true&header=false&height=395" name="I19">
```
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 '&'.
Line 646, Column 298: reference to entity "header" for which no system identifier could be generated
```
…lorscheme=dark&show_faces=true&stream=true&header=false&height=395" name="I19">
```
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.

Line 646, Column 291: entity was defined here

…lorscheme=dark&show_faces=true&stream=true&header=false&height=395" name="I19">

Line 646, Column 311: reference not terminated by REFC delimiter
```
…lorscheme=dark&show_faces=true&stream=true&header=false&height=395" name="I19">
```
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.
Line 646, Column 311: reference to external entity in attribute value
```
…lorscheme=dark&show_faces=true&stream=true&header=false&height=395" name="I19">
```
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 '&'.
Line 646, Column 311: reference to entity "height" for which no system identifier could be generated
```
…lorscheme=dark&show_faces=true&stream=true&header=false&height=395" name="I19">
```
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.

Line 557, Column 246: entity was defined here

…ction=like&colorscheme=dark&font=arial&height=21&appId=181309348555036" scroll…

Line 652, Column 7: end tag for element "font" which is not open
```
</font>
```
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.
Line 653, Column 7: end tag for element "font" which is not open
```
</font>
```
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.
Line 654, Column 7: end tag for element "font" which is not open
```
</font>
```
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.
Line 657, Column 7: end tag for element "font" which is not open
```
</font>
```
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.
Line 658, Column 7: end tag for element "font" which is not open
```
</font>
```
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.
Line 659, Column 7: end tag for element "font" which is not open
```
</font>
```
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.
Line 660, Column 7: end tag for element "span" which is not open
```
</span>
```
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.
Line 661, Column 7: end tag for element "font" which is not open
```
</font>
```
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.
Line 662, Column 9: end tag for element "strong" which is not open
```
</strong>
```
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.
Line 668, Column 15: end tag for "br" omitted, but OMITTAG NO was specified
```
¡Siguenos!<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 ">".
Line 668, Column 11: start tag was here
```
¡Siguenos!<br>
```
Line 669, Column 242: end tag for "br" omitted, but OMITTAG NO was specified
```
…nsmitiendo en tiempo real"/></a></span></font></strong><font face="Tahoma"><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 ">".

Line 669, Column 238: start tag was here

…nsmitiendo en tiempo real"/></a></span></font></strong><font face="Tahoma"><br>

Line 670, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
```
<br>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 670, Column 1: start tag was here
```
<br>
```
Line 674, Column 66: reference not terminated by REFC delimiter
```
…dmanager.com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventos…
```
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.
Line 674, Column 66: reference to external entity in attribute value
```
…dmanager.com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventos…
```
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 '&'.
Line 674, Column 66: reference to entity "ad_size" for which no system identifier could be generated
```
…dmanager.com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventos…
```
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.

Line 367, Column 58: entity was defined here

…/ad.yieldmanager.com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url…

Line 674, Column 82: reference not terminated by REFC delimiter
```
…ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventosppv.com" width="…
```
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.
Line 674, Column 82: reference to external entity in attribute value
```
…ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventosppv.com" width="…
```
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 '&'.
Line 674, Column 82: reference to entity "section" for which no system identifier could be generated
```
…ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventosppv.com" width="…
```
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.

Line 367, Column 74: entity was defined here

….com/st?ad_type=iframe&ad_size=160x600&section=3607391&pub_url=eventosppv.com"…

Line 674, Column 98: reference not terminated by REFC delimiter
```
…d_size=160x600&section=3607391&pub_url=eventosppv.com" width="160" height="600…
```
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.
Line 674, Column 98: reference to external entity in attribute value
```
…d_size=160x600&section=3607391&pub_url=eventosppv.com" width="160" height="600…
```
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 '&'.
Line 674, Column 98: reference to entity "pub_url" for which no system identifier could be generated
```
…d_size=160x600&section=3607391&pub_url=eventosppv.com" width="160" height="600…
```
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.

Line 367, Column 90: entity was defined here

…iframe&ad_size=160x600&section=3607391&pub_url=eventosppv.com" width="160" hei…

Line 686, Column 7: end tag for element "font" which is not open
```
</font>
```
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.
Line 692, Column 13: there is no attribute "SRC"
```
<IFRAME SRC="http://ads.networkhm.com/tt?id=1038744&referer=" FRAMEBORDER="0" S…
```
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

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

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 692, Column 53: cannot generate system identifier for general entity "referer"
```
…ttp://ads.networkhm.com/tt?id=1038744&referer=" FRAMEBORDER="0" SCROLLING="no"…
```
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 "&" (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 æ 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.
Line 692, Column 53: general entity "referer" not defined and no default entity
```
…ttp://ads.networkhm.com/tt?id=1038744&referer=" FRAMEBORDER="0" SCROLLING="no"…
```
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.
Line 692, Column 60: reference not terminated by REFC delimiter
```
…ds.networkhm.com/tt?id=1038744&referer=" FRAMEBORDER="0" SCROLLING="no" MARGIN…
```
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.
Line 692, Column 60: reference to external entity in attribute value
```
…ds.networkhm.com/tt?id=1038744&referer=" FRAMEBORDER="0" SCROLLING="no" MARGIN…
```
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 '&'.
Line 692, Column 60: reference to entity "referer" for which no system identifier could be generated
```
…ds.networkhm.com/tt?id=1038744&referer=" FRAMEBORDER="0" SCROLLING="no" MARGIN…
```
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.

Line 692, Column 52: entity was defined here

…http://ads.networkhm.com/tt?id=1038744&referer=" FRAMEBORDER="0" SCROLLING="no…

Line 692, Column 75: there is no attribute "FRAMEBORDER"
```
…m/tt?id=1038744&referer=" FRAMEBORDER="0" SCROLLING="no" MARGINHEIGHT="0" MARG…
```
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.
Line 692, Column 89: there is no attribute "SCROLLING"
```
…4&referer=" FRAMEBORDER="0" SCROLLING="no" MARGINHEIGHT="0" MARGINWIDTH="0" TO…
```
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.
Line 692, Column 107: there is no attribute "MARGINHEIGHT"
```
…ORDER="0" SCROLLING="no" MARGINHEIGHT="0" MARGINWIDTH="0" TOPMARGIN="0" LEFTMA…
```
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.
Line 692, Column 123: there is no attribute "MARGINWIDTH"
```
…ING="no" MARGINHEIGHT="0" MARGINWIDTH="0" TOPMARGIN="0" LEFTMARGIN="0" ALLOWTR…
```
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.
Line 692, Column 137: there is no attribute "TOPMARGIN"
```
…NHEIGHT="0" MARGINWIDTH="0" TOPMARGIN="0" LEFTMARGIN="0" ALLOWTRANSPARENCY="tr…
```
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.
Line 692, Column 152: there is no attribute "LEFTMARGIN"
```
…GINWIDTH="0" TOPMARGIN="0" LEFTMARGIN="0" ALLOWTRANSPARENCY="true" WIDTH="728"…
```
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.
Line 692, Column 174: there is no attribute "ALLOWTRANSPARENCY"
```
…="0" LEFTMARGIN="0" ALLOWTRANSPARENCY="true" WIDTH="728" HEIGHT="90" name="I48…
```
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.
Line 692, Column 187: there is no attribute "WIDTH"
```
…ARGIN="0" ALLOWTRANSPARENCY="true" WIDTH="728" HEIGHT="90" name="I48"></IFRAME>
```
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

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

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 692, Column 200: there is no attribute "HEIGHT"
```
…ARGIN="0" ALLOWTRANSPARENCY="true" WIDTH="728" HEIGHT="90" name="I48"></IFRAME>
```
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

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

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 692, Column 210: there is no attribute "name"
```
…ARGIN="0" ALLOWTRANSPARENCY="true" WIDTH="728" HEIGHT="90" name="I48"></IFRAME>
```
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

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

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 692, Column 215: element "IFRAME" undefined
```
…ARGIN="0" ALLOWTRANSPARENCY="true" WIDTH="728" HEIGHT="90" name="I48"></IFRAME>
```
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).
Line 693, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
```
<br>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 693, Column 1: start tag was here
```
<br>
```
Line 700, Column 152: end tag for "br" omitted, but OMITTAG NO was specified
```
…r="#00bdc4" size="2" face="Tahoma"><span style="COLOR: rgb(204,204,204); "><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 ">".

Line 700, Column 148: start tag was here

…r="#00bdc4" size="2" face="Tahoma"><span style="COLOR: rgb(204,204,204); "><br>

Line 710, Column 10: end tag for "br" omitted, but OMITTAG NO was specified
```
laws.<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 ">".
Line 710, Column 6: start tag was here
```
laws.<br>
```
Line 734, Column 30: end tag for "br" omitted, but OMITTAG NO was specified
```
acquired by ZonaSports.me<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 ">".
Line 734, Column 26: start tag was here
```
acquired by ZonaSports.me<br>
```
Line 739, Column 34: end tag for "br" omitted, but OMITTAG NO was specified
```
or is hosted by ZonaSports.me<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 ">".
Line 739, Column 30: start tag was here
```
or is hosted by ZonaSports.me<br>
```
Line 740, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
```
<br>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 740, Column 1: start tag was here
```
<br>
```
Line 757, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
```
causes. <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 ">".
Line 757, Column 9: start tag was here
```
causes. <br>
```
Line 758, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
```
<br>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 758, Column 1: start tag was here
```
<br>
```
Line 759, Column 58: end tag for "br" omitted, but OMITTAG NO was specified
```
</strong>Advertencia<strong style="font-weight: 400"><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 ">".

Line 759, Column 54: start tag was here

</strong>Advertencia<strong style="font-weight: 400"><br>

Line 763, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
```
<br>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 763, Column 1: start tag was here
```
<br>
```
Line 778, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
```
<br>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 778, Column 1: start tag was here
```
<br>
```
Line 785, Column 38: end tag for "br" omitted, but OMITTAG NO was specified
```
servicios ajenos a ZonaSports.me.<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 ">".
Line 785, Column 34: start tag was here
```
servicios ajenos a ZonaSports.me.<br>
```
Line 795, Column 16: end tag for "br" omitted, but OMITTAG NO was specified
```
lo ofrece. <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 ">".
Line 795, Column 12: start tag was here
```
lo ofrece. <br>
```
Line 803, Column 17: end tag for "br" omitted, but OMITTAG NO was specified
```
mencionados.<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 ">".
Line 803, Column 13: start tag was here
```
mencionados.<br>
```
Line 813, Column 27: end tag for element "span" which is not open
```
de derecho de autor.</span></strong></font></font></font></b><span style="color…
```
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.
Line 813, Column 159: end tag for "br" omitted, but OMITTAG NO was specified
```
…: #CCCCCC; font-weight: bold"><font size="3" face="Tahoma" color="#00BDC4"><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 ">".

Line 813, Column 155: start tag was here

…: #CCCCCC; font-weight: bold"><font size="3" face="Tahoma" color="#00BDC4"><br>

Line 816, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
```
<br>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 816, Column 1: start tag was here
```
<br>
```
Line 820, Column 87: end tag for "br" omitted, but OMITTAG NO was specified
```
… amigos!</font><font size="2"><font size="3" face="Tahoma" color="#00BDC4"><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 ">".

Line 820, Column 83: start tag was here

… amigos!</font><font size="2"><font size="3" face="Tahoma" color="#00BDC4"><br>

Line 821, Column 5: end tag for "font" omitted, but OMITTAG NO was specified
```
</h3>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 820, Column 38: start tag was here

con tus amigos!</font><font size="2"><font size="3" face="Tahoma" color="#00BDC…

Line 821, Column 5: end tag for "font" omitted, but OMITTAG NO was specified
```
</h3>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 820, Column 23: start tag was here

con tus amigos!</font><font size="2"><font size="3" face="Tahoma" color="#00BDC…

Line 821, Column 5: end tag for "font" omitted, but OMITTAG NO was specified
```
</h3>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 817, Column 8: start tag was here

</font><font size="3" face="Trebuchet MS" color="#00BDC4">

Line 821, Column 5: end tag for "span" omitted, but OMITTAG NO was specified
```
</h3>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 813, Column 62: start tag was here

…pan></strong></font></font></font></b><span style="color: #CCCCCC; font-weight…

Line 822, Column 7: end tag for element "font" which is not open
```
</font><font size="3" face="Trebuchet MS" color="#00BDC4">
```
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.
Line 824, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
<center>
```
The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 826, Column 75: cannot generate system identifier for general entity "pub"
```
…tton" href="http://www.addthis.com/bookmark.php?v=250&pub=xa-4b11d1d61ebe078e">
```
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 "&" (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 æ 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.
Line 826, Column 75: general entity "pub" not defined and no default entity
```
…tton" href="http://www.addthis.com/bookmark.php?v=250&pub=xa-4b11d1d61ebe078e">
```
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.
Line 826, Column 78: reference not terminated by REFC delimiter
```
…tton" href="http://www.addthis.com/bookmark.php?v=250&pub=xa-4b11d1d61ebe078e">
```
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.
Line 826, Column 78: reference to external entity in attribute value
```
…tton" href="http://www.addthis.com/bookmark.php?v=250&pub=xa-4b11d1d61ebe078e">
```
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 '&'.
Line 826, Column 78: reference to entity "pub" for which no system identifier could be generated
```
…tton" href="http://www.addthis.com/bookmark.php?v=250&pub=xa-4b11d1d61ebe078e">
```
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.

Line 826, Column 74: entity was defined here

…tton" href="http://www.addthis.com/bookmark.php?v=250&pub=xa-4b11d1d61ebe078e">

Line 827, Column 256: end tag for "br" omitted, but OMITTAG NO was specified
```
…/s7.addthis.com/js/250/addthis_widget.js#pub=xa-4b11d1d61ebe078e"></script><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 ">".

Line 827, Column 252: start tag was here

…/s7.addthis.com/js/250/addthis_widget.js#pub=xa-4b11d1d61ebe078e"></script><br>

Line 828, Column 7: end tag for "center" omitted, but OMITTAG NO was specified
```
</font><font size="3" face="Trebuchet MS" color="#00BDC4">
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 824, Column 1: start tag was here
```
<center>
```
Line 829, Column 48: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
<table border="0" width="80%" bgcolor="#CCCCCC">
```
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>").
Line 841, Column 38: there is no attribute "alt"
```
<a href="http://www.histats.com" alt="page hit counter" target="_blank">
```
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.
Line 842, Column 12: there is no attribute "src"
```
<embed src="http://s10.histats.com/138.swf" flashvars="jver=1&acsid=1803107&dom…
```
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.
Line 842, Column 55: there is no attribute "flashvars"
```
…://s10.histats.com/138.swf" flashvars="jver=1&acsid=1803107&domi=4" quality="h…
```
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

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

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 842, Column 63: cannot generate system identifier for general entity "acsid"
```
…istats.com/138.swf" flashvars="jver=1&acsid=1803107&domi=4" quality="high" wid…
```
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 "&" (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 æ 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.
Line 842, Column 63: general entity "acsid" not defined and no default entity
```
…istats.com/138.swf" flashvars="jver=1&acsid=1803107&domi=4" quality="high" wid…
```
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.
Line 842, Column 68: reference not terminated by REFC delimiter
```
…s.com/138.swf" flashvars="jver=1&acsid=1803107&domi=4" quality="high" width="1…
```
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.
Line 842, Column 68: reference to external entity in attribute value
```
…s.com/138.swf" flashvars="jver=1&acsid=1803107&domi=4" quality="high" width="1…
```
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.
Line 842, Column 68: reference to entity "acsid" for which no system identifier could be generated
```
…s.com/138.swf" flashvars="jver=1&acsid=1803107&domi=4" quality="high" width="1…
```
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Line 842, Column 62: entity was defined here

…histats.com/138.swf" flashvars="jver=1&acsid=1803107&domi=4" quality="high" wi…

Line 842, Column 77: cannot generate system identifier for general entity "domi"
```
….swf" flashvars="jver=1&acsid=1803107&domi=4" quality="high" width="112" heigh…
```
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 "&" (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 æ 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.
Line 842, Column 77: general entity "domi" not defined and no default entity
```
….swf" flashvars="jver=1&acsid=1803107&domi=4" quality="high" width="112" heigh…
```
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.
Line 842, Column 81: reference not terminated by REFC delimiter
```
…" flashvars="jver=1&acsid=1803107&domi=4" quality="high" width="112" height="3…
```
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.
Line 842, Column 81: reference to external entity in attribute value
```
…" flashvars="jver=1&acsid=1803107&domi=4" quality="high" width="112" height="3…
```
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 '&'.
Line 842, Column 81: reference to entity "domi" for which no system identifier could be generated
```
…" flashvars="jver=1&acsid=1803107&domi=4" quality="high" width="112" height="3…
```
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.

Line 842, Column 76: entity was defined here

…8.swf" flashvars="jver=1&acsid=1803107&domi=4" quality="high" width="112" heig…

Line 842, Column 93: there is no attribute "quality"
```
…"jver=1&acsid=1803107&domi=4" quality="high" width="112" height="33" name="138…
```
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.
Line 842, Column 106: there is no attribute "width"
```
…=1803107&domi=4" quality="high" width="112" height="33" name="138.swf" align="…
```
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.
Line 842, Column 119: there is no attribute "height"
```
…=4" quality="high" width="112" height="33" name="138.swf" align="middle" type=…
```
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.
Line 842, Column 129: there is no attribute "name"
```
…y="high" width="112" height="33" name="138.swf" align="middle" type="applicati…
```
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.
Line 842, Column 145: there is no attribute "align"
```
…112" height="33" name="138.swf" align="middle" type="application/x-shockwave-f…
```
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.
Line 842, Column 159: there is no attribute "type"
```
…3" name="138.swf" align="middle" type="application/x-shockwave-flash" pluginsp…
```
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.
Line 842, Column 203: there is no attribute "pluginspage"
```
…cation/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashpl…
```
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.
Line 842, Column 255: there is no attribute "wmode"
```
…inspage="http://www.macromedia.com/go/getflashplayer" wmode="transparent"/></a>
```
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

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

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 842, Column 269: element "embed" undefined
```
…inspage="http://www.macromedia.com/go/getflashplayer" wmode="transparent"/></a>
```
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
- incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
- by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
- by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
Line 843, Column 52: character "&" is the first character of a delimiter but occurred as data
```
…rc="http://sstatic1.histats.com/0.gif?1803107&101" alt="contadores" border="0">
```
This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 843, Column 86: end tag for "img" omitted, but OMITTAG NO was specified
```
…rc="http://sstatic1.histats.com/0.gif?1803107&101" alt="contadores" border="0">
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 843, Column 1: start tag was here

<img src="http://sstatic1.histats.com/0.gif?1803107&101" alt="contadores" borde…

Line 844, Column 64: there is no attribute "border"
```
…="0" height="0" scrolling="no" border="0" frameborder="0" src="hits.html">El e…
```
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.
Line 852, Column 4: end tag for element "a" which is not open
```
</a>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 853, Column 136: cannot generate system identifier for general entity "t"
```
…ext.host-tracker.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><nos…
```
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 "&" (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 æ 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.
Line 853, Column 136: general entity "t" not defined and no default entity
```
…ext.host-tracker.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><nos…
```
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.
Line 853, Column 137: reference not terminated by REFC delimiter
```
…xt.host-tracker.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><nosc…
```
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.
Line 853, Column 137: reference to external entity in attribute value
```
…xt.host-tracker.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><nosc…
```
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 '&'.
Line 853, Column 137: reference to entity "t" for which no system identifier could be generated
```
…xt.host-tracker.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><nosc…
```
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.

Line 853, Column 135: entity was defined here

…/ext.host-tracker.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><no…

Line 853, Column 145: cannot generate system identifier for general entity "m"
```
…tracker.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a …
```
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 "&" (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 æ 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.
Line 853, Column 145: general entity "m" not defined and no default entity
```
…tracker.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a …
```
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.
Line 853, Column 146: reference not terminated by REFC delimiter
```
…racker.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a h…
```
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.
Line 853, Column 146: reference to external entity in attribute value
```
…racker.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a h…
```
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 '&'.
Line 853, Column 146: reference to entity "m" for which no system identifier could be generated
```
…racker.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a h…
```
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.

Line 853, Column 144: entity was defined here

…-tracker.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a…

Line 853, Column 152: cannot generate system identifier for general entity "p"
```
….com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="h…
```
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 "&" (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 æ 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.
Line 853, Column 152: general entity "p" not defined and no default entity
```
….com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="h…
```
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.
Line 853, Column 153: reference not terminated by REFC delimiter
```
…com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="ht…
```
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.
Line 853, Column 153: reference to external entity in attribute value
```
…com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="ht…
```
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 '&'.
Line 853, Column 153: reference to entity "p" for which no system identifier could be generated
```
…com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="ht…
```
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.

Line 853, Column 151: entity was defined here

…r.com/uptime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="…

Line 853, Column 160: cannot generate system identifier for general entity "src"
```
…ime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="http://ho…
```
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 "&" (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 æ 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.
Line 853, Column 160: general entity "src" not defined and no default entity
```
…ime-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="http://ho…
```
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.
Line 853, Column 163: reference not terminated by REFC delimiter
```
…-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="http://host-…
```
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.
Line 853, Column 163: reference to external entity in attribute value
```
…-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="http://host-…
```
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 '&'.
Line 853, Column 163: reference to entity "src" for which no system identifier could be generated
```
…-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="http://host-…
```
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.

Line 853, Column 159: entity was defined here

…time-img/?s=15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="http://h…

Line 853, Column 171: end tag for element "a" which is not open
```
…15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="http://host-tracker.…
```
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.
Line 853, Column 171: end tag for "img" omitted, but OMITTAG NO was specified
```
…15&t=525941&m=0.59&p=Total&src=ff"></a><noscript><a href="http://host-tracker.…
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 853, Column 1: start tag was here

<img width="80" height="15" border="0" alt="script monitorizaci n tiempo online…

Line 853, Column 181: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
…1&m=0.59&p=Total&src=ff"></a><noscript><a href="http://host-tracker.com/es/">S…
```
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>").
Line 856, Column 53: end tag for element "font" which is not open
```
…ipt></span></span></font></font></font></font><font size="3" face="Trebuchet M…
```
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.
Line 856, Column 60: end tag for element "font" which is not open
```
…pan></span></font></font></font></font><font size="3" face="Trebuchet MS" colo…
```
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.
Line 856, Column 116: end tag for "br" omitted, but OMITTAG NO was specified
```
…nt></font></font></font><font size="3" face="Trebuchet MS" color="#00BDC4"><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 ">".

Line 856, Column 112: start tag was here

…nt></font></font></font><font size="3" face="Trebuchet MS" color="#00BDC4"><br>

Line 858, Column 11: end tag for "br" omitted, but OMITTAG NO was specified
```
amigos<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 ">".
Line 858, Column 7: start tag was here
```
amigos<br>
```
Line 859, Column 14: end tag for element "font" which is not open
```
</font></font>
```
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.
Line 860, Column 7: end tag for element "span" which is not open
```
</span>
```
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.
Line 866, Column 66: end tag for element "span" which is not open
```
Advertencia legal</a></font><font size="2" color="#00FFFF"></span>
```
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.
Line 889, Column 128: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
…t></a></font></span></font></b></font><span style="letter-spacing: normal"><h3>
```
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>").
Line 891, Column 9: end tag for "span" omitted, but OMITTAG NO was specified
```
</center>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 889, Column 88: start tag was here

…t></a></font></span></font></b></font><span style="letter-spacing: normal"><h3…

Line 892, Column 24: end tag for element "b" which is not open
```
<font face="Tahoma"></b>
```
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.
Line 893, Column 14: end tag for element "span" which is not open
```
</font></span>
```
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.
Line 895, Column 14: end tag for element "font" which is not open
```
</font></font></center>
```
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.
Line 895, Column 23: end tag for element "center" which is not open
```
</font></font></center>
```
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.
Line 896, Column 6: end tag for "td" omitted, but OMITTAG NO was specified
```
</div>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 234, Column 1: start tag was here

<td class="main-bg" valign="top" align="center">

Line 896, Column 6: end tag for "tr" omitted, but OMITTAG NO was specified
```
</div>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 233, Column 1: start tag was here
```
<tr>
```
Line 896, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
```
</div>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 232, Column 1: start tag was here

<table class="side-both" cellspacing="0" cellpadding="0" width="1006">

Line 898, Column 9: end tag for element "strong" which is not open
```
</strong></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.
Line 898, Column 14: end tag for element "td" which is not open
```
</strong></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.
Line 899, Column 5: 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.
Line 900, Column 8: 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.
Line 902, Column 7: end tag for element "font" which is not open
```
</font><font face="Tahoma"></span>
```
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.
Line 902, Column 34: end tag for element "span" which is not open
```
</font><font face="Tahoma"></span>
```
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.
Line 903, Column 16: end tag for element "strong" which is not open
```
</font></strong><font face="Tahoma"></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 903, Column 42: end tag for "font" omitted, but OMITTAG NO was specified
```
</font></strong><font face="Tahoma"></div>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 903, Column 17: start tag was here

</font></strong><font face="Tahoma"></div>

Line 904, Column 7: end tag for element "font" which is not open
```
</font>
```
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.
Line 905, Column 5: 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.
Line 906, Column 5: 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.
Line 907, Column 8: 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.
Line 910, Column 6: end tag for "font" omitted, but OMITTAG NO was specified
```
</div>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 909, Column 1: start tag was here
```
<font face="Tahoma">
```
Line 911, Column 7: end tag for element "font" which is not open
```
</font></span></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 911, Column 14: end tag for element "span" which is not open
```
</font></span></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 911, Column 20: end tag for element "div" which is not open
```
</font></span></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 912, Column 9: end tag for element "strong" which is not open
```
</strong></font></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.
Line 912, Column 16: end tag for element "font" which is not open
```
</strong></font></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.
Line 912, Column 21: end tag for element "td" which is not open
```
</strong></font></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.
Line 913, Column 6: end tag for element "div" which is not open
```
</div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 914, Column 5: 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.
Line 915, Column 8: 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.
Line 917, Column 14: end tag for element "span" which is not open
```
</font></span></strong>
```
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.
Line 917, Column 23: end tag for element "strong" which is not open
```
</font></span></strong>
```
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.
Line 918, Column 41: end tag for element "a" which is not open
```
<span style="letter-spacing: normal"></a></span></font>
```
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.
Line 918, Column 55: end tag for element "font" which is not open
```
<span style="letter-spacing: normal"></a></span></font>
```
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.
Line 919, Column 7: end tag for element "font" which is not open
```
</font></font></font></b></font></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 919, Column 14: end tag for element "font" which is not open
```
</font></font></font></b></font></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 919, Column 21: end tag for element "font" which is not open
```
</font></font></font></b></font></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 919, Column 25: end tag for element "b" which is not open
```
</font></font></font></b></font></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 919, Column 32: end tag for element "font" which is not open
```
</font></font></font></b></font></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 919, Column 38: end tag for element "div" which is not open
```
</font></font></font></b></font></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 920, Column 6: end tag for element "div" which is not open
```
</div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 922, Column 14: end tag for element "span" which is not open
```
</font></span></font></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 922, Column 21: end tag for element "font" which is not open
```
</font></span></font></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 922, Column 27: end tag for element "div" which is not open
```
</font></span></font></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 924, Column 5: 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.
Line 925, Column 5: 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.
Line 926, Column 8: 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.
Line 927, Column 16: end tag for element "strong" which is not open
```
</font></strong></font></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 927, Column 23: end tag for element "font" which is not open
```
</font></strong></font></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 927, Column 29: end tag for element "div" which is not open
```
</font></strong></font></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 929, Column 5: 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.
Line 930, Column 5: 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.
Line 931, Column 8: 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.
Line 932, Column 14: end tag for element "font" which is not open
```
</font></font>
```
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.
Line 934, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
<p></span>
```
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>").
Line 934, Column 10: end tag for "p" omitted, but OMITTAG NO was specified
```
<p></span>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 934, Column 1: start tag was here
```
<p></span>
```
Line 936, Column 4: end tag for element "p" which is not open
```
</p>
```
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.
Line 938, Column 7: end tag for "font" omitted, but OMITTAG NO was specified
```
</html>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 937, Column 1: start tag was here

<font face="Verdana" color="#00bdc4" size="4">

Line 938, Column 7: end tag for "body" omitted, but OMITTAG NO was specified
```
</html>
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 121, Column 1: start tag was here
```
<script> 
```
Line 939, Column 3: document type does not allow element "p" here
```
<p></p>
```
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).
Line 940, Column 7: end tag for element "font" which is not open
```
</font><font face="Tahoma"></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.
Line 940, Column 27: document type does not allow element "font" here
```
</font><font face="Tahoma"></td>
```
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).
Line 940, Column 32: end tag for element "td" which is not open
```
</font><font face="Tahoma"></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.
Line 941, Column 5: 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.
Line 942, Column 8: 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.
Line 944, Column 6: end tag for element "div" which is not open
```
</div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 945, Column 8: document type does not allow element "center" here
```
<center>
```
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).
Line 969, Column 14: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
```
</a><noscript><a href="http://www.histats.com" target="_blank">
```
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>").
Line 970, Column 52: character "&" is the first character of a delimiter but occurred as data
```
…rc="http://sstatic1.histats.com/0.gif?1803107&101" alt="contadores" border="0">
```
This message may appear in several cases:
- You tried to include the "<" character in your page: you should escape it as "<"
- You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&", which is always safe.
- Another possibility is that you forgot to close quotes in a previous tag.
Line 970, Column 86: end tag for "img" omitted, but OMITTAG NO was specified
```
…rc="http://sstatic1.histats.com/0.gif?1803107&101" alt="contadores" border="0">
```
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Line 970, Column 1: start tag was here

<img src="http://sstatic1.histats.com/0.gif?1803107&101" alt="contadores" borde…

Line 973, Column 7: end tag for element "body" which is not open
```
</body>
```
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.
Line 974, Column 7: end tag for element "html" which is not open
```
</html>
```
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.
Line 975, Column 7: end tag for element "body" which is not open
```
</body>
```
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.
Line 981, Column 15: end tag for element "div" which is not open
```
</center></div>
```
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

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

Visitor Analysis

Daily Visitor

15.750 visits

Showsite.us

zonasports.me

Website Meta Analysis

Technical Analysis

HTML Analysis

IP 141.101.116.146 Analysis

In Page Analysis

Outbound Links

Traffic Analysis

Magestic Backlinks

Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

HTML Analysis

HTML validation

Ratio Text/Html

Message Error

Visitor Analysis

Daily Visitor

Daily Visitor

Recently Domain

Recently Update