Watch Online TV, Sports, News and Entertainment for free at ATDee.Net ...

atdee.net
  • Domain Name
    atdee.net
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #11006
  • Page Size
    14.9 KB
  • Ip Address
    88.80.11.29
  • Heading
    H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    12 GIF, 0 JPG, 3 PNG

Website Meta Analysis

  • Title
    ATDee.Net - Watch Free Live Sports TV
  • Meta Keyword
    atdhe, P2P, football, NBA, MLB, Live, Freesoccer, Schedules, Sports, Livep2p, PPLive, Sopcast, TVAnts, Best , Gratis , Free, Euro2008, WC2010, Streams, Cricket, Golf, NFL, NHL, Formula1, Cycling, Tennis, ATP, WTA, Handball, Horse Racing, Boxing, UEFA, live tv, live television, watch tv, live internet, live tv channels,live tv online, live internet tv, tv broadcast, live tv broadcasts, television, tv, livetv, vod, video on demand, free, player, media player, serie a, ligue 1, premier league, la liga, liga sagres, bundesliga, atdhenet, atdhe.net
  • Meta Description
    Watch Online TV, Sports, News and Entertainment for free at ATDee.Net

Technical Analysis

  • Webserver
    lighttpd/1.4.19
  • Ip Address
    88.80.11.29
  • Domain Age
    8 Months, 24 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • connection: close
  • content-type: text/html
  • accept-ranges: bytes
  • etag: "451312335"
  • last-modified: Fri, 27 Sep 2013 08:04:23 GMT
  • content-length: 13868
  • date: Fri, 27 Sep 2013 11:41:27 GMT
  • server: lighttpd/1.4.19
  • age: 4
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
No data whois for atdee.net

DNS Analysis


DNS servers
dns2.registrar-servers.com [208.64.122.242]
dns1.registrar-servers.com [38.101.213.194]
dns3.registrar-servers.com [173.224.125.12]
dns4.registrar-servers.com [173.236.55.99]
dns5.registrar-servers.com [188.138.2.23]


DNS Records

Answer records
atdee.net MX
preference: 15
exchange: eforward4.registrar-servers.com
1800s
atdee.net MX
preference: 20
exchange: eforward5.registrar-servers.com
1800s
atdee.net A 88.80.11.29 1800s
atdee.net MX
preference: 10
exchange: eforward3.registrar-servers.com
1800s
atdee.net MX
preference: 10
exchange: eforward1.registrar-servers.com
1800s
atdee.net NS  dns5.registrar-servers.com 1800s
atdee.net NS  dns1.registrar-servers.com 1800s
atdee.net NS  dns3.registrar-servers.com 1800s
atdee.net TXT v=spf1 include:spf.efwd.registrar-servers.com ~all 1800s
atdee.net NS  dns4.registrar-servers.com 1800s
atdee.net SOA
server: dns1.registrar-servers.com
email: hostmaster@registrar-servers.com
serial: 2013012000
refresh: 3600
retry: 1801
expire: 604800
minimum ttl: 3601
3601s
atdee.net NS  dns2.registrar-servers.com 1800s
atdee.net MX
preference: 10
exchange: eforward2.registrar-servers.com
1800s

Authority records

Additional records

IP 88.80.11.29 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 41 Errors
  • 21 Warnings
Ratio Text/Html
  • 0.6407130685542011
