Taringa! Juegos Gratis Online es una comunidad virtual donde los usuarios Taringa juegos para PC PS2 PS3 PSP XBOX con juegos de taringa y juegos online Juegos Descargar Gratis en 1 link ...

taringajuegos.net
  • Domain Name
    taringajuegos.net
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #20092
  • Page Size
    36.8 KB
  • Ip Address
    37.0.124.150
  • Heading
    H1: 1, H2: 10, H3: 5, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 1 JPG, 1 PNG

Website Meta Analysis

  • Title
    Taringa! Juegos Descargar Juegos Gratis [PC - PS3 - PS2 - PSP]
  • Meta Keyword
    Descargar Juegos Gratis , Juegos Nuevos , Juegos De Futbol , Juegos Taringa, Taringa Bajar Gratis Juegos, Juegos, Taringa, Taringa Juegos Gratis, Juegos De Acción, Juegos De Tiros, Juegos De Carreras, Juegos De Autos, Juegos De Estrategia, Juegos para PC, ps3, ps2, psp, descargar, 1 link
  • Meta Description
    Taringa! Juegos Gratis Online es una comunidad virtual donde los usuarios Taringa juegos para PC PS2 PS3 PSP XBOX con juegos de taringa y juegos online Juegos Descargar Gratis en 1 link

Technical Analysis

  • Webserver
    nginx/0.8.55
  • Ip Address
    37.0.124.150
  • Domain Age
    1 Years, 10 Months, 28 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/0.8.55
  • date: Wed, 23 Jan 2013 18:34:21 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.4.5
  • x-pingback: http://www.taringajuegos.net/xmlrpc.php
  • content-encoding: gzip
  • vary: Accept-Encoding
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: taringajuegos.net
Registrar: Name.com LLC

Protected Domain Services Customer ID: NCR-3146363

Expiration Date: 2013-03-08 03:32:35
Creation Date: 2011-03-08 03:32:35

Name Servers:
ns1fkl.name.com
ns2jqz.name.com
ns3gnv.name.com
ns4ghm.name.com

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

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

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

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

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

DNS Analysis


DNS servers
ns1fkl.name.com [108.168.138.47]
ns2jqz.name.com [5.153.6.219]
ns3gnv.name.com [208.43.116.40]
ns4ghm.name.com [184.72.223.220]


DNS Records

Answer records
taringajuegos.net NS  ns1fkl.name.com 300s
taringajuegos.net NS  ns3gnv.name.com 300s
taringajuegos.net A 37.0.124.150 300s
taringajuegos.net NS  ns2jqz.name.com 300s
taringajuegos.net NS  ns4ghm.name.com 300s
taringajuegos.net SOA
server: ns1fkl.name.com
email: support@name.com
serial: 1
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
300s

Authority records

Additional records
ns4ghm.name.com A 184.72.223.220 86400s
ns1fkl.name.com A 108.168.138.47 86400s
ns3gnv.name.com A 208.43.116.40 86400s
ns2jqz.name.com A 5.153.6.219 86400s

IP 37.0.124.150 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 94 Errors
  • 16 Warnings
Ratio Text/Html
  • 0.720682981149084
