bleachget.com

Watch Bleach Episodes English Subbed & Dubbed Movies Online. English Subbed and English Dubbed Streaming. The best place to Watch Bleach Episodes for FREE. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 15-09-2013 12:46:17  (update).

Overview Info

  • Domain Name
    bleachget.com
  • Favicon
  • Alexa Rank
    #24323
  • Google Page Rank
    PR 3
  • Ip Address
    78.152.50.102
  • Page Size
    227.2 KB
  • Images
    1 GIF, 3 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 0 0 0 0

Website Meta Analysis



  • Title
    Watch Bleach Episodes English Subbed & Dubbed Movies Online
  • Meta Keyword
    Bleach Episode, Bleach Episodes, Bleach Manga, Watch Bleach Online, free
  • Meta Description
    Watch Bleach Episodes English Subbed & Dubbed Movies Online. English Subbed and English Dubbed Streaming. The best place to Watch Bleach Episodes for FREE.

Technical Analysis



  • Webserver
    LiteSpeed
  • Ip Address
    78.152.50.102
  • Domain Age
    5 Years, 10 Months, 20 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • x-powered-by: PHP/5.4.16
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-type: text/html
  • date: Sun, 15 Sep 2013 12:45:36 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: bleachget.com
Registrar: Spot Domain LLC

Protected Domain Services Customer ID: DSR-2015068

Expiration Date: 2014-10-27 12:11:40
Creation Date: 2007-10-27 06:11:40

Name Servers:
ns1.domainsite.com
ns2.domainsite.com
ns3.domainsite.com
ns4.domainsite.com

Domain privacy provided by Protected Domain Services. For more information see www.protecteddomainservices.com

REGISTRANT CONTACT INFO
Protected Domain Services - Customer ID: DSR-2015068
P.O. Box 6197
Denver
CO
80206
US
Phone: +1.3034596012
Email Address: email

ADMINISTRATIVE CONTACT INFO
Protected Domain Services - Customer ID: DSR-2015068
P.O. Box 6197
Denver
CO
80206
US
Phone: +1.3034596012
Email Address: email

TECHNICAL CONTACT INFO
Protected Domain Services - Customer ID: DSR-2015068
P.O. Box 6197
Denver
CO
80206
US
Phone: +1.3034596012
Email Address: email

BILLING CONTACT INFO
Protected Domain Services - Customer ID: DSR-2015068
P.O. Box 6197
Denver
CO
80206
US
Phone: +1.3034596012
Email Address: email

Timestamp: 1337412668.8526

The Data in the Spot Domain LLC WHOIS database is provided by Spot Domain LLC for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Spot Domain LLC does not guarantee its accuracy. By submitting a WHOIS query, you agree that you will use this Data only for lawful purposes and that, under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via e-mail (spam); or (2) enable high volume, automated, electronic processes that apply to Spot Domain LLC (or its systems). Spot Domain LLC reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

Cached on: 2012-05-19T01:31:08-06:00

IP 78.152.50.102 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 78.152.50.102

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 82 Errors
  • 23 Warnings
Ratio Text/Html
  • 0.6347399318403535
