Just Games Welcome to bubble shooter, this website is fully dedicated to the populair game: Bubble Shooter. You will find various online variants of the game and the possibility to play them all ...

bubbleshooter.net
  • Domain Name
    bubbleshooter.net
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #67190
  • Page Size
    30.5 KB
  • Ip Address
    77.245.52.68
  • Heading
    H1: 0, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 41 JPG, 1 PNG

Website Meta Analysis

  • Title
    Bubble Shooter
  • Meta Keyword
  • Meta Description
    Just Games Welcome to bubble shooter, this website is fully dedicated to the populair game: Bubble Shooter. You will find various online variants of the game and the possibility to play them all for free! Bubble Shooter Bubbles Extreme Woobies ...

Technical Analysis

  • Webserver
    Apache/1.3.37 (Unix) PHP/5.2.2 mod_ssl/2.8.28 OpenSSL/0.9.7e-p1
  • Ip Address
    77.245.52.68
  • Domain Age
    6 Years, 7 Months, 27 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 26 Feb 2013 22:16:16 GMT
  • server: Apache/1.3.37 (Unix) PHP/5.2.2 mod_ssl/2.8.28 OpenSSL/0.9.7e-p1
  • x-powered-by: PHP/5.2.2
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
DOMAIN: BUBBLESHOOTER.NET

owner-contact: P-SUE57
owner-organization: Eijer Media
owner-fname: S
owner-lname: Eijer
owner-street: Hengelstraat 3
owner-city: Rotterdam
owner-zip: 3078XM
owner-country: NL
owner-phone: +31643080726
owner-email: email

admin-contact: P-SUE57
admin-organization: Eijer Media
admin-fname: S
admin-lname: Eijer
admin-street: Hengelstraat 3
admin-city: Rotterdam
admin-zip: 3078XM
admin-country: NL
admin-phone: +31643080726
admin-email: email

tech-contact: P-SUE57
tech-organization: Eijer Media
tech-fname: S
tech-lname: Eijer
tech-street: Hengelstraat 3
tech-city: Rotterdam
tech-zip: 3078XM
tech-country: NL
tech-phone: +31643080726
tech-email: email

billing-contact: P-SUE57
billing-organization: Eijer Media
billing-fname: S
billing-lname: Eijer
billing-street: Hengelstraat 3
billing-city: Rotterdam
billing-zip: 3078XM
billing-country: NL
billing-phone: +31643080726
billing-email: email

nameserver: ns.webair.net
nameserver: ns2.webair.net

DNS Analysis


DNS servers
ns.webair.net
ns2.webair.net


DNS Records

Answer records
bubbleshooter.net SOA
server: ns.webair.net
email: webmaster@bubbleshooter.net
serial: 2008012901
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 43200
43200s
bubbleshooter.net NS  ns.webair.net 43200s
bubbleshooter.net NS  ns2.webair.net 43200s
bubbleshooter.net MX
preference: 10
exchange: filter.bubbleshooter.net
43200s
bubbleshooter.net A 77.245.52.68 43200s

Authority records

Additional records
filter.bubbleshooter.net A 216.130.191.236 43200s

