ILEMI: watch sport streams for free. Best ILEMI links for soccer, football, tennis right here. Updates every few minutes. ...

ilemi.co
  • Domain Name
    ilemi.co
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #485912
  • Page Size
    57.1 KB
  • Ip Address
    93.170.16.175
  • Heading
    H1: 1, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 3 JPG, 0 PNG

Website Meta Analysis

  • Title
    Watch live sports online at ILEMI
  • Meta Keyword
    ilemi, ilemi.com, ilemi.eu, ilemi football, watch online tv, sport streams, free sport streaming, illemi, ilemi.net
  • Meta Description
    ILEMI: watch sport streams for free. Best ILEMI links for soccer, football, tennis right here. Updates every few minutes.

Technical Analysis

  • Webserver
    Apache/2.2.16 (Debian)
  • Ip Address
    93.170.16.175
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from ilemi.co.

HTML Analysis

  • date: Thu, 12 Sep 2013 18:03:57 GMT
  • server: Apache/2.2.16 (Debian)
  • x-powered-by: Nette Framework
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 8428
  • connection: close
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for ilemi.co

DNS Analysis


DNS servers
ns2.uplink.cz [37.157.196.141]
ns1.uplink.cz [46.105.230.2]
ns3.uplink.cz [77.93.202.189]


DNS Records

Answer records
ilemi.co SOA
server: ns1.uplink.cz
email: support@uplink.cz
serial: 2008110104
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
3600s
ilemi.co NS  ns2.uplink.cz 3600s
ilemi.co NS  ns1.uplink.cz 3600s
ilemi.co NS  ns3.uplink.cz 3600s
ilemi.co A 93.170.16.175 3600s
ilemi.co MX
preference: 10
exchange: devnull.uplink.cz
3600s
ilemi.co TXT fa8ecc732c57225417adcd19b4ef4ba0 3600s

Authority records

Additional records
ns1.uplink.cz A 46.105.230.2 3600s
ns1.uplink.cz 28 [16 bytes] 3600s
ns2.uplink.cz A 37.157.196.141 3600s
ns3.uplink.cz A 77.93.202.189 3600s
ns3.uplink.cz 28 [16 bytes] 3600s
devnull.uplink.cz A 93.170.16.5 3600s

IP 93.170.16.175 Analysis

  • Country Code
    CZ
  • Country Code3
    CZE
  • Country Name
    Czech Republic
  • City
    EU
  • Continent Code
    49°75' North
  • Latitude
    15.5.
  • Longitude
  • No whois ip data for 93.170.16.175

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 109 Errors
  • 127 Warnings
Ratio Text/Html
  • 0.6526288791997948
