toongames.com

ToonGames is a free online cartoon flash games site where you can find games from all your favorite cartoons such as Ben10, Dora, Tom and Jerry, Spongebob and many more! ...

Display Widget for this domain on your website. Click Here
This data was last updated from 10-08-2013 02:11:20  (update).

Overview Info

  • Domain Name
    toongames.com
  • Favicon
  • Alexa Rank
    #23056
  • Google Page Rank
    PR 5
  • Ip Address
    108.162.199.162
  • Page Size
    38.4 KB
  • Images
    0 GIF, 17 JPG, 79 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    23 0 0 0 0 0

Website Meta Analysis



  • Title
    Home - ToonGames.com
  • Meta Keyword
    cartoon games, toongames, ben10, kids games, flash games, fun games, tom and jerry games, spongebob games, action games, adventure games, community
  • Meta Description
    ToonGames is a free online cartoon flash games site where you can find games from all your favorite cartoons such as Ben10, Dora, Tom and Jerry, Spongebob and many more!

Technical Analysis



  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.199.162
  • Domain Age
    12 Years, 1 Months, 4 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: cloudflare-nginx
  • date: Sat, 10 Aug 2013 14:11:19 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3
  • vary: Accept-Encoding
  • last-modified: Sat, 10 Aug 2013 13:32:26 GMT
  • expires: Sat, 10 Aug 2013 18:11:19 GMT
  • cf-cache-status: HIT
  • cache-control: public, max-age=14400
  • cf-ray: 9bd464c701f05af
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: TOONGAMES.COM
Created on: 10-Jul-01
Expires on: 10-Jul-16
Last Updated on: 18-Sep-12

Registrant:
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States

Administrative Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Technical Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Domain servers in listed order:
LILY.NS.CLOUDFLARE.COM
NORM.NS.CLOUDFLARE.COM

DNS Analysis


DNS servers
lily.ns.cloudflare.com [173.245.58.130]
norm.ns.cloudflare.com [173.245.59.134]


DNS Records

Answer records
toongames.com NS  lily.ns.cloudflare.com 86400s
toongames.com MX
preference: 10
exchange: ASPMX.L.GOOGLE.com
300s
toongames.com MX
preference: 30
exchange: ALT2.ASPMX.L.GOOGLE.com
300s
toongames.com SOA
server: lily.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2012120918
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s
toongames.com MX
preference: 50
exchange: ASPMX3.GOOGLEMAIL.com
300s
toongames.com NS  norm.ns.cloudflare.com 86400s
toongames.com A 108.162.199.162 300s
toongames.com A 108.162.198.162 300s
toongames.com MX
preference: 40
exchange: ASPMX2.GOOGLEMAIL.com
300s
toongames.com MX
preference: 20
exchange: ALT1.ASPMX.L.GOOGLE.com
300s

Authority records

Additional records

IP 108.162.199.162 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 108.162.199.162"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=108.162.199.162?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 108.162.192.0 - 108.162.255.255
    CIDR: 108.162.192.0/18
    OriginAS: AS13335
    NetName: CLOUDFLARENET
    NetHandle: NET-108-162-192-0-1
    Parent: NET-108-0-0-0-0
    NetType: Direct Assignment
    Comment: http://www.cloudflare.com
    RegDate: 2011-10-28
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-108-162-192-0-1


    OrgName: CloudFlare, Inc.
    OrgId: CLOUD14
    Address: 665 Third Street #207
    City: San Francisco
    StateProv: CA
    PostalCode: 94107
    Country: US
    RegDate: 2010-07-09
    Updated: 2013-01-04
    Comment: http://www.cloudflare.com/
    Ref: http://whois.arin.net/rest/org/CLOUD14

    OrgNOCHandle: NOC11962-ARIN
    OrgNOCName: NOC
    OrgNOCPhone: +1-650-319-8930
    OrgNOCEmail: noc@cloudflare.com
    OrgNOCRef: http://whois.arin.net/rest/poc/NOC11962-ARIN

    OrgAbuseHandle: ABUSE2916-ARIN
    OrgAbuseName: Abuse
    OrgAbusePhone: +1-650-319-8930
    OrgAbuseEmail: abuse@cloudflare.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE2916-ARIN

    OrgTechHandle: ADMIN2521-ARIN
    OrgTechName: Admin
    OrgTechPhone: +1-650-319-8930
    OrgTechEmail: admin@cloudflare.com
    OrgTechRef: http://whois.arin.net/rest/poc/ADMIN2521-ARIN

    RNOCHandle: NOC11962-ARIN
    RNOCName: NOC
    RNOCPhone: +1-650-319-8930
    RNOCEmail: noc@cloudflare.com
    RNOCRef: http://whois.arin.net/rest/poc/NOC11962-ARIN

    RTechHandle: ADMIN2521-ARIN
    RTechName: Admin
    RTechPhone: +1-650-319-8930
    RTechEmail: admin@cloudflare.com
    RTechRef: http://whois.arin.net/rest/poc/ADMIN2521-ARIN

    RAbuseHandle: ABUSE2916-ARIN
    RAbuseName: Abuse
    RAbusePhone: +1-650-319-8930
    RAbuseEmail: abuse@cloudflare.com
    RAbuseRef: http://whois.arin.net/rest/poc/ABUSE2916-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 28 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.7962029826436606