IP 77.245.52.68 Analysis

  • Country Code
    NL
  • Country Code3
    NLD
  • Country Name
    Netherlands
  • City
    EU
  • Continent Code
    52.5° North
  • Latitude
    5.75
  • Longitude
  • No whois ip data for 77.245.52.68

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 103 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.7031079782121115
Message Error
  • Error Line 12, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 16, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/nl_NL/all.js#xfbml=1&appId=176393505778649";

    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 16, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/nl_NL/all.js#xfbml=1&appId=176393505778649";

    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 16, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/nl_NL/all.js#xfbml=1&appId=176393505778649";

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

  • Error Line 16, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/nl_NL/all.js#xfbml=1&appId=176393505778649";

    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 16, Column 56: entity was defined here
      js.src = "//connect.facebook.net/nl_NL/all.js#xfbml=1&appId=176393505778649";
  • Error Line 20, Column 15: element "center" undefined
           <center>   <div class='container'>

    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 22, Column 12: 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 24, Column 99: there is no attribute "border"
    …o.png" width="317" height="85" border="0" align="left" alt="Bubble Shooter" ti…

    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 24, Column 109: there is no attribute "align"
    …th="317" height="85" border="0" align="left" alt="Bubble Shooter" title="Bubbl…

    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 26, Column 27: there is no attribute "height"
    <table width="210" height="80" cellpadding="2px" cellspacing="0" style='border:…

    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 26, Column 162: there is no attribute "align"
    …#000000; padding-right:0px; padding-left:0px; padding-top:10px;' align="right">

    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 28, Column 168: there is no attribute "bgColor"
    …r='#EEEEEE';" onmouseout="this.style.background='#FFFFFF';" bgColor="#FFFFFF"> 

    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 29, Column 43: there is no attribute "target"
    <a href="http://www.justgames.com" target="_blank"><H2>Just Games</h2></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 29, Column 55: element "H2" undefined
    <a href="http://www.justgames.com" target="_blank"><H2>Just Games</h2></a>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 29, Column 70: end tag for element "h2" which is not open
    <a href="http://www.justgames.com" target="_blank"><H2>Just Games</h2></a>

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

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

  • Error Line 29, Column 74: end tag for "H2" omitted, but OMITTAG NO was specified
    <a href="http://www.justgames.com" target="_blank"><H2>Just Games</h2></a>

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

  • Info Line 29, Column 52: start tag was here
    <a href="http://www.justgames.com" target="_blank"><H2>Just Games</h2></a>
  • Error Line 37, Column 108: end tag for "br" omitted, but OMITTAG NO was specified
    …his website is fully dedicated to the populair game: <b>Bubble Shooter</b>.<br>

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

  • Info Line 37, Column 104: start tag was here
    …his website is fully dedicated to the populair game: <b>Bubble Shooter</b>.<br>
  • Error Line 38, Column 107: end tag for element "font" which is not open
    … variants of the game and the possibility to play them all for free!<br></font>

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

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

  • Error Line 38, Column 107: end tag for "br" omitted, but OMITTAG NO was specified
    … variants of the game and the possibility to play them all for free!<br></font>

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

  • Info Line 38, Column 97: start tag was here
    … variants of the game and the possibility to play them all for free!<br></font>
  • Error Line 39, Column 18: there is no attribute "align"
            <p align="center"><font face="Verdana" size="2">

    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 39, Column 38: there is no attribute "face"
            <p align="center"><font face="Verdana" size="2">

    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 39, Column 53: there is no attribute "size"
            <p align="center"><font face="Verdana" size="2">

    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 39, Column 56: element "font" undefined
            <p align="center"><font face="Verdana" size="2">

    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 42, Column 6: end tag for "font" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 39, Column 27: start tag was here
            <p align="center"><font face="Verdana" size="2">
  • Error Line 42, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 39, Column 9: start tag was here
            <p align="center"><font face="Verdana" size="2">
  • Error Line 51, Column 54: element "center" undefined
    …class='maincontent'>           <center><table cellpadding='2px' cellspacing='0…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 51, Column 123: there is no attribute "width"
    …pacing='0' width='100%'><tr><td width="65%" valign="middle">	<div class='conte…

    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 51, Column 228: element "center" undefined
    … class='contentbox'>	 <div style='padding: 4px; text-align: left; '>	  <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 91, Column 9: end tag for "table" omitted, but OMITTAG NO was specified
    </center>

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

  • Info Line 53, Column 1: start tag was here
    <table cellpadding='2px' cellspacing='0' width='100%'>
  • Error Line 92, Column 8: end tag for "div" omitted, but OMITTAG NO was specified
    </table>

    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 51, Column 172: start tag was here
    …n="middle">	<div class='contentbox'>	 <div style='padding: 4px; text-align: le…
  • Error Line 92, Column 8: end tag for "div" omitted, but OMITTAG NO was specified
    </table>

    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 51, Column 146: start tag was here
    …><tr><td width="65%" valign="middle">	<div class='contentbox'>	 <div style='pa…
  • Error Line 92, Column 8: end tag for "td" omitted, but OMITTAG NO was specified
    </table>

    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 51, Column 113: start tag was here
    …2px' cellspacing='0' width='100%'><tr><td width="65%" valign="middle">	<div cl…
  • Error Line 92, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </table>

    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 51, Column 109: start tag was here
    …ng='2px' cellspacing='0' width='100%'><tr><td width="65%" valign="middle">	<di…
  • Error Line 93, Column 5: end tag for element "td" which is not open
    </td>

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

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

  • Error Line 108, Column 10: end tag for element "tr" which is not open
    </td></tr></center></table>     <table cellpadding='0' cellspacing='0' width='1…

    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 108, Column 27: end tag for element "table" which is not open
    </td></tr></center></table>     <table cellpadding='0' cellspacing='0' width='1…

    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 135, Column 20: element "center" undefined
    <br /><br /><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 150, Column 87: end tag for "param" omitted, but OMITTAG NO was specified
    …ame="movie" value="http://www.bubbleshooter.net/games/001_bubble_shooter.swf"> 

    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 150, Column 1: start tag was here
    <param name="movie" value="http://www.bubbleshooter.net/games/001_bubble_shoote…
  • Error Line 151, Column 36: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="quality" value="high"> 

    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 151, Column 1: start tag was here
    <param name="quality" value="high"> 
  • Error Line 152, Column 33: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="play" value="true"> 

    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 152, Column 1: start tag was here
    <param name="play" value="true"> 
  • Error Line 153, Column 34: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="LOOP" value="false"> 

    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 153, Column 1: start tag was here
    <param name="LOOP" value="false"> 
  • Error Line 154, Column 12: there is no attribute "src"
    <embed src="http://www.bubbleshooter.net/games/001_bubble_shooter.swf" width="7…

    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 154, Column 78: there is no attribute "width"
    …t/games/001_bubble_shooter.swf" width="728" height="568" play="true" loop="fal…

    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 154, Column 91: there is no attribute "height"
    …ubble_shooter.swf" width="728" height="568" play="true" loop="false" quality="…

    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 154, Column 102: there is no attribute "play"
    …er.swf" width="728" height="568" play="true" loop="false" quality="high" plugi…

    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 154, Column 114: there is no attribute "loop"
    …h="728" height="568" play="true" loop="false" quality="high" pluginspage="http…

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

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

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

  • Error Line 154, Column 130: there is no attribute "quality"
    …568" play="true" loop="false" quality="high" pluginspage="http://www.macromedi…

    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 154, Column 149: there is no attribute "pluginspage"
    …op="false" quality="high" 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 155, Column 6: there is no attribute "type"
    type="application/x-shockwave-flash"> 

    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 155, Column 37: element "embed" undefined
    type="application/x-shockwave-flash"> 

    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 163, Column 32: there is no attribute "data-href"
    <div class="fb-like" data-href="http://www.facebook.com/pages/Bubbleshootercom/…

    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 163, Column 107: there is no attribute "data-send"
    …shootercom/281955478523577" data-send="false" data-width="450" data-show-faces…

    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 163, Column 126: there is no attribute "data-width"
    …955478523577" data-send="false" data-width="450" data-show-faces="false"></div>

    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 163, Column 148: there is no attribute "data-show-faces"
    …955478523577" data-send="false" data-width="450" data-show-faces="false"></div>

    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 165, Column 11: element "g:plusone" undefined
    <g:plusone></g:plusone>

    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 181, Column 126: element "center" undefined
    …g: 4px; text-align: left; '>	  <center><table cellpadding='2px' cellspacing='0…

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

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

    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 181, Column 127: start tag was here
    …: 4px; text-align: left; '>	  <center><table cellpadding='2px' cellspacing='0'…
  • Error Line 202, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    </center></table></div></div>	<div class='contentbox'>	 <div style='padding: 4p…

    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 181, Column 70: start tag was here
    …/div></div>	<div class='contentbox'>	 <div style='padding: 4px; text-align: le…
  • Error Line 202, Column 17: end tag for "div" omitted, but OMITTAG NO was specified
    </center></table></div></div>	<div class='contentbox'>	 <div style='padding: 4p…

    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 181, Column 44: start tag was here
    …>  </tr></table></center></div></div>	<div class='contentbox'>	 <div style='pa…
  • Error Line 202, Column 17: end tag for "td" omitted, but OMITTAG NO was specified
    </center></table></div></div>	<div class='contentbox'>	 <div style='padding: 4p…

    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 108, Column 101: start tag was here
    …cing='0' width='100%'>      <tr>      <td width='78%' valign='top'>	<div class…
  • Error Line 202, Column 17: end tag for "tr" omitted, but OMITTAG NO was specified
    </center></table></div></div>	<div class='contentbox'>	 <div style='padding: 4p…

    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 108, Column 91: start tag was here
    …0' cellspacing='0' width='100%'>      <tr>      <td width='78%' valign='top'>	…
  • Error Line 202, Column 29: end tag for "center" omitted, but OMITTAG NO was specified
    </center></table></div></div>	<div class='contentbox'>	 <div style='padding: 4p…

    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 22, Column 5: start tag was here
       	<center>
  • Error Line 217, Column 141: element "center" undefined
    …g: 4px; text-align: left; '>	  <center><table cellpadding='2px' cellspacing='0…

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

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

    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 217, Column 142: start tag was here
    …: 4px; text-align: left; '>	  <center><table cellpadding='2px' cellspacing='0'…
  • Error Line 253, Column 17: end tag for element "table" which is not open
    </center></table></div></div>	<div class='contentbox'>	 <div style='padding: 4p…

    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 255, Column 113: required attribute "alt" not specified
    …img src="http://www.bubbleshooter.net/banner.jpg" border="0"><br>Just Games</a>

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

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

  • Error Line 255, Column 114: end tag for "img" omitted, but OMITTAG NO was specified
    …img src="http://www.bubbleshooter.net/banner.jpg" border="0"><br>Just Games</a>

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

  • Info Line 255, Column 52: start tag was here
    …://www.justgames.com" target="_blank"><img src="http://www.bubbleshooter.net/b…
  • Error Line 255, Column 118: end tag for "br" omitted, but OMITTAG NO was specified
    …img src="http://www.bubbleshooter.net/banner.jpg" border="0"><br>Just Games</a>

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

  • Info Line 255, Column 114: start tag was here
    …img src="http://www.bubbleshooter.net/banner.jpg" border="0"><br>Just Games</a>
  • Error Line 258, Column 141: element "center" undefined
    …g: 4px; text-align: left; '>	  <center><table cellpadding='2px' cellspacing='0…

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

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

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

  • Info Line 258, Column 142: start tag was here
    …: 4px; text-align: left; '>	  <center><table cellpadding='2px' cellspacing='0'…
  • Error Line 295, Column 17: end tag for element "table" which is not open
    </center></table></div></div>	<div class='contentbox'>	 <div style='padding: 4p…

    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 297, Column 113: required attribute "alt" not specified
    …img src="http://www.bubbleshooter.net/banner.jpg" border="0"><br>Just Games</a>

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

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

  • Error Line 297, Column 114: end tag for "img" omitted, but OMITTAG NO was specified
    …img src="http://www.bubbleshooter.net/banner.jpg" border="0"><br>Just Games</a>

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

  • Info Line 297, Column 52: start tag was here
    …://www.justgames.com" target="_blank"><img src="http://www.bubbleshooter.net/b…
  • Error Line 297, Column 118: end tag for "br" omitted, but OMITTAG NO was specified
    …img src="http://www.bubbleshooter.net/banner.jpg" border="0"><br>Just Games</a>

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

  • Info Line 297, Column 114: start tag was here
    …img src="http://www.bubbleshooter.net/banner.jpg" border="0"><br>Just Games</a>
  • Error Line 300, Column 141: element "center" undefined
    …g: 4px; text-align: left; '>	  <center><table cellpadding='2px' cellspacing='0…

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

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

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

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

  • Error Line 336, Column 5: end tag for "tr" which is not finished
    </tr>

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

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

  • Error Line 338, Column 9: end tag for "table" omitted, but OMITTAG NO was specified
    </center></table></div></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 300, Column 142: start tag was here
    …: 4px; text-align: left; '>	  <center><table cellpadding='2px' cellspacing='0'…
  • Error Line 338, Column 17: end tag for element "table" which is not open
    </center></table></div></div>	

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

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

  • Error Line 414, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr></td></center></table></div></div>       </td>      <td width='22%' valign…

    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 345, Column 344: start tag was here
    …lign: left; '>	  <table cellpadding='2px' cellspacing='0' width='100%'><tr><td>
  • Error Line 414, Column 10: end tag for element "td" which is not open
    </tr></td></center></table></div></div>       </td>      <td width='22%' valign…

    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 414, Column 19: end tag for "table" omitted, but OMITTAG NO was specified
    </tr></td></center></table></div></div>       </td>      <td width='22%' valign…

    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 345, Column 286: start tag was here
    …'padding: 4px; text-align: left; '>	  <table cellpadding='2px' cellspacing='0'…
  • Error Line 414, Column 19: end tag for "div" omitted, but OMITTAG NO was specified
    </tr></td></center></table></div></div>       </td>      <td width='22%' valign…

    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 345, Column 237: start tag was here
    …d-color: #FFFFFF;'>	  </div>	 </div>	 <div style='padding: 4px; text-align: le…
  • Error Line 414, Column 19: end tag for "div" omitted, but OMITTAG NO was specified
    </tr></td></center></table></div></div>       </td>      <td width='22%' valign…

    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 345, Column 1: start tag was here
    <div class='contentbox'>	 <div class='contentboxheader' style='background-color…
  • Error Line 414, Column 27: end tag for element "table" which is not open
    </tr></td></center></table></div></div>       </td>      <td width='22%' valign…

    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 414, Column 33: end tag for element "div" which is not open
    </tr></td></center></table></div></div>       </td>      <td width='22%' valign…

    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 414, Column 39: end tag for element "div" which is not open
    </tr></td></center></table></div></div>       </td>      <td width='22%' valign…

    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 414, Column 51: end tag for element "td" which is not open
    …d></center></table></div></div>       </td>      <td width='22%' valign='top'>	

    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 414, Column 86: document type does not allow element "td" here
    …d></center></table></div></div>       </td>      <td width='22%' valign='top'>	

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

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

  • Error Line 416, Column 9: end tag for element "center" which is not open
    </center>

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

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

  • Error Line 417, Column 199: element "center" undefined
    …g: 4px; text-align: left; '>	  <center><table cellpadding='2px' cellspacing='0…

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

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

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

  • Info Line 417, Column 200: start tag was here
    …: 4px; text-align: left; '>	  <center><table cellpadding='2px' cellspacing='0'…
  • Error Line 445, Column 17: end tag for element "table" which is not open
    </center></table>

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

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

  • Error Line 449, Column 21: end tag for element "center" which is not open
    </div></div></center></div></div></td>       </tr>     </table>    </div>  </ce…

    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 449, Column 27: end tag for element "div" which is not open
    </div></div></center></div></div></td>       </tr>     </table>    </div>  </ce…

    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 449, Column 33: end tag for element "div" which is not open
    </div></div></center></div></div></td>       </tr>     </table>    </div>  </ce…

    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 449, Column 50: end tag for element "tr" which is not open
    …></center></div></div></td>       </tr>     </table>    </div>  </center>     …

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

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

  • Error Line 449, Column 63: end tag for element "table" which is not open
    …iv></div></td>       </tr>     </table>    </div>  </center>        <center>	 …

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

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

  • Error Line 449, Column 73: end tag for element "div" which is not open
    …/td>       </tr>     </table>    </div>  </center>        <center>	     <div c…

    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 449, Column 84: end tag for element "center" which is not open
    …</tr>     </table>    </div>  </center>        <center>	     <div class='thefo…

    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 449, Column 100: element "center" undefined
    …e>    </div>  </center>        <center>	     <div class='thefooter'>		      	<…

    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 481, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 449, Column 165: start tag was here
    …r'>		      	<div class='contentbox'>	 <div style='padding: 4px; text-align: le…
  • Error Line 481, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 449, Column 139: start tag was here
    …	     <div class='thefooter'>		      	<div class='contentbox'>	 <div style='pa…
  • Error Line 481, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 449, Column 107: start tag was here
    …/div>  </center>        <center>	     <div class='thefooter'>		      	<div cla…
  • Error Line 481, Column 7: end tag for "center" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 449, Column 93: start tag was here
    … </table>    </div>  </center>        <center>	     <div class='thefooter'>		 …

Visitor Analysis

Daily Visitor
  • 2.800 visits
Daily Visitor