Tamil Movies Online | TAMIL MOVIES ONLINE,NEW TAMIL MOVIES ONLINE,DVD TAMIL MOVIES,TAMIL OLD TAMIL MOVIES ONLINE,TAMIL PADAM ONLINE ,TAMIL MOVIE ONLINE ...

runtamil.com
  • Domain Name
    runtamil.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #21252
  • Page Size
    67.1 KB
  • Ip Address
    141.101.116.51
  • Heading
    H1: 1, H2: 0, H3: 30, H4: 0, H5: 3, H6: 0
  • Images
    2 GIF, 33 JPG, 0 PNG

Website Meta Analysis

  • Title
    Tamil Movies Online | TAMIL MOVIES ONLINE,NEW TAMIL MOVIES ONLINE,DVD TAMIL MOVIES,TAMIL OLD TAMIL MOVIES ONLINE,TAMIL PADAM ONLINE ,TAMIL MOVIE ONLINE
  • Meta Keyword
  • Meta Description
    Tamil Movies Online | TAMIL MOVIES ONLINE,NEW TAMIL MOVIES ONLINE,DVD TAMIL MOVIES,TAMIL OLD TAMIL MOVIES ONLINE,TAMIL PADAM ONLINE ,TAMIL MOVIE ONLINE

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    141.101.116.51
  • Domain Age
    3 Years, 8 Months, 10 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: cloudflare-nginx
  • date: Sat, 28 Sep 2013 05:25:34 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.3.8
  • x-pingback: http://runtamil.com/xmlrpc.php
  • cf-ray: b4e0385064b02b6
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for runtamil.com

DNS Analysis


DNS servers
ns1.runtamil.com [85.17.169.195]
ns2.runtamil.com [85.17.169.232]


DNS Records

Answer records
runtamil.com TXT v=spf1 +a +mx +ip4:85.17.169.195 ?all 14400s
runtamil.com MX
preference: 0
exchange: runtamil.com
14400s
runtamil.com SOA
server: ns1.runtamil.com
email: eelavaanam@gmail.com
serial: 2012050200
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
runtamil.com NS  ns2.runtamil.com 86400s
runtamil.com NS  ns1.runtamil.com 86400s
runtamil.com A 85.17.169.195 14400s

Authority records

Additional records
runtamil.com A 85.17.169.195 14400s
ns1.runtamil.com A 85.17.169.195 14400s
ns2.runtamil.com A 85.17.169.232 14400s

IP 141.101.116.51 Analysis

  • Country Code
    EU
  • Country Code3
    EU
  • Country Name
    Europe
  • City
    EU
  • Continent Code
    47° North
  • Latitude
    8.
  • Longitude
  • No whois ip data for 141.101.116.51

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 57 Errors
  • 27 Warnings
Ratio Text/Html
  • 0.8486149725614638
