arcadesafari.com

ArcadeSafari - Free online games, flash games, online games, free games to play, download games, free flash games and much more ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    arcadesafari.com
  • Favicon
  • Alexa Rank
    #6396
  • Google Page Rank
    PR 0
  • Ip Address
    74.120.16.117
  • Page Size
    39.5 KB
  • Images
    0 GIF, 30 JPG, 3 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 0 1 3 0

Website Meta Analysis



  • Title
    ArcadeSafari™ - Wildly Fun Games! Play Free Online Games and Fun Premium Games.
  • Meta Keyword
    free online games, online flash games, free games, free games to play, free games online, online games, sports games, addicting games, flash games, action agmes, sports games, shooting games, strategy games, submit games, arcade games
  • Meta Description
    ArcadeSafari - Free online games, flash games, online games, free games to play, download games, free flash games and much more

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    74.120.16.117
  • Domain Age
    12 Months, 0 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 08 Sep 2013 05:23:23 GMT
  • server: Apache
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 8815
  • connection: close
  • content-type: text/html;charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains By Proxy, LLC

Domain Name: ARCADESAFARI.COM

Domain servers in listed order:
NS21.DOMAINCONTROL.COM
NS22.DOMAINCONTROL.COM

DNS Analysis


DNS servers
ns1.arcadesafari.com [74.120.16.60]
ns2.arcadesafari.com [208.43.92.37]
ns3.arcadesafari.com [174.133.157.219]
ns4.arcadesafari.com [174.142.6.252]


DNS Records

Answer records
arcadesafari.com SOA
server: ns1.arcadesafari.com
email: hostmaster@arcadesafari.com
serial: 2012091306
refresh: 10800
retry: 600
expire: 2419200
minimum ttl: 3600
10800s
arcadesafari.com NS  ns1.arcadesafari.com 10800s
arcadesafari.com NS  ns2.arcadesafari.com 10800s
arcadesafari.com NS  ns3.arcadesafari.com 10800s
arcadesafari.com NS  ns4.arcadesafari.com 10800s
arcadesafari.com A 74.120.16.118 10800s
arcadesafari.com A 74.120.16.119 10800s
arcadesafari.com A 74.120.16.117 10800s
arcadesafari.com MX
preference: 10
exchange: mx.arcadesafari.com
10800s

Authority records

Additional records
ns1.arcadesafari.com A 74.120.16.60 10800s
ns2.arcadesafari.com A 208.43.92.37 10800s
ns3.arcadesafari.com A 174.133.157.219 10800s
ns4.arcadesafari.com A 174.142.6.252 10800s
mx.arcadesafari.com A 74.120.16.60 10800s

IP 74.120.16.117 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 109 Errors
  • 34 Warnings
Ratio Text/Html
  • 0.6060089020771513
