Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 31,
Column 105:
required attribute "alt" not specified
…g/index.php?c=Dokumentation"><img src="http://hd-area.org/button/doku.jpg"></a>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 31,
Column 109:
end tag for "img" omitted, but OMITTAG NO was specified
…g/index.php?c=Dokumentation"><img src="http://hd-area.org/button/doku.jpg"></a>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 31,
Column 60:
start tag was here
…d-area.org/index.php?c=Dokumentation"><img src="http://hd-area.org/button/doku……ea.org/index.php?c=Serien"><img src="http://hd-area.org/button/serien.jpg"></a>The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.
Typical values for type are
type="text/css" for <style>
and type="text/javascript" for <script>.
Line 32,
Column 104:
end tag for "img" omitted, but OMITTAG NO was specified
…ea.org/index.php?c=Serien"><img src="http://hd-area.org/button/serien.jpg"></a>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 32,
Column 53:
start tag was here
…//www.hd-area.org/index.php?c=Serien"><img src="http://hd-area.org/button/seri…<br><b>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 52,
Column 1:
start tag was here
<br><b><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 53,
Column 1:
start tag was here
<br>euer hda team wünscht euch einen guten ruscht ins neue jahr<br><br>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 54,
Column 60:
start tag was here
euer hda team wünscht euch einen guten ruscht ins neue jahr<br><br>euer hda team wünscht euch einen guten ruscht ins neue jahr<br><br>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 54,
Column 64:
start tag was here
euer hda team wünscht euch einen guten ruscht ins neue jahr<br><br><br><br>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 56,
Column 1:
start tag was here
<br><br><br><br>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 56,
Column 5:
start tag was here
<br><br><center><img border="0" alt="Wir Speichern Nicht" src="http://e-pic.biz/img/21B…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 59,
Column 8:
document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
<center><br><p>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 59,
Column 13:
end tag for "br" omitted, but OMITTAG NO was specified
<center><br><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 59,
Column 9:
start tag was here
<center><br><p><br><br>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 60,
Column 1:
start tag was here
<br><br><br><br>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 60,
Column 5:
start tag was here
<br><br></b>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 59,
Column 13:
start tag was here
<center><br><p></b>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 59,
Column 1:
start tag was here
<center><br><p></p></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 261,
Column 5:
end tag for "ul" omitted, but OMITTAG NO was specified
</li>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 258,
Column 42:
start tag was here
<li><a href="index.php?s=Musik">Musik</a><ul></ul></li>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 274,
Column 4:
document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
<li><a href="index.php?s=XXX">XXX</a><ul>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 286,
Column 5:
end tag for element "ul" which is not open
</ul>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 299,
Column 3631:
end tag for element "a" which is not open
…H.XXX.1080p.MP4-KTR">QuebecProductions.17.04.20.A...</a></span><br /></a><br />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 325,
Column 131:
element "nobr" undefined
….DUBBED.DL.1080p.WebHD.x264-TVP"><nobr><h1>American.Horror.Story.S07.GERMAN.DU…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:
Line 403,
Column 10:
ID "title" already defined
<div id="title" class="title">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 324,
Column 10:
ID "title" first defined here
<div id="title" class="title">…N.DUBBED.DL.720p.WebHD.x264-TVP"><nobr><h1>American.Horror.Story.S07.GERMAN.DU…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:
Line 482,
Column 10:
ID "title" already defined
<div id="title" class="title">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 324,
Column 10:
ID "title" first defined here
<div id="title" class="title">….DUBBED.DL.720p.WebHD.h264-euHD"><nobr><h1>Elementary.S05.GERMAN.DUBBED.DL.720…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:
Line 573,
Column 10:
ID "title" already defined
<div id="title" class="title">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 324,
Column 10:
ID "title" first defined here
<div id="title" class="title">….S01.GERMAN.720p.HDTV.x264-ACED"><nobr><h1>SMILF.S01.GERMAN.720p.HDTV.x264-ACE…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:
Line 649,
Column 10:
ID "title" already defined
<div id="title" class="title">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 324,
Column 10:
ID "title" first defined here
<div id="title" class="title">…DL.DUBBED.1080p.WebHD.x264-AIDA"><nobr><h1>The.Grand.Tour.S02.German.DL.DUBBED…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:
Line 724,
Column 10:
ID "title" already defined
<div id="title" class="title">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 324,
Column 10:
ID "title" first defined here
<div id="title" class="title">….DL.DUBBED.720p.WebHD.x264-AIDA"><nobr><h1>The.Grand.Tour.S02.German.DL.DUBBED…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:
Line 799,
Column 10:
ID "title" already defined
<div id="title" class="title">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 324,
Column 10:
ID "title" first defined here
<div id="title" class="title">…MAN.DUBBED.720p.HDTV.x264-ZZGtv"><nobr><h1>The.Exorcist.S02.GERMAN.DUBBED.720p…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:
Line 871,
Column 10:
ID "title" already defined
<div id="title" class="title">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 324,
Column 10:
ID "title" first defined here
<div id="title" class="title">….DL.720p.BluRay.x264-GOREHOUNDS"><nobr><h1>The.Villainess.GERMAN.2017.DL.720p.…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:
Line 938,
Column 10:
ID "title" already defined
<div id="title" class="title">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 324,
Column 10:
ID "title" first defined here
<div id="title" class="title">…man.DL.AC3.1080p.WebHD.x265-FuN"><nobr><h1>Bright.2017.German.DL.AC3.1080p.Web…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:
Line 1005,
Column 10:
ID "title" already defined
<div id="title" class="title">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 324,
Column 10:
ID "title" first defined here
<div id="title" class="title">…man.DL.AC3.1080p.WebHD.x265-FuN"><nobr><h1>Stranger.Things.S01.COMPLETE.German…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:
Line 1072,
Column 91:
cannot generate system identifier for general entity "s"
…ked">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><li…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 1072,
Column 91:
general entity "s" not defined and no default entity
…ked">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><li…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 1072,
Column 92:
reference not terminated by REFC delimiter
…ed">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><li>…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 1072,
Column 92:
reference to external entity in attribute value
…ed">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><li>…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 1072,
Column 92:
reference to entity "s" for which no system identifier could be generated
…ed">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><li>…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 1072,
Column 90:
entity was defined here
…nked">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><l……age 2">2</a> </li><li><a href="?pg=3&s=default" title="Page 3">3</a> </li><li>…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 1072,
Column 148:
reference to external entity in attribute value
…age 2">2</a> </li><li><a href="?pg=3&s=default" title="Page 3">3</a> </li><li>…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 1072,
Column 148:
reference to entity "s" for which no system identifier could be generated
…age 2">2</a> </li><li><a href="?pg=3&s=default" title="Page 3">3</a> </li><li>…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 1072,
Column 90:
entity was defined here
…nked">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><l……age 3">3</a> </li><li><a href="?pg=4&s=default" title="Page 4">4</a> </li><li>…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 1072,
Column 204:
reference to external entity in attribute value
…age 3">3</a> </li><li><a href="?pg=4&s=default" title="Page 4">4</a> </li><li>…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 1072,
Column 204:
reference to entity "s" for which no system identifier could be generated
…age 3">3</a> </li><li><a href="?pg=4&s=default" title="Page 4">4</a> </li><li>…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 1072,
Column 90:
entity was defined here
…nked">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><l……age 4">4</a> </li><li><a href="?pg=5&s=default" title="Page 5">5</a> </li><li>…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 1072,
Column 260:
reference to external entity in attribute value
…age 4">4</a> </li><li><a href="?pg=5&s=default" title="Page 5">5</a> </li><li>…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 1072,
Column 260:
reference to entity "s" for which no system identifier could be generated
…age 4">4</a> </li><li><a href="?pg=5&s=default" title="Page 5">5</a> </li><li>…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 1072,
Column 90:
entity was defined here
…nked">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><l……age 5">5</a> </li><li><a href="?pg=6&s=default" title="Page 6">6</a> </li><li>…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 1072,
Column 316:
reference to external entity in attribute value
…age 5">5</a> </li><li><a href="?pg=6&s=default" title="Page 6">6</a> </li><li>…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 1072,
Column 316:
reference to entity "s" for which no system identifier could be generated
…age 5">5</a> </li><li><a href="?pg=6&s=default" title="Page 6">6</a> </li><li>…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 1072,
Column 90:
entity was defined here
…nked">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><l……age 6">6</a> </li><li><a href="?pg=7&s=default" title="Page 7">7</a> </li><li>…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 1072,
Column 372:
reference to external entity in attribute value
…age 6">6</a> </li><li><a href="?pg=7&s=default" title="Page 7">7</a> </li><li>…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 1072,
Column 372:
reference to entity "s" for which no system identifier could be generated
…age 6">6</a> </li><li><a href="?pg=7&s=default" title="Page 7">7</a> </li><li>…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 1072,
Column 90:
entity was defined here
…nked">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><l……age 7">7</a> </li><li><a href="?pg=8&s=default" title="Page 8">8</a> </li><li>…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 1072,
Column 428:
reference to external entity in attribute value
…age 7">7</a> </li><li><a href="?pg=8&s=default" title="Page 8">8</a> </li><li>…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 1072,
Column 428:
reference to entity "s" for which no system identifier could be generated
…age 7">7</a> </li><li><a href="?pg=8&s=default" title="Page 8">8</a> </li><li>…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 1072,
Column 90:
entity was defined here
…nked">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><l……age 8">8</a> </li><li><a href="?pg=9&s=default" title="Page 9">9</a> </li><li>…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 1072,
Column 484:
reference to external entity in attribute value
…age 8">8</a> </li><li><a href="?pg=9&s=default" title="Page 9">9</a> </li><li>…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 1072,
Column 484:
reference to entity "s" for which no system identifier could be generated
…age 8">8</a> </li><li><a href="?pg=9&s=default" title="Page 9">9</a> </li><li>…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 1072,
Column 90:
entity was defined here
…nked">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><l……ge 9">9</a> </li><li><a href="?pg=10&s=default" title="Page 10">10</a> </li><l…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 1072,
Column 541:
reference to external entity in attribute value
…ge 9">9</a> </li><li><a href="?pg=10&s=default" title="Page 10">10</a> </li><l…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 1072,
Column 541:
reference to entity "s" for which no system identifier could be generated
…ge 9">9</a> </li><li><a href="?pg=10&s=default" title="Page 10">10</a> </li><l…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 1072,
Column 90:
entity was defined here
…nked">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><l……0</a> </li><li>... <a href="?pg=2092&s=default" title="Page 2092">2092</a></li…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 1072,
Column 606:
reference to external entity in attribute value
…0</a> </li><li>... <a href="?pg=2092&s=default" title="Page 2092">2092</a></li…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 1072,
Column 606:
reference to entity "s" for which no system identifier could be generated
…0</a> </li><li>... <a href="?pg=2092&s=default" title="Page 2092">2092</a></li…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 1072,
Column 90:
entity was defined here
…nked">1</span> </li><li><a href="?pg=2&s=default" title="Page 2">2</a> </li><l…</body>You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 1078,
Column 1:
start tag was here
<div id="footer">