Message Error
  • Error Line 17, Column 101: end tag for "link" omitted, but OMITTAG NO was specified
    …//fonts.googleapis.com/css?family=Poller+One' rel='stylesheet' type='text/css'>

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

  • Info Line 17, Column 5: start tag was here
        <link href='http://fonts.googleapis.com/css?family=Poller+One' rel='stylesh…
  • Warning Line 52, Column 90: cannot generate system identifier for general entity "mediaTypeID"
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

    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 52, Column 90: general entity "mediaTypeID" not defined and no default entity
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

    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 52, Column 101: reference not terminated by REFC delimiter
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

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

  • Error Line 52, Column 101: reference to entity "mediaTypeID" for which no system identifier could be generated
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

    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 52, Column 89: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 52, Column 106: cannot generate system identifier for general entity "AffUrlID"
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

    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 52, Column 106: general entity "AffUrlID" not defined and no default entity
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

    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 52, Column 114: reference not terminated by REFC delimiter
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

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

  • Error Line 52, Column 114: reference to entity "AffUrlID" for which no system identifier could be generated
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

    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 52, Column 105: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 62, Column 101: reference not terminated by REFC delimiter
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

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

  • Error Line 62, Column 101: reference to entity "mediaTypeID" for which no system identifier could be generated
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

    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 52, Column 89: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 62, Column 114: reference not terminated by REFC delimiter
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

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

  • Error Line 62, Column 114: reference to entity "AffUrlID" for which no system identifier could be generated
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

    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 52, Column 105: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 82, Column 101: reference not terminated by REFC delimiter
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

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

  • Error Line 82, Column 101: reference to entity "mediaTypeID" for which no system identifier could be generated
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

    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 52, Column 89: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 82, Column 114: reference not terminated by REFC delimiter
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

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

  • Error Line 82, Column 114: reference to entity "AffUrlID" for which no system identifier could be generated
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';

    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 52, Column 105: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Error Line 91, Column 60: there is no attribute "allowtransparency"
    …frame id="adsFrame" allowtransparency="true" frameborder="0" scrolling="no" sr…

    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 91, Column 135: cannot generate system identifier for general entity "zeme"
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></iframe>';

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

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

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

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

  • Error Line 91, Column 135: general entity "zeme" not defined and no default entity
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></iframe>';

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

  • Warning Line 91, Column 139: reference not terminated by REFC delimiter
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></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 91, Column 139: reference to external entity in attribute value
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></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 91, Column 139: reference to entity "zeme" for which no system identifier could be generated
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></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 91, Column 134: entity was defined here
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></iframe>';
  • Warning Line 91, Column 143: cannot generate system identifier for general entity "pop_typ"
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></iframe>';

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

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

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

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

  • Error Line 91, Column 143: general entity "pop_typ" not defined and no default entity
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></iframe>';

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

  • Warning Line 91, Column 150: reference not terminated by REFC delimiter
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></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 91, Column 150: reference to external entity in attribute value
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></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 91, Column 150: reference to entity "pop_typ" for which no system identifier could be generated
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></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 91, Column 142: entity was defined here
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></iframe>';
  • Error Line 91, Column 154: document type does not allow element "iframe" here
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></iframe>';

    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 117, Column 29: ID "adsFrame" already defined
    	BANNER_CODE = '<iframe id="adsFrame" allowtransparency="true" frameborder="0" …

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

  • Info Line 91, Column 32: ID "adsFrame" first defined here
    var BANNER_CODE = '<iframe id="adsFrame" allowtransparency="true" frameborder="…
  • Warning Line 117, Column 136: reference not terminated by REFC delimiter
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></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 117, Column 136: reference to external entity in attribute value
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></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 117, Column 136: reference to entity "zeme" for which no system identifier could be generated
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></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 91, Column 134: entity was defined here
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></iframe>';
  • Warning Line 117, Column 147: reference not terminated by REFC delimiter
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></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 117, Column 147: reference to external entity in attribute value
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></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 117, Column 147: reference to entity "pop_typ" for which no system identifier could be generated
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></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 91, Column 142: entity was defined here
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></iframe>';
  • Error Line 117, Column 151: document type does not allow element "iframe" here
    …lling="no" src="/getAds.php?id='+BANNER_CYCLE+'&zeme=US&pop_typ=up"></iframe>';

    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 230, Column 349: there is no attribute "allowTransparency"
    … overflow:hidden; width:150px; height:90px;" allowTransparency="true"></iframe>

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

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

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

  • Error Line 235, Column 21: there is no attribute "size"
        <g:plusone size="tall"></g:plusone>

    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 235, Column 27: element "g:plusone" undefined
        <g:plusone size="tall"></g:plusone>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 239, Column 79: there is no attribute "data-text"
    …lass="twitter-share-button" data-text="I am watching sports for free at " data…

    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 239, Column 126: there is no attribute "data-count"
    …ching sports for free at " data-count="vertical" data-via="Atdhe_tv">Tweet</a>…

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

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

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

  • Error Line 239, Column 146: there is no attribute "data-via"
    …e at " data-count="vertical" data-via="Atdhe_tv">Tweet</a><script type="text/j…

    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 259, Column 5: 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 259, Column 1: start tag was here
    <br><br>
  • Error Line 259, Column 9: 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 259, Column 5: start tag was here
    <br><br>
  • Warning Line 261, Column 91: reference not terminated by REFC delimiter
    …iliate.asp?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D12…

    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 261, Column 91: reference to external entity in attribute value
    …iliate.asp?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D12…

    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 261, Column 91: reference to entity "mediaTypeID" for which no system identifier could be generated
    …iliate.asp?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D12…

    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 52, Column 89: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 261, Column 96: cannot generate system identifier for general entity "Image"
    …e.asp?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D120x600…

    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 261, Column 96: general entity "Image" not defined and no default entity
    …e.asp?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D120x600…

    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 261, Column 101: reference not terminated by REFC delimiter
    …?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D120x600_01_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 261, Column 101: reference to external entity in attribute value
    …?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D120x600_01_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 261, Column 101: reference to entity "Image" for which no system identifier could be generated
    …?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D120x600_01_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 261, Column 95: entity was defined here
    …te.asp?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D120x60…
  • Warning Line 261, Column 158: reference not terminated by REFC delimiter
    …e=/tracking/banner/120x600/5D120x600_01_14_10.gif&AffUrlID=3425" target="_top">

    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 261, Column 158: reference to external entity in attribute value
    …e=/tracking/banner/120x600/5D120x600_01_14_10.gif&AffUrlID=3425" target="_top">

    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 261, Column 158: reference to entity "AffUrlID" for which no system identifier could be generated
    …e=/tracking/banner/120x600/5D120x600_01_14_10.gif&AffUrlID=3425" target="_top">

    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 52, Column 105: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 262, Column 89: reference not terminated by REFC delimiter
    …banner.asp?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D12…

    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 262, Column 89: reference to external entity in attribute value
    …banner.asp?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D12…

    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 262, Column 89: reference to entity "mediaTypeID" for which no system identifier could be generated
    …banner.asp?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D12…

    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 52, Column 89: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 262, Column 99: reference not terminated by REFC delimiter
    …?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D120x600_01_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 262, Column 99: reference to external entity in attribute value
    …?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D120x600_01_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 262, Column 99: reference to entity "Image" for which no system identifier could be generated
    …?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D120x600_01_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 261, Column 95: entity was defined here
    …te.asp?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D120x60…
  • Warning Line 262, Column 156: reference not terminated by REFC delimiter
    …20x600/5D120x600_01_14_10.gif&AffUrlID=3425" hspace="0" vspace="0" border="0" …

    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 262, Column 156: reference to external entity in attribute value
    …20x600/5D120x600_01_14_10.gif&AffUrlID=3425" hspace="0" vspace="0" border="0" …

    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 262, Column 156: reference to entity "AffUrlID" for which no system identifier could be generated
    …20x600/5D120x600_01_14_10.gif&AffUrlID=3425" hspace="0" vspace="0" border="0" …

    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 52, Column 105: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Error Line 262, Column 216: end tag for "img" omitted, but OMITTAG NO was specified
    …_14_10.gif&AffUrlID=3425" hspace="0" vspace="0" border="0" alt="Bet at 5dimes">

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

  • Info Line 262, Column 3: start tag was here
      <img src="http://affiliates.5dimes.com/tracking/banner.asp?AffID=AF0002949&me…
  • Warning Line 270, Column 91: reference not terminated by REFC delimiter
    …iliate.asp?AffID=af0002949&mediaTypeID=1030&Image=/tracking/banner/728x90/5D72…

    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 270, Column 91: reference to external entity in attribute value
    …iliate.asp?AffID=af0002949&mediaTypeID=1030&Image=/tracking/banner/728x90/5D72…

    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 270, Column 91: reference to entity "mediaTypeID" for which no system identifier could be generated
    …iliate.asp?AffID=af0002949&mediaTypeID=1030&Image=/tracking/banner/728x90/5D72…

    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 52, Column 89: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 270, Column 102: reference not terminated by REFC delimiter
    …AffID=af0002949&mediaTypeID=1030&Image=/tracking/banner/728x90/5D728x90_08_23_…

    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 270, Column 102: reference to external entity in attribute value
    …AffID=af0002949&mediaTypeID=1030&Image=/tracking/banner/728x90/5D728x90_08_23_…

    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 270, Column 102: reference to entity "Image" for which no system identifier could be generated
    …AffID=af0002949&mediaTypeID=1030&Image=/tracking/banner/728x90/5D728x90_08_23_…

    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 261, Column 95: entity was defined here
    …te.asp?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D120x60…
  • Warning Line 270, Column 157: reference not terminated by REFC delimiter
    …age=/tracking/banner/728x90/5D728x90_08_23_12.gif&AffUrlID=4474" target="_top">

    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 270, Column 157: reference to external entity in attribute value
    …age=/tracking/banner/728x90/5D728x90_08_23_12.gif&AffUrlID=4474" target="_top">

    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 270, Column 157: reference to entity "AffUrlID" for which no system identifier could be generated
    …age=/tracking/banner/728x90/5D728x90_08_23_12.gif&AffUrlID=4474" target="_top">

    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 52, Column 105: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 271, Column 89: reference not terminated by REFC delimiter
    …banner.asp?AffID=af0002949&mediaTypeID=1030&Image=/tracking/banner/728x90/5D72…

    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 271, Column 89: reference to external entity in attribute value
    …banner.asp?AffID=af0002949&mediaTypeID=1030&Image=/tracking/banner/728x90/5D72…

    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 271, Column 89: reference to entity "mediaTypeID" for which no system identifier could be generated
    …banner.asp?AffID=af0002949&mediaTypeID=1030&Image=/tracking/banner/728x90/5D72…

    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 52, Column 89: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 271, Column 100: reference not terminated by REFC delimiter
    …AffID=af0002949&mediaTypeID=1030&Image=/tracking/banner/728x90/5D728x90_08_23_…

    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 271, Column 100: reference to external entity in attribute value
    …AffID=af0002949&mediaTypeID=1030&Image=/tracking/banner/728x90/5D728x90_08_23_…

    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 271, Column 100: reference to entity "Image" for which no system identifier could be generated
    …AffID=af0002949&mediaTypeID=1030&Image=/tracking/banner/728x90/5D728x90_08_23_…

    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 261, Column 95: entity was defined here
    …te.asp?AffID=AF0002949&mediaTypeID=314&Image=/tracking/banner/120x600/5D120x60…
  • Warning Line 271, Column 155: reference not terminated by REFC delimiter
    …/728x90/5D728x90_08_23_12.gif&AffUrlID=4474" hspace="0" vspace="0" border="0" …

    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 271, Column 155: reference to external entity in attribute value
    …/728x90/5D728x90_08_23_12.gif&AffUrlID=4474" hspace="0" vspace="0" border="0" …

    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 271, Column 155: reference to entity "AffUrlID" for which no system identifier could be generated
    …/728x90/5D728x90_08_23_12.gif&AffUrlID=4474" hspace="0" vspace="0" border="0" …

    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 52, Column 105: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Error Line 271, Column 215: end tag for "img" omitted, but OMITTAG NO was specified
    …_23_12.gif&AffUrlID=4474" hspace="0" vspace="0" border="0" alt="Bet at 5dimes">

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

  • Info Line 271, Column 3: start tag was here
      <img src="http://affiliates.5dimes.com/tracking/banner.asp?AffID=af0002949&me…
  • Error Line 278, Column 1: character data is not allowed here
    <!-- CODE STARTS HERE -->

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 280, Column 87: end tag for "img" omitted, but OMITTAG NO was specified
    …span='2' ><img src='/img/atdhe_USA.jpg' alt='usa' title='usa' height="14"></td>

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

  • Info Line 280, Column 19: start tag was here
    <td  colspan='2' ><img src='/img/atdhe_USA.jpg' alt='usa' title='usa' height="1…
  • Warning Line 281, Column 218: character "<" is the first character of a delimiter but occurred as data
    …/atdhe.org/bodog/' title='Bodog review'>BODOG/BOVADA</a> <- do not miss it</td>

    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 284, Column 86: end tag for "img" omitted, but OMITTAG NO was specified
    …span='2' ><img src='/img/atdhe_USA.jpg' alt='usa' title='usa' height="14"></td>

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

  • Info Line 284, Column 18: start tag was here
    <td colspan='2' ><img src='/img/atdhe_USA.jpg' alt='usa' title='usa' height="14…
  • Warning Line 285, Column 106: reference not terminated by REFC delimiter
    …iliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425' rel='nofollow'>Best …

    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 285, Column 106: reference to external entity in attribute value
    …iliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425' rel='nofollow'>Best …

    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 285, Column 106: reference to entity "mediaTypeID" for which no system identifier could be generated
    …iliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425' rel='nofollow'>Best …

    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 52, Column 89: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 285, Column 119: reference not terminated by REFC delimiter
    …fID=AF0002949&mediaTypeID=220&AffUrlID=3425' rel='nofollow'>Best sportsbook fo…

    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 285, Column 119: reference to external entity in attribute value
    …fID=AF0002949&mediaTypeID=220&AffUrlID=3425' rel='nofollow'>Best sportsbook fo…

    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 285, Column 119: reference to entity "AffUrlID" for which no system identifier could be generated
    …fID=AF0002949&mediaTypeID=220&AffUrlID=3425' rel='nofollow'>Best sportsbook fo…

    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 52, Column 105: entity was defined here
    …imes.com/tracking/Affiliate.asp?AffID=AF0002949&mediaTypeID=220&AffUrlID=3425';
  • Warning Line 285, Column 255: character "<" is the first character of a delimiter but occurred as data
    …f='http://atdhe.org/5dimes/' title='5dimes review'>5Dimes</a> <- arguments</td>

    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 288, Column 86: end tag for "img" omitted, but OMITTAG NO was specified
    …span='2' ><img src='/img/atdhe_USA.jpg' alt='usa' title='usa' height="14"></td>

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

  • Info Line 288, Column 18: start tag was here
    <td colspan='2' ><img src='/img/atdhe_USA.jpg' alt='usa' title='usa' height="14…
  • Error Line 295, Column 46: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … style= 'text-align:center' colspan = 3> Streams with less annoying ads</td></…
  • Error Line 928, Column 7: document type does not allow element "tfoot" here
    <tfoot>

    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 930, Column 4: document type does not allow element "tr" here
    <tr><td colspan="3">More links on <a href="http://myp2p.la">MyP2P.la</a></td></…

    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 934, Column 57: there is no attribute "datetime"
    …158 links. Last update <time datetime='2013-03-03T11:16:01'>11:16:01</time> UT…

    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 934, Column 78: element "time" undefined
    …e <time datetime='2013-03-03T11:16:01'>11:16:01</time> UTC = 298 seconds ago.<…

    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 963, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br> ILEMI thanks to: <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 963, Column 1: start tag was here
    <br> ILEMI thanks to: <br>
  • Error Line 963, Column 27: end tag for "br" omitted, but OMITTAG NO was specified
    <br> ILEMI thanks to: <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 963, Column 23: start tag was here
    <br> ILEMI thanks to: <br>
  • Error Line 965, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 965, Column 1: start tag was here
    <br>
  • Error Line 981, Column 24: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    //--></script><noscript><img src="http://toplist.cz/dot.asp?id=1359484" border=…

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

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

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

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

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

Visitor Analysis

Daily Visitor
  • 175 visits