Message Error
  • Error Line 31, Column 17: there is no attribute "property"
    	<meta property="og:type" content="article" />

    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 143, Column 4: document type does not allow element "td" here
    <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 151, Column 80: required attribute "alt" not specified
    …<img src="http://freezetamil.com/FreezeTamil1.jpg" height="90" width="700"></a>

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

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

  • Error Line 151, Column 84: end tag for "img" omitted, but OMITTAG NO was specified
    …<img src="http://freezetamil.com/FreezeTamil1.jpg" height="90" width="700"></a>

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

  • Info Line 151, Column 6: start tag was here
    					<img src="http://freezetamil.com/FreezeTamil1.jpg" height="90" width="700"…
  • Error Line 157, Column 78: required attribute "alt" not specified
    …		<img src="http://runtamil.com/viji/tamilmp3.jpg" height="90" width="250"></a>

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

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

  • Error Line 157, Column 82: end tag for "img" omitted, but OMITTAG NO was specified
    …		<img src="http://runtamil.com/viji/tamilmp3.jpg" height="90" width="250"></a>

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

  • Info Line 157, Column 6: start tag was here
    					<img src="http://runtamil.com/viji/tamilmp3.jpg" height="90" width="250"><…
  • Error Line 159, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </table>

    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 148, Column 1: start tag was here
    <tr>
  • Error Line 160, Column 5: end tag for element "tr" which is not open
    </tr>        <center>

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

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

  • Error Line 162, Column 75: required attribute "alt" not specified
    …src="http://runtamil.com/viji/radio.jpg" height="70" width="650"></a></center> 

    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 162, Column 79: end tag for "img" omitted, but OMITTAG NO was specified
    …src="http://runtamil.com/viji/radio.jpg" height="70" width="650"></a></center> 

    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 162, Column 6: start tag was here
    					<img src="http://runtamil.com/viji/radio.jpg" height="70" width="650"></a>…
  • Error Line 258, Column 13: there is no attribute "SRC"
    <SCRIPT SRC="http://ib.adnxs.com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CL…

    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 258, Column 49: cannot generate system identifier for general entity "cb"
    …C="http://ib.adnxs.com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_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 258, Column 49: general entity "cb" not defined and no default entity
    …C="http://ib.adnxs.com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_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 258, Column 51: reference not terminated by REFC delimiter
    …"http://ib.adnxs.com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" T…

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

  • Warning Line 258, Column 51: reference to external entity in attribute value
    …"http://ib.adnxs.com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" T…

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

  • Error Line 258, Column 51: reference to entity "cb" for which no system identifier could be generated
    …"http://ib.adnxs.com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" T…

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

  • Info Line 258, Column 48: entity was defined here
    …RC="http://ib.adnxs.com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}…
  • Warning Line 258, Column 67: cannot generate system identifier for general entity "pubclick"
    ….com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javasc…

    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 258, Column 67: general entity "pubclick" not defined and no default entity
    ….com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javasc…

    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 258, Column 75: reference not terminated by REFC delimiter
    …?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></…

    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 258, Column 75: reference to external entity in attribute value
    …?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></…

    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 258, Column 75: reference to entity "pubclick" for which no system identifier could be generated
    …?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></…

    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 258, Column 66: entity was defined here
    …s.com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javas…
  • Error Line 258, Column 95: there is no attribute "TYPE"
    …41972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></SCRIPT>

    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 258, Column 112: element "SCRIPT" undefined
    …41972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></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).
  • Error Line 285, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia----runtamil.com (141761)--banner--728x90---->
  • Info Line 285, Column 1: comment declaration started here
    <!----Tlvmedia----runtamil.com (141761)--banner--728x90---->
  • Error Line 286, Column 21: there is no attribute "FRAMEBORDER"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGH…

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

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

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

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

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

  • Error Line 286, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="…
  • Error Line 286, Column 62: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://tag.t…

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

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

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

  • Error Line 286, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://tag.t…
  • Error Line 286, Column 71: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://tag.tlvmedia.c…

    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 286, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://tag.tlvmedia.c…
  • Error Line 286, Column 82: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://tag.tlvmedia.com/?id=1024…

    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 286, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://tag.tlvmedia.com/?id=1024…
  • Error Line 286, Column 89: there is no attribute "SRC"
    … SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://tag.tlvmedia.com/?id=102490_1417…

    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 286, Column 132: cannot generate system identifier for general entity "ad_type"
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></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 286, Column 132: general entity "ad_type" not defined and no default entity
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></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 286, Column 139: reference not terminated by REFC delimiter
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></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 286, Column 139: reference to external entity in attribute value
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></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 286, Column 139: reference to entity "ad_type" for which no system identifier could be generated
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></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 286, Column 131: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME…
  • Warning Line 286, Column 147: cannot generate system identifier for general entity "ad_size"
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></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 286, Column 147: general entity "ad_size" not defined and no default entity
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></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 286, Column 154: reference not terminated by REFC delimiter
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></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 286, Column 154: reference to external entity in attribute value
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></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 286, Column 154: reference to entity "ad_size" for which no system identifier could be generated
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></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 286, Column 146: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME>
  • Error Line 286, Column 162: element "IFRAME" undefined
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 287, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia-------------------------------------------------->
  • Info Line 287, Column 1: comment declaration started here
    <!----Tlvmedia-------------------------------------------------->
  • Error Line 298, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia----runtamil.com (141761)--banner--300x250---->
  • Info Line 298, Column 1: comment declaration started here
    <!----Tlvmedia----runtamil.com (141761)--banner--300x250---->
  • Warning Line 299, Column 93: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=300x250"></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 299, Column 93: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=300x250"></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 299, Column 93: reference to entity "ad_type" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=300x250"></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 286, Column 131: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME…
  • Warning Line 299, Column 108: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=300x250"></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 299, Column 108: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=300x250"></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 299, Column 108: reference to entity "ad_size" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=300x250"></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 286, Column 146: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME>
  • Error Line 300, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia-------------------------------------------------->
  • Info Line 300, Column 1: comment declaration started here
    <!----Tlvmedia-------------------------------------------------->
  • Error Line 308, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia----runtamil.com (141761)--banner--300x250---->
  • Info Line 308, Column 1: comment declaration started here
    <!----Tlvmedia----runtamil.com (141761)--banner--300x250---->
  • Warning Line 309, Column 93: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=300x250"></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 309, Column 93: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=300x250"></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 309, Column 93: reference to entity "ad_type" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=300x250"></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 286, Column 131: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME…
  • Warning Line 309, Column 108: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=300x250"></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 309, Column 108: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=300x250"></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 309, Column 108: reference to entity "ad_size" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=300x250"></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 286, Column 146: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME>
  • Error Line 310, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia-------------------------------------------------->
  • Info Line 310, Column 1: comment declaration started here
    <!----Tlvmedia-------------------------------------------------->
  • Error Line 323, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia----runtamil.com (141761)--banner--468x60---->
  • Info Line 323, Column 1: comment declaration started here
    <!----Tlvmedia----runtamil.com (141761)--banner--468x60---->
  • Warning Line 324, Column 93: reference not terminated by REFC delimiter
    ….tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=468x60"></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 324, Column 93: reference to external entity in attribute value
    ….tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=468x60"></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 324, Column 93: reference to entity "ad_type" for which no system identifier could be generated
    ….tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=468x60"></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 286, Column 131: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME…
  • Warning Line 324, Column 108: reference not terminated by REFC delimiter
    ….tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=468x60"></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 324, Column 108: reference to external entity in attribute value
    ….tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=468x60"></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 324, Column 108: reference to entity "ad_size" for which no system identifier could be generated
    ….tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=468x60"></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 286, Column 146: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME>
  • Error Line 325, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia-------------------------------------------------->
  • Info Line 325, Column 1: comment declaration started here
    <!----Tlvmedia-------------------------------------------------->
  • Error Line 328, 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 328, Column 1: start tag was here
    <br>
  • Error Line 330, Column 6: end tag for "center" omitted, but OMITTAG NO was specified
    </div><!-- #container -->

    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 322, Column 1: start tag was here
    <center>
  • Error Line 330, Column 6: end tag for "td" omitted, but OMITTAG NO was specified
    </div><!-- #container -->

    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 143, Column 1: start tag was here
    <td>
  • Error Line 334, 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 334, Column 1: start tag was here
    <br>
  • Error Line 335, 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 335, Column 1: start tag was here
    <br>
  • Error Line 336, 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 336, Column 1: start tag was here
    <br>
  • Error Line 337, 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 337, Column 1: start tag was here
    <br>
  • Error Line 338, 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 338, Column 1: start tag was here
    <br>
  • Error Line 339, 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 339, Column 1: start tag was here
    <br>
  • Error Line 340, 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 340, Column 1: start tag was here
    <br>
  • Error Line 373, Column 99: required attribute "alt" not specified
    …w.tamilstar.com/cinema-images/advt/tamilstar.jpg" height="400" width="160"></a>

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

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

  • Error Line 373, Column 103: end tag for "img" omitted, but OMITTAG NO was specified
    …w.tamilstar.com/cinema-images/advt/tamilstar.jpg" height="400" width="160"></a>

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

  • Info Line 373, Column 6: start tag was here
    					<img src="http://www.tamilstar.com/cinema-images/advt/tamilstar.jpg" heigh…
  • Warning Line 376, Column 51: reference not terminated by REFC delimiter
    …"http://ib.adnxs.com/ttj?id=1141970&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" T…

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

  • Warning Line 376, Column 51: reference to external entity in attribute value
    …"http://ib.adnxs.com/ttj?id=1141970&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" T…

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

  • Error Line 376, Column 51: reference to entity "cb" for which no system identifier could be generated
    …"http://ib.adnxs.com/ttj?id=1141970&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" T…

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

  • Info Line 258, Column 48: entity was defined here
    …RC="http://ib.adnxs.com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}…
  • Warning Line 376, Column 75: reference not terminated by REFC delimiter
    …?id=1141970&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></…

    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 376, Column 75: reference to external entity in attribute value
    …?id=1141970&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></…

    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 376, Column 75: reference to entity "pubclick" for which no system identifier could be generated
    …?id=1141970&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></…

    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 258, Column 66: entity was defined here
    …s.com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javas…
  • Error Line 376, Column 112: element "SCRIPT" undefined
    …41970&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></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).
  • Error Line 378, Column 91: invalid comment declaration: found name start character outside comment but inside comment declaration
    …fix">			<div class="textwidget"><!----Tlvmedia----runtamil.com (141761)--banne…
  • Info Line 378, Column 85: comment declaration started here
    … clearfix">			<div class="textwidget"><!----Tlvmedia----runtamil.com (141761)-…
  • Warning Line 379, Column 93: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=160x600"></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 379, Column 93: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=160x600"></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 379, Column 93: reference to entity "ad_type" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=160x600"></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 286, Column 131: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME…
  • Warning Line 379, Column 108: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=160x600"></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 379, Column 108: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=160x600"></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 379, Column 108: reference to entity "ad_size" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=160x600"></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 286, Column 146: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME>
  • Error Line 380, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia-------------------------------------------------->
  • Info Line 380, Column 1: comment declaration started here
    <!----Tlvmedia-------------------------------------------------->
  • Error Line 383, Column 72: required attribute "alt" not specified
    					<img src="http://oktamil.com/oktamil.jpg" height="400" width="160"></a>

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

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

  • Error Line 383, Column 76: end tag for "img" omitted, but OMITTAG NO was specified
    					<img src="http://oktamil.com/oktamil.jpg" height="400" width="160"></a>

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

  • Info Line 383, Column 6: start tag was here
    					<img src="http://oktamil.com/oktamil.jpg" height="400" width="160"></a>
  • Error Line 390, 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 390, Column 1: start tag was here
    <br>
  • Error Line 391, 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 391, Column 1: start tag was here
    <br>
  • Error Line 392, 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 392, Column 1: start tag was here
    <br>
  • Error Line 393, 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 393, Column 1: start tag was here
    <br>
  • Error Line 394, 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 394, Column 1: start tag was here
    <br>
  • Error Line 395, 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 395, Column 1: start tag was here
    <br>
  • Error Line 396, 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 396, Column 1: start tag was here
    <br>
  • Error Line 405, Column 79: required attribute "alt" not specified
    …	<img src="http://runtamil.com/viji/runtamil.jpg" height="400" width="160"></a>

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

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

  • Error Line 405, Column 83: end tag for "img" omitted, but OMITTAG NO was specified
    …	<img src="http://runtamil.com/viji/runtamil.jpg" height="400" width="160"></a>

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

  • Info Line 405, Column 6: start tag was here
    					<img src="http://runtamil.com/viji/runtamil.jpg" height="400" width="160">…
  • Error Line 407, Column 230: there is no attribute "allowtransparency"
    …px; height: 230px;" allowtransparency="true" scrolling="no" frameborder="0" 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 407, Column 363: cannot generate system identifier for general entity "width"
    …p%3A%2F%2Fwww.facebook.com%2Fruntamil&width=160&colorscheme=light&show_faces=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 407, Column 363: general entity "width" not defined and no default entity
    …p%3A%2F%2Fwww.facebook.com%2Fruntamil&width=160&colorscheme=light&show_faces=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 407, Column 368: reference not terminated by REFC delimiter
    …2F%2Fwww.facebook.com%2Fruntamil&width=160&colorscheme=light&show_faces=true&s…

    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 407, Column 368: reference to external entity in attribute value
    …2F%2Fwww.facebook.com%2Fruntamil&width=160&colorscheme=light&show_faces=true&s…

    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 407, Column 368: reference to entity "width" for which no system identifier could be generated
    …2F%2Fwww.facebook.com%2Fruntamil&width=160&colorscheme=light&show_faces=true&s…

    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 407, Column 362: entity was defined here
    …tp%3A%2F%2Fwww.facebook.com%2Fruntamil&width=160&colorscheme=light&show_faces=…
  • Warning Line 407, Column 373: cannot generate system identifier for general entity "colorscheme"
    …www.facebook.com%2Fruntamil&width=160&colorscheme=light&show_faces=true&stream…

    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 407, Column 373: general entity "colorscheme" not defined and no default entity
    …www.facebook.com%2Fruntamil&width=160&colorscheme=light&show_faces=true&stream…

    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 407, Column 384: reference not terminated by REFC delimiter
    …k.com%2Fruntamil&width=160&colorscheme=light&show_faces=true&stream=false&head…

    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 407, Column 384: reference to external entity in attribute value
    …k.com%2Fruntamil&width=160&colorscheme=light&show_faces=true&stream=false&head…

    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 407, Column 384: reference to entity "colorscheme" for which no system identifier could be generated
    …k.com%2Fruntamil&width=160&colorscheme=light&show_faces=true&stream=false&head…

    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 407, Column 372: entity was defined here
    …Fwww.facebook.com%2Fruntamil&width=160&colorscheme=light&show_faces=true&strea…
  • Warning Line 407, Column 391: cannot generate system identifier for general entity "show_faces"
    …Fruntamil&width=160&colorscheme=light&show_faces=true&stream=false&header=true…

    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 407, Column 391: general entity "show_faces" not defined and no default entity
    …Fruntamil&width=160&colorscheme=light&show_faces=true&stream=false&header=true…

    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 407, Column 401: reference not terminated by REFC delimiter
    …width=160&colorscheme=light&show_faces=true&stream=false&header=true&height=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 407, Column 401: reference to external entity in attribute value
    …width=160&colorscheme=light&show_faces=true&stream=false&header=true&height=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 407, Column 401: reference to entity "show_faces" for which no system identifier could be generated
    …width=160&colorscheme=light&show_faces=true&stream=false&header=true&height=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 407, Column 390: entity was defined here
    …2Fruntamil&width=160&colorscheme=light&show_faces=true&stream=false&header=tru…
  • Warning Line 407, Column 407: cannot generate system identifier for general entity "stream"
    …160&colorscheme=light&show_faces=true&stream=false&header=true&height=230" nam…

    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 407, Column 407: general entity "stream" not defined and no default entity
    …160&colorscheme=light&show_faces=true&stream=false&header=true&height=230" nam…

    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 407, Column 413: reference not terminated by REFC delimiter
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2"…

    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 407, Column 413: reference to external entity in attribute value
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2"…

    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 407, Column 413: reference to entity "stream" for which no system identifier could be generated
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2"…

    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 407, Column 406: entity was defined here
    …=160&colorscheme=light&show_faces=true&stream=false&header=true&height=230" na…
  • Warning Line 407, Column 420: cannot generate system identifier for general entity "header"
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2">

    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 407, Column 420: general entity "header" not defined and no default entity
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2">

    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 407, Column 426: reference not terminated by REFC delimiter
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2">

    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 407, Column 426: reference to external entity in attribute value
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2">

    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 407, Column 426: reference to entity "header" for which no system identifier could be generated
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2">

    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 407, Column 419: entity was defined here
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2">
  • Warning Line 407, Column 432: cannot generate system identifier for general entity "height"
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2">

    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 407, Column 432: general entity "height" not defined and no default entity
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2">

    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 407, Column 438: reference not terminated by REFC delimiter
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2">

    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 407, Column 438: reference to external entity in attribute value
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2">

    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 407, Column 438: reference to entity "height" for which no system identifier could be generated
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2">

    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 407, Column 431: entity was defined here
    …lorscheme=light&show_faces=true&stream=false&header=true&height=230" name="I2">
  • Warning Line 410, Column 51: reference not terminated by REFC delimiter
    …"http://ib.adnxs.com/ttj?id=1141967&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" T…

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

  • Warning Line 410, Column 51: reference to external entity in attribute value
    …"http://ib.adnxs.com/ttj?id=1141967&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" T…

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

  • Error Line 410, Column 51: reference to entity "cb" for which no system identifier could be generated
    …"http://ib.adnxs.com/ttj?id=1141967&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" T…

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

  • Info Line 258, Column 48: entity was defined here
    …RC="http://ib.adnxs.com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}…
  • Warning Line 410, Column 75: reference not terminated by REFC delimiter
    …?id=1141967&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></…

    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 410, Column 75: reference to external entity in attribute value
    …?id=1141967&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></…

    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 410, Column 75: reference to entity "pubclick" for which no system identifier could be generated
    …?id=1141967&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></…

    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 258, Column 66: entity was defined here
    …s.com/ttj?id=1141972&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javas…
  • Error Line 410, Column 112: element "SCRIPT" undefined
    …41967&cb=${CACHEBUSTER}&pubclick=${CLICK_URL}" TYPE="text/javascript"></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).
  • Error Line 412, Column 91: invalid comment declaration: found name start character outside comment but inside comment declaration
    …fix">			<div class="textwidget"><!----Tlvmedia----runtamil.com (141761)--banne…
  • Info Line 412, Column 85: comment declaration started here
    … clearfix">			<div class="textwidget"><!----Tlvmedia----runtamil.com (141761)-…
  • Warning Line 413, Column 93: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=160x600"></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 413, Column 93: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=160x600"></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 413, Column 93: reference to entity "ad_type" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=160x600"></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 286, Column 131: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME…
  • Warning Line 413, Column 108: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=160x600"></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 413, Column 108: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=160x600"></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 413, Column 108: reference to entity "ad_size" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=160x600"></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 286, Column 146: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME>
  • Error Line 414, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia-------------------------------------------------->
  • Info Line 414, Column 1: comment declaration started here
    <!----Tlvmedia-------------------------------------------------->
  • Error Line 416, Column 91: invalid comment declaration: found name start character outside comment but inside comment declaration
    …fix">			<div class="textwidget"><!----Tlvmedia----runtamil.com (141761)--banne…
  • Info Line 416, Column 85: comment declaration started here
    … clearfix">			<div class="textwidget"><!----Tlvmedia----runtamil.com (141761)-…
  • Warning Line 417, Column 93: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=120x600"></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 417, Column 93: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=120x600"></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 417, Column 93: reference to entity "ad_type" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=120x600"></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 286, Column 131: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME…
  • Warning Line 417, Column 108: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=120x600"></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 417, Column 108: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=120x600"></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 417, Column 108: reference to entity "ad_size" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=102490_141761&ad_type=banner&ad_size=120x600"></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 286, Column 146: entity was defined here
    …p://tag.tlvmedia.com/?id=102490_141761&ad_type=banner&ad_size=728x90"></IFRAME>
  • Error Line 418, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia-------------------------------------------------->
  • Info Line 418, Column 1: comment declaration started here
    <!----Tlvmedia-------------------------------------------------->
  • Warning Line 424, Column 12: S separator in comment declaration
    	</div><!-- #main -->

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 424, Column 13: invalid comment declaration: found delimiter "#" outside comment but inside comment declaration
    	</div><!-- #main -->
  • Info Line 423, Column 1: comment declaration started here
    <!-- 82 queries. 0.650 
  • Error Line 472, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 135, Column 1: start tag was here
    <div id="wrapper">

Visitor Analysis

Daily Visitor
  • 9.683 visits