Message Error
  • Warning Line 5, Column 45: character "&" is the first character of a delimiter but occurred as data
    <title>Watch Bleach Episodes English Subbed & Dubbed Movies Online</title>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 6, Column 72: character "&" is the first character of a delimiter but occurred as data
    …"Watch Bleach Episodes English Subbed & Dubbed Movies Online. English Subbed a…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 11, Column 92: end tag for "link" omitted, but OMITTAG NO was specified
    …tylesheet" type="text/css" href="http://www.bleachget.com/template/global.css">

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

  • Info Line 11, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="http://www.bleachget.com/template/…
  • Error Line 35, Column 18: there is no attribute "language"
    <script language="javascript"><!--

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

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

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

  • Error Line 35, 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>.

  • Error Line 55, Column 48: there is no attribute "target"
    …="separator">&nbsp;</li><li><a target="_blank" href="http://www.mangahit.com">…

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

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

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

  • Error Line 59, Column 8: element "center" undefined
    <center>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 60, Column 67: there is no attribute "align"
    …sition: relative; width: 87em;" align="left"><div id="main"><div id="logo" cla…

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

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

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

  • Error Line 60, Column 187: there is no attribute "border"
    …ttp://www.bleachget.com/"><img border="0" src="http://www.bleachget.com/templa…

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

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

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

  • Error Line 60, Column 337: end tag for "img" omitted, but OMITTAG NO was specified
    …sodes English Subbed &amp; Dubbed"></a></div><div id="links" class="clr"><a 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 ">".

  • Info Line 60, Column 175: start tag was here
    …"><a href="http://www.bleachget.com/"><img border="0" src="http://www.bleachge…
  • Error Line 63, Column 3: element "u" undefined
    <u>Bleach Episode 366</u></a>. Next Bleach Episode: 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 65, Column 3: element "u" undefined
    <u>Bleach Episode 367</u></a>. Read the latest Bleach Manga online: <a target="…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 65, Column 121: element "u" undefined
    …ank" href="http://www.mangahit.com"><u>Bleach Chapter 524</u></a>.</div><div><…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 69, Column 12: there is no attribute "id"
    <iframe id="" name="I1" allowtransparency="1" frameborder="0" height="90" scrol…

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

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

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

  • Error Line 69, Column 20: there is no attribute "name"
    <iframe id="" name="I1" allowtransparency="1" frameborder="0" height="90" scrol…

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

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

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

  • Error Line 69, Column 43: there is no attribute "allowtransparency"
    …ame id="" name="I1" allowtransparency="1" frameborder="0" height="90" scrollin…

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

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

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

  • Error Line 69, Column 59: there is no attribute "frameborder"
    …I1" allowtransparency="1" frameborder="0" height="90" scrolling="no" width="72…

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

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

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

  • Error Line 69, Column 70: there is no attribute "height"
    …ansparency="1" frameborder="0" height="90" scrolling="no" width="728" src="htt…

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

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

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

  • Error Line 69, Column 85: there is no attribute "scrolling"
    …frameborder="0" height="90" scrolling="no" width="728" src="http://www.bleachg…

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

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

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

  • Error Line 69, Column 96: there is no attribute "width"
    …="0" height="90" scrolling="no" width="728" src="http://www.bleachget.com/ads/…

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

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

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

  • Error Line 69, Column 106: there is no attribute "src"
    …t="90" scrolling="no" width="728" src="http://www.bleachget.com/ads/728x90.htm…

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

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

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

  • Error Line 69, Column 148: element "iframe" undefined
    …lling="no" width="728" src="http://www.bleachget.com/ads/728x90.html"></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).
  • Error Line 73, Column 78: there is no attribute "width"
    … cellpadding="0" cellspacing="0"><tr><td width="50%" valign="top" align="left">

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

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

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

  • Error Line 75, Column 12: there is no attribute "size"
    <font size="2"><b>Bleach Episode 281 English Dubbed</b></font></a><br /><i>Late…

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

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

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

  • Error Line 75, Column 15: element "font" undefined
    <font size="2"><b>Bleach Episode 281 English Dubbed</b></font></a><br /><i>Late…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 75, Column 98: end tag for "br" omitted, but OMITTAG NO was specified
    …nt></a><br /><i>Latest Episode</i><br>Episode Title: Crown of Lies, Barragan's…

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

  • Info Line 75, Column 94: start tag was here
    …</font></a><br /><i>Latest Episode</i><br>Episode Title: Crown of Lies, Barrag…
  • Error Line 76, Column 15: element "font" undefined
    <font size="2"><b>Bleach Episode 280 English Dubbed</b></font></a><br /><i>Late…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 76, Column 98: end tag for "br" omitted, but OMITTAG NO was specified
    …nt></a><br /><i>Latest Episode</i><br>Episode Title: Hisagi and T&#333;sen, th…

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

  • Info Line 76, Column 94: start tag was here
    …</font></a><br /><i>Latest Episode</i><br>Episode Title: Hisagi and T&#333;sen…
  • Warning Line 78, Column 43855: character "&" is the first character of a delimiter but occurred as data
    …/a> <br />Imprisonment?! Senbonzakura & Zabimaru</td></tr></table></td><td wid…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 78, Column 54359: character "&" is the first character of a delimiter but occurred as data
    …/a> <br />Friendship? Hatred? Haineko & Tobiume</td></tr></table></td></tr></t…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 78, Column 61058: character "&" is the first character of a delimiter but occurred as data
    …/a> <br />The Most Evil Tag!? Soi Fon & Omaeda</td></tr></table></td></tr></ta…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 78, Column 152966: there is no attribute "src"
    …></table></td></tr></table><embed src="http://www.bleachget.com/player/bleachg…

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

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

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

  • Error Line 78, Column 153034: there is no attribute "quality"
    …er/bleachget_gao_gamebox.swf" quality="high" width="728" height="176" wmode="w…

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

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

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

  • Error Line 78, Column 153047: there is no attribute "width"
    …gao_gamebox.swf" quality="high" width="728" height="176" wmode="window" 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.

  • Error Line 78, Column 153060: there is no attribute "height"
    …wf" quality="high" width="728" height="176" wmode="window" type="application/x…

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

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

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

  • Error Line 78, Column 153072: there is no attribute "wmode"
    …"high" width="728" height="176" wmode="window" 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.

  • Error Line 78, Column 153086: there is no attribute "type"
    …728" height="176" wmode="window" 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.

  • Error Line 78, Column 153130: 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.

  • Error Line 78, Column 153175: element "embed" undefined
    …/www.macromedia.com/go/getflashplayer"><noembed><a href="http://www.game-adver…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 78, Column 153184: element "noembed" undefined
    …omedia.com/go/getflashplayer"><noembed><a href="http://www.game-advertising-on…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 78, Column 153575: required attribute "alt" not specified
    …l/p-57mrc03j0BaV2.gif' style='display: none;' height='1' width='1'/></noscript>

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

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

  • Error Line 78, Column 153575: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    …l/p-57mrc03j0BaV2.gif' style='display: none;' height='1' width='1'/></noscript>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 79, Column 6: end tag for "embed" omitted, but OMITTAG NO was specified
    </div><div id="side-b"><center>

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

  • Info Line 78, Column 152955: start tag was here
    …n!</td></tr></table></td></tr></table><embed src="http://www.bleachget.com/pla…
  • Error Line 79, Column 31: element "center" undefined
    </div><div id="side-b"><center>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 80, Column 22: there is no attribute "marginheight"
    <iframe marginheight="0" marginwidth="0" scrolling="no" frameborder="0" width="…

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

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

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

  • Error Line 80, Column 38: there is no attribute "marginwidth"
    <iframe marginheight="0" marginwidth="0" scrolling="no" frameborder="0" width="…

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

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

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

  • Warning Line 80, Column 167: cannot generate system identifier for general entity "id"
    …ng-online.com/index.php?section=serve&id=1436" target="_blank"></iframe><nofra…

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

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

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

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

  • Error Line 80, Column 167: general entity "id" not defined and no default entity
    …ng-online.com/index.php?section=serve&id=1436" target="_blank"></iframe><nofra…

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

  • Warning Line 80, Column 169: reference not terminated by REFC delimiter
    …-online.com/index.php?section=serve&id=1436" target="_blank"></iframe><noframe…

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

  • Warning Line 80, Column 169: reference to external entity in attribute value
    …-online.com/index.php?section=serve&id=1436" target="_blank"></iframe><noframe…

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

  • Error Line 80, Column 169: reference to entity "id" for which no system identifier could be generated
    …-online.com/index.php?section=serve&id=1436" target="_blank"></iframe><noframe…

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

  • Info Line 80, Column 166: entity was defined here
    …ing-online.com/index.php?section=serve&id=1436" target="_blank"></iframe><nofr…
  • Error Line 80, Column 183: there is no attribute "target"
    …dex.php?section=serve&id=1436" target="_blank"></iframe><noframes>Game adverti…

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

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

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

  • Error Line 80, Column 191: element "iframe" undefined
    …section=serve&id=1436" target="_blank"></iframe><noframes>Game advertisements …

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 80, Column 210: element "noframes" undefined
    …36" target="_blank"></iframe><noframes>Game advertisements by <a href="http://…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 81, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 81, Column 1: start tag was here
    <br>
  • Error Line 82, Column 135: required attribute "alt" not specified
    …if" border="0" height="81" width="160"></a></p><p><a href="http://www.dbz.tv/"…

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

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

  • Error Line 82, Column 139: end tag for "img" omitted, but OMITTAG NO was specified
    …border="0" height="81" width="160"></a></p><p><a href="http://www.dbz.tv/"><fo…

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

  • Info Line 82, Column 49: start tag was here
    …et="_blank" href="http://www.dbz.tv/"><img src="http://www.narutoget.com/image…
  • Error Line 82, Column 190: element "font" undefined
    …><p><a href="http://www.dbz.tv/"><font size="4">Watch Dragonball</font></a></p>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 83, Column 150: element "iframe" undefined
    …="no" width="160" src="http://www.bleachget.com/ads/120x600.html"></iframe><br>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 83, Column 164: end tag for "br" omitted, but OMITTAG NO was specified
    …="no" width="160" src="http://www.bleachget.com/ads/120x600.html"></iframe><br>

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

  • Info Line 83, Column 160: start tag was here
    …="no" width="160" src="http://www.bleachget.com/ads/120x600.html"></iframe><br>
  • Warning Line 84, Column 85: cannot generate system identifier for general entity "m"
    …a.fastclick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><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 "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

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

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

  • Error Line 84, Column 85: general entity "m" not defined and no default entity
    …a.fastclick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><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.

  • Warning Line 84, Column 86: reference not terminated by REFC delimiter
    ….fastclick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><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.

  • Warning Line 84, Column 86: reference to external entity in attribute value
    ….fastclick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><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 '&amp;'.

  • Error Line 84, Column 86: reference to entity "m" for which no system identifier could be generated
    ….fastclick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><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.

  • Info Line 84, Column 84: entity was defined here
    …ia.fastclick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a…
  • Warning Line 84, Column 89: cannot generate system identifier for general entity "tp"
    …stclick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href…

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

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

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

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

  • Error Line 84, Column 89: general entity "tp" not defined and no default entity
    …stclick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href…

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

  • Warning Line 84, Column 91: reference not terminated by REFC delimiter
    …click.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="…

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

  • Warning Line 84, Column 91: reference to external entity in attribute value
    …click.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="…

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

  • Error Line 84, Column 91: reference to entity "tp" for which no system identifier could be generated
    …click.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="…

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

  • Info Line 84, Column 88: entity was defined here
    …astclick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a hre…
  • Warning Line 84, Column 94: cannot generate system identifier for general entity "d"
    …ck.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="htt…

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

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

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

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

  • Error Line 84, Column 94: general entity "d" not defined and no default entity
    …ck.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="htt…

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

  • Warning Line 84, Column 95: reference not terminated by REFC delimiter
    …k.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="http…

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

  • Warning Line 84, Column 95: reference to external entity in attribute value
    …k.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="http…

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

  • Error Line 84, Column 95: reference to entity "d" for which no system identifier could be generated
    …k.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="http…

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

  • Info Line 84, Column 93: entity was defined here
    …ick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="ht…
  • Warning Line 84, Column 98: cannot generate system identifier for general entity "t"
    …et/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="http://…

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

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

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

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

  • Error Line 84, Column 98: general entity "t" not defined and no default entity
    …et/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="http://…

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

  • Warning Line 84, Column 99: reference not terminated by REFC delimiter
    …t/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="http://m…

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

  • Warning Line 84, Column 99: reference to external entity in attribute value
    …t/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="http://m…

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

  • Error Line 84, Column 99: reference to entity "t" for which no system identifier could be generated
    …t/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="http://m…

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

  • Info Line 84, Column 97: entity was defined here
    …net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="http:/…
  • Error Line 84, Column 102: required attribute "type" not specified
    …/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="http://medi…

    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>.

  • Warning Line 84, Column 182: reference not terminated by REFC delimiter
    …fastclick.net/w/click.here?sid=49608&m=7&c=1" target="_blank"><img src="http:/…

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

  • Warning Line 84, Column 182: reference to external entity in attribute value
    …fastclick.net/w/click.here?sid=49608&m=7&c=1" target="_blank"><img src="http:/…

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

  • Error Line 84, Column 182: reference to entity "m" for which no system identifier could be generated
    …fastclick.net/w/click.here?sid=49608&m=7&c=1" target="_blank"><img src="http:/…

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

  • Info Line 84, Column 84: entity was defined here
    …ia.fastclick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a…
  • Warning Line 84, Column 185: cannot generate system identifier for general entity "c"
    …tclick.net/w/click.here?sid=49608&m=7&c=1" target="_blank"><img src="http://me…

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

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

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

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

  • Error Line 84, Column 185: general entity "c" not defined and no default entity
    …tclick.net/w/click.here?sid=49608&m=7&c=1" target="_blank"><img src="http://me…

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

  • Warning Line 84, Column 186: reference not terminated by REFC delimiter
    …click.net/w/click.here?sid=49608&m=7&c=1" target="_blank"><img src="http://med…

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

  • Warning Line 84, Column 186: reference to external entity in attribute value
    …click.net/w/click.here?sid=49608&m=7&c=1" target="_blank"><img src="http://med…

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

  • Error Line 84, Column 186: reference to entity "c" for which no system identifier could be generated
    …click.net/w/click.here?sid=49608&m=7&c=1" target="_blank"><img src="http://med…

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

  • Info Line 84, Column 184: entity was defined here
    …stclick.net/w/click.here?sid=49608&m=7&c=1" target="_blank"><img src="http://m…
  • Error Line 84, Column 205: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …ere?sid=49608&m=7&c=1" target="_blank"><img src="http://media.fastclick.net/w/…

    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>").

  • Warning Line 84, Column 266: reference not terminated by REFC delimiter
    ….fastclick.net/w/get.media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 bo…

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

  • Warning Line 84, Column 266: reference to external entity in attribute value
    ….fastclick.net/w/get.media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 bo…

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

  • Error Line 84, Column 266: reference to entity "m" for which no system identifier could be generated
    ….fastclick.net/w/get.media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 bo…

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

  • Info Line 84, Column 84: entity was defined here
    …ia.fastclick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a…
  • Warning Line 84, Column 271: reference not terminated by REFC delimiter
    …click.net/w/get.media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=…

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

  • Warning Line 84, Column 271: reference to external entity in attribute value
    …click.net/w/get.media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=…

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

  • Error Line 84, Column 271: reference to entity "tp" for which no system identifier could be generated
    …click.net/w/get.media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=…

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

  • Info Line 84, Column 88: entity was defined here
    …astclick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a hre…
  • Warning Line 84, Column 275: reference not terminated by REFC delimiter
    …k.net/w/get.media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=1></…

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

  • Warning Line 84, Column 275: reference to external entity in attribute value
    …k.net/w/get.media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=1></…

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

  • Error Line 84, Column 275: reference to entity "d" for which no system identifier could be generated
    …k.net/w/get.media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=1></…

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

  • Info Line 84, Column 93: entity was defined here
    …ick.net/w/get.media?sid=49608&m=7&tp=9&d=j&t=n"></script><noscript><a href="ht…
  • Warning Line 84, Column 279: reference not terminated by REFC delimiter
    …t/w/get.media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=1></a></…

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

  • Warning Line 84, Column 279: reference to external entity in attribute value
    …t/w/get.media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=1></a></…

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

  • Error Line 84, Column 279: reference to entity "c" for which no system identifier could be generated
    …t/w/get.media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=1></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.

  • Info Line 84, Column 184: entity was defined here
    …stclick.net/w/click.here?sid=49608&m=7&c=1" target="_blank"><img src="http://m…
  • Error Line 84, Column 289: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=1></a></noscript>
  • Error Line 84, Column 300: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=1></a></noscript>
  • Error Line 84, Column 311: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=1></a></noscript>
  • Error Line 84, Column 312: required attribute "alt" not specified
    …media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=1></a></noscript>

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

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

  • Error Line 84, Column 316: end tag for "img" omitted, but OMITTAG NO was specified
    …media?sid=49608&m=7&tp=9&d=s&c=1" width=180 height=150 border=1></a></noscript>

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

  • Info Line 84, Column 206: start tag was here
    …re?sid=49608&m=7&c=1" target="_blank"><img src="http://media.fastclick.net/w/g…
  • Error Line 85, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><p><b>Upcoming Episodes:<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 ">".

  • Info Line 85, Column 1: start tag was here
    <br><br><p><b>Upcoming Episodes:<br></b>
  • Error Line 85, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><p><b>Upcoming Episodes:<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 ">".

  • Info Line 85, Column 5: start tag was here
    <br><br><p><b>Upcoming Episodes:<br></b>
  • Error Line 85, Column 40: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><p><b>Upcoming Episodes:<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 ">".

  • Info Line 85, Column 33: start tag was here
    <br><br><p><b>Upcoming Episodes:<br></b>
  • Error Line 86, Column 91: end tag for "br" omitted, but OMITTAG NO was specified
    …de-368/">Bleach Episode 368</a><br></p></center><b>&nbsp;</b></div></p></div><…

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

  • Info Line 86, Column 84: start tag was here
    …h-episode-368/">Bleach Episode 368</a><br></p></center><b>&nbsp;</b></div></p>…
  • Error Line 86, Column 123: end tag for element "p" which is not open
    …br></p></center><b>&nbsp;</b></div></p></div></div></div><div id="footer" clas…

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

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

  • Error Line 87, Column 15: element "font" undefined
    <font size="2"><a target="_blank" href="http://bleachget.chatango.com">Larger C…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 87, Column 250: element "iframe" undefined
    …://www.bleachget.com/ads/300x250.html"></iframe>&nbsp;</td><td style="border-s…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 87, Column 361: there is no attribute "SRC"
    … valign="top" width="63%"><IFRAME SRC="http://www.bleachget.com/template/chat.…

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

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

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

  • Error Line 87, Column 418: there is no attribute "FRAMEBORDER"
    …et.com/template/chat.htm" FRAMEBORDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCR…

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

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

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

  • Error Line 87, Column 434: there is no attribute "MARGINWIDTH"
    …chat.htm" FRAMEBORDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDT…

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

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

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

  • Error Line 87, Column 451: there is no attribute "MARGINHEIGHT"
    …RDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="612" HEIGHT="3…

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

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

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

  • Error Line 87, Column 465: there is no attribute "SCROLLING"
    …NWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="612" HEIGHT="309"></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.

  • Error Line 87, Column 476: there is no attribute "WIDTH"
    …MARGINHEIGHT="0" SCROLLING="NO" WIDTH="612" HEIGHT="309"></IFRAME></td></tr><t…

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

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

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

  • Error Line 87, Column 489: there is no attribute "HEIGHT"
    …"0" SCROLLING="NO" WIDTH="612" HEIGHT="309"></IFRAME></td></tr><tr><td style="…

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

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

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

  • Error Line 87, Column 494: element "IFRAME" undefined
    …CROLLING="NO" WIDTH="612" HEIGHT="309"></IFRAME></td></tr><tr><td style="borde…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 87, Column 608: there is no attribute "style"
    … valign="top" colspan="2"><font style="font-size: 9pt;"><b>Affiliates: </b><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.

  • Error Line 87, Column 625: element "font" undefined
    …span="2"><font style="font-size: 9pt;"><b>Affiliates: </b><a target="_blank" h…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 87, Column 753: element "font" undefined
    …a></font><font style="font-size: 9pt;"> - </font><span style="font-size: 9pt">…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 87, Column 895: element "font" undefined
    …a></span><font style="font-size: 9pt;"> - <a target="_blank" href="http://www.…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 87, Column 1059: element "font" undefined
    … -</font><font style="font-size: 9pt;"> <a target="_blank" href="http://www.an…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 87, Column 2033: element "center" undefined
    …center><div id="spacer" style="height:15px;">&nbsp;</div><center></body></html>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 87, Column 2040: end tag for "center" omitted, but OMITTAG NO was specified
    …center><div id="spacer" style="height:15px;">&nbsp;</div><center></body></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 ">".

  • Info Line 87, Column 2026: start tag was here
    …center><div id="spacer" style="height:15px;">&nbsp;</div><center></body></html>

Visitor Analysis

Daily Visitor
  • 7.000 visits

In Page Analysis