Message Error
  • Error Line 4, Column 158: end tag for "meta" omitted, but OMITTAG NO was specified
    …ontent="Watch Online TV, Sports, News and Entertainment for free at ATDee.Net">

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

  • Info Line 4, Column 53: start tag was here
    …et - Watch Free Live Sports TV</title><meta name="description" content="Watch …
  • Error Line 5, Column 583: end tag for "meta" omitted, but OMITTAG NO was specified
    …igue 1, premier league, la liga, liga sagres, bundesliga, atdhenet, atdhe.net">

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

  • Info Line 5, Column 1: start tag was here
    <meta name="keywords" content="atdhe, P2P, football, NBA, MLB, Live, Freesoccer…
  • Error Line 6, Column 45: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="robots" content="INDEX, FOLLOW">

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

  • Info Line 6, Column 1: start tag was here
    <meta name="robots" content="INDEX, FOLLOW">
  • Error Line 7, Column 45: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="revisit-after" content="1 DAYS">

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

  • Info Line 7, Column 1: start tag was here
    <meta name="revisit-after" content="1 DAYS">
  • Error Line 8, Column 44: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="copyright" content="ATDee.Net">

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

  • Info Line 8, Column 1: start tag was here
    <meta name="copyright" content="ATDee.Net">
  • Error Line 10, Column 96: end tag for "meta" omitted, but OMITTAG NO was specified
    …e" content="Watch Online Sports, News and Entertainment for free at ATDee.Net">

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

  • Info Line 10, Column 1: start tag was here
    <meta name="title" content="Watch Online Sports, News and Entertainment for fre…
  • Error Line 11, Column 50: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Language" content="EN">

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

  • Info Line 11, Column 1: start tag was here
    <meta http-equiv="Content-Language" content="EN">
  • Error Line 27, Column 21: there is no attribute "onClick"
    <a href="#" onClick="bookmark('http://atdee.net/','ATDee.Net - Free Live Sports…

    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 27, Column 119: end tag for "br" omitted, but OMITTAG NO was specified
    …tdee.net/','ATDee.Net - Free Live Sports')">Bookmark this website</a><br /><br>

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

  • Info Line 27, Column 115: start tag was here
    …tdee.net/','ATDee.Net - Free Live Sports')">Bookmark this website</a><br /><br>
  • Warning Line 30, Column 89: cannot generate system identifier for general entity "u"
    …t.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 30, Column 89: general entity "u" not defined and no default entity
    …t.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 30, Column 90: reference not terminated by REFC delimiter
    ….com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 30, Column 90: reference to external entity in attribute value
    ….com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 30, Column 90: reference to entity "u" for which no system identifier could be generated
    ….com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 30, Column 88: entity was defined here
    …it.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script…
  • Warning Line 30, Column 99: cannot generate system identifier for general entity "width"
    …w/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END T…

    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 30, Column 99: general entity "width" not defined and no default entity
    …w/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END T…

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

  • Warning Line 30, Column 104: reference not terminated by REFC delimiter
    …ivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END TAG --…

    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 30, Column 104: reference to external entity in attribute value
    …ivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END TAG --…

    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 30, Column 104: reference to entity "width" for which no system identifier could be generated
    …ivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END TAG --…

    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 30, Column 98: entity was defined here
    …ww/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END …
  • Warning Line 30, Column 109: cannot generate system identifier for general entity "height"
    …ivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END TAG -->

    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 30, Column 109: general entity "height" not defined and no default entity
    …ivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END TAG -->

    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 30, Column 115: reference not terminated by REFC delimiter
    …ivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END TAG -->

    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 30, Column 115: reference to external entity in attribute value
    …ivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END TAG -->

    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 30, Column 115: reference to entity "height" for which no system identifier could be generated
    …ivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END TAG -->

    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 30, Column 108: entity was defined here
    …ivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END TAG -->
  • Error Line 32, Column 11: end tag for "br" omitted, but OMITTAG NO was specified
    <br /><br>

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

  • Info Line 32, Column 7: start tag was here
    <br /><br>
  • Error Line 38, Column 153: required attribute "alt" not specified
    …SYGhJrx3-XI/AAAAAAAAAAM/Rb4cL_EQqYw/s320/tv.gif" width="13" height="13" /></td>

    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 44, Column 153: required attribute "alt" not specified
    …SYGhJrx3-XI/AAAAAAAAAAM/Rb4cL_EQqYw/s320/tv.gif" width="13" height="13" /></td>

    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 50, Column 153: required attribute "alt" not specified
    …SYGhJrx3-XI/AAAAAAAAAAM/Rb4cL_EQqYw/s320/tv.gif" width="13" height="13" /></td>

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

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

  • Error Line 56, Column 118: required attribute "alt" not specified
    …p://img190.imageshack.us/img190/4600/pokerk.png" width="13" height="13" /></td>

    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 62, Column 153: required attribute "alt" not specified
    …SYGhJrx3-XI/AAAAAAAAAAM/Rb4cL_EQqYw/s320/tv.gif" width="13" height="13" /></td>

    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 68, Column 153: required attribute "alt" not specified
    …SYGhJrx3-XI/AAAAAAAAAAM/Rb4cL_EQqYw/s320/tv.gif" width="13" height="13" /></td>

    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 74, Column 153: required attribute "alt" not specified
    …SYGhJrx3-XI/AAAAAAAAAAM/Rb4cL_EQqYw/s320/tv.gif" width="13" height="13" /></td>

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

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

  • Error Line 80, Column 101: required attribute "alt" not specified
    …px"><img src="http://i48.tinypic.com/fktldg.png" width="32" height="10" /></td>

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

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

  • Error Line 86, Column 101: required attribute "alt" not specified
    …px"><img src="http://i48.tinypic.com/fktldg.png" width="32" height="10" /></td>

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

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

  • Error Line 92, Column 101: required attribute "alt" not specified
    …px"><img src="http://i48.tinypic.com/fktldg.png" width="32" height="10" /></td>

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

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

  • Error Line 98, Column 158: required attribute "alt" not specified
    …pI2SgI/AAAAAAAAACU/Q7VqRkdOS08/s320/hockey3.gif" width="13" height="13" /></td>

    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 100, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

    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 100, Column 214: there is no attribute "event"
    …etapp.com/product_download.php" event="Chicago Blackhawks vs Detroit Red Wings…

    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 100, Column 260: there is no attribute "cat"
    … Blackhawks vs Detroit Red Wings" cat="hockey" src="1"><u>Link 1</u></a> <a hr…

    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 100, Column 273: there is no attribute "src"
    …s Detroit Red Wings" cat="hockey" src="1"><u>Link 1</u></a> <a href="http://do…

    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 104, Column 159: required attribute "alt" not specified
    …CXyrI/AAAAAAAAAAk/-XGRau5_u-I/s320/football.gif" width="13" height="13" /></td>

    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 106, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 110, Column 159: required attribute "alt" not specified
    …CXyrI/AAAAAAAAAAk/-XGRau5_u-I/s320/football.gif" width="13" height="13" /></td>

    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 112, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 116, Column 159: required attribute "alt" not specified
    …CXyrI/AAAAAAAAAAk/-XGRau5_u-I/s320/football.gif" width="13" height="13" /></td>

    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 118, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 122, Column 159: required attribute "alt" not specified
    …CXyrI/AAAAAAAAAAk/-XGRau5_u-I/s320/football.gif" width="13" height="13" /></td>

    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 124, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 128, Column 159: required attribute "alt" not specified
    …CXyrI/AAAAAAAAAAk/-XGRau5_u-I/s320/football.gif" width="13" height="13" /></td>

    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 130, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 134, Column 159: required attribute "alt" not specified
    …CXyrI/AAAAAAAAAAk/-XGRau5_u-I/s320/football.gif" width="13" height="13" /></td>

    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 136, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 140, Column 158: required attribute "alt" not specified
    …pI2SgI/AAAAAAAAACU/Q7VqRkdOS08/s320/hockey3.gif" width="13" height="13" /></td>

    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 142, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 146, Column 158: required attribute "alt" not specified
    …pI2SgI/AAAAAAAAACU/Q7VqRkdOS08/s320/hockey3.gif" width="13" height="13" /></td>

    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 148, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 152, Column 158: required attribute "alt" not specified
    …pI2SgI/AAAAAAAAACU/Q7VqRkdOS08/s320/hockey3.gif" width="13" height="13" /></td>

    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 154, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 158, Column 153: required attribute "alt" not specified
    …SYGhJrx3-XI/AAAAAAAAAAM/Rb4cL_EQqYw/s320/tv.gif" width="13" height="13" /></td>

    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 160, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 164, Column 161: required attribute "alt" not specified
    …iKI/AAAAAAAAAAc/JVYM_hn9Uzo/s320/basketball.gif" width="13" height="13" /></td>

    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 166, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 170, Column 159: required attribute "alt" not specified
    …CXyrI/AAAAAAAAAAk/-XGRau5_u-I/s320/football.gif" width="13" height="13" /></td>

    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 172, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 176, Column 161: required attribute "alt" not specified
    …iKI/AAAAAAAAAAc/JVYM_hn9Uzo/s320/basketball.gif" width="13" height="13" /></td>

    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 178, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 182, Column 161: required attribute "alt" not specified
    …iKI/AAAAAAAAAAc/JVYM_hn9Uzo/s320/basketball.gif" width="13" height="13" /></td>

    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 184, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 188, Column 161: required attribute "alt" not specified
    …iKI/AAAAAAAAAAc/JVYM_hn9Uzo/s320/basketball.gif" width="13" height="13" /></td>

    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 190, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 194, Column 158: required attribute "alt" not specified
    …pI2SgI/AAAAAAAAACU/Q7VqRkdOS08/s320/hockey3.gif" width="13" height="13" /></td>

    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 196, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 200, Column 161: required attribute "alt" not specified
    …iKI/AAAAAAAAAAc/JVYM_hn9Uzo/s320/basketball.gif" width="13" height="13" /></td>

    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 202, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 206, Column 161: required attribute "alt" not specified
    …iKI/AAAAAAAAAAc/JVYM_hn9Uzo/s320/basketball.gif" width="13" height="13" /></td>

    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 208, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 212, Column 159: required attribute "alt" not specified
    …CXyrI/AAAAAAAAAAk/-XGRau5_u-I/s320/football.gif" width="13" height="13" /></td>

    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 214, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 218, Column 158: required attribute "alt" not specified
    …pI2SgI/AAAAAAAAACU/Q7VqRkdOS08/s320/hockey3.gif" width="13" height="13" /></td>

    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 220, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 224, Column 158: required attribute "alt" not specified
    …pI2SgI/AAAAAAAAACU/Q7VqRkdOS08/s320/hockey3.gif" width="13" height="13" /></td>

    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 226, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 230, Column 161: required attribute "alt" not specified
    …iKI/AAAAAAAAAAc/JVYM_hn9Uzo/s320/basketball.gif" width="13" height="13" /></td>

    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 232, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

    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 158: required attribute "alt" not specified
    …pI2SgI/AAAAAAAAACU/Q7VqRkdOS08/s320/hockey3.gif" width="13" height="13" /></td>

    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 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

    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 158: required attribute "alt" not specified
    …pI2SgI/AAAAAAAAACU/Q7VqRkdOS08/s320/hockey3.gif" width="13" height="13" /></td>

    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 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 248, Column 161: required attribute "alt" not specified
    …iKI/AAAAAAAAAAc/JVYM_hn9Uzo/s320/basketball.gif" width="13" height="13" /></td>

    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 250, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

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

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

  • Error Line 254, Column 159: required attribute "alt" not specified
    …CXyrI/AAAAAAAAAAk/-XGRau5_u-I/s320/football.gif" width="13" height="13" /></td>

    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 256, Column 139: required attribute "alt" not specified
    …5.tinypic.com/wbvwwz.png" border="0" /></a> <a href="http://download.atdheneta…

    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 265, Column 90: reference not terminated by REFC delimiter
    …it.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 265, Column 90: reference to external entity in attribute value
    …it.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 265, Column 90: reference to entity "u" for which no system identifier could be generated
    …it.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 30, Column 88: entity was defined here
    …it.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script…
  • Warning Line 265, Column 104: reference not terminated by REFC delimiter
    …it.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 265, Column 104: reference to external entity in attribute value
    …it.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 265, Column 104: reference to entity "width" for which no system identifier could be generated
    …it.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 30, Column 98: entity was defined here
    …ww/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END …
  • Warning Line 265, Column 115: reference not terminated by REFC delimiter
    …it.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 265, Column 115: reference to external entity in attribute value
    …it.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 265, Column 115: reference to entity "height" for which no system identifier could be generated
    …it.com///www/delivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></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 30, Column 108: entity was defined here
    …ivery/fpi.js#?z=187436&u=atdlive&width=728&height=90"></script><!-- END TAG -->
  • Warning Line 268, Column 91: cannot generate system identifier for general entity "rotateur"
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=84936"></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 268, Column 91: general entity "rotateur" not defined and no default entity
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=84936"></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 268, Column 99: reference not terminated by REFC delimiter
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=84936"></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 268, Column 99: reference to external entity in attribute value
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=84936"></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 268, Column 99: reference to entity "rotateur" for which no system identifier could be generated
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=84936"></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 268, Column 90: entity was defined here
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=84936"></script>
  • Error Line 270, Column 6: end tag for "center" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 259, Column 1: start tag was here
    <center><br />
  • Error Line 274, Column 14: there is no attribute "TYPE"
    <SCRIPT TYPE="text/javascript" SRC="http://ad.harrenmedianetwork.com/st?ad_type…

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

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

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

  • Error Line 274, Column 36: there is no attribute "SRC"
    <SCRIPT TYPE="text/javascript" SRC="http://ad.harrenmedianetwork.com/st?ad_type…

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

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

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

  • Warning Line 274, Column 85: cannot generate system identifier for general entity "ad_size"
    …harrenmedianetwork.com/st?ad_type=pop&ad_size=0x0&section=2686422&banned_pop_t…

    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 274, Column 85: general entity "ad_size" not defined and no default entity
    …harrenmedianetwork.com/st?ad_type=pop&ad_size=0x0&section=2686422&banned_pop_t…

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

  • Warning Line 274, Column 92: reference not terminated by REFC delimiter
    …edianetwork.com/st?ad_type=pop&ad_size=0x0&section=2686422&banned_pop_types=29…

    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 274, Column 92: reference to external entity in attribute value
    …edianetwork.com/st?ad_type=pop&ad_size=0x0&section=2686422&banned_pop_types=29…

    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 274, Column 92: reference to entity "ad_size" for which no system identifier could be generated
    …edianetwork.com/st?ad_type=pop&ad_size=0x0&section=2686422&banned_pop_types=29…

    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 274, Column 84: entity was defined here
    ….harrenmedianetwork.com/st?ad_type=pop&ad_size=0x0&section=2686422&banned_pop_…
  • Warning Line 274, Column 97: cannot generate system identifier for general entity "section"
    …etwork.com/st?ad_type=pop&ad_size=0x0&section=2686422&banned_pop_types=29&pop_…

    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 274, Column 97: general entity "section" not defined and no default entity
    …etwork.com/st?ad_type=pop&ad_size=0x0&section=2686422&banned_pop_types=29&pop_…

    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 274, Column 104: reference not terminated by REFC delimiter
    …com/st?ad_type=pop&ad_size=0x0&section=2686422&banned_pop_types=29&pop_times=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 274, Column 104: reference to external entity in attribute value
    …com/st?ad_type=pop&ad_size=0x0&section=2686422&banned_pop_types=29&pop_times=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 274, Column 104: reference to entity "section" for which no system identifier could be generated
    …com/st?ad_type=pop&ad_size=0x0&section=2686422&banned_pop_types=29&pop_times=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 274, Column 96: entity was defined here
    …network.com/st?ad_type=pop&ad_size=0x0&section=2686422&banned_pop_types=29&pop…
  • Warning Line 274, Column 113: cannot generate system identifier for general entity "banned_pop_types"
    …_type=pop&ad_size=0x0&section=2686422&banned_pop_types=29&pop_times=1&pop_freq…

    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 274, Column 113: general entity "banned_pop_types" not defined and no default entity
    …_type=pop&ad_size=0x0&section=2686422&banned_pop_types=29&pop_times=1&pop_freq…

    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 274, Column 129: reference not terminated by REFC delimiter
    …e=0x0&section=2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_…

    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 274, Column 129: reference to external entity in attribute value
    …e=0x0&section=2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_…

    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 274, Column 129: reference to entity "banned_pop_types" for which no system identifier could be generated
    …e=0x0&section=2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_…

    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 274, Column 112: entity was defined here
    …d_type=pop&ad_size=0x0&section=2686422&banned_pop_types=29&pop_times=1&pop_fre…
  • Warning Line 274, Column 133: cannot generate system identifier for general entity "pop_times"
    …0&section=2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url=…

    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 274, Column 133: general entity "pop_times" not defined and no default entity
    …0&section=2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url=…

    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 274, Column 142: reference not terminated by REFC delimiter
    …=2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></SCRIP…

    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 274, Column 142: reference to external entity in attribute value
    …=2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></SCRIP…

    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 274, Column 142: reference to entity "pop_times" for which no system identifier could be generated
    …=2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></SCRIP…

    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 274, Column 132: entity was defined here
    …x0&section=2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url…
  • Warning Line 274, Column 145: cannot generate system identifier for general entity "pop_frequency"
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></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 274, Column 145: general entity "pop_frequency" not defined and no default entity
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></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 274, Column 158: reference not terminated by REFC delimiter
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></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 274, Column 158: reference to external entity in attribute value
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></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 274, Column 158: reference to entity "pop_frequency" for which no system identifier could be generated
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></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 274, Column 144: entity was defined here
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></SCRIPT>
  • Warning Line 274, Column 165: cannot generate system identifier for general entity "pub_url"
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></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 274, Column 165: general entity "pub_url" not defined and no default entity
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></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 274, Column 172: reference not terminated by REFC delimiter
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></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 274, Column 172: reference to external entity in attribute value
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></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 274, Column 172: reference to entity "pub_url" for which no system identifier could be generated
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></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 274, Column 164: entity was defined here
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></SCRIPT>
  • Error Line 274, Column 174: element "SCRIPT" undefined
    …2686422&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url="></SCRIPT>

    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
  • 13.067 visits