Message Error
  • Error Line 52, Column 8: invalid comment declaration: found delimiter "[" outside comment but inside comment declaration
    			<!--[if IE 7]><![endif]-->
  • Info Line 44, Column 3: comment declaration started here
    		<!--[if IE 7]>
  • Error Line 52, Column 9: character data is not allowed here
    			<!--[if IE 7]><![endif]-->

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 52, Column 21: "endif" is not a reserved name
    			<!--[if IE 7]><![endif]-->
  • Error Line 166, Column 59: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <a class="addthis_button_facebook"><div class="addthis_fb"></div></a>

    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 167, Column 58: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <a class="addthis_button_twitter"><div class="addthis_tw"></div></a>

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

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

  • Warning Line 170, Column 85: cannot generate system identifier for general entity "domready"
    …this.com/js/300/addthis_widget.js#pub=ra-50868e653768ee77&domready=1"></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 170, Column 85: general entity "domready" not defined and no default entity
    …this.com/js/300/addthis_widget.js#pub=ra-50868e653768ee77&domready=1"></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 170, Column 93: reference not terminated by REFC delimiter
    …this.com/js/300/addthis_widget.js#pub=ra-50868e653768ee77&domready=1"></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 170, Column 93: reference to external entity in attribute value
    …this.com/js/300/addthis_widget.js#pub=ra-50868e653768ee77&domready=1"></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 170, Column 93: reference to entity "domready" for which no system identifier could be generated
    …this.com/js/300/addthis_widget.js#pub=ra-50868e653768ee77&domready=1"></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 170, Column 84: entity was defined here
    …this.com/js/300/addthis_widget.js#pub=ra-50868e653768ee77&domready=1"></script>
  • Error Line 170, Column 96: required attribute "type" not specified
    …this.com/js/300/addthis_widget.js#pub=ra-50868e653768ee77&domready=1"></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 175, Column 32: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<div class="latest-game-bg"></div>

    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 186, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<iframe style='border: 0px;' src=http://b1.arcadesafari.com/aj/b.php?siteID=11…
  • Error Line 186, Column 41: NET-enabling start-tag not immediately followed by null end-tag
    …iframe style='border: 0px;' src=http://b1.arcadesafari.com/aj/b.php?siteID=11&…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Warning Line 186, Column 81: cannot generate system identifier for general entity "size"
    …1.arcadesafari.com/aj/b.php?siteID=11&size=728x90&tag=old16 width=728 height=9…

    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 186, Column 81: general entity "size" not defined and no default entity
    …1.arcadesafari.com/aj/b.php?siteID=11&size=728x90&tag=old16 width=728 height=9…

    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 186, Column 85: reference not terminated by REFC delimiter
    …cadesafari.com/aj/b.php?siteID=11&size=728x90&tag=old16 width=728 height=90></…

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

  • Error Line 186, Column 85: reference to entity "size" for which no system identifier could be generated
    …cadesafari.com/aj/b.php?siteID=11&size=728x90&tag=old16 width=728 height=90></…

    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 186, Column 80: entity was defined here
    …b1.arcadesafari.com/aj/b.php?siteID=11&size=728x90&tag=old16 width=728 height=…
  • Warning Line 186, Column 93: cannot generate system identifier for general entity "tag"
    …fari.com/aj/b.php?siteID=11&size=728x90&tag=old16 width=728 height=90></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 186, Column 93: general entity "tag" not defined and no default entity
    …fari.com/aj/b.php?siteID=11&size=728x90&tag=old16 width=728 height=90></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 186, Column 96: reference not terminated by REFC delimiter
    …fari.com/aj/b.php?siteID=11&size=728x90&tag=old16 width=728 height=90></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.

  • Error Line 186, Column 96: reference to entity "tag" for which no system identifier could be generated
    …fari.com/aj/b.php?siteID=11&size=728x90&tag=old16 width=728 height=90></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 186, Column 92: entity was defined here
    …fari.com/aj/b.php?siteID=11&size=728x90&tag=old16 width=728 height=90></iframe>
  • Error Line 186, Column 131: end tag for element "iframe" which is not open
    …fari.com/aj/b.php?siteID=11&size=728x90&tag=old16 width=728 height=90></iframe>

    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 191, Column 5: end tag for element "td" which is not open
    </td>

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

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

  • Error Line 199, Column 27: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width="904" border=0 cellpadding="0" cellspacing="0">
  • Error Line 201, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<td width=5 rowspan="5"></td>
  • Error Line 202, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
       <td colspan=3><div style="height:5px;"></div></td>  
  • Error Line 205, Column 64: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<td class="loaderMainStageInner" id="loaderMainStage" rowspan=4 valign="top">
  • Error Line 208, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<td width=8 rowspan=4></td>
  • Error Line 208, Column 22: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<td width=8 rowspan=4></td>
  • Error Line 263, Column 27: character ";" not allowed in attribute specification list
    				for (i=0;i<elms.length;i++) {
  • Error Line 263, Column 27: element "elms.length" undefined
    				for (i=0;i<elms.length;i++) {

    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 266, Column 29: character ";" not allowed in attribute specification list
    							for (j=0;j<ecl.length;j++) {
  • Error Line 266, Column 29: element "ecl.length" undefined
    							for (j=0;j<ecl.length;j++) {

    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 273, Column 29: character ";" not allowed in attribute specification list
    							for (j=0;j<ecl.length;j++) {
  • Error Line 273, Column 29: element "ecl.length" undefined
    							for (j=0;j<ecl.length;j++) {

    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).
  • Warning Line 283, Column 14: character "&" is the first character of a delimiter but occurred as data
    		// Getting & Parsing XML data

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 296, Column 26: character ";" not allowed in attribute specification list
    		for(var x=0; x<elsCount; x++){	
  • Error Line 296, Column 26: element "elsCount" undefined
    		for(var x=0; x<elsCount; x++){	

    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 314, Column 164: required attribute "alt" not specified
    …derPrecache").innerHTML + '<img width="425" height="235" src="'+gameImage+'">';

    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 314, Column 165: end tag for "img" omitted, but OMITTAG NO was specified
    …derPrecache").innerHTML + '<img width="425" height="235" src="'+gameImage+'">';

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

  • Info Line 314, Column 115: start tag was here
    …ntById("loaderPrecache").innerHTML + '<img width="425" height="235" src="'+gam…
  • Error Line 317, Column 136: required attribute "alt" not specified
    …f="'+gameLink+'">'+'<img width="425" height="235" src="'+gameImage+'">'+'</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 317, Column 137: end tag for "img" omitted, but OMITTAG NO was specified
    …f="'+gameLink+'">'+'<img width="425" height="235" src="'+gameImage+'">'+'</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 317, Column 87: start tag was here
    …nnerHTML = '<a href="'+gameLink+'">'+'<img width="425" height="235" src="'+gam…
  • Error Line 320, Column 175: required attribute "alt" not specified
    …"46" src="http://aa.gv.facdn.com/as//images/slider-play-now.png">'+'</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 320, Column 176: end tag for "img" omitted, but OMITTAG NO was specified
    …"46" src="http://aa.gv.facdn.com/as//images/slider-play-now.png">'+'</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 320, Column 87: start tag was here
    …nerHTML  = '<a href="'+gameLink+'">'+'<img width="168" height="46" src="http:/…
  • Error Line 326, Column 49: character "'" is not allowed in the value of attribute "id"
    …ImgItems.innerHTML = '<div id="loaderS'+key+'" class="buttonClickHover" title=…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 326, Column 317: required attribute "alt" not specified
    …key].gameImage.replace('screenshot', 'image').replace('_s1', '_i1')+'"></div>';

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

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

  • Error Line 326, Column 323: end tag for "img" omitted, but OMITTAG NO was specified
    …key].gameImage.replace('screenshot', 'image').replace('_s1', '_i1')+'"></div>';

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

  • Info Line 326, Column 201: start tag was here
    …" onclick="loaderClickSlide('+key+')"><img width="78" height="78" src="'+loade…
  • Error Line 328, Column 99: character "'" is not allowed in the value of attribute "id"
    …Slider').innerHTML + '<div id="loaderS'+key+'" class="buttonClick" title="'+lo…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 328, Column 92: ID "loaderS'+key+'" already defined
    …d('mainSlider').innerHTML + '<div id="loaderS'+key+'" class="buttonClick" titl…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 326, Column 42: ID "loaderS'+key+'" first defined here
    …	loaderImgItems.innerHTML = '<div id="loaderS'+key+'" class="buttonClickHover"…
  • Error Line 328, Column 362: required attribute "alt" not specified
    …key].gameImage.replace('screenshot', 'image').replace('_s1', '_i1')+'"></div>';

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

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

  • Error Line 328, Column 368: end tag for "img" omitted, but OMITTAG NO was specified
    …key].gameImage.replace('screenshot', 'image').replace('_s1', '_i1')+'"></div>';

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

  • Info Line 328, Column 246: start tag was here
    …" onclick="loaderClickSlide('+key+')"><img width="78" height="78" src="'+loade…
  • Error Line 335, Column 49: character "'" is not allowed in the value of attribute "id"
    …CatItems.innerHTML = '<div id="loaderC'+loaderDataCat[key].gameCatId+'" class=…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 337, Column 103: character "'" is not allowed in the value of attribute "id"
    …tItems').innerHTML + '<div id="loaderC'+loaderDataCat[key].gameCatId+'" class=…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 337, Column 96: ID "loaderC'+loaderDataCat[key].gameCatId+'" already defined
    …oaderCatItems').innerHTML + '<div id="loaderC'+loaderDataCat[key].gameCatId+'"…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 335, Column 42: ID "loaderC'+loaderDataCat[key].gameCatId+'" first defined here
    …	loaderCatItems.innerHTML = '<div id="loaderC'+loaderDataCat[key].gameCatId+'"…
  • Error Line 346, Column 26: character ";" not allowed in attribute specification list
    		for(var x=0; x<elsCount; x++){
  • Error Line 346, Column 26: element "elsCount" undefined
    		for(var x=0; x<elsCount; x++){

    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 347, Column 176: required attribute "alt" not specified
    …innerHTML + '<img width="425" height="235" src="'+loaderData[x].gameImage+'">';

    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 347, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …innerHTML + '<img width="425" height="235" src="'+loaderData[x].gameImage+'">';

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

  • Info Line 347, Column 113: start tag was here
    …ntById("loaderPrecache").innerHTML + '<img width="425" height="235" src="'+loa…
  • Error Line 351, Column 164: required attribute "alt" not specified
    …">'+'<img width="425" height="235" src="'+loaderData[id].gameImage+'">'+'</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 351, Column 165: end tag for "img" omitted, but OMITTAG NO was specified
    …">'+'<img width="425" height="235" src="'+loaderData[id].gameImage+'">'+'</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 351, Column 100: start tag was here
    …href="'+loaderData[id].gameLink+'">'+'<img width="425" height="235" src="'+loa…
  • Error Line 354, Column 187: required attribute "alt" not specified
    …ht="46" src="http://aa.gv.facdn.com/as//images/slider-play-now.png">'+'</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 354, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …ht="46" src="http://aa.gv.facdn.com/as//images/slider-play-now.png">'+'</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 354, Column 99: start tag was here
    …href="'+loaderData[id].gameLink+'">'+'<img width="168" height="46" src="http:/…
  • Error Line 407, Column 9: end tag for "elsCount" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 346, Column 17: start tag was here
    		for(var x=0; x<elsCount; x++){
  • Error Line 407, Column 9: end tag for "elsCount" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 296, Column 17: start tag was here
    		for(var x=0; x<elsCount; x++){	
  • Error Line 407, Column 9: end tag for "ecl.length" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 273, Column 18: start tag was here
    							for (j=0;j<ecl.length;j++) {
  • Error Line 407, Column 9: end tag for "ecl.length" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 266, Column 18: start tag was here
    							for (j=0;j<ecl.length;j++) {
  • Error Line 407, Column 9: end tag for "elms.length" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 263, Column 15: start tag was here
    				for (i=0;i<elms.length;i++) {
  • Error Line 424, Column 11: there is no attribute "Alt"
    						Alt="Play Genie Jewels" /> 

    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 424, Column 32: required attribute "alt" not specified
    						Alt="Play Genie Jewels" /> 

    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 437, Column 31: required attribute "alt" not specified
    						Alt="Play Slots of Oz" /> 

    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 450, Column 30: required attribute "alt" not specified
    						Alt="Play Cupid Slot" /> 

    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 463, Column 32: required attribute "alt" not specified
    						Alt="Play Fairy Island" /> 

    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 476, Column 29: required attribute "alt" not specified
    						Alt="Play Wild Gold" /> 

    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 489, Column 32: required attribute "alt" not specified
    						Alt="Play Militia Wars" /> 

    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 502, Column 41: required attribute "alt" not specified
    						Alt="Play Fantasy DJ Beat Maker" /> 

    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 515, Column 38: required attribute "alt" not specified
    						Alt="Play Boardwalk Fortunes" /> 

    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 528, Column 41: required attribute "alt" not specified
    						Alt="Play Lost Kingdom Prophecy" /> 

    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 541, Column 34: required attribute "alt" not specified
    						Alt="Play Panda Fortunes" /> 

    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 554, Column 42: required attribute "alt" not specified
    						Alt="Play Atlantic City Fortunes" /> 

    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 567, Column 29: required attribute "alt" not specified
    						Alt="Play Jewel Fox" /> 

    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 580, Column 33: required attribute "alt" not specified
    						Alt="Play Chopper Slots" /> 

    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 593, Column 34: required attribute "alt" not specified
    						Alt="Play Aquarium Craze" /> 

    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 599, Column 29: document type does not allow element "br" here; assuming missing "li" start-tag
    				<br style="clear:both" />
  • Error Line 600, Column 8: end tag for "li" omitted, but OMITTAG NO was specified
    			</ul>			

    You may 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 5: start tag was here
    				<br style="clear:both" />
  • Error Line 627, Column 519: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ages/featured_download_game_bg.png" border=0 style="margin-left: -289px;"/></a>
  • Error Line 627, Column 550: required attribute "alt" not specified
    …ages/featured_download_game_bg.png" border=0 style="margin-left: -289px;"/></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>.

  • Warning Line 636, Column 75: character "&" is the first character of a delimiter but occurred as data
    …content_ctl1_FeaturedGames_01_sectionTitle">Action & Shooting Games</span></h5>

    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 708, Column 75: character "&" is the first character of a delimiter but occurred as data
    …0_content_ctl1_FeaturedGames_02_sectionTitle">Sports & Racing Games</span></h5>

    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 780, Column 75: character "&" is the first character of a delimiter but occurred as data
    …ontent_ctl1_FeaturedGames_03_sectionTitle">Arcade & Adventure Games</span></h5>

    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 989, Column 90: cannot generate system identifier for general entity "srvc"
    …dvertising.com/adcedge/lb?site=695501&srvc=1&betr=futureads_cs=1&betq=12054=42…

    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 989, Column 90: general entity "srvc" not defined and no default entity
    …dvertising.com/adcedge/lb?site=695501&srvc=1&betr=futureads_cs=1&betq=12054=42…

    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 989, Column 94: reference not terminated by REFC delimiter
    …tising.com/adcedge/lb?site=695501&srvc=1&betr=futureads_cs=1&betq=12054=428170…

    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 989, Column 94: reference to external entity in attribute value
    …tising.com/adcedge/lb?site=695501&srvc=1&betr=futureads_cs=1&betq=12054=428170…

    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 989, Column 94: reference to entity "srvc" for which no system identifier could be generated
    …tising.com/adcedge/lb?site=695501&srvc=1&betr=futureads_cs=1&betq=12054=428170…

    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 989, Column 89: entity was defined here
    …advertising.com/adcedge/lb?site=695501&srvc=1&betr=futureads_cs=1&betq=12054=4…
  • Warning Line 989, Column 97: cannot generate system identifier for general entity "betr"
    …ing.com/adcedge/lb?site=695501&srvc=1&betr=futureads_cs=1&betq=12054=428170" w…

    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 989, Column 97: general entity "betr" not defined and no default entity
    …ing.com/adcedge/lb?site=695501&srvc=1&betr=futureads_cs=1&betq=12054=428170" w…

    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 989, Column 101: reference not terminated by REFC delimiter
    …com/adcedge/lb?site=695501&srvc=1&betr=futureads_cs=1&betq=12054=428170" width…

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

  • Warning Line 989, Column 101: reference to external entity in attribute value
    …com/adcedge/lb?site=695501&srvc=1&betr=futureads_cs=1&betq=12054=428170" width…

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

  • Error Line 989, Column 101: reference to entity "betr" for which no system identifier could be generated
    …com/adcedge/lb?site=695501&srvc=1&betr=futureads_cs=1&betq=12054=428170" width…

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

  • Info Line 989, Column 96: entity was defined here
    …sing.com/adcedge/lb?site=695501&srvc=1&betr=futureads_cs=1&betq=12054=428170" …
  • Warning Line 989, Column 117: cannot generate system identifier for general entity "betq"
    …ite=695501&srvc=1&betr=futureads_cs=1&betq=12054=428170" width = "1" height = …

    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 989, Column 117: general entity "betq" not defined and no default entity
    …ite=695501&srvc=1&betr=futureads_cs=1&betq=12054=428170" width = "1" height = …

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

  • Warning Line 989, Column 121: reference not terminated by REFC delimiter
    …695501&srvc=1&betr=futureads_cs=1&betq=12054=428170" width = "1" height = "1" …

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

  • Warning Line 989, Column 121: reference to external entity in attribute value
    …695501&srvc=1&betr=futureads_cs=1&betq=12054=428170" width = "1" height = "1" …

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

  • Error Line 989, Column 121: reference to entity "betq" for which no system identifier could be generated
    …695501&srvc=1&betr=futureads_cs=1&betq=12054=428170" width = "1" height = "1" …

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

  • Info Line 989, Column 116: entity was defined here
    …site=695501&srvc=1&betr=futureads_cs=1&betq=12054=428170" width = "1" height =…
  • Error Line 989, Column 173: required attribute "alt" not specified
    …betq=12054=428170" width = "1" height = "1" border = "0"><!-- End AOL pixel -->

    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 989, Column 174: end tag for "img" omitted, but OMITTAG NO was specified
    …betq=12054=428170" width = "1" height = "1" border = "0"><!-- End AOL pixel -->

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

  • Info Line 989, Column 25: start tag was here
    <!-- Start AOL pixel --><img src="http://leadback.advertising.com/adcedge/lb?si…
  • Error Line 990, Column 165: required attribute "alt" not specified
    …35;rand=55576991" width="1" height="1" border="0"><!-- End ValueClick pixel -->

    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 990, Column 166: end tag for "img" omitted, but OMITTAG NO was specified
    …35;rand=55576991" width="1" height="1" border="0"><!-- End ValueClick pixel -->

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

  • Info Line 990, Column 32: start tag was here
    <!-- Start ValueClick pixel --><img src="http://media.fastclick.net/w/tre?ad_id…
  • Warning Line 991, Column 83: cannot generate system identifier for general entity "t"
    …//ads.bluelithium.com/pixel?id=979863&t=2" width="1" height="1" /><!-- End Yah…

    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 991, Column 83: general entity "t" not defined and no default entity
    …//ads.bluelithium.com/pixel?id=979863&t=2" width="1" height="1" /><!-- End Yah…

    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 991, Column 84: reference not terminated by REFC delimiter
    …/ads.bluelithium.com/pixel?id=979863&t=2" width="1" height="1" /><!-- End Yaho…

    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 991, Column 84: reference to external entity in attribute value
    …/ads.bluelithium.com/pixel?id=979863&t=2" width="1" height="1" /><!-- End Yaho…

    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 991, Column 84: reference to entity "t" for which no system identifier could be generated
    …/ads.bluelithium.com/pixel?id=979863&t=2" width="1" height="1" /><!-- End Yaho…

    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 991, Column 82: entity was defined here
    …://ads.bluelithium.com/pixel?id=979863&t=2" width="1" height="1" /><!-- End Ya…
  • Error Line 991, Column 110: required attribute "alt" not specified
    …ium.com/pixel?id=979863&t=2" width="1" height="1" /><!-- End Yahoo campaign -->

    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 992, Column 84: cannot generate system identifier for general entity "id"
    …tp://ad.trafficmp.com/a/bpix?adv=1717&id=2&format=javascript&r="></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 992, Column 84: general entity "id" not defined and no default entity
    …tp://ad.trafficmp.com/a/bpix?adv=1717&id=2&format=javascript&r="></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 992, Column 86: reference not terminated by REFC delimiter
    …://ad.trafficmp.com/a/bpix?adv=1717&id=2&format=javascript&r="></script><!-- E…

    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 992, Column 86: reference to external entity in attribute value
    …://ad.trafficmp.com/a/bpix?adv=1717&id=2&format=javascript&r="></script><!-- E…

    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 992, Column 86: reference to entity "id" for which no system identifier could be generated
    …://ad.trafficmp.com/a/bpix?adv=1717&id=2&format=javascript&r="></script><!-- E…

    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 992, Column 83: entity was defined here
    …ttp://ad.trafficmp.com/a/bpix?adv=1717&id=2&format=javascript&r="></script><!-…
  • Warning Line 992, Column 89: cannot generate system identifier for general entity "format"
    …ad.trafficmp.com/a/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End …

    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 992, Column 89: general entity "format" not defined and no default entity
    …ad.trafficmp.com/a/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End …

    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 992, Column 95: reference not terminated by REFC delimiter
    …fficmp.com/a/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End DB-TMP…

    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 992, Column 95: reference to external entity in attribute value
    …fficmp.com/a/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End DB-TMP…

    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 992, Column 95: reference to entity "format" for which no system identifier could be generated
    …fficmp.com/a/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End DB-TMP…

    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 992, Column 88: entity was defined here
    …/ad.trafficmp.com/a/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End…
  • Warning Line 992, Column 107: cannot generate system identifier for general entity "r"
    …/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End DB-TMP campaign --…

    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 992, Column 107: general entity "r" not defined and no default entity
    …/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End DB-TMP campaign --…

    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 992, Column 108: reference not terminated by REFC delimiter
    …/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End DB-TMP campaign -->

    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 992, Column 108: reference to external entity in attribute value
    …/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End DB-TMP campaign -->

    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 992, Column 108: reference to entity "r" for which no system identifier could be generated
    …/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End DB-TMP campaign -->

    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 992, Column 106: entity was defined here
    …a/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End DB-TMP campaign -…
  • Error Line 992, Column 110: required attribute "type" not specified
    …/bpix?adv=1717&id=2&format=javascript&r="></script><!-- End DB-TMP campaign -->

    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 993, Column 13: there is no attribute "SRC"
    <IFRAME SRC='http://this.content.served.by.adshuffle.com/p/kl/46/799/r/12/4/8/t…

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

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

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

  • Error Line 993, Column 116: there is no attribute "FRAMEBORDER"
    …/t/3847/rmktg/track.html' FRAMEBORDER='0' SCROLLING='NO' WIDTH='1' HEIGHT='1'>…

    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 993, Column 130: there is no attribute "SCROLLING"
    …rmktg/track.html' FRAMEBORDER='0' SCROLLING='NO' WIDTH='1' HEIGHT='1'></IFRAME>

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

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

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

  • Error Line 993, Column 141: there is no attribute "WIDTH"
    …rmktg/track.html' FRAMEBORDER='0' SCROLLING='NO' WIDTH='1' HEIGHT='1'></IFRAME>

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

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

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

  • Error Line 993, Column 152: there is no attribute "HEIGHT"
    …rmktg/track.html' FRAMEBORDER='0' SCROLLING='NO' WIDTH='1' HEIGHT='1'></IFRAME>

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

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

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

  • Error Line 993, Column 155: element "IFRAME" undefined
    …rmktg/track.html' FRAMEBORDER='0' SCROLLING='NO' WIDTH='1' HEIGHT='1'></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).

Visitor Analysis

Daily Visitor
  • 37.333 visits

In Page Analysis