Message Error
  • Error Line 151, Column 12: element "u" undefined
    						<p><u>CAPÍTULO 1: EMBOSCADO</u> </p>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 183, Column 37: there is no attribute "border"
    						<p><img class="imagen" border="0" src="http://www.gameit.es/wp-content/up…

    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 183, Column 127: required attribute "alt" not specified
    …www.gameit.es/wp-content/uploads/2012/11/Call_of_Duty_Black_Ops_2_1.jpg" /></p>

    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 233, Column 124: required attribute "alt" not specified
    …28.photobucket.com/albums/ee449/IvanEdin54/tigrebarra2.png?t=1354417582" /></p>

    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 234, Column 145: required attribute "alt" not specified
    …rl=http://k40.kn3.net/taringa/1/2/1/5/4/1/04/no_soy_nadiee/434.jpg?4948" /></p>

    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 235, Column 124: required attribute "alt" not specified
    …28.photobucket.com/albums/ee449/IvanEdin54/tigrebarra2.png?t=1354417582" /></p>

    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 145: required attribute "alt" not specified
    …rl=http://k38.kn3.net/taringa/1/2/1/5/4/1/04/no_soy_nadiee/1E1.jpg?5274" /></p>

    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 237, Column 124: required attribute "alt" not specified
    …28.photobucket.com/albums/ee449/IvanEdin54/tigrebarra2.png?t=1354417582" /></p>

    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 238, Column 145: required attribute "alt" not specified
    …rl=http://k36.kn3.net/taringa/1/2/1/5/4/1/04/no_soy_nadiee/D7B.jpg?5249" /></p>

    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 239, Column 124: required attribute "alt" not specified
    …28.photobucket.com/albums/ee449/IvanEdin54/tigrebarra2.png?t=1354417582" /></p>

    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 240, Column 145: required attribute "alt" not specified
    …rl=http://k32.kn3.net/taringa/1/2/1/5/4/1/04/no_soy_nadiee/079.jpg?9182" /></p>

    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 241, Column 124: required attribute "alt" not specified
    …28.photobucket.com/albums/ee449/IvanEdin54/tigrebarra2.png?t=1354417582" /></p>

    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 145: required attribute "alt" not specified
    …rl=http://k39.kn3.net/taringa/1/2/1/5/4/1/04/no_soy_nadiee/928.jpg?5348" /></p>

    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 243, Column 124: required attribute "alt" not specified
    …28.photobucket.com/albums/ee449/IvanEdin54/tigrebarra2.png?t=1354417582" /></p>

    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 244, Column 145: required attribute "alt" not specified
    …rl=http://k43.kn3.net/taringa/1/2/1/5/4/1/04/no_soy_nadiee/EA6.jpg?4600" /></p>

    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 245, Column 124: required attribute "alt" not specified
    …28.photobucket.com/albums/ee449/IvanEdin54/tigrebarra2.png?t=1354417582" /></p>

    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 246, Column 145: required attribute "alt" not specified
    …rl=http://k38.kn3.net/taringa/1/2/1/5/4/1/04/no_soy_nadiee/AB2.jpg?7376" /></p>

    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 145: required attribute "alt" not specified
    …rl=http://k35.kn3.net/taringa/1/2/1/5/4/1/04/no_soy_nadiee/380.jpg?4928" /></p>

    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 266, Column 145: required attribute "alt" not specified
    …rl=http://k41.kn3.net/taringa/1/2/1/5/4/1/04/no_soy_nadiee/FFF.jpg?2080" /></p>

    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 267, Column 144: required attribute "alt" not specified
    …url=http://k36.kn3.net/taringa/1/2/1/5/4/1/04/no_soy_nadiee/9B3.jpg?731" /></p>

    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 269, Column 108: required attribute "alt" not specified
    … src="http://descargar.buscaid.com/images/mediafire_premium_buscaid.png" /></p>

    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 271, Column 63: there is no attribute "target"
    …ediafire.com/?7a53119ad1sawpt" target="_blank" rel="nofollow">http://www.media…

    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 288, Column 247: required attribute "alt" not specified
    …x; clip:rect(374px 16px 390px 0px);" /><img src="http://46.165.211.72/curl.php…

    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 288, Column 383: required attribute "alt" not specified
    …/images/space.gif" style="vertical-align:middle; width:16px;height:16px" /></p>

    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 371, Column 111: there is no attribute "FRAMEBORDER"
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…

    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 371, Column 111: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 371, Column 125: there is no attribute "MARGINWIDTH"
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …

    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 371, Column 125: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …
  • Error Line 371, Column 140: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 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 371, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 371, Column 152: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.m…

    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 371, Column 152: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.m…
  • Error Line 371, Column 161: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.metanetwor…

    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 371, Column 161: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.metanetwor…
  • Error Line 371, Column 172: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.metanetwork.com/st?ad…

    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 371, Column 172: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.metanetwork.com/st?ad…
  • Error Line 371, Column 180: there is no attribute "SRC"
    …SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.metanetwork.com/st?ad_type=if…

    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 371, Column 225: cannot generate system identifier for general entity "ad_size"
    …/ad.metanetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAM…

    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 371, Column 225: general entity "ad_size" not defined and no default entity
    …/ad.metanetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAM…

    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 371, Column 232: reference not terminated by REFC delimiter
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAME></div…

    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 371, Column 232: reference to external entity in attribute value
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAME></div…

    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 371, Column 232: reference to entity "ad_size" for which no system identifier could be generated
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAME></div…

    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 371, Column 224: entity was defined here
    …//ad.metanetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRA…
  • Warning Line 371, Column 241: cannot generate system identifier for general entity "section"
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAME></div>

    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 371, Column 241: general entity "section" not defined and no default entity
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAME></div>

    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 371, Column 248: reference not terminated by REFC delimiter
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAME></div>

    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 371, Column 248: reference to external entity in attribute value
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAME></div>

    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 371, Column 248: reference to entity "section" for which no system identifier could be generated
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAME></div>

    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 371, Column 240: entity was defined here
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAME></div>
  • Error Line 371, Column 257: element "IFRAME" undefined
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAME></div>

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

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

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

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

  • Error Line 495, Column 12: there is no attribute "id"
    <IFRAME id=fcontainer FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO W…

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

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

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

  • Error Line 495, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME id=fcontainer FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO W…
  • Error Line 495, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME id=fcontainer FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO W…
  • Error Line 495, Column 49: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=fcontainer FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …
  • Error Line 495, Column 64: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 495, Column 76: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.m…
  • Error Line 495, Column 85: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.metanetwor…
  • Error Line 495, Column 96: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://ad.metanetwork.com/st?ad…
  • Warning Line 495, Column 156: reference not terminated by REFC delimiter
    …ad.metanetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></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 495, Column 156: reference to external entity in attribute value
    …ad.metanetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></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 495, Column 156: reference to entity "ad_size" for which no system identifier could be generated
    …ad.metanetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></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 371, Column 224: entity was defined here
    …//ad.metanetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRA…
  • Warning Line 495, Column 172: reference not terminated by REFC delimiter
    …ad.metanetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></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 495, Column 172: reference to external entity in attribute value
    …ad.metanetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></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 495, Column 172: reference to entity "section" for which no system identifier could be generated
    …ad.metanetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></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 371, Column 240: entity was defined here
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAME></div>
  • Error Line 495, Column 181: element "IFRAME" undefined
    …ad.metanetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></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 497, Column 8: 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>.

  • Warning Line 500, Column 26: character "&" is the first character of a delimiter but occurred as data
    if($.cookie('dklik') !=1 && window.start){

    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 500, Column 27: character "&" is the first character of a delimiter but occurred as data
    if($.cookie('dklik') !=1 && window.start){

    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 510, Column 8: 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 520, Column 39: document type does not allow element "style" here
    document.write('<style type="text/css">#zzadfooter{position:fixed;left:0px; bot…

    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 521, Column 37: document type does not allow element "div" here
    document.write('<div id="zzadfooter"><TABLE width=100% border=0 cellspacing=0 c…

    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 521, Column 51: there is no attribute "width"
    …te('<div id="zzadfooter"><TABLE width=100% border=0 cellspacing=0 cellpadding=…

    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 521, Column 51: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …te('<div id="zzadfooter"><TABLE width=100% border=0 cellspacing=0 cellpadding=…
  • Error Line 521, Column 54: an attribute value must be a literal unless it contains only name characters
    …'<div id="zzadfooter"><TABLE width=100% border=0 cellspacing=0 cellpadding=0><…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 521, Column 63: there is no attribute "border"
    …"zzadfooter"><TABLE width=100% border=0 cellspacing=0 cellpadding=0><TR><TD va…

    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 521, Column 63: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …"zzadfooter"><TABLE width=100% border=0 cellspacing=0 cellpadding=0><TR><TD va…
  • Error Line 521, Column 77: there is no attribute "cellspacing"
    …TABLE width=100% border=0 cellspacing=0 cellpadding=0><TR><TD valign="bottom" …

    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 521, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …TABLE width=100% border=0 cellspacing=0 cellpadding=0><TR><TD valign="bottom" …
  • Error Line 521, Column 91: there is no attribute "cellpadding"
    …0% border=0 cellspacing=0 cellpadding=0><TR><TD valign="bottom" width=49%><div…

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

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

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

  • Error Line 521, Column 91: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0% border=0 cellspacing=0 cellpadding=0><TR><TD valign="bottom" width=49%><div…
  • Error Line 521, Column 92: element "TABLE" undefined
    …% border=0 cellspacing=0 cellpadding=0><TR><TD valign="bottom" width=49%><div …

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 521, Column 96: element "TR" undefined
    …rder=0 cellspacing=0 cellpadding=0><TR><TD valign="bottom" width=49%><div id="…

    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 521, Column 108: there is no attribute "valign"
    …pacing=0 cellpadding=0><TR><TD valign="bottom" width=49%><div id="zzleft" styl…

    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 521, Column 123: there is no attribute "width"
    …dding=0><TR><TD valign="bottom" width=49%><div id="zzleft" style="height:50px"…

    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 521, Column 123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …dding=0><TR><TD valign="bottom" width=49%><div id="zzleft" style="height:50px"…
  • Error Line 521, Column 125: an attribute value must be a literal unless it contains only name characters
    …ing=0><TR><TD valign="bottom" width=49%><div id="zzleft" style="height:50px"><…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 521, Column 126: element "TD" undefined
    …ng=0><TR><TD valign="bottom" width=49%><div id="zzleft" style="height:50px"></…

    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 521, Column 178: element "TD" undefined
    …ft" style="height:50px"></div></TD><TD><div id="zzadcontent" style="z-index:99…

    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 521, Column 236: there is no attribute "src"
    …t" style="z-index:99998;"><iframe src="http://ad.xtendmedia.com/st?ad_type=ifr…

    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 521, Column 287: reference not terminated by REFC delimiter
    …endmedia.com/st?ad_type=iframe&ad_size=728x90&section=2616315" frameborder=0 m…

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

  • Warning Line 521, Column 287: reference to external entity in attribute value
    …endmedia.com/st?ad_type=iframe&ad_size=728x90&section=2616315" frameborder=0 m…

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

  • Error Line 521, Column 287: reference to entity "ad_size" for which no system identifier could be generated
    …endmedia.com/st?ad_type=iframe&ad_size=728x90&section=2616315" frameborder=0 m…

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

  • Info Line 371, Column 224: entity was defined here
    …//ad.metanetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRA…
  • Warning Line 521, Column 302: reference not terminated by REFC delimiter
    …?ad_type=iframe&ad_size=728x90&section=2616315" frameborder=0 marginheight=0 m…

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

  • Warning Line 521, Column 302: reference to external entity in attribute value
    …?ad_type=iframe&ad_size=728x90&section=2616315" frameborder=0 marginheight=0 m…

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

  • Error Line 521, Column 302: reference to entity "section" for which no system identifier could be generated
    …?ad_type=iframe&ad_size=728x90&section=2616315" frameborder=0 marginheight=0 m…

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

  • Info Line 371, Column 240: entity was defined here
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=2831297"></IFRAME></div>
  • Error Line 521, Column 324: there is no attribute "frameborder"
    …e=728x90&section=2616315" frameborder=0 marginheight=0 marginwidth=0 scrolling…

    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 521, Column 324: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e=728x90&section=2616315" frameborder=0 marginheight=0 marginwidth=0 scrolling…
  • Error Line 521, Column 339: there is no attribute "marginheight"
    …n=2616315" frameborder=0 marginheight=0 marginwidth=0 scrolling="no" allowTran…

    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 521, Column 339: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …n=2616315" frameborder=0 marginheight=0 marginwidth=0 scrolling="no" allowTran…
  • Error Line 521, Column 353: there is no attribute "marginwidth"
    …meborder=0 marginheight=0 marginwidth=0 scrolling="no" allowTransparency="true…

    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 521, Column 353: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 scrolling="no" allowTransparency="true…
  • Error Line 521, Column 365: there is no attribute "scrolling"
    …arginheight=0 marginwidth=0 scrolling="no" allowTransparency="true" width=728 …

    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 521, Column 388: there is no attribute "allowTransparency"
    …th=0 scrolling="no" allowTransparency="true" width=728 height=90></iframe></di…

    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 521, Column 401: there is no attribute "width"
    …g="no" allowTransparency="true" width=728 height=90></iframe></div></TD><TD va…

    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 521, Column 401: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …g="no" allowTransparency="true" width=728 height=90></iframe></div></TD><TD va…
  • Error Line 521, Column 412: there is no attribute "height"
    …wTransparency="true" width=728 height=90></iframe></div></TD><TD valign="botto…

    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 521, Column 412: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …wTransparency="true" width=728 height=90></iframe></div></TD><TD valign="botto…
  • Error Line 521, Column 414: element "iframe" undefined
    …ransparency="true" width=728 height=90></iframe></div></TD><TD valign="bottom"…

    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 521, Column 461: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …></div></TD><TD valign="bottom" width=49%><div id="zzright" style="height:50px…
  • Error Line 521, Column 463: an attribute value must be a literal unless it contains only name characters
    …/div></TD><TD valign="bottom" width=49%><div id="zzright" style="height:50px">…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 521, Column 464: element "TD" undefined
    …div></TD><TD valign="bottom" width=49%><div id="zzright" style="height:50px"><…

    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
  • 11.200 visits
Daily Visitor