Message Error
  • Error Line 16, Column 68: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">   

    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 16, Column 1: start tag was here
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">   
  • Warning Line 35, Column 91: cannot generate system identifier for general entity "rotateur"
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=32863"></script>

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

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

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

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

  • Error Line 35, Column 91: general entity "rotateur" not defined and no default entity
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=32863"></script>

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

  • Warning Line 35, Column 99: reference not terminated by REFC delimiter
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=32863"></script>

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

  • Warning Line 35, Column 99: reference to external entity in attribute value
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=32863"></script>

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

  • Error Line 35, Column 99: reference to entity "rotateur" for which no system identifier could be generated
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=32863"></script>

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

  • Info Line 35, Column 90: entity was defined here
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=32863"></script>
  • Error Line 40, Column 14: there is no attribute "text"
    <script text="text/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 40, Column 31: required attribute "type" not specified
    <script text="text/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 56, Column 7: end tag for element "head" which is not open
    </head>

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

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

  • Error Line 59, Column 40: document type does not allow element "div" here; assuming missing "body" start-tag
    <div style='margin:0 auto;width:860px;'>
  • Error Line 73, Column 28: there is no attribute "alt"
                        <a alt='en' class='lang' href='http://www.toongames.com/en'>

    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 74, Column 95: required attribute "alt" not specified
    …        <img src='http://cdn.toongames.com/templates/red/images/lang/en.png' />

    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 80, Column 95: required attribute "alt" not specified
    …        <img src='http://cdn.toongames.com/templates/red/images/lang/br.png' />

    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 86, Column 95: required attribute "alt" not specified
    …        <img src='http://cdn.toongames.com/templates/red/images/lang/fr.png' />

    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 92, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/es.png' />

    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 98, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/de.png' />

    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 104, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/jp.png' />

    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 110, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/iz.png' />

    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 116, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/kr.png' />

    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 122, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/ch.png' />

    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 128, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/th.png' />

    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 134, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/tl.png' />

    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 140, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/tr.png' />

    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 146, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/rm.png' />

    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 152, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/ro.png' />

    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 158, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/sa.png' />

    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 164, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/be.png' />

    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 170, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/ar.png' />

    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 176, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/mx.png' />

    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 182, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/hr.png' />

    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 188, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/hu.png' />

    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 194, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/da.png' />

    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 200, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/sk.png' />

    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 206, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/fn.png' />

    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 212, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/it.png' />

    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 218, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/nl.png' />

    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 224, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/nr.png' />

    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 230, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/pl.png' />

    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 236, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/cz.png' />

    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 242, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/gr.png' />

    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 248, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/sr.png' />

    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 254, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/sw.png' />

    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 260, Column 127: required attribute "alt" not specified
    …eight:16px;' src='http://cdn.toongames.com/templates/red/images/lang/uk.png' />

    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 265, Column 76: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                        <input id='lang_val' name='lang' type='hidden' value=''>

    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 265, Column 77: end tag for "input" omitted, but OMITTAG NO was specified
                        <input id='lang_val' name='lang' type='hidden' value=''>

    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 265, Column 21: start tag was here
                        <input id='lang_val' name='lang' type='hidden' value=''>
  • Error Line 272, Column 94: required attribute "alt" not specified
    …     <img src='http://www.toongames.com/templates/red/images/toongames6.jpg' />

    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 289, Column 131: required attribute "alt" not specified
    …om/templates/red/images/Sign in.png' /><a style='padding-right:3px;' href='htt…

    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 289, Column 360: required attribute "alt" not specified
    …/templates/red/images/Top games.png' /><a style='padding-right:3px;' href='htt…

    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 290, Column 97: required attribute "alt" not specified
    …m/templates/red/images/Homepage.png' /><a href='http://www.toongames.com'>Home…

    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 290, Column 248: required attribute "alt" not specified
    …/templates/red/images/Community.png' /><a href='http://www.toongames.com/commu…

    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 290, Column 410: required attribute "alt" not specified
    …/templates/red/images/New games.gif' /><a href='http://www.toongames.com/login…

    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 290, Column 574: required attribute "alt" not specified
    …es/red/images/Sign up for free!.png' /><a href='http://www.toongames.com/regis…

    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 294, Column 78: cannot generate system identifier for general entity "utm_medium"
    …free-games/452/mario?utm_source=games&utm_medium=mario_banner"target="_blank">…

    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 294, Column 78: general entity "utm_medium" not defined and no default entity
    …free-games/452/mario?utm_source=games&utm_medium=mario_banner"target="_blank">…

    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 294, Column 88: reference not terminated by REFC delimiter
    …/452/mario?utm_source=games&utm_medium=mario_banner"target="_blank"><img src="…

    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 294, Column 88: reference to external entity in attribute value
    …/452/mario?utm_source=games&utm_medium=mario_banner"target="_blank"><img src="…

    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 294, Column 88: reference to entity "utm_medium" for which no system identifier could be generated
    …/452/mario?utm_source=games&utm_medium=mario_banner"target="_blank"><img src="…

    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 294, Column 77: entity was defined here
    …/free-games/452/mario?utm_source=games&utm_medium=mario_banner"target="_blank"…
  • Error Line 294, Column 109: there is no attribute "target"
    …=games&utm_medium=mario_banner"target="_blank"><img src="http://cdn.toongames.…

    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 294, Column 171: required attribute "alt" not specified
    …nner"target="_blank"><img src="http://cdn.toongames.com/images/banner.gif"></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 294, Column 175: end tag for "img" omitted, but OMITTAG NO was specified
    …nner"target="_blank"><img src="http://cdn.toongames.com/images/banner.gif"></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 294, Column 118: start tag was here
    …m_medium=mario_banner"target="_blank"><img src="http://cdn.toongames.com/image…
  • Warning Line 303, Column 107: cannot generate system identifier for general entity "q"
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>

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

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&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 303, Column 107: general entity "q" not defined and no default entity
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>

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

  • Warning Line 303, Column 108: reference not terminated by REFC delimiter
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>

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

  • Warning Line 303, Column 108: reference to external entity in attribute value
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>

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

  • Error Line 303, Column 108: reference to entity "q" for which no system identifier could be generated
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 303, Column 115: cannot generate system identifier for general entity "ts"
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>

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

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&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 303, Column 115: general entity "ts" not defined and no default entity
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>

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

  • Warning Line 303, Column 117: reference not terminated by REFC delimiter
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>

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

  • Warning Line 303, Column 117: reference to external entity in attribute value
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>

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

  • Error Line 303, Column 117: reference to entity "ts" for which no system identifier could be generated
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 304, Column 108: reference not terminated by REFC delimiter
    …w.toongames.com/index.php?task=search&q=avatar&ts=avatar'>Avatar Games</a></li>

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

  • Warning Line 304, Column 108: reference to external entity in attribute value
    …w.toongames.com/index.php?task=search&q=avatar&ts=avatar'>Avatar Games</a></li>

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

  • Error Line 304, Column 108: reference to entity "q" for which no system identifier could be generated
    …w.toongames.com/index.php?task=search&q=avatar&ts=avatar'>Avatar Games</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 304, Column 118: reference not terminated by REFC delimiter
    …w.toongames.com/index.php?task=search&q=avatar&ts=avatar'>Avatar Games</a></li>

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

  • Warning Line 304, Column 118: reference to external entity in attribute value
    …w.toongames.com/index.php?task=search&q=avatar&ts=avatar'>Avatar Games</a></li>

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

  • Error Line 304, Column 118: reference to entity "ts" for which no system identifier could be generated
    …w.toongames.com/index.php?task=search&q=avatar&ts=avatar'>Avatar Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 305, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=astro boy&ts=astro-boy'>Astro Boy</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 305, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=astro boy&ts=astro-boy'>Astro Boy</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 305, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=astro boy&ts=astro-boy'>Astro Boy</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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 305, Column 121: reference not terminated by REFC delimiter
    …oongames.com/index.php?task=search&q=astro boy&ts=astro-boy'>Astro Boy</a></li>

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

  • Warning Line 305, Column 121: reference to external entity in attribute value
    …oongames.com/index.php?task=search&q=astro boy&ts=astro-boy'>Astro Boy</a></li>

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

  • Error Line 305, Column 121: reference to entity "ts" for which no system identifier could be generated
    …oongames.com/index.php?task=search&q=astro boy&ts=astro-boy'>Astro Boy</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 306, Column 108: reference not terminated by REFC delimiter
    …w.toongames.com/index.php?task=search&q=batman&ts=batman'>Batman Games</a></li>

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

  • Warning Line 306, Column 108: reference to external entity in attribute value
    …w.toongames.com/index.php?task=search&q=batman&ts=batman'>Batman Games</a></li>

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

  • Error Line 306, Column 108: reference to entity "q" for which no system identifier could be generated
    …w.toongames.com/index.php?task=search&q=batman&ts=batman'>Batman Games</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 306, Column 118: reference not terminated by REFC delimiter
    …w.toongames.com/index.php?task=search&q=batman&ts=batman'>Batman Games</a></li>

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

  • Warning Line 306, Column 118: reference to external entity in attribute value
    …w.toongames.com/index.php?task=search&q=batman&ts=batman'>Batman Games</a></li>

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

  • Error Line 306, Column 118: reference to entity "ts" for which no system identifier could be generated
    …w.toongames.com/index.php?task=search&q=batman&ts=batman'>Batman Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 307, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=bejeweled&ts=bejeweled'>Bejeweled</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 307, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=bejeweled&ts=bejeweled'>Bejeweled</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 307, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=bejeweled&ts=bejeweled'>Bejeweled</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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 307, Column 121: reference not terminated by REFC delimiter
    …oongames.com/index.php?task=search&q=bejeweled&ts=bejeweled'>Bejeweled</a></li>

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

  • Warning Line 307, Column 121: reference to external entity in attribute value
    …oongames.com/index.php?task=search&q=bejeweled&ts=bejeweled'>Bejeweled</a></li>

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

  • Error Line 307, Column 121: reference to entity "ts" for which no system identifier could be generated
    …oongames.com/index.php?task=search&q=bejeweled&ts=bejeweled'>Bejeweled</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 308, Column 108: reference not terminated by REFC delimiter
    …ww.toongames.com/index.php?task=search&q=ben10&ts=ben-10'>Ben 10 Games</a></li>

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

  • Warning Line 308, Column 108: reference to external entity in attribute value
    …ww.toongames.com/index.php?task=search&q=ben10&ts=ben-10'>Ben 10 Games</a></li>

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

  • Error Line 308, Column 108: reference to entity "q" for which no system identifier could be generated
    …ww.toongames.com/index.php?task=search&q=ben10&ts=ben-10'>Ben 10 Games</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 308, Column 117: reference not terminated by REFC delimiter
    …ww.toongames.com/index.php?task=search&q=ben10&ts=ben-10'>Ben 10 Games</a></li>

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

  • Warning Line 308, Column 117: reference to external entity in attribute value
    …ww.toongames.com/index.php?task=search&q=ben10&ts=ben-10'>Ben 10 Games</a></li>

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

  • Error Line 308, Column 117: reference to entity "ts" for which no system identifier could be generated
    …ww.toongames.com/index.php?task=search&q=ben10&ts=ben-10'>Ben 10 Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 309, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=billy and mandy&ts=billy-and-mandy'>Bil…

    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 309, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=billy and mandy&ts=billy-and-mandy'>Bil…

    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 309, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=billy and mandy&ts=billy-and-mandy'>Bil…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 309, Column 127: reference not terminated by REFC delimiter
    …x.php?task=search&q=billy and mandy&ts=billy-and-mandy'>Billy And Mandy</a></l…

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

  • Warning Line 309, Column 127: reference to external entity in attribute value
    …x.php?task=search&q=billy and mandy&ts=billy-and-mandy'>Billy And Mandy</a></l…

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

  • Error Line 309, Column 127: reference to entity "ts" for which no system identifier could be generated
    …x.php?task=search&q=billy and mandy&ts=billy-and-mandy'>Billy And Mandy</a></l…

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 310, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=captain america&ts=captain-america'>Cap…

    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 310, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=captain america&ts=captain-america'>Cap…

    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 310, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=captain america&ts=captain-america'>Cap…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 310, Column 127: reference not terminated by REFC delimiter
    …x.php?task=search&q=captain america&ts=captain-america'>Captain America</a></l…

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

  • Warning Line 310, Column 127: reference to external entity in attribute value
    …x.php?task=search&q=captain america&ts=captain-america'>Captain America</a></l…

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

  • Error Line 310, Column 127: reference to entity "ts" for which no system identifier could be generated
    …x.php?task=search&q=captain america&ts=captain-america'>Captain America</a></l…

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 311, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=danny phantom&ts=danny-phantom'>Danny P…

    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 311, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=danny phantom&ts=danny-phantom'>Danny P…

    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 311, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=danny phantom&ts=danny-phantom'>Danny P…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 311, Column 125: reference not terminated by REFC delimiter
    …/index.php?task=search&q=danny phantom&ts=danny-phantom'>Danny Phantom</a></li>

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

  • Warning Line 311, Column 125: reference to external entity in attribute value
    …/index.php?task=search&q=danny phantom&ts=danny-phantom'>Danny Phantom</a></li>

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

  • Error Line 311, Column 125: reference to entity "ts" for which no system identifier could be generated
    …/index.php?task=search&q=danny phantom&ts=danny-phantom'>Danny Phantom</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 312, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=dora&ts=dora'>Dora the Explorer</a></li…

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

  • Warning Line 312, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=dora&ts=dora'>Dora the Explorer</a></li…

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

  • Error Line 312, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=dora&ts=dora'>Dora the Explorer</a></li…

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 312, Column 116: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=dora&ts=dora'>Dora the Explorer</a></li>

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

  • Warning Line 312, Column 116: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=dora&ts=dora'>Dora the Explorer</a></li>

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

  • Error Line 312, Column 116: reference to entity "ts" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=dora&ts=dora'>Dora the Explorer</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 313, Column 108: reference not terminated by REFC delimiter
    …/www.toongames.com/index.php?task=search&q=diego&ts=diego'>Diego Games</a></li>

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

  • Warning Line 313, Column 108: reference to external entity in attribute value
    …/www.toongames.com/index.php?task=search&q=diego&ts=diego'>Diego Games</a></li>

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

  • Error Line 313, Column 108: reference to entity "q" for which no system identifier could be generated
    …/www.toongames.com/index.php?task=search&q=diego&ts=diego'>Diego Games</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 313, Column 117: reference not terminated by REFC delimiter
    …/www.toongames.com/index.php?task=search&q=diego&ts=diego'>Diego Games</a></li>

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

  • Warning Line 313, Column 117: reference to external entity in attribute value
    …/www.toongames.com/index.php?task=search&q=diego&ts=diego'>Diego Games</a></li>

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

  • Error Line 313, Column 117: reference to entity "ts" for which no system identifier could be generated
    …/www.toongames.com/index.php?task=search&q=diego&ts=diego'>Diego Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 314, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=disney fairies&ts=disney-fairies'>Disne…

    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 314, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=disney fairies&ts=disney-fairies'>Disne…

    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 314, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=disney fairies&ts=disney-fairies'>Disne…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 314, Column 126: reference not terminated by REFC delimiter
    …dex.php?task=search&q=disney fairies&ts=disney-fairies'>Disney Fairies</a></li>

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

  • Warning Line 314, Column 126: reference to external entity in attribute value
    …dex.php?task=search&q=disney fairies&ts=disney-fairies'>Disney Fairies</a></li>

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

  • Error Line 314, Column 126: reference to entity "ts" for which no system identifier could be generated
    …dex.php?task=search&q=disney fairies&ts=disney-fairies'>Disney Fairies</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 315, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=fairly odd parents&ts=fairly-odd-parent…

    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 315, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=fairly odd parents&ts=fairly-odd-parent…

    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 315, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=fairly odd parents&ts=fairly-odd-parent…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 315, Column 130: reference not terminated by REFC delimiter
    …hp?task=search&q=fairly odd parents&ts=fairly-odd-parents'>Fairly Odd Parents<…

    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 315, Column 130: reference to external entity in attribute value
    …hp?task=search&q=fairly odd parents&ts=fairly-odd-parents'>Fairly Odd Parents<…

    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 315, Column 130: reference to entity "ts" for which no system identifier could be generated
    …hp?task=search&q=fairly odd parents&ts=fairly-odd-parents'>Fairly Odd Parents<…

    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 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 316, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=fanboy &-chum-chum&ts=fanboy-&-chum-chu…

    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 316, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=fanboy &-chum-chum&ts=fanboy-&-chum-chu…

    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 316, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=fanboy &-chum-chum&ts=fanboy-&-chum-chu…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 316, Column 116: character "&" is the first character of a delimiter but occurred as data
    …es.com/index.php?task=search&q=fanboy &-chum-chum&ts=fanboy-&-chum-chum'>Fanbo…

    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 316, Column 130: reference not terminated by REFC delimiter
    …hp?task=search&q=fanboy &-chum-chum&ts=fanboy-&-chum-chum'>Fanboy &amp; Chum C…

    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 316, Column 130: reference to external entity in attribute value
    …hp?task=search&q=fanboy &-chum-chum&ts=fanboy-&-chum-chum'>Fanboy &amp; Chum C…

    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 316, Column 130: reference to entity "ts" for which no system identifier could be generated
    …hp?task=search&q=fanboy &-chum-chum&ts=fanboy-&-chum-chum'>Fanboy &amp; Chum C…

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 316, Column 138: character "&" is the first character of a delimiter but occurred as data
    …search&q=fanboy &-chum-chum&ts=fanboy-&-chum-chum'>Fanboy &amp; Chum Chum</a><…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 317, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=flintstones&ts=flintstones'>Flintstones…

    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 317, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=flintstones&ts=flintstones'>Flintstones…

    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 317, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=flintstones&ts=flintstones'>Flintstones…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 317, Column 123: reference not terminated by REFC delimiter
    …es.com/index.php?task=search&q=flintstones&ts=flintstones'>Flintstones</a></li>

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

  • Warning Line 317, Column 123: reference to external entity in attribute value
    …es.com/index.php?task=search&q=flintstones&ts=flintstones'>Flintstones</a></li>

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

  • Error Line 317, Column 123: reference to entity "ts" for which no system identifier could be generated
    …es.com/index.php?task=search&q=flintstones&ts=flintstones'>Flintstones</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 318, Column 108: reference not terminated by REFC delimiter
    …/www.toongames.com/index.php?task=search&q=g force&ts=g-force'>G Force</a></li>

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

  • Warning Line 318, Column 108: reference to external entity in attribute value
    …/www.toongames.com/index.php?task=search&q=g force&ts=g-force'>G Force</a></li>

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

  • Error Line 318, Column 108: reference to entity "q" for which no system identifier could be generated
    …/www.toongames.com/index.php?task=search&q=g force&ts=g-force'>G Force</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 318, Column 119: reference not terminated by REFC delimiter
    …/www.toongames.com/index.php?task=search&q=g force&ts=g-force'>G Force</a></li>

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

  • Warning Line 318, Column 119: reference to external entity in attribute value
    …/www.toongames.com/index.php?task=search&q=g force&ts=g-force'>G Force</a></li>

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

  • Error Line 318, Column 119: reference to entity "ts" for which no system identifier could be generated
    …/www.toongames.com/index.php?task=search&q=g force&ts=g-force'>G Force</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 319, Column 108: reference not terminated by REFC delimiter
    …w.toongames.com/index.php?task=search&q=gi joe&ts=gi-joe'>Gi JOE Games</a></li>

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

  • Warning Line 319, Column 108: reference to external entity in attribute value
    …w.toongames.com/index.php?task=search&q=gi joe&ts=gi-joe'>Gi JOE Games</a></li>

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

  • Error Line 319, Column 108: reference to entity "q" for which no system identifier could be generated
    …w.toongames.com/index.php?task=search&q=gi joe&ts=gi-joe'>Gi JOE Games</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 319, Column 118: reference not terminated by REFC delimiter
    …w.toongames.com/index.php?task=search&q=gi joe&ts=gi-joe'>Gi JOE Games</a></li>

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

  • Warning Line 319, Column 118: reference to external entity in attribute value
    …w.toongames.com/index.php?task=search&q=gi joe&ts=gi-joe'>Gi JOE Games</a></li>

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

  • Error Line 319, Column 118: reference to entity "ts" for which no system identifier could be generated
    …w.toongames.com/index.php?task=search&q=gi joe&ts=gi-joe'>Gi JOE Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 320, Column 108: reference not terminated by REFC delimiter
    …http://www.toongames.com/index.php?task=search&q=h2o&ts=h2o'>H2o Games</a></li>

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

  • Warning Line 320, Column 108: reference to external entity in attribute value
    …http://www.toongames.com/index.php?task=search&q=h2o&ts=h2o'>H2o Games</a></li>

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

  • Error Line 320, Column 108: reference to entity "q" for which no system identifier could be generated
    …http://www.toongames.com/index.php?task=search&q=h2o&ts=h2o'>H2o Games</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 320, Column 115: reference not terminated by REFC delimiter
    …http://www.toongames.com/index.php?task=search&q=h2o&ts=h2o'>H2o Games</a></li>

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

  • Warning Line 320, Column 115: reference to external entity in attribute value
    …http://www.toongames.com/index.php?task=search&q=h2o&ts=h2o'>H2o Games</a></li>

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

  • Error Line 320, Column 115: reference to entity "ts" for which no system identifier could be generated
    …http://www.toongames.com/index.php?task=search&q=h2o&ts=h2o'>H2o Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 321, Column 108: reference not terminated by REFC delimiter
    …ww.toongames.com/index.php?task=search&q=hulk&ts=hulk'>Incredible Hulk</a></li>

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

  • Warning Line 321, Column 108: reference to external entity in attribute value
    …ww.toongames.com/index.php?task=search&q=hulk&ts=hulk'>Incredible Hulk</a></li>

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

  • Error Line 321, Column 108: reference to entity "q" for which no system identifier could be generated
    …ww.toongames.com/index.php?task=search&q=hulk&ts=hulk'>Incredible Hulk</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 321, Column 116: reference not terminated by REFC delimiter
    …ww.toongames.com/index.php?task=search&q=hulk&ts=hulk'>Incredible Hulk</a></li>

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

  • Warning Line 321, Column 116: reference to external entity in attribute value
    …ww.toongames.com/index.php?task=search&q=hulk&ts=hulk'>Incredible Hulk</a></li>

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

  • Error Line 321, Column 116: reference to entity "ts" for which no system identifier could be generated
    …ww.toongames.com/index.php?task=search&q=hulk&ts=hulk'>Incredible Hulk</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 322, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=iron-man&ts=iron man'>Iron Man Games</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 322, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=iron-man&ts=iron man'>Iron Man Games</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 322, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=iron-man&ts=iron man'>Iron Man Games</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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 322, Column 120: reference not terminated by REFC delimiter
    …games.com/index.php?task=search&q=iron-man&ts=iron man'>Iron Man Games</a></li>

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

  • Warning Line 322, Column 120: reference to external entity in attribute value
    …games.com/index.php?task=search&q=iron-man&ts=iron man'>Iron Man Games</a></li>

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

  • Error Line 322, Column 120: reference to entity "ts" for which no system identifier could be generated
    …games.com/index.php?task=search&q=iron-man&ts=iron man'>Iron Man Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 323, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=jungle-book&ts=jungle-book'>Jungle Book…

    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 323, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=jungle-book&ts=jungle-book'>Jungle Book…

    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 323, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=jungle-book&ts=jungle-book'>Jungle Book…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 323, Column 123: reference not terminated by REFC delimiter
    …es.com/index.php?task=search&q=jungle-book&ts=jungle-book'>Jungle Book</a></li>

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

  • Warning Line 323, Column 123: reference to external entity in attribute value
    …es.com/index.php?task=search&q=jungle-book&ts=jungle-book'>Jungle Book</a></li>

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

  • Error Line 323, Column 123: reference to entity "ts" for which no system identifier could be generated
    …es.com/index.php?task=search&q=jungle-book&ts=jungle-book'>Jungle Book</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 324, Column 108: reference not terminated by REFC delimiter
    …w.toongames.com/index.php?task=search&q=kailan&ts=kailan'>Kailan Games</a></li>

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

  • Warning Line 324, Column 108: reference to external entity in attribute value
    …w.toongames.com/index.php?task=search&q=kailan&ts=kailan'>Kailan Games</a></li>

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

  • Error Line 324, Column 108: reference to entity "q" for which no system identifier could be generated
    …w.toongames.com/index.php?task=search&q=kailan&ts=kailan'>Kailan Games</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 324, Column 118: reference not terminated by REFC delimiter
    …w.toongames.com/index.php?task=search&q=kailan&ts=kailan'>Kailan Games</a></li>

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

  • Warning Line 324, Column 118: reference to external entity in attribute value
    …w.toongames.com/index.php?task=search&q=kailan&ts=kailan'>Kailan Games</a></li>

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

  • Error Line 324, Column 118: reference to entity "ts" for which no system identifier could be generated
    …w.toongames.com/index.php?task=search&q=kailan&ts=kailan'>Kailan Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 325, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=lilo & stitch&ts=lilo-&-stitch'>Lilo-&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 325, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=lilo & stitch&ts=lilo-&-stitch'>Lilo-&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 325, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=lilo & stitch&ts=lilo-&-stitch'>Lilo-&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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 325, Column 114: character "&" is the first character of a delimiter but occurred as data
    …ames.com/index.php?task=search&q=lilo & stitch&ts=lilo-&-stitch'>Lilo-&amp;-St…

    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 325, Column 125: reference not terminated by REFC delimiter
    …dex.php?task=search&q=lilo & stitch&ts=lilo-&-stitch'>Lilo-&amp;-Stitch</a></l…

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

  • Warning Line 325, Column 125: reference to external entity in attribute value
    …dex.php?task=search&q=lilo & stitch&ts=lilo-&-stitch'>Lilo-&amp;-Stitch</a></l…

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

  • Error Line 325, Column 125: reference to entity "ts" for which no system identifier could be generated
    …dex.php?task=search&q=lilo & stitch&ts=lilo-&-stitch'>Lilo-&amp;-Stitch</a></l…

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 325, Column 131: character "&" is the first character of a delimiter but occurred as data
    …ex.php?task=search&q=lilo & stitch&ts=lilo-&-stitch'>Lilo-&amp;-Stitch</a></li>

    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 326, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=looney tunes&ts=looney-tunes'>Looney Tu…

    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 326, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=looney tunes&ts=looney-tunes'>Looney Tu…

    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 326, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=looney tunes&ts=looney-tunes'>Looney Tu…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 326, Column 124: reference not terminated by REFC delimiter
    …com/index.php?task=search&q=looney tunes&ts=looney-tunes'>Looney Tunes</a></li>

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

  • Warning Line 326, Column 124: reference to external entity in attribute value
    …com/index.php?task=search&q=looney tunes&ts=looney-tunes'>Looney Tunes</a></li>

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

  • Error Line 326, Column 124: reference to entity "ts" for which no system identifier could be generated
    …com/index.php?task=search&q=looney tunes&ts=looney-tunes'>Looney Tunes</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 327, Column 108: reference not terminated by REFC delimiter
    …/www.toongames.com/index.php?task=search&q=mario&ts=mario'>Mario Games</a></li>

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

  • Warning Line 327, Column 108: reference to external entity in attribute value
    …/www.toongames.com/index.php?task=search&q=mario&ts=mario'>Mario Games</a></li>

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

  • Error Line 327, Column 108: reference to entity "q" for which no system identifier could be generated
    …/www.toongames.com/index.php?task=search&q=mario&ts=mario'>Mario Games</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 327, Column 117: reference not terminated by REFC delimiter
    …/www.toongames.com/index.php?task=search&q=mario&ts=mario'>Mario Games</a></li>

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

  • Warning Line 327, Column 117: reference to external entity in attribute value
    …/www.toongames.com/index.php?task=search&q=mario&ts=mario'>Mario Games</a></li>

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

  • Error Line 327, Column 117: reference to entity "ts" for which no system identifier could be generated
    …/www.toongames.com/index.php?task=search&q=mario&ts=mario'>Mario Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 328, Column 108: reference not terminated by REFC delimiter
    …/www.toongames.com/index.php?task=search&q=megaman&ts=megaman'>Megaman</a></li>

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

  • Warning Line 328, Column 108: reference to external entity in attribute value
    …/www.toongames.com/index.php?task=search&q=megaman&ts=megaman'>Megaman</a></li>

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

  • Error Line 328, Column 108: reference to entity "q" for which no system identifier could be generated
    …/www.toongames.com/index.php?task=search&q=megaman&ts=megaman'>Megaman</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 328, Column 119: reference not terminated by REFC delimiter
    …/www.toongames.com/index.php?task=search&q=megaman&ts=megaman'>Megaman</a></li>

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

  • Warning Line 328, Column 119: reference to external entity in attribute value
    …/www.toongames.com/index.php?task=search&q=megaman&ts=megaman'>Megaman</a></li>

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

  • Error Line 328, Column 119: reference to entity "ts" for which no system identifier could be generated
    …/www.toongames.com/index.php?task=search&q=megaman&ts=megaman'>Megaman</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 329, Column 108: reference not terminated by REFC delimiter
    …w.toongames.com/index.php?task=search&q=naruto&ts=naruto'>Naruto Games</a></li>

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

  • Warning Line 329, Column 108: reference to external entity in attribute value
    …w.toongames.com/index.php?task=search&q=naruto&ts=naruto'>Naruto Games</a></li>

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

  • Error Line 329, Column 108: reference to entity "q" for which no system identifier could be generated
    …w.toongames.com/index.php?task=search&q=naruto&ts=naruto'>Naruto Games</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 329, Column 118: reference not terminated by REFC delimiter
    …w.toongames.com/index.php?task=search&q=naruto&ts=naruto'>Naruto Games</a></li>

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

  • Warning Line 329, Column 118: reference to external entity in attribute value
    …w.toongames.com/index.php?task=search&q=naruto&ts=naruto'>Naruto Games</a></li>

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

  • Error Line 329, Column 118: reference to entity "ts" for which no system identifier could be generated
    …w.toongames.com/index.php?task=search&q=naruto&ts=naruto'>Naruto Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 330, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=ninja turtles&ts=ninja-turtles'>Ninja T…

    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 330, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=ninja turtles&ts=ninja-turtles'>Ninja T…

    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 330, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=ninja turtles&ts=ninja-turtles'>Ninja T…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 330, Column 125: reference not terminated by REFC delimiter
    …/index.php?task=search&q=ninja turtles&ts=ninja-turtles'>Ninja Turtles</a></li>

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

  • Warning Line 330, Column 125: reference to external entity in attribute value
    …/index.php?task=search&q=ninja turtles&ts=ninja-turtles'>Ninja Turtles</a></li>

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

  • Error Line 330, Column 125: reference to entity "ts" for which no system identifier could be generated
    …/index.php?task=search&q=ninja turtles&ts=ninja-turtles'>Ninja Turtles</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 331, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=pokemon&ts=pokemon'>Pokemon Games</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 331, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=pokemon&ts=pokemon'>Pokemon Games</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 331, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=pokemon&ts=pokemon'>Pokemon Games</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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 331, Column 119: reference not terminated by REFC delimiter
    …oongames.com/index.php?task=search&q=pokemon&ts=pokemon'>Pokemon Games</a></li>

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

  • Warning Line 331, Column 119: reference to external entity in attribute value
    …oongames.com/index.php?task=search&q=pokemon&ts=pokemon'>Pokemon Games</a></li>

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

  • Error Line 331, Column 119: reference to entity "ts" for which no system identifier could be generated
    …oongames.com/index.php?task=search&q=pokemon&ts=pokemon'>Pokemon Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 332, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=popeye&ts=popeye'>Popeye Sailor Man</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 332, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=popeye&ts=popeye'>Popeye Sailor Man</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 332, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=popeye&ts=popeye'>Popeye Sailor Man</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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 332, Column 118: reference not terminated by REFC delimiter
    …ngames.com/index.php?task=search&q=popeye&ts=popeye'>Popeye Sailor Man</a></li>

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

  • Warning Line 332, Column 118: reference to external entity in attribute value
    …ngames.com/index.php?task=search&q=popeye&ts=popeye'>Popeye Sailor Man</a></li>

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

  • Error Line 332, Column 118: reference to entity "ts" for which no system identifier could be generated
    …ngames.com/index.php?task=search&q=popeye&ts=popeye'>Popeye Sailor Man</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 333, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=power-rangers&ts=power-ranger'>Power Ra…

    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 333, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=power-rangers&ts=power-ranger'>Power Ra…

    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 333, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=power-rangers&ts=power-ranger'>Power Ra…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 333, Column 125: reference not terminated by REFC delimiter
    …m/index.php?task=search&q=power-rangers&ts=power-ranger'>Power Rangers</a></li>

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

  • Warning Line 333, Column 125: reference to external entity in attribute value
    …m/index.php?task=search&q=power-rangers&ts=power-ranger'>Power Rangers</a></li>

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

  • Error Line 333, Column 125: reference to entity "ts" for which no system identifier could be generated
    …m/index.php?task=search&q=power-rangers&ts=power-ranger'>Power Rangers</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 334, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=scooby-doo&ts=scooby doo'>Scooby Doo</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 334, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=scooby-doo&ts=scooby doo'>Scooby Doo</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 334, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=scooby-doo&ts=scooby doo'>Scooby Doo</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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 334, Column 122: reference not terminated by REFC delimiter
    …games.com/index.php?task=search&q=scooby-doo&ts=scooby doo'>Scooby Doo</a></li>

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

  • Warning Line 334, Column 122: reference to external entity in attribute value
    …games.com/index.php?task=search&q=scooby-doo&ts=scooby doo'>Scooby Doo</a></li>

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

  • Error Line 334, Column 122: reference to entity "ts" for which no system identifier could be generated
    …games.com/index.php?task=search&q=scooby-doo&ts=scooby doo'>Scooby Doo</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 335, Column 108: reference not terminated by REFC delimiter
    …/www.toongames.com/index.php?task=search&q=sonic&ts=sonic'>Sonic Games</a></li>

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

  • Warning Line 335, Column 108: reference to external entity in attribute value
    …/www.toongames.com/index.php?task=search&q=sonic&ts=sonic'>Sonic Games</a></li>

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

  • Error Line 335, Column 108: reference to entity "q" for which no system identifier could be generated
    …/www.toongames.com/index.php?task=search&q=sonic&ts=sonic'>Sonic Games</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 335, Column 117: reference not terminated by REFC delimiter
    …/www.toongames.com/index.php?task=search&q=sonic&ts=sonic'>Sonic Games</a></li>

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

  • Warning Line 335, Column 117: reference to external entity in attribute value
    …/www.toongames.com/index.php?task=search&q=sonic&ts=sonic'>Sonic Games</a></li>

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

  • Error Line 335, Column 117: reference to entity "ts" for which no system identifier could be generated
    …/www.toongames.com/index.php?task=search&q=sonic&ts=sonic'>Sonic Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 336, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=spiderman&ts=spiderman'>Spiderman Games…

    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 336, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=spiderman&ts=spiderman'>Spiderman Games…

    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 336, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=spiderman&ts=spiderman'>Spiderman Games…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 336, Column 121: reference not terminated by REFC delimiter
    …es.com/index.php?task=search&q=spiderman&ts=spiderman'>Spiderman Games</a></li>

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

  • Warning Line 336, Column 121: reference to external entity in attribute value
    …es.com/index.php?task=search&q=spiderman&ts=spiderman'>Spiderman Games</a></li>

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

  • Error Line 336, Column 121: reference to entity "ts" for which no system identifier could be generated
    …es.com/index.php?task=search&q=spiderman&ts=spiderman'>Spiderman Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 337, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=spongebob&ts=sponge-bob'>SpongeBob Game…

    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 337, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=spongebob&ts=sponge-bob'>SpongeBob Game…

    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 337, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=spongebob&ts=sponge-bob'>SpongeBob Game…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 337, Column 121: reference not terminated by REFC delimiter
    …s.com/index.php?task=search&q=spongebob&ts=sponge-bob'>SpongeBob Games</a></li>

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

  • Warning Line 337, Column 121: reference to external entity in attribute value
    …s.com/index.php?task=search&q=spongebob&ts=sponge-bob'>SpongeBob Games</a></li>

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

  • Error Line 337, Column 121: reference to entity "ts" for which no system identifier could be generated
    …s.com/index.php?task=search&q=spongebob&ts=sponge-bob'>SpongeBob Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 338, Column 108: reference not terminated by REFC delimiter
    …href='http://www.toongames.com/index.php?task=search&q=tak&ts=tak'>Tak</a></li>

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

  • Warning Line 338, Column 108: reference to external entity in attribute value
    …href='http://www.toongames.com/index.php?task=search&q=tak&ts=tak'>Tak</a></li>

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

  • Error Line 338, Column 108: reference to entity "q" for which no system identifier could be generated
    …href='http://www.toongames.com/index.php?task=search&q=tak&ts=tak'>Tak</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 338, Column 115: reference not terminated by REFC delimiter
    …href='http://www.toongames.com/index.php?task=search&q=tak&ts=tak'>Tak</a></li>

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

  • Warning Line 338, Column 115: reference to external entity in attribute value
    …href='http://www.toongames.com/index.php?task=search&q=tak&ts=tak'>Tak</a></li>

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

  • Error Line 338, Column 115: reference to entity "ts" for which no system identifier could be generated
    …href='http://www.toongames.com/index.php?task=search&q=tak&ts=tak'>Tak</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 339, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=simpsons&ts=simpsons'>The Simpsons</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 339, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=simpsons&ts=simpsons'>The Simpsons</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 339, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=simpsons&ts=simpsons'>The Simpsons</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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 339, Column 120: reference not terminated by REFC delimiter
    …ongames.com/index.php?task=search&q=simpsons&ts=simpsons'>The Simpsons</a></li>

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

  • Warning Line 339, Column 120: reference to external entity in attribute value
    …ongames.com/index.php?task=search&q=simpsons&ts=simpsons'>The Simpsons</a></li>

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

  • Error Line 339, Column 120: reference to entity "ts" for which no system identifier could be generated
    …ongames.com/index.php?task=search&q=simpsons&ts=simpsons'>The Simpsons</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 340, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=tom and jerry&ts=tom-and-jerry'>Tom And…

    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 340, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=tom and jerry&ts=tom-and-jerry'>Tom And…

    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 340, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=tom and jerry&ts=tom-and-jerry'>Tom And…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 340, Column 125: reference not terminated by REFC delimiter
    …/index.php?task=search&q=tom and jerry&ts=tom-and-jerry'>Tom And Jerry</a></li>

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

  • Warning Line 340, Column 125: reference to external entity in attribute value
    …/index.php?task=search&q=tom and jerry&ts=tom-and-jerry'>Tom And Jerry</a></li>

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

  • Error Line 340, Column 125: reference to entity "ts" for which no system identifier could be generated
    …/index.php?task=search&q=tom and jerry&ts=tom-and-jerry'>Tom And Jerry</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 341, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=Toy story&ts=toy-story'>Toy Story Games…

    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 341, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=Toy story&ts=toy-story'>Toy Story Games…

    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 341, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=Toy story&ts=toy-story'>Toy Story Games…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 341, Column 121: reference not terminated by REFC delimiter
    …es.com/index.php?task=search&q=Toy story&ts=toy-story'>Toy Story Games</a></li>

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

  • Warning Line 341, Column 121: reference to external entity in attribute value
    …es.com/index.php?task=search&q=Toy story&ts=toy-story'>Toy Story Games</a></li>

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

  • Error Line 341, Column 121: reference to entity "ts" for which no system identifier could be generated
    …es.com/index.php?task=search&q=Toy story&ts=toy-story'>Toy Story Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 342, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=transformers&ts=transformers'>Transform…

    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 342, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=transformers&ts=transformers'>Transform…

    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 342, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=transformers&ts=transformers'>Transform…

    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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 342, Column 124: reference not terminated by REFC delimiter
    …com/index.php?task=search&q=transformers&ts=transformers'>Transformers</a></li>

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

  • Warning Line 342, Column 124: reference to external entity in attribute value
    …com/index.php?task=search&q=transformers&ts=transformers'>Transformers</a></li>

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

  • Error Line 342, Column 124: reference to entity "ts" for which no system identifier could be generated
    …com/index.php?task=search&q=transformers&ts=transformers'>Transformers</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 343, Column 108: reference not terminated by REFC delimiter
    …://www.toongames.com/index.php?task=search&q=xmen&ts=xmen'>X-Men Games</a></li>

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

  • Warning Line 343, Column 108: reference to external entity in attribute value
    …://www.toongames.com/index.php?task=search&q=xmen&ts=xmen'>X-Men Games</a></li>

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

  • Error Line 343, Column 108: reference to entity "q" for which no system identifier could be generated
    …://www.toongames.com/index.php?task=search&q=xmen&ts=xmen'>X-Men Games</a></li>

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

  • Info Line 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 343, Column 116: reference not terminated by REFC delimiter
    …://www.toongames.com/index.php?task=search&q=xmen&ts=xmen'>X-Men Games</a></li>

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

  • Warning Line 343, Column 116: reference to external entity in attribute value
    …://www.toongames.com/index.php?task=search&q=xmen&ts=xmen'>X-Men Games</a></li>

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

  • Error Line 343, Column 116: reference to entity "ts" for which no system identifier could be generated
    …://www.toongames.com/index.php?task=search&q=xmen&ts=xmen'>X-Men Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 344, Column 108: reference not terminated by REFC delimiter
    ….toongames.com/index.php?task=search&q=zoey 101&ts=zoey-101'>zoey-101 Games</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 344, Column 108: reference to external entity in attribute value
    ….toongames.com/index.php?task=search&q=zoey 101&ts=zoey-101'>zoey-101 Games</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 344, Column 108: reference to entity "q" for which no system identifier could be generated
    ….toongames.com/index.php?task=search&q=zoey 101&ts=zoey-101'>zoey-101 Games</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 303, Column 106: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Warning Line 344, Column 120: reference not terminated by REFC delimiter
    …games.com/index.php?task=search&q=zoey 101&ts=zoey-101'>zoey-101 Games</a></li>

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

  • Warning Line 344, Column 120: reference to external entity in attribute value
    …games.com/index.php?task=search&q=zoey 101&ts=zoey-101'>zoey-101 Games</a></li>

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

  • Error Line 344, Column 120: reference to entity "ts" for which no system identifier could be generated
    …games.com/index.php?task=search&q=zoey 101&ts=zoey-101'>zoey-101 Games</a></li>

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

  • Info Line 303, Column 114: entity was defined here
    …www.toongames.com/index.php?task=search&q=6teen&ts=6-teen'>6Teen Games</a></li>
  • Error Line 403, Column 9: required attribute "type" not specified
    	<script>

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

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

  • Error Line 441, Column 45: document type does not allow element "div" here
      document.write('<div class="homepage_game">');

    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 443, Column 130: there is no attribute "border"
    …"'+title+'"><img height="69" width="96" src="'+imageUrl+'" border="0" /></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 443, Column 135: required attribute "alt" not specified
    …"'+title+'"><img height="69" width="96" src="'+imageUrl+'" border="0" /></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 447, Column 166: end tag for element "p" which is not open
    …px;font-family:Verdana;" target="_blank" title="'+title+'">'+title+'</a></p>');

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

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

  • Error Line 471, Column 7: 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 471, Column 3: start tag was here
    		<br>
  • Error Line 503, Column 7: 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 503, Column 3: start tag was here
    		<br>
  • Error Line 535, Column 7: 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 535, Column 3: start tag was here
    		<br>
  • Error Line 567, Column 7: 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 567, Column 3: start tag was here
    		<br>
  • Error Line 599, Column 7: 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 599, Column 3: start tag was here
    		<br>
  • Error Line 631, Column 7: 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 631, Column 3: start tag was here
    		<br>
  • Error Line 663, Column 7: 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 663, Column 3: start tag was here
    		<br>
  • Error Line 695, Column 7: 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 695, Column 3: start tag was here
    		<br>
  • Error Line 727, Column 7: 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 727, Column 3: start tag was here
    		<br>
  • Error Line 759, Column 7: 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 759, Column 3: start tag was here
    		<br>
  • Error Line 791, Column 7: 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 791, Column 3: start tag was here
    		<br>
  • Error Line 823, Column 7: 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 823, Column 3: start tag was here
    		<br>
  • Error Line 855, Column 7: 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 855, Column 3: start tag was here
    		<br>
  • Error Line 887, Column 7: 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 887, Column 3: start tag was here
    		<br>
  • Error Line 919, Column 7: 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 919, Column 3: start tag was here
    		<br>
  • Error Line 951, Column 7: 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 951, Column 3: start tag was here
    		<br>
  • Error Line 983, Column 7: 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 983, Column 3: start tag was here
    		<br>
  • Error Line 1015, Column 7: 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 1015, Column 3: start tag was here
    		<br>
  • Error Line 1047, Column 7: 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 1047, Column 3: start tag was here
    		<br>
  • Error Line 1079, Column 7: 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 1079, Column 3: start tag was here
    		<br>
  • Error Line 1111, Column 7: 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 1111, Column 3: start tag was here
    		<br>
  • Error Line 1143, Column 7: 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 1143, Column 3: start tag was here
    		<br>
  • Error Line 1175, Column 7: 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 1175, Column 3: start tag was here
    		<br>
  • Error Line 1208, Column 7: 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 1208, Column 3: start tag was here
    		<br>
  • Error Line 1240, Column 7: 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 1240, Column 3: start tag was here
    		<br>
  • Error Line 1272, Column 7: 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 1272, Column 3: start tag was here
    		<br>
  • Error Line 1304, Column 7: 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 1304, Column 3: start tag was here
    		<br>
  • Error Line 1336, Column 7: 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 1336, Column 3: start tag was here
    		<br>
  • Error Line 1368, Column 7: 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 1368, Column 3: start tag was here
    		<br>
  • Error Line 1400, Column 7: 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 1400, Column 3: start tag was here
    		<br>
  • Error Line 1432, Column 7: 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 1432, Column 3: start tag was here
    		<br>
  • Error Line 1464, Column 7: 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 1464, Column 3: start tag was here
    		<br>
  • Error Line 1496, Column 7: 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 1496, Column 3: start tag was here
    		<br>
  • Error Line 1528, Column 7: 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 1528, Column 3: start tag was here
    		<br>
  • Error Line 1561, Column 7: 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 1561, Column 3: start tag was here
    		<br>
  • Error Line 1586, Column 23: there is no attribute "FRAMEBORDER"
    		<IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEI…

    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 1586, Column 23: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEI…
  • Error Line 1586, Column 37: there is no attribute "MARGINWIDTH"
    		<IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEI…

    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 1586, Column 37: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		<IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEI…
  • Error Line 1586, Column 52: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="…

    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 1586, Column 52: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="…
  • Error Line 1586, Column 64: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://adser…

    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 1586, Column 64: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://adser…
  • Error Line 1586, Column 73: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://adserving.cpxi…

    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 1586, Column 73: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://adserving.cpxi…
  • Error Line 1586, Column 84: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://adserving.cpxinteractive.…

    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 1586, Column 84: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://adserving.cpxinteractive.…
  • Error Line 1586, Column 91: there is no attribute "SRC"
    … SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://adserving.cpxinteractive.com/st?…

    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 1586, Column 146: cannot generate system identifier for general entity "ad_size"
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></IFRAME…

    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 1586, Column 146: general entity "ad_size" not defined and no default entity
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></IFRAME…

    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 1586, Column 153: reference not terminated by REFC delimiter
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></IFRAME>

    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 1586, Column 153: reference to external entity in attribute value
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></IFRAME>

    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 1586, Column 153: reference to entity "ad_size" for which no system identifier could be generated
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></IFRAME>

    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 1586, Column 145: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></IFRAM…
  • Warning Line 1586, Column 161: cannot generate system identifier for general entity "section"
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></IFRAME>

    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 1586, Column 161: general entity "section" not defined and no default entity
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></IFRAME>

    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 1586, Column 168: reference not terminated by REFC delimiter
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></IFRAME>

    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 1586, Column 168: reference to external entity in attribute value
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></IFRAME>

    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 1586, Column 168: reference to entity "section" for which no system identifier could be generated
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></IFRAME>

    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 1586, Column 160: entity was defined here
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></IFRAME>
  • Error Line 1586, Column 177: element "IFRAME" undefined
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1808538"></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 1612, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    								<br><a class="alst" href="http://www.toongames.com/cat/1/Shooting/newes…

    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 1612, Column 9: start tag was here
    								<br><a class="alst" href="http://www.toongames.com/cat/1/Shooting/newes…
  • Error Line 1612, Column 106: end tag for "br" omitted, but OMITTAG NO was specified
    …ooting/newest-1.html">Shooting</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 102: start tag was here
    …1/Shooting/newest-1.html">Shooting</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 199: end tag for "br" omitted, but OMITTAG NO was specified
    …ghting/newest-1.html">Fighting</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 195: start tag was here
    …2/Fighting/newest-1.html">Fighting</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 294: end tag for "br" omitted, but OMITTAG NO was specified
    …nture/newest-1.html">Adventure</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 290: start tag was here
    …Adventure/newest-1.html">Adventure</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 401: end tag for "br" omitted, but OMITTAG NO was specified
    …newest-1.html">Bloody and Gore</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 397: start tag was here
    …ore/newest-1.html">Bloody and Gore</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 506: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">Jump and Shoot</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 502: start tag was here
    …hoot/newest-1.html">Jump and Shoot</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 609: end tag for "br" omitted, but OMITTAG NO was specified
    …t/newest-1.html">Run and Shoot</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 605: start tag was here
    …Shoot/newest-1.html">Run and Shoot</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 714: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">Whacking Games</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 710: start tag was here
    …ames/newest-1.html">Whacking Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 813: end tag for "br" omitted, but OMITTAG NO was specified
    …mes/newest-1.html">Funny Games</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 809: start tag was here
    …y-Games/newest-1.html">Funny Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 918: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">Platform Games</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 914: start tag was here
    …ames/newest-1.html">Platform Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 1024: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">Wreck the City</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 1020: start tag was here
    …City/newest-1.html">Wreck the City</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 1126: end tag for "br" omitted, but OMITTAG NO was specified
    …es/newest-1.html">Escape Games</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 1122: start tag was here
    …-Games/newest-1.html">Escape Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 1234: end tag for "br" omitted, but OMITTAG NO was specified
    …newest-1.html">Secret Escaping</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 1230: start tag was here
    …ing/newest-1.html">Secret Escaping</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 1336: end tag for "br" omitted, but OMITTAG NO was specified
    …ng/newest-1.html">Role Playing</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 1332: start tag was here
    …laying/newest-1.html">Role Playing</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 1444: end tag for "br" omitted, but OMITTAG NO was specified
    …newest-1.html">Point and Click</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 1440: start tag was here
    …ick/newest-1.html">Point and Click</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 1538: end tag for "br" omitted, but OMITTAG NO was specified
    …rcraft/newest-1.html">Aircraft</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 1534: start tag was here
    …5/Aircraft/newest-1.html">Aircraft</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 1644: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">Space Invaders</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 1640: start tag was here
    …ders/newest-1.html">Space Invaders</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 1740: end tag for "br" omitted, but OMITTAG NO was specified
    …roids/newest-1.html">Asteroids</a><br><a class="alst" href="http://www.toongam…

    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 1612, Column 1736: start tag was here
    …Asteroids/newest-1.html">Asteroids</a><br><a class="alst" href="http://www.too…
  • Error Line 1612, Column 1844: end tag for "br" omitted, but OMITTAG NO was specified
    …www.toongames.com/cat/18/War-Games/newest-1.html">War Games</a>								<br><br>

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

  • Info Line 1612, Column 1840: start tag was here
    …www.toongames.com/cat/18/War-Games/newest-1.html">War Games</a>								<br><br>
  • Error Line 1612, Column 1848: end tag for "br" omitted, but OMITTAG NO was specified
    …www.toongames.com/cat/18/War-Games/newest-1.html">War Games</a>								<br><br>

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

  • Info Line 1612, Column 1844: start tag was here
    …www.toongames.com/cat/18/War-Games/newest-1.html">War Games</a>								<br><br>
  • Error Line 1614, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    								<br><a class="alst" href="http://www.toongames.com/cat/19/Action/newest…

    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 1614, Column 9: start tag was here
    								<br><a class="alst" href="http://www.toongames.com/cat/19/Action/newest…
  • Error Line 1614, Column 103: end tag for "br" omitted, but OMITTAG NO was specified
    …9/Action/newest-1.html">Action</a><br><a class="alst" href="http://www.toongam…

    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 1614, Column 99: start tag was here
    …at/19/Action/newest-1.html">Action</a><br><a class="alst" href="http://www.too…
  • Error Line 1614, Column 193: end tag for "br" omitted, but OMITTAG NO was specified
    …2/Puzzle/newest-1.html">Puzzle</a><br><a class="alst" href="http://www.toongam…

    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 1614, Column 189: start tag was here
    …at/22/Puzzle/newest-1.html">Puzzle</a><br><a class="alst" href="http://www.too…
  • Error Line 1614, Column 295: end tag for "br" omitted, but OMITTAG NO was specified
    …rd/newest-1.html">Board - Card</a><br><a class="alst" href="http://www.toongam…

    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 1614, Column 291: start tag was here
    …--Card/newest-1.html">Board - Card</a><br><a class="alst" href="http://www.too…
  • Error Line 1614, Column 383: end tag for "br" omitted, but OMITTAG NO was specified
    …/24/Skill/newest-1.html">Skill</a><br><a class="alst" href="http://www.toongam…

    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 1614, Column 379: start tag was here
    …/cat/24/Skill/newest-1.html">Skill</a><br><a class="alst" href="http://www.too…
  • Error Line 1614, Column 489: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">RPG - Strategy</a><br><a class="alst" href="http://www.toongam…

    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 1614, Column 485: start tag was here
    …tegy/newest-1.html">RPG - Strategy</a><br><a class="alst" href="http://www.too…
  • Error Line 1614, Column 585: end tag for "br" omitted, but OMITTAG NO was specified
    …games/newest-1.html">Kid games</a><br><a class="alst" href="http://www.toongam…

    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 1614, Column 581: start tag was here
    …Kid-games/newest-1.html">Kid games</a><br><a class="alst" href="http://www.too…
  • Error Line 1614, Column 683: end tag for "br" omitted, but OMITTAG NO was specified
    …ames/newest-1.html">Girl games</a><br><a class="alst" href="http://www.toongam…

    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 1614, Column 679: start tag was here
    …rl-games/newest-1.html">Girl games</a><br><a class="alst" href="http://www.too…
  • Error Line 1614, Column 781: end tag for "br" omitted, but OMITTAG NO was specified
    …f="http://www.toongames.com/cat/28/Racing/newest-1.html">Racing</a>								<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 1614, Column 777: start tag was here
    …f="http://www.toongames.com/cat/28/Racing/newest-1.html">Racing</a>								<br>
  • Error Line 1618, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    								<br><a class="alst" href="http://www.toongames.com/cat/29/Racing-Games/…

    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 1618, Column 9: start tag was here
    								<br><a class="alst" href="http://www.toongames.com/cat/29/Racing-Games/…
  • Error Line 1618, Column 115: end tag for "br" omitted, but OMITTAG NO was specified
    …es/newest-1.html">Racing Games</a><br><a class="alst" href="http://www.toongam…

    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 1618, Column 111: start tag was here
    …-Games/newest-1.html">Racing Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1618, Column 221: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">Circuit Racing</a><br><a class="alst" href="http://www.toongam…

    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 1618, Column 217: start tag was here
    …cing/newest-1.html">Circuit Racing</a><br><a class="alst" href="http://www.too…
  • Error Line 1618, Column 313: end tag for "br" omitted, but OMITTAG NO was specified
    …Karting/newest-1.html">Karting</a><br><a class="alst" href="http://www.toongam…

    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 1618, Column 309: start tag was here
    …/31/Karting/newest-1.html">Karting</a><br><a class="alst" href="http://www.too…
  • Error Line 1618, Column 401: end tag for "br" omitted, but OMITTAG NO was specified
    …/32/Rally/newest-1.html">Rally</a><br><a class="alst" href="http://www.toongam…

    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 1618, Column 397: start tag was here
    …/cat/32/Rally/newest-1.html">Rally</a><br><a class="alst" href="http://www.too…
  • Error Line 1618, Column 501: end tag for "br" omitted, but OMITTAG NO was specified
    …ing/newest-1.html">City Racing</a><br><a class="alst" href="http://www.toongam…

    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 1618, Column 497: start tag was here
    …-Racing/newest-1.html">City Racing</a><br><a class="alst" href="http://www.too…
  • Error Line 1618, Column 603: end tag for "br" omitted, but OMITTAG NO was specified
    …ng/newest-1.html">Motor Racing</a><br><a class="alst" href="http://www.toongam…

    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 1618, Column 599: start tag was here
    …Racing/newest-1.html">Motor Racing</a><br><a class="alst" href="http://www.too…
  • Error Line 1618, Column 707: end tag for "br" omitted, but OMITTAG NO was specified
    …g/newest-1.html">Stunt Driving</a><br><a class="alst" href="http://www.toongam…

    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 1618, Column 703: start tag was here
    …iving/newest-1.html">Stunt Driving</a><br><a class="alst" href="http://www.too…
  • Error Line 1618, Column 811: end tag for "br" omitted, but OMITTAG NO was specified
    …g/newest-1.html">Uphill Racing</a><br><a class="alst" href="http://www.toongam…

    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 1618, Column 807: start tag was here
    …acing/newest-1.html">Uphill Racing</a><br><a class="alst" href="http://www.too…
  • Error Line 1618, Column 911: end tag for "br" omitted, but OMITTAG NO was specified
    …ing/newest-1.html">Boat Racing</a><br><a class="alst" href="http://www.toongam…

    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 1618, Column 907: start tag was here
    …-Racing/newest-1.html">Boat Racing</a><br><a class="alst" href="http://www.too…
  • Error Line 1618, Column 1011: end tag for "br" omitted, but OMITTAG NO was specified
    …ing/newest-1.html">Line Racing</a><br><a class="alst" href="http://www.toongam…

    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 1618, Column 1007: start tag was here
    …-Racing/newest-1.html">Line Racing</a><br><a class="alst" href="http://www.too…
  • Error Line 1618, Column 1121: end tag for "br" omitted, but OMITTAG NO was specified
    …ongames.com/cat/39/Pimp-My-Ride/newest-1.html">Pimp My Ride</a>								<br><br>

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

  • Info Line 1618, Column 1117: start tag was here
    …ongames.com/cat/39/Pimp-My-Ride/newest-1.html">Pimp My Ride</a>								<br><br>
  • Error Line 1618, Column 1125: end tag for "br" omitted, but OMITTAG NO was specified
    …ongames.com/cat/39/Pimp-My-Ride/newest-1.html">Pimp My Ride</a>								<br><br>

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

  • Info Line 1618, Column 1121: start tag was here
    …ongames.com/cat/39/Pimp-My-Ride/newest-1.html">Pimp My Ride</a>								<br><br>
  • Error Line 1620, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    								<br><a class="alst" href="http://www.toongames.com/cat/40/Bejeweled/new…

    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 1620, Column 9: start tag was here
    								<br><a class="alst" href="http://www.toongames.com/cat/40/Bejeweled/new…
  • Error Line 1620, Column 109: end tag for "br" omitted, but OMITTAG NO was specified
    …weled/newest-1.html">Bejeweled</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 105: start tag was here
    …Bejeweled/newest-1.html">Bejeweled</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 211: end tag for "br" omitted, but OMITTAG NO was specified
    …es/newest-1.html">Puzzle Games</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 207: start tag was here
    …-Games/newest-1.html">Puzzle Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 311: end tag for "br" omitted, but OMITTAG NO was specified
    …mes/newest-1.html">Board Games</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 307: start tag was here
    …d-Games/newest-1.html">Board Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 403: end tag for "br" omitted, but OMITTAG NO was specified
    …Mahjong/newest-1.html">Mahjong</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 399: start tag was here
    …/43/Mahjong/newest-1.html">Mahjong</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 493: end tag for "br" omitted, but OMITTAG NO was specified
    …4/Tetris/newest-1.html">Tetris</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 489: start tag was here
    …at/44/Tetris/newest-1.html">Tetris</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 599: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">Chain Reaction</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 595: start tag was here
    …tion/newest-1.html">Chain Reaction</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 707: end tag for "br" omitted, but OMITTAG NO was specified
    …newest-1.html">Coloured Blocks</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 703: start tag was here
    …cks/newest-1.html">Coloured Blocks</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 809: end tag for "br" omitted, but OMITTAG NO was specified
    …ch/newest-1.html">Image Search</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 805: start tag was here
    …Search/newest-1.html">Image Search</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 913: end tag for "br" omitted, but OMITTAG NO was specified
    …e/newest-1.html">Jigsaw Puzzle</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 909: start tag was here
    …uzzle/newest-1.html">Jigsaw Puzzle</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 1011: end tag for "br" omitted, but OMITTAG NO was specified
    …mind/newest-1.html">Mastermind</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 1007: start tag was here
    …stermind/newest-1.html">Mastermind</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 1113: end tag for "br" omitted, but OMITTAG NO was specified
    …es/newest-1.html">Memory Games</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 1109: start tag was here
    …-Games/newest-1.html">Memory Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 1219: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">Pushing Blocks</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 1215: start tag was here
    …ocks/newest-1.html">Pushing Blocks</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 1331: end tag for "br" omitted, but OMITTAG NO was specified
    …west-1.html">Road Construction</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 1327: start tag was here
    …n/newest-1.html">Road Construction</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 1437: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">Sliding Puzzle</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 1433: start tag was here
    …zzle/newest-1.html">Sliding Puzzle</a><br><a class="alst" href="http://www.too…
  • Error Line 1620, Column 1543: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">Sorting Blocks</a><br><a class="alst" href="http://www.toongam…

    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 1620, Column 1539: start tag was here
    …ocks/newest-1.html">Sorting Blocks</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    								<br><a class="alst" href="http://www.toongames.com/cat/56/Dress-Up-Game…

    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 1623, Column 9: start tag was here
    								<br><a class="alst" href="http://www.toongames.com/cat/56/Dress-Up-Game…
  • Error Line 1623, Column 119: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">Dress Up Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 115: start tag was here
    …ames/newest-1.html">Dress Up Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 229: end tag for "br" omitted, but OMITTAG NO was specified
    …ewest-1.html">Fashion Dress Up</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 225: start tag was here
    …Up/newest-1.html">Fashion Dress Up</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 341: end tag for "br" omitted, but OMITTAG NO was specified
    …west-1.html">Shopping Dress Up</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 337: start tag was here
    …p/newest-1.html">Shopping Dress Up</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 451: end tag for "br" omitted, but OMITTAG NO was specified
    …ewest-1.html">Wedding Dress Up</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 447: start tag was here
    …Up/newest-1.html">Wedding Dress Up</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 559: end tag for "br" omitted, but OMITTAG NO was specified
    …newest-1.html">Make Over Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 555: start tag was here
    …mes/newest-1.html">Make Over Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 657: end tag for "br" omitted, but OMITTAG NO was specified
    …ames/newest-1.html">Nail Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 653: start tag was here
    …il-Games/newest-1.html">Nail Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 769: end tag for "br" omitted, but OMITTAG NO was specified
    …west-1.html">Hairdresser Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 765: start tag was here
    …s/newest-1.html">Hairdresser Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 873: end tag for "br" omitted, but OMITTAG NO was specified
    …s/newest-1.html">Make Up Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 869: start tag was here
    …Games/newest-1.html">Make Up Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 977: end tag for "br" omitted, but OMITTAG NO was specified
    …s/newest-1.html">Cooking Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 973: start tag was here
    …Games/newest-1.html">Cooking Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 1079: end tag for "br" omitted, but OMITTAG NO was specified
    …ng/newest-1.html">Food serving</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 1075: start tag was here
    …erving/newest-1.html">Food serving</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 1189: end tag for "br" omitted, but OMITTAG NO was specified
    …ewest-1.html">Decorating Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 1185: start tag was here
    …es/newest-1.html">Decorating Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 1289: end tag for "br" omitted, but OMITTAG NO was specified
    …mes/newest-1.html">Actor Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 1285: start tag was here
    …r-Games/newest-1.html">Actor Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 1393: end tag for "br" omitted, but OMITTAG NO was specified
    …s/newest-1.html">Actress Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 1389: start tag was here
    …Games/newest-1.html">Actress Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 1503: end tag for "br" omitted, but OMITTAG NO was specified
    …ewest-1.html">Pop Singer Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 1499: start tag was here
    …es/newest-1.html">Pop Singer Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 1605: end tag for "br" omitted, but OMITTAG NO was specified
    …es/newest-1.html">Barbie Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 1601: start tag was here
    …-Games/newest-1.html">Barbie Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 1705: end tag for "br" omitted, but OMITTAG NO was specified
    …mes/newest-1.html">Bratz Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 1701: start tag was here
    …z-Games/newest-1.html">Bratz Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 1801: end tag for "br" omitted, but OMITTAG NO was specified
    …Games/newest-1.html">Sue Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 1797: start tag was here
    …Sue-Games/newest-1.html">Sue Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 1899: end tag for "br" omitted, but OMITTAG NO was specified
    …ames/newest-1.html">Love Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 1895: start tag was here
    …ve-Games/newest-1.html">Love Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 2001: end tag for "br" omitted, but OMITTAG NO was specified
    …es/newest-1.html">Dating Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 1997: start tag was here
    …-Games/newest-1.html">Dating Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 2103: end tag for "br" omitted, but OMITTAG NO was specified
    …es/newest-1.html">Caring Games</a><br><a class="alst" href="http://www.toongam…

    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 1623, Column 2099: start tag was here
    …-Games/newest-1.html">Caring Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1623, Column 2213: end tag for "br" omitted, but OMITTAG NO was specified
    …ongames.com/cat/76/Animal-Games/newest-1.html">Animal Games</a>								<br><br>

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

  • Info Line 1623, Column 2209: start tag was here
    …ongames.com/cat/76/Animal-Games/newest-1.html">Animal Games</a>								<br><br>
  • Error Line 1623, Column 2217: end tag for "br" omitted, but OMITTAG NO was specified
    …ongames.com/cat/76/Animal-Games/newest-1.html">Animal Games</a>								<br><br>

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

  • Info Line 1623, Column 2213: start tag was here
    …ongames.com/cat/76/Animal-Games/newest-1.html">Animal Games</a>								<br><br>
  • Error Line 1625, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    								<br><a class="alst" href="http://www.toongames.com/cat/77/Hannah-Montan…

    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 1625, Column 9: start tag was here
    								<br><a class="alst" href="http://www.toongames.com/cat/77/Hannah-Montan…
  • Error Line 1625, Column 131: end tag for "br" omitted, but OMITTAG NO was specified
    …t-1.html">Hannah Montana Games</a><br><a class="alst" href="http://www.toongam…

    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 1625, Column 127: start tag was here
    …ewest-1.html">Hannah Montana Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1625, Column 247: end tag for "br" omitted, but OMITTAG NO was specified
    …st-1.html">High School Musical</a><br><a class="alst" href="http://www.toongam…

    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 1625, Column 243: start tag was here
    …newest-1.html">High School Musical</a><br><a class="alst" href="http://www.too…
  • Error Line 1625, Column 349: end tag for "br" omitted, but OMITTAG NO was specified
    …es/newest-1.html">Disney Games</a><br><a class="alst" href="http://www.toongam…

    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 1625, Column 345: start tag was here
    …-Games/newest-1.html">Disney Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1625, Column 449: end tag for "br" omitted, but OMITTAG NO was specified
    …mes/newest-1.html">Mario Games</a><br><a class="alst" href="http://www.toongam…

    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 1625, Column 445: start tag was here
    …o-Games/newest-1.html">Mario Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1625, Column 563: end tag for "br" omitted, but OMITTAG NO was specified
    …est-1.html">The Simpsons Games</a><br><a class="alst" href="http://www.toongam…

    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 1625, Column 559: start tag was here
    …/newest-1.html">The Simpsons Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1625, Column 679: end tag for "br" omitted, but OMITTAG NO was specified
    …games.com/cat/82/SpongeBob-Games/newest-1.html">SpongeBob Games</a>								<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 1625, Column 675: start tag was here
    …games.com/cat/82/SpongeBob-Games/newest-1.html">SpongeBob Games</a>								<br>
  • Error Line 1629, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    								<br><a class="alst" href="http://www.toongames.com/cat/83/Skill-games/n…

    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 1629, Column 9: start tag was here
    								<br><a class="alst" href="http://www.toongames.com/cat/83/Skill-games/n…
  • Error Line 1629, Column 113: end tag for "br" omitted, but OMITTAG NO was specified
    …mes/newest-1.html">Skill games</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 109: start tag was here
    …l-games/newest-1.html">Skill games</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 205: end tag for "br" omitted, but OMITTAG NO was specified
    …Drawing/newest-1.html">Drawing</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 201: start tag was here
    …/84/Drawing/newest-1.html">Drawing</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 311: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">Coloring Games</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 307: start tag was here
    …ames/newest-1.html">Coloring Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 415: end tag for "br" omitted, but OMITTAG NO was specified
    …h/newest-1.html">Draw The Path</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 411: start tag was here
    …-Path/newest-1.html">Draw The Path</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 509: end tag for "br" omitted, but OMITTAG NO was specified
    …stacle/newest-1.html">Obstacle</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 505: start tag was here
    …7/Obstacle/newest-1.html">Obstacle</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 599: end tag for "br" omitted, but OMITTAG NO was specified
    …8/Flying/newest-1.html">Flying</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 595: start tag was here
    …at/88/Flying/newest-1.html">Flying</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 691: end tag for "br" omitted, but OMITTAG NO was specified
    …Running/newest-1.html">Running</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 687: start tag was here
    …/89/Running/newest-1.html">Running</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 787: end tag for "br" omitted, but OMITTAG NO was specified
    …ncing/newest-1.html">Balancing</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 783: start tag was here
    …Balancing/newest-1.html">Balancing</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 881: end tag for "br" omitted, but OMITTAG NO was specified
    …tching/newest-1.html">Catching</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 877: start tag was here
    …1/Catching/newest-1.html">Catching</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 979: end tag for "br" omitted, but OMITTAG NO was specified
    …ting/newest-1.html">Collecting</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 975: start tag was here
    …llecting/newest-1.html">Collecting</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 1071: end tag for "br" omitted, but OMITTAG NO was specified
    …Jumping/newest-1.html">Jumping</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 1067: start tag was here
    …/93/Jumping/newest-1.html">Jumping</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 1163: end tag for "br" omitted, but OMITTAG NO was specified
    …Landing/newest-1.html">Landing</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 1159: start tag was here
    …/94/Landing/newest-1.html">Landing</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 1255: end tag for "br" omitted, but OMITTAG NO was specified
    …Fishing/newest-1.html">Fishing</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 1251: start tag was here
    …/95/Fishing/newest-1.html">Fishing</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 1345: end tag for "br" omitted, but OMITTAG NO was specified
    …6/Typing/newest-1.html">Typing</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 1341: start tag was here
    …at/96/Typing/newest-1.html">Typing</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 1437: end tag for "br" omitted, but OMITTAG NO was specified
    …Parking/newest-1.html">Parking</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 1433: start tag was here
    …/97/Parking/newest-1.html">Parking</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 1537: end tag for "br" omitted, but OMITTAG NO was specified
    …nal/newest-1.html">Educational</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 1533: start tag was here
    …ational/newest-1.html">Educational</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 1625: end tag for "br" omitted, but OMITTAG NO was specified
    …/99/Music/newest-1.html">Music</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 1621: start tag was here
    …/cat/99/Music/newest-1.html">Music</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 1714: end tag for "br" omitted, but OMITTAG NO was specified
    …100/Snake/newest-1.html">Snake</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 1710: start tag was here
    …cat/100/Snake/newest-1.html">Snake</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 1807: end tag for "br" omitted, but OMITTAG NO was specified
    …Pinball/newest-1.html">Pinball</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 1803: start tag was here
    …101/Pinball/newest-1.html">Pinball</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 1894: end tag for "br" omitted, but OMITTAG NO was specified
    …t/102/Pong/newest-1.html">Pong</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 1890: start tag was here
    …m/cat/102/Pong/newest-1.html">Pong</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 1997: end tag for "br" omitted, but OMITTAG NO was specified
    …ll/newest-1.html">Rolling Ball</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 1993: start tag was here
    …g-Ball/newest-1.html">Rolling Ball</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 2092: end tag for "br" omitted, but OMITTAG NO was specified
    …eakout/newest-1.html">Breakout</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 2088: start tag was here
    …4/Breakout/newest-1.html">Breakout</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 2201: end tag for "br" omitted, but OMITTAG NO was specified
    …newest-1.html">Distance Record</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 2197: start tag was here
    …ord/newest-1.html">Distance Record</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 2292: end tag for "br" omitted, but OMITTAG NO was specified
    …6/Pacman/newest-1.html">Pacman</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 2288: start tag was here
    …t/106/Pacman/newest-1.html">Pacman</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 2389: end tag for "br" omitted, but OMITTAG NO was specified
    …erman/newest-1.html">Bomberman</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 2385: start tag was here
    …Bomberman/newest-1.html">Bomberman</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 2478: end tag for "br" omitted, but OMITTAG NO was specified
    …108/Worms/newest-1.html">Worms</a><br><a class="alst" href="http://www.toongam…

    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 1629, Column 2474: start tag was here
    …cat/108/Worms/newest-1.html">Worms</a><br><a class="alst" href="http://www.too…
  • Error Line 1629, Column 2577: end tag for "br" omitted, but OMITTAG NO was specified
    …="http://www.toongames.com/cat/109/Bubble/newest-1.html">Bubble</a>								<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 1629, Column 2573: start tag was here
    …="http://www.toongames.com/cat/109/Bubble/newest-1.html">Bubble</a>								<br>
  • Error Line 1633, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    								<br><a class="alst" href="http://www.toongames.com/cat/110/Air-Hockey/n…

    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 1633, Column 9: start tag was here
    								<br><a class="alst" href="http://www.toongames.com/cat/110/Air-Hockey/n…
  • Error Line 1633, Column 112: end tag for "br" omitted, but OMITTAG NO was specified
    …ckey/newest-1.html">Air Hockey</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 108: start tag was here
    …r-Hockey/newest-1.html">Air Hockey</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 209: end tag for "br" omitted, but OMITTAG NO was specified
    …etics/newest-1.html">Athletics</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 205: start tag was here
    …Athletics/newest-1.html">Athletics</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 304: end tag for "br" omitted, but OMITTAG NO was specified
    …seball/newest-1.html">Baseball</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 300: start tag was here
    …2/Baseball/newest-1.html">Baseball</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 403: end tag for "br" omitted, but OMITTAG NO was specified
    …ball/newest-1.html">Basketball</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 399: start tag was here
    …sketball/newest-1.html">Basketball</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 500: end tag for "br" omitted, but OMITTAG NO was specified
    …iards/newest-1.html">Billiards</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 496: start tag was here
    …Billiards/newest-1.html">Billiards</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 593: end tag for "br" omitted, but OMITTAG NO was specified
    …Bowling/newest-1.html">Bowling</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 589: start tag was here
    …115/Bowling/newest-1.html">Bowling</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 684: end tag for "br" omitted, but OMITTAG NO was specified
    …6/Boxing/newest-1.html">Boxing</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 680: start tag was here
    …t/116/Boxing/newest-1.html">Boxing</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 777: end tag for "br" omitted, but OMITTAG NO was specified
    …Cricket/newest-1.html">Cricket</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 773: start tag was here
    …117/Cricket/newest-1.html">Cricket</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 870: end tag for "br" omitted, but OMITTAG NO was specified
    …Cycling/newest-1.html">Cycling</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 866: start tag was here
    …118/Cycling/newest-1.html">Cycling</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 959: end tag for "br" omitted, but OMITTAG NO was specified
    …119/Darts/newest-1.html">Darts</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 955: start tag was here
    …cat/119/Darts/newest-1.html">Darts</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 1056: end tag for "br" omitted, but OMITTAG NO was specified
    …eball/newest-1.html">Dodgeball</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 1052: start tag was here
    …Dodgeball/newest-1.html">Dodgeball</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 1151: end tag for "br" omitted, but OMITTAG NO was specified
    …otball/newest-1.html">Football</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 1147: start tag was here
    …1/Football/newest-1.html">Football</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 1256: end tag for "br" omitted, but OMITTAG NO was specified
    …g/newest-1.html">Goal Shooting</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 1252: start tag was here
    …oting/newest-1.html">Goal Shooting</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 1343: end tag for "br" omitted, but OMITTAG NO was specified
    …t/123/Golf/newest-1.html">Golf</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 1339: start tag was here
    …m/cat/123/Golf/newest-1.html">Golf</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 1434: end tag for "br" omitted, but OMITTAG NO was specified
    …4/Hockey/newest-1.html">Hockey</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 1430: start tag was here
    …t/124/Hockey/newest-1.html">Hockey</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 1523: end tag for "br" omitted, but OMITTAG NO was specified
    …125/Rugby/newest-1.html">Rugby</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 1519: start tag was here
    …cat/125/Rugby/newest-1.html">Rugby</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 1628: end tag for "br" omitted, but OMITTAG NO was specified
    …g/newest-1.html">Skateboarding</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 1624: start tag was here
    …rding/newest-1.html">Skateboarding</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 1731: end tag for "br" omitted, but OMITTAG NO was specified
    …is/newest-1.html">Table Tennis</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 1727: start tag was here
    …Tennis/newest-1.html">Table Tennis</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 1822: end tag for "br" omitted, but OMITTAG NO was specified
    …8/Tennis/newest-1.html">Tennis</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 1818: start tag was here
    …t/128/Tennis/newest-1.html">Tennis</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 1921: end tag for "br" omitted, but OMITTAG NO was specified
    …ball/newest-1.html">Volleyball</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 1917: start tag was here
    …lleyball/newest-1.html">Volleyball</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 2024: end tag for "br" omitted, but OMITTAG NO was specified
    …ts/newest-1.html">Water Sports</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 2020: start tag was here
    …Sports/newest-1.html">Water Sports</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 2129: end tag for "br" omitted, but OMITTAG NO was specified
    …s/newest-1.html">Winter Sports</a><br><a class="alst" href="http://www.toongam…

    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 1633, Column 2125: start tag was here
    …ports/newest-1.html">Winter Sports</a><br><a class="alst" href="http://www.too…
  • Error Line 1633, Column 2234: end tag for "br" omitted, but OMITTAG NO was specified
    …ww.toongames.com/cat/132/Wrestling/newest-1.html">Wrestling</a>								<br><br>

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

  • Info Line 1633, Column 2230: start tag was here
    …ww.toongames.com/cat/132/Wrestling/newest-1.html">Wrestling</a>								<br><br>
  • Error Line 1633, Column 2238: end tag for "br" omitted, but OMITTAG NO was specified
    …ww.toongames.com/cat/132/Wrestling/newest-1.html">Wrestling</a>								<br><br>

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

  • Info Line 1633, Column 2234: start tag was here
    …ww.toongames.com/cat/132/Wrestling/newest-1.html">Wrestling</a>								<br><br>
  • Error Line 1635, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    								<br><a class="alst" href="http://www.toongames.com/cat/133/Strategy/new…

    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 1635, Column 9: start tag was here
    								<br><a class="alst" href="http://www.toongames.com/cat/133/Strategy/new…
  • Error Line 1635, Column 108: end tag for "br" omitted, but OMITTAG NO was specified
    …rategy/newest-1.html">Strategy</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 104: start tag was here
    …3/Strategy/newest-1.html">Strategy</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 213: end tag for "br" omitted, but OMITTAG NO was specified
    …e/newest-1.html">Tower Defense</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 209: start tag was here
    …fense/newest-1.html">Tower Defense</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 306: end tag for "br" omitted, but OMITTAG NO was specified
    …Farming/newest-1.html">Farming</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 302: start tag was here
    …135/Farming/newest-1.html">Farming</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 405: end tag for "br" omitted, but OMITTAG NO was specified
    …ment/newest-1.html">Management</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 401: start tag was here
    …nagement/newest-1.html">Management</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 512: end tag for "br" omitted, but OMITTAG NO was specified
    …/newest-1.html">101 Dalmatians</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 508: start tag was here
    …ians/newest-1.html">101 Dalmatians</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 601: end tag for "br" omitted, but OMITTAG NO was specified
    …138/Bambi/newest-1.html">Bambi</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 597: start tag was here
    …cat/138/Bambi/newest-1.html">Bambi</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 688: end tag for "br" omitted, but OMITTAG NO was specified
    …t/139/Bolt/newest-1.html">Bolt</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 684: start tag was here
    …m/cat/139/Bolt/newest-1.html">Bolt</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 787: end tag for "br" omitted, but OMITTAG NO was specified
    …ella/newest-1.html">Cinderella</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 783: start tag was here
    …nderella/newest-1.html">Cinderella</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 888: end tag for "br" omitted, but OMITTAG NO was specified
    …uck/newest-1.html">Donald Duck</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 884: start tag was here
    …ld-Duck/newest-1.html">Donald Duck</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 977: end tag for "br" omitted, but OMITTAG NO was specified
    …142/Dumbo/newest-1.html">Dumbo</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 973: start tag was here
    …cat/142/Dumbo/newest-1.html">Dumbo</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 1078: end tag for "br" omitted, but OMITTAG NO was specified
    …les/newest-1.html">Incredibles</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 1074: start tag was here
    …edibles/newest-1.html">Incredibles</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 1179: end tag for "br" omitted, but OMITTAG NO was specified
    …uck/newest-1.html">Donald Duck</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 1175: start tag was here
    …ld-Duck/newest-1.html">Donald Duck</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 1268: end tag for "br" omitted, but OMITTAG NO was specified
    …145/Dumbo/newest-1.html">Dumbo</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 1264: start tag was here
    …cat/145/Dumbo/newest-1.html">Dumbo</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 1377: end tag for "br" omitted, but OMITTAG NO was specified
    …newest-1.html">The Incredibles</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 1373: start tag was here
    …les/newest-1.html">The Incredibles</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 1492: end tag for "br" omitted, but OMITTAG NO was specified
    …est-1.html">Lady And The Tramp</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 1488: start tag was here
    …/newest-1.html">Lady And The Tramp</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 1589: end tag for "br" omitted, but OMITTAG NO was specified
    …r-Pan/newest-1.html">Peter Pan</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 1585: start tag was here
    …Peter-Pan/newest-1.html">Peter Pan</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 1686: end tag for "br" omitted, but OMITTAG NO was specified
    …cchio/newest-1.html">Pinocchio</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 1682: start tag was here
    …Pinocchio/newest-1.html">Pinocchio</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 1795: end tag for "br" omitted, but OMITTAG NO was specified
    …newest-1.html">Sleeping Beauty</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 1791: start tag was here
    …uty/newest-1.html">Sleeping Beauty</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 1892: end tag for "br" omitted, but OMITTAG NO was specified
    …Story/newest-1.html">Toy Story</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 1888: start tag was here
    …Toy-Story/newest-1.html">Toy Story</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 1995: end tag for "br" omitted, but OMITTAG NO was specified
    …ns/newest-1.html">The Simpsons</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 1991: start tag was here
    …mpsons/newest-1.html">The Simpsons</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 2100: end tag for "br" omitted, but OMITTAG NO was specified
    …y/newest-1.html">Tom And Jerry</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 2096: start tag was here
    …Jerry/newest-1.html">Tom And Jerry</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 2203: end tag for "br" omitted, but OMITTAG NO was specified
    …nc/newest-1.html">Monsters Inc</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 2199: start tag was here
    …rs-Inc/newest-1.html">Monsters Inc</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 2306: end tag for "br" omitted, but OMITTAG NO was specified
    …vo/newest-1.html">Johnny Bravo</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 2302: start tag was here
    …-Bravo/newest-1.html">Johnny Bravo</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 2395: end tag for "br" omitted, but OMITTAG NO was specified
    …156/Sonic/newest-1.html">Sonic</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 2391: start tag was here
    …cat/156/Sonic/newest-1.html">Sonic</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 2486: end tag for "br" omitted, but OMITTAG NO was specified
    …7/Batman/newest-1.html">Batman</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 2482: start tag was here
    …t/157/Batman/newest-1.html">Batman</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 2585: end tag for "br" omitted, but OMITTAG NO was specified
    …-Doo/newest-1.html">Scooby Doo</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 2581: start tag was here
    …ooby-Doo/newest-1.html">Scooby Doo</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 2686: end tag for "br" omitted, but OMITTAG NO was specified
    …ong/newest-1.html">Donkey Kong</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 2682: start tag was here
    …ey-Kong/newest-1.html">Donkey Kong</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 2799: end tag for "br" omitted, but OMITTAG NO was specified
    …west-1.html">Dora The Explorer</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 2795: start tag was here
    …r/newest-1.html">Dora The Explorer</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 2888: end tag for "br" omitted, but OMITTAG NO was specified
    …161/Ben10/newest-1.html">Ben10</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 2884: start tag was here
    …cat/161/Ben10/newest-1.html">Ben10</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 2987: end tag for "br" omitted, but OMITTAG NO was specified
    …Slug/newest-1.html">Metal Slug</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 2983: start tag was here
    …tal-Slug/newest-1.html">Metal Slug</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 3084: end tag for "br" omitted, but OMITTAG NO was specified
    …erman/newest-1.html">Spiderman</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 3080: start tag was here
    …Spiderman/newest-1.html">Spiderman</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 3195: end tag for "br" omitted, but OMITTAG NO was specified
    …ewest-1.html">Other Toon Games</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 3191: start tag was here
    …es/newest-1.html">Other Toon Games</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 3298: end tag for "br" omitted, but OMITTAG NO was specified
    …ns/newest-1.html">Looney Toons</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 3294: start tag was here
    …-Toons/newest-1.html">Looney Toons</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 3389: end tag for "br" omitted, but OMITTAG NO was specified
    …6/Naruto/newest-1.html">Naruto</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 3385: start tag was here
    …t/166/Naruto/newest-1.html">Naruto</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 3476: end tag for "br" omitted, but OMITTAG NO was specified
    …t/167/Hulk/newest-1.html">Hulk</a><br><a class="alst" href="http://www.toongam…

    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 1635, Column 3472: start tag was here
    …m/cat/167/Hulk/newest-1.html">Hulk</a><br><a class="alst" href="http://www.too…
  • Error Line 1635, Column 3587: end tag for "br" omitted, but OMITTAG NO was specified
    ….toongames.com/cat/168/Transformers/newest-1.html">Transformers</a>								<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 1635, Column 3583: start tag was here
    ….toongames.com/cat/168/Transformers/newest-1.html">Transformers</a>								<br>
  • Error Line 1698, Column 7: end tag for "br" omitted, but OMITTAG NO was specified
    		<br> Admin<b>@</b>ToonGames.com

    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 1698, Column 3: start tag was here
    		<br> Admin<b>@</b>ToonGames.com
  • Error Line 1701, Column 166: end tag for "br" omitted, but OMITTAG NO was specified
    …lize, and play new games everyday.<br>With an ever-expanding showcase of free …

    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 1701, Column 162: start tag was here
    …ocialize, and play new games everyday.<br>With an ever-expanding showcase of f…
  • Error Line 1701, Column 307: end tag for "br" omitted, but OMITTAG NO was specified
    …es suitable for the entire family.<br>&copy; Copyright 2013 ToonGame, Inc. All…

    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 1701, Column 303: start tag was here
    … games suitable for the entire family.<br>&copy; Copyright 2013 ToonGame, Inc.…
  • Error Line 1707, Column 57: required attribute "type" not specified
    		<script src="http://connect.facebook.net/en_US/all.js"></script>

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

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

  • Error Line 1708, Column 10: required attribute "type" not specified
    		<script>

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

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

  • Error Line 1721, Column 6: end tag for element "div" which is not open
    </div>

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

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

  • Error Line 1743, Column 140: document type does not allow element "script" here
    …/ai01538f50bcb1970b014e8b11de7a970d.js?ord='+ Math.random() + '"></sc'+'ript>')

    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 1743, Column 145: delimiter "'" invalid: only S separators and TAGC allowed here
    …/ai01538f50bcb1970b014e8b11de7a970d.js?ord='+ Math.random() + '"></sc'+'ript>')
  • Error Line 1743, Column 145: end tag for element "sc" which is not open
    …/ai01538f50bcb1970b014e8b11de7a970d.js?ord='+ Math.random() + '"></sc'+'ript>')

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

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

Visitor Analysis

Daily Visitor
  • 8.517 visits

In Page Analysis