iran-livetv.com

Iran Live TV is online streaming Iranian TV channels where you can watch online live TV channels free also you can listen online live radio channels in UK. Streaming live channels free, live ...

Display Widget for this domain on your website. Click Here
This data was last updated from 18-07-2013 08:27:27  (update).

Overview Info

  • Domain Name
    iran-livetv.com
  • Favicon
  • Alexa Rank
    #39946
  • Google Page Rank
    PR 0
  • Ip Address
    46.32.254.63
  • Page Size
    138.7 KB
  • Images
    2 GIF, 41 JPG, 119 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 6 0 0 0

Website Meta Analysis



  • Title
    Iran TV تلوزیون زنده ایران | Watch Iranian Live Tv online Persian Internet Radio In Uk
  • Meta Keyword
    iran tv, glwiz, glwiz.com, iran.tv, irantvradio.com, pars tv, voapersian, bbcpersian, iran tv network, presstv, iranianlivetv.com, iraniantlivetv, iranian tv live, nalbeki, iranproud, iran proud, iranianuk, iranian uk, irib tv, irib, iranian television, iran news, iran entertainment, online TV, internet TV, Iranian news, farsi tv, iranian tv, glwiz, farsi news, tv series, iran radio station, persian tv, persian radio, Watch iran TV, iranian TV online, iran live TV online, persian live TV streaming, iranian internet radio, free persian radio live, iran TV channels online, online iran radio, persian radio live, iran free radio, live iran radio streaming, iran TV streaming online, Download, Iran, Persian, Iranian Album, Iranian Music Video, Iranian MP3, Iranian Movie, Persian Album, Persian Music Video, Persian MP3, Persian Movie, Iranian Community, Forum, Persian Community, Persian Forum, Iranian Forum, Download, Movie, Film, Serial
  • Meta Description
    Iran Live TV is online streaming Iranian TV channels where you can watch online live TV channels free also you can listen online live radio channels in UK. Streaming live channels free, live TV and live radio Station

Technical Analysis



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

Hyper Text Transfer Protocol (HTTP) header show data header response from iran-livetv.com.

HTML Analysis

  • date: Thu, 18 Jul 2013 20:27:19 GMT
  • server: Apache
  • x-powered-by: PleskLin
  • ms-author-via: DAV
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
******************************************************************
Registrar: Internet-webhosting
Email: email
Tel: 0208 5370258
Url: http://www.Internet-webhosting.co.uk
******************************************************************

Domain Name: IRAN-LIVETV.COM
Created Date: 10-Aug-2012
Expiry Date: 10-Aug-2013
Nameserver: ns.mainnameserver.com
Nameserver: ns2.mainnameserver.com
Registrant Name: Identity Protection Service
Registrant Company: Identity Protect Limited
Registrant Address: PO Box 795
Registrant Address:
Registrant Address:
Registrant Address: Godalming
Registrant Address: Surrey
Registrant Address: GU7 9GA
Registrant Address: United Kingdom
Technical Name: Identity Protection Service
Technical Company: Identity Protect Limited
Technical Address: PO Box 795
Technical Address:
Technical Address:
Technical Address: Godalming
Technical Address: Surrey
Technical Address: GU7 9GA
Technical Address: United Kingdom
Technical Email: email
Technical Tel: +44.1483307527
Technical Fax: +44.1483304031
Administrative Name: Identity Protection Service
Administrative Company: Identity Protect Limited
Administrative Address: PO Box 795
Administrative Address:
Administrative Address:
Administrative Address: Godalming
Administrative Address: Surrey
Administrative Address: GU7 9GA
Administrative Address: United Kingdom
Administrative Email: email
Administrative Tel: +44.1483307527
Administrative Fax: +44.1483304031

The Data in this WHOIS database is provided
for information purposes only, and is designed to assist persons in
obtaining information related to domain name registration records.
It's accuracy is not guarenteed. By submitting a
WHOIS query, you agree that you will use this Data only for lawful
purposes and that, under no circumstances will you use this Data to:
(1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail(spam);
or (2) enable high volume, automated, electronic processes that
apply to this WHOIS or any of its related systems. The provider of
this WHOIS reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by this policy.

LACK OF A DOMAIN RECORD IN THE WHOIS DATABASE DOES
NOT INDICATE DOMAIN AVAILABILITY.

IP 46.32.254.63 Analysis

  • Country Code
    GB
  • Country Code3
    GBR
  • Country Name
    United Kingdom
  • City
    EU
  • Continent Code
    54° North
  • Latitude
    2.
  • Longitude
  • No whois ip data for 46.32.254.63

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 187 Errors
  • 42 Warnings
Ratio Text/Html
  • 0.7594452852768294
Message Error
  • Error Line 40, Column 24: invalid comment declaration: found name character outside comment but inside comment declaration
     <!--google webmaster--->
  • Info Line 40, Column 2: comment declaration started here
     <!--google webmaster--->
  • Error Line 40, Column 25: character data is not allowed here
     <!--google webmaster--->

    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 72, Column 10: document type does not allow element "noscript" here; assuming missing "object" start-tag
    <noscript>
  • Warning Line 85, Column 3: multiple comments in comment declaration
    <!--disques script-->
  • Error Line 85, Column 5: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!--disques script-->
  • Info Line 78, Column 1: comment declaration started here
    <!------>
  • Error Line 100, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

    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 72, Column 1: start tag was here
    <noscript>
  • Error Line 103, Column 13: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--header--->
  • Info Line 103, Column 1: comment declaration started here
    <!--header--->
  • Error Line 105, Column 6: document type does not allow element "head" here
    <head>

    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 114, Column 7: end tag for "head" which is not finished
    </head>

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

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

  • Error Line 117, Column 156: end tag for "img" omitted, but OMITTAG NO was specified
    …بگذارید" style="border-width:0px" src="http://iran-livetv.com/images/like.png">

    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 117, Column 1: start tag was here
    <img alt="Don't Forget Like Button" title="یادتان نره این صفحه را به اشتراک بگذ…
  • Error Line 119, Column 75: there is no attribute "data-via"
    …class="twitter-share-button" data-via="iranlivetvcom" data-lang="fa" data-coun…

    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 119, Column 101: there is no attribute "data-lang"
    …button" data-via="iranlivetvcom" data-lang="fa" data-count="vertical">توییت</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 119, Column 117: there is no attribute "data-count"
    …button" data-via="iranlivetvcom" data-lang="fa" data-count="vertical">توییت</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 120, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

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

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

  • Error Line 124, Column 91: there is no attribute "data-show-count"
    …witter-follow-button" data-show-count="false" data-lang="fa" data-show-screen-…

    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 124, Column 136: there is no attribute "data-show-screen-name"
    … data-lang="fa" data-show-screen-name="false" data-dnt="true">دنبال کردن @iran…

    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 124, Column 153: there is no attribute "data-dnt"
    …fa" data-show-screen-name="false" data-dnt="true">دنبال کردن @iranlivetvcom</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 125, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

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

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

  • Error Line 130, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 137, Column 32: there is no attribute "data-href"
    <div class="fb-like" data-href="http://www.facebook.com/pages/iran-livetvcom/34…

    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 137, Column 105: there is no attribute "data-send"
    …-livetvcom/346685872079758" data-send="true" data-layout="box_count" data-widt…

    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 137, Column 124: there is no attribute "data-layout"
    …2079758" data-send="true" data-layout="box_count" data-width="100" data-show-f…

    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 137, Column 147: there is no attribute "data-width"
    …="true" data-layout="box_count" data-width="100" data-show-faces="true"></div>	

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

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

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

  • Error Line 137, Column 169: there is no attribute "data-show-faces"
    …="true" data-layout="box_count" data-width="100" data-show-faces="true"></div>	

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

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

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

  • Error Line 146, Column 178: end tag for "img" omitted, but OMITTAG NO was specified
    …p://iran-livetv.com/images/home.png" width="25" style="border-width: 0px" ></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 146, Column 68: start tag was here
    …http://iran-livetv.com/" title="خانه"><img alt="iran live tv" src="http://iran…
  • Warning Line 179, Column 91: character "&" is the first character of a delimiter but occurred as data
    …dow.external.addFavorite(window.top.location.href,'Persian Live Tv & Radio');">

    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 180, Column 152: end tag for "img" omitted, but OMITTAG NO was specified
    …rites" src="http://iran-livetv.com/images/addtofavorites.png" height="35" ></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 180, Column 1: start tag was here
    <img style="border-width:0px" alt="Add to favourites" title="Add to favourites"…
  • Error Line 188, Column 194: end tag for "img" omitted, but OMITTAG NO was specified
    …د" alt="login" src="http://iran-livetv.com/images/login-icon.png" height="35" >

    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 188, Column 1: start tag was here
    <img style="cursor:pointer; border-width:0px;" onclick="return popUp1('http://d…
  • Error Line 190, Column 175: end tag for "img" omitted, but OMITTAG NO was specified
    …60" src="http://iran-livetv.com/images/facebook1.png" class="auto-style1" ></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 190, Column 1: start tag was here
    <img title="فیسبوک" style=" position:relative; left:30px; float: right;" alt="f…
  • Warning Line 193, Column 121: character "&" is the first character of a delimiter but occurred as data
    …etv.com Toolbar to enable you to View & Access your favourite Live Tv & Radio …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 193, Column 153: character "&" is the first character of a delimiter but occurred as data
    … View & Access your favourite Live Tv & Radio channels, Movies & Serials or Li…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 193, Column 178: character "&" is the first character of a delimiter but occurred as data
    …rite Live Tv & Radio channels, Movies & Serials or Listen to your Music all fr…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 194, Column 213: character "&" is the first character of a delimiter but occurred as data
    …etv.com Toolbar to enable you to View & Access your favourite Live Tv & Radio …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 194, Column 245: character "&" is the first character of a delimiter but occurred as data
    … View & Access your favourite Live Tv & Radio channels, Movies & Serials or Li…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 194, Column 270: character "&" is the first character of a delimiter but occurred as data
    …rite Live Tv & Radio channels, Movies & Serials or Listen to your Music all fr…

    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 194, Column 388: end tag for "img" omitted, but OMITTAG NO was specified
    …om a click that will navigate you fast and directly from your PC.. ENJOY!"></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 194, Column 1: start tag was here
    <img style="position:relative; top:10px; left: 0px; border-width:0px;" alt="Ira…
  • Error Line 201, Column 69: end tag for "img" omitted, but OMITTAG NO was specified
    alt="Iranian Live Tv online" title="Iran Live Tv" class=" logo" ></a></div>

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

  • Info Line 200, Column 2: start tag was here
    	<img src="http://iran-livetv.com/images/logo.png" style="border-width:0px;" 
  • Warning Line 216, Column 34: multiple comments in comment declaration
     <!-- Start Facebook Cookies --------------------------------------------------…
  • Warning Line 216, Column 38: multiple comments in comment declaration
     <!-- Start Facebook Cookies --------------------------------------------------…
  • Warning Line 216, Column 42: multiple comments in comment declaration
    …-- Start Facebook Cookies ----------------------------------------------------…
  • Warning Line 216, Column 46: multiple comments in comment declaration
    …tart Facebook Cookies --------------------------------------------------------…
  • Warning Line 216, Column 50: multiple comments in comment declaration
    … Facebook Cookies ------------------------------------------------------------…
  • Warning Line 216, Column 54: multiple comments in comment declaration
    …ebook Cookies ----------------------------------------------------------------…
  • Warning Line 216, Column 58: multiple comments in comment declaration
    …k Cookies ----------------------------------------------------------------- --…
  • Warning Line 216, Column 62: multiple comments in comment declaration
    …k Cookies ----------------------------------------------------------------- -->
  • Warning Line 216, Column 66: multiple comments in comment declaration
    …k Cookies ----------------------------------------------------------------- -->
  • Warning Line 216, Column 70: multiple comments in comment declaration
    …k Cookies ----------------------------------------------------------------- -->
  • Warning Line 216, Column 74: multiple comments in comment declaration
    …k Cookies ----------------------------------------------------------------- -->
  • Warning Line 216, Column 78: multiple comments in comment declaration
    …k Cookies ----------------------------------------------------------------- -->
  • Warning Line 216, Column 82: multiple comments in comment declaration
    …k Cookies ----------------------------------------------------------------- -->
  • Warning Line 216, Column 86: multiple comments in comment declaration
    …k Cookies ----------------------------------------------------------------- -->
  • Warning Line 216, Column 90: multiple comments in comment declaration
    …k Cookies ----------------------------------------------------------------- -->
  • Warning Line 216, Column 96: multiple comments in comment declaration
    …k Cookies ----------------------------------------------------------------- -->
  • Error Line 217, Column 96: document type does not allow element "link" here
    …sheet" type="text/css" href="http://iran-livetv.com/facebook-cookie/main.css"/>

    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 219, Column 106: there is no attribute "read_more"
    …k-cookie/require-opt-in.js" read_more="http://www.facebook.com/pages/iran-live…

    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 220, Column 31: multiple comments in comment declaration
     <!-- End Facebook Cookies-----------------------------------------------------…
  • Warning Line 220, Column 35: multiple comments in comment declaration
     <!-- End Facebook Cookies-----------------------------------------------------…
  • Warning Line 220, Column 39: multiple comments in comment declaration
     <!-- End Facebook Cookies-----------------------------------------------------…
  • Warning Line 220, Column 43: multiple comments in comment declaration
    …- End Facebook Cookies--------------------------------------------------------…
  • Warning Line 220, Column 47: multiple comments in comment declaration
    …d Facebook Cookies------------------------------------------------------------…
  • Warning Line 220, Column 51: multiple comments in comment declaration
    …cebook Cookies----------------------------------------------------------------…
  • Warning Line 220, Column 55: multiple comments in comment declaration
    …ok Cookies--------------------------------------------------------------------…
  • Warning Line 220, Column 59: multiple comments in comment declaration
    …Cookies-------------------------------------------------------------------- -->
  • Warning Line 220, Column 63: multiple comments in comment declaration
    …Cookies-------------------------------------------------------------------- -->
  • Warning Line 220, Column 67: multiple comments in comment declaration
    …Cookies-------------------------------------------------------------------- -->
  • Warning Line 220, Column 71: multiple comments in comment declaration
    …Cookies-------------------------------------------------------------------- -->
  • Warning Line 220, Column 75: multiple comments in comment declaration
    …Cookies-------------------------------------------------------------------- -->
  • Warning Line 220, Column 79: multiple comments in comment declaration
    …Cookies-------------------------------------------------------------------- -->
  • Warning Line 220, Column 83: multiple comments in comment declaration
    …Cookies-------------------------------------------------------------------- -->
  • Warning Line 220, Column 87: multiple comments in comment declaration
    …Cookies-------------------------------------------------------------------- -->
  • Warning Line 220, Column 91: multiple comments in comment declaration
    …Cookies-------------------------------------------------------------------- -->
  • Warning Line 220, Column 96: multiple comments in comment declaration
    …Cookies-------------------------------------------------------------------- -->
  • Error Line 231, Column 16: invalid comment declaration: found name character outside comment but inside comment declaration
    <!--ad-header--->
  • Info Line 231, Column 1: comment declaration started here
    <!--ad-header--->
  • Error Line 247, Column 4: "if" is not a reserved name
    <![if !IE]>
  • Error Line 249, Column 4: "endif" is not a reserved name
    <![endif]>
  • Error Line 255, Column 157: end tag for "img" omitted, but OMITTAG NO was specified
    …idth="140"  style="border-width: 0px; padding-top:10px;"  title="Live Tv" ></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 255, Column 1: start tag was here
    <img alt="Iranian Live tv" src="http://iran-livetv.com/images/botton-tv.png" wi…
  • Error Line 257, Column 146: end tag for "img" omitted, but OMITTAG NO was specified
    …tton-radio.png" width="140" style="border-width: 0px"  title="Live Radio" ></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 257, Column 1: start tag was here
    <img alt="Iranian Live Radio" src="http://iran-livetv.com/images/botton-radio.p…
  • Error Line 259, Column 138: end tag for "img" omitted, but OMITTAG NO was specified
    …s/botton-movies.png" width="140" style="border-width: 0px" title="Movies" ></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 259, Column 1: start tag was here
    <img alt="Iranian Movies" src="http://iran-livetv.com/images/botton-movies.png"…
  • Error Line 261, Column 149: end tag for "img" omitted, but OMITTAG NO was specified
    …erials.png" width="140" style="border-width: 0px" title="Iranian Serials" ></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 261, Column 1: start tag was here
    <img alt="Iranian Serials" src="http://iran-livetv.com/images/botton-serials.pn…
  • Error Line 263, Column 150: end tag for "img" omitted, but OMITTAG NO was specified
    …ton-music.png" width="140" style="border-width: 0px" title="Music Videos" ></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 263, Column 1: start tag was here
    <img alt="Iranian Live tv Music" src="http://iran-livetv.com/images/botton-musi…
  • Error Line 274, Column 2: required attribute "alt" not specified
    /></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 281, Column 5: document type does not allow element "div" here
    <div>

    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 284, Column 147: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …m/music/images/googoosh-bimanoto-long.jpg') no-repeat scroll 0 0 transparent;">

    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 289, Column 145: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …com/music/images/ebi-haminkhoobe-long.jpg') no-repeat scroll 0 0 transparent;">

    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 294, Column 161: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …/bijanmortazavi-asheghtaramkardi-long.jpg') no-repeat scroll 0 0 transparent;">

    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 299, Column 145: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …com/music/images/andy-khodahafez-long.jpg') no-repeat scroll 0 0 transparent;">

    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 304, Column 153: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …c/images/leilafroohar-sarzaminam-long.jpg') no-repeat scroll 0 0 transparent;">

    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 312, Column 5: document type does not allow element "div" here
    <div>

    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 316, Column 154: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …/images/reza-sadeghi-namardomiha-long.jpg') no-repeat scroll 0 0 transparent;">

    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 321, Column 149: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …music/images/shamaizadeh-javooni-long.jpg') no-repeat scroll 0 0 transparent;">

    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 326, Column 152: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ic/images/reza-sadeghi-adamahani-long.jpg') no-repeat scroll 0 0 transparent;">

    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 331, Column 148: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …/music/images/manoto-samanoo1392-long.jpg') no-repeat scroll 0 0 transparent;">

    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 336, Column 161: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …/mohsenchavoshi-aberooyemardomet-long.jpg') no-repeat scroll 0 0 transparent;">

    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 351, Column 74: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="seriescomingwrapper">

    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 358, Column 74: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="seriescomingwrapper">

    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 365, Column 74: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="seriescomingwrapper">

    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 372, Column 74: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="seriescomingwrapper">

    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 379, Column 74: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="seriescomingwrapper">

    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 413, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 425, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 436, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 447, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 458, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 469, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 480, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 547, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 557, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 567, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 577, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 588, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 599, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 610, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 621, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 632, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div style="float:left; margin-bottom: 5px; " class="indexcomingwrapper">

    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 728, Column 30: document type does not allow element "body" here
    <body onload="firstMessage()">

    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 732, Column 23: document type does not allow element "style" here
    <style type="text/css">

    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 739, Column 13: there is no attribute "id"
    <marquee id="mymarquee" behavior="scroll" direction="right" scrollamount="4" on…

    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 739, Column 34: there is no attribute "behavior"
    <marquee id="mymarquee" behavior="scroll" direction="right" scrollamount="4" on…

    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 739, Column 53: there is no attribute "direction"
    …ymarquee" behavior="scroll" direction="right" scrollamount="4" onmouseover="th…

    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 739, Column 74: there is no attribute "scrollamount"
    …croll" direction="right" scrollamount="4" onmouseover="this.setAttribute('scro…

    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 739, Column 90: there is no attribute "onmouseover"
    …="right" scrollamount="4" onmouseover="this.setAttribute('scrollamount', 0, 0)…

    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 739, Column 144: there is no attribute "onmouseout"
    …te('scrollamount', 0, 0);" onmouseout="this.setAttribute('scrollamount', 4, 0)…

    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 739, Column 186: element "marquee" undefined
    …('scrollamount', 0, 0);" onmouseout="this.setAttribute('scrollamount', 4, 0);">

    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 923, Column 23: document type does not allow element "style" here
    <style type="text/css">

    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 1443, Column 16: invalid comment declaration: found name character outside comment but inside comment declaration
    	<!--ad-right--->		
  • Info Line 1443, Column 2: comment declaration started here
    	<!--ad-right--->		
  • Error Line 1446, Column 22: required attribute "type" not specified
    <script id="_wau5sl" >var _wau = _wau || [];

    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 1452, Column 23: document type does not allow element "style" here
    <style type="text/css">

    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 1461, Column 136: end tag for "img" omitted, but OMITTAG NO was specified
    …t:-5px; " alt="Iran Live tv" src="http://iran-livetv.com/images/new_icon.gif" >

    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 1461, Column 1: start tag was here
    <img style="position:relative; float:left; top:15px; left:-5px; " alt="Iran Liv…
  • Error Line 1462, Column 128: end tag for "img" omitted, but OMITTAG NO was specified
    …:100;" alt="Recently Added" src="http://iran-livetv.com/images/bg-recent.png" >

    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 1462, Column 1: start tag was here
    <img style="position:relative; left:24px;z-index:100;" alt="Recently Added" src…
  • Error Line 1522, Column 133: end tag for "img" omitted, but OMITTAG NO was specified
    …" title="Gem TV" height="17" src="http://iran-livetv.com/images/gem-icon.jpg" >

    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 1522, Column 1: start tag was here
    <img style="float:left; padding-top:0px;" alt="Gem TV" title="Gem TV" height="1…
  • Error Line 1600, Column 123: end tag for "img" omitted, but OMITTAG NO was specified
    … TV" src="http://iran-livetv.com/images/gem-icon.jpg" style="padding-top:5px;">

    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 1600, Column 1: start tag was here
    <img class="imgnew" alt="Gem TV" title="Gem TV" src="http://iran-livetv.com/ima…
  • Error Line 1608, Column 126: duplicate specification of attribute "style"
    …" src="http://iran-livetv.com/images/farsi1-icon.jpg" style="padding-top:5px;">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1608, Column 145: end tag for "img" omitted, but OMITTAG NO was specified
    …" src="http://iran-livetv.com/images/farsi1-icon.jpg" style="padding-top:5px;">

    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 1608, Column 1: start tag was here
    <img style="float:left" alt="Farsi1 TV" title="Farsi1" height="17" src="http://…
  • Error Line 1613, Column 4: document type does not allow element "tr" here
    <tr>

    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 1615, Column 144: duplicate specification of attribute "style"
    …" src="http://iran-livetv.com/images/farsi1-icon.jpg" style="padding-top:5px;">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1615, Column 163: end tag for "img" omitted, but OMITTAG NO was specified
    …" src="http://iran-livetv.com/images/farsi1-icon.jpg" style="padding-top:5px;">

    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 1615, Column 1: start tag was here
    <img style="float:left; padding-top:0px;" alt="Farsi1 TV" title="Farsi1" height…
  • Error Line 1621, Column 4: document type does not allow element "tr" here
    <tr>

    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 1623, Column 133: end tag for "img" omitted, but OMITTAG NO was specified
    …" title="Gem TV" height="17" src="http://iran-livetv.com/images/gem-icon.jpg" >

    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 1623, Column 1: start tag was here
    <img style="float:left; padding-top:0px;" alt="Gem TV" title="Gem TV" height="1…
  • Error Line 1629, Column 4: document type does not allow element "tr" here
    <tr>

    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 1636, Column 4: document type does not allow element "tr" here
    <tr>

    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 1643, Column 4: document type does not allow element "tr" here
    <tr>

    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 1645, Column 133: end tag for "img" omitted, but OMITTAG NO was specified
    …" title="Gem TV" height="17" src="http://iran-livetv.com/images/gem-icon.jpg" >

    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 1645, Column 1: start tag was here
    <img style="float:left; padding-top:0px;" alt="Gem TV" title="Gem TV" height="1…
  • Error Line 1651, Column 4: document type does not allow element "tr" here
    <tr>

    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 1658, Column 4: document type does not allow element "tr" here
    <tr>

    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 1665, Column 4: document type does not allow element "tr" here
    <tr>

    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 1672, Column 4: document type does not allow element "tr" here
    <tr>

    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 1679, Column 4: document type does not allow element "tr" here
    <tr>

    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 1686, Column 4: document type does not allow element "tr" here
    <tr>

    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 1694, Column 4: document type does not allow element "tr" here
    <tr>

    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 1700, Column 4: document type does not allow element "tr" here
    <tr>

    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 1710, 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 1606, Column 1: start tag was here
    <tr>
  • Error Line 1718, Column 113: end tag for "img" omitted, but OMITTAG NO was specified
    …//iran-livetv.com/ad/images/ps3.png" width="210" style="border-width: 0px"></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 1718, Column 1: start tag was here
    <img alt="Persian Star" src="http://iran-livetv.com/ad/images/ps3.png" width="2…
  • Error Line 1724, Column 126: end tag for "img" omitted, but OMITTAG NO was specified
    …radiofarda-3.jpg" title="رادیو فردا" width="210" style="border-width: 0px"></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 1724, Column 1: start tag was here
    <img alt="" src="http://iran-livetv.com/images/radiofarda-3.jpg" title="رادیو ف…
  • Error Line 1738, Column 122: end tag for "img" omitted, but OMITTAG NO was specified
    …ges/bia2-r.jpg" title="رادیو بیا تو" width="210" style="border-width: 0px"></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 1738, Column 1: start tag was here
    <img alt="" src="http://iran-livetv.com/images/bia2-r.jpg" title="رادیو بیا تو"…
  • Error Line 1786, Column 114: end tag for "img" omitted, but OMITTAG NO was specified
    …t:24px;" alt="Featured News" src="http://iran-livetv.com/images/bg-fnews.png" >

    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 1786, Column 1: start tag was here
    <img style="position:relative; left:24px;" alt="Featured News" src="http://iran…
  • Error Line 1950, Column 159: there is no attribute "data-height"
    …2079758" data-width="200" data-height="360" data-colorscheme="dark" data-show-…

    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 1950, Column 182: there is no attribute "data-colorscheme"
    …0" data-height="360" data-colorscheme="dark" data-show-faces="true" data-strea…

    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 1950, Column 224: there is no attribute "data-stream"
    …eme="dark" data-show-faces="true" data-stream="false" data-header="true"></div>

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

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

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

  • Error Line 1950, Column 244: there is no attribute "data-header"
    …eme="dark" data-show-faces="true" data-stream="false" data-header="true"></div>

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

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

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

  • Error Line 1960, Column 14: invalid comment declaration: found name character outside comment but inside comment declaration
    	<!--footer--->
  • Info Line 1960, Column 2: comment declaration started here
    	<!--footer--->
  • Error Line 1962, Column 15: there is no attribute "height"
    <table height="250">

    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 1966, Column 81: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://iran-livetv.com/tv/voa/" title="صدای آمریکا">صدای آمریکا</a><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 1966, Column 77: start tag was here
    <a href="http://iran-livetv.com/tv/voa/" title="صدای آمریکا">صدای آمریکا</a><br>
  • Error Line 1967, Column 87: end tag for "br" omitted, but OMITTAG NO was specified
    …="http://iran-livetv.com/tv/bbc/" title="بی بی سی فارسی">بی بی سی فارسی</a><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 1967, Column 83: start tag was here
    …="http://iran-livetv.com/tv/bbc/" title="بی بی سی فارسی">بی بی سی فارسی</a><br>
  • Error Line 1968, Column 99: end tag for "br" omitted, but OMITTAG NO was specified
    …n-livetv.com/tv/euronews-pers/" title="یورو نیوز فارسی">یورو نیوز فارسی</a><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 1968, Column 95: start tag was here
    …n-livetv.com/tv/euronews-pers/" title="یورو نیوز فارسی">یورو نیوز فارسی</a><br>
  • Error Line 1969, Column 77: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://iran-livetv.com/tv/manoto1/" title="من و تو">من و تو</a><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 1969, Column 73: start tag was here
    <a href="http://iran-livetv.com/tv/manoto1/" title="من و تو">من و تو</a><br>
  • Error Line 1970, Column 74: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://iran-livetv.com/tv/farsi1/" title="فارسی1">فارسی1</a><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 1970, Column 70: start tag was here
    <a href="http://iran-livetv.com/tv/farsi1/" title="فارسی1">فارسی1</a><br>
  • Error Line 1971, Column 65: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://iran-livetv.com/tv/pmc/" title="PMC">PMC</a><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 1971, Column 61: start tag was here
    <a href="http://iran-livetv.com/tv/pmc/" title="PMC">PMC</a><br>
  • Error Line 1972, Column 86: end tag for "br" omitted, but OMITTAG NO was specified
    …f="http://iran-livetv.com/tv/pmc-family/" title="PMC Family">PMC Family</a><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 1972, Column 82: start tag was here
    …f="http://iran-livetv.com/tv/pmc-family/" title="PMC Family">PMC Family</a><br>
  • Error Line 1973, Column 80: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://iran-livetv.com/tv/channel1/" title="کانال یک">کانال یک</a><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 1973, Column 76: start tag was here
    <a href="http://iran-livetv.com/tv/channel1/" title="کانال یک">کانال یک</a><br>
  • Error Line 1980, Column 90: end tag for "br" omitted, but OMITTAG NO was specified
    …ttp://iran-livetv.com/radio/radio-farda/" title="رادیو فردا">رادیو فردا</a><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 1980, Column 86: start tag was here
    …ttp://iran-livetv.com/radio/radio-farda/" title="رادیو فردا">رادیو فردا</a><br>
  • Error Line 1981, Column 84: end tag for "br" omitted, but OMITTAG NO was specified
    …ref="http://iran-livetv.com/radio/payam/" title="رادیو پیام">رادیو پیام</a><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 1981, Column 80: start tag was here
    …ref="http://iran-livetv.com/radio/payam/" title="رادیو پیام">رادیو پیام</a><br>
  • Error Line 1982, Column 75: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://iran-livetv.com/radio/bia2/" title="بیا تو">بیا تو</a><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 1982, Column 71: start tag was here
    <a href="http://iran-livetv.com/radio/bia2/" title="بیا تو">بیا تو</a><br>
  • Error Line 1983, Column 90: end tag for "br" omitted, but OMITTAG NO was specified
    …ttp://iran-livetv.com/radio/radio-javan/" title="رادیو جوان">رادیو جوان</a><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 1983, Column 86: start tag was here
    …ttp://iran-livetv.com/radio/radio-javan/" title="رادیو جوان">رادیو جوان</a><br>
  • Error Line 1984, Column 88: end tag for "br" omitted, but OMITTAG NO was specified
    …"http://iran-livetv.com/radio/zamaneh/" title="رادیو زمانه">رادیو زمانه</a><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 1984, Column 84: start tag was here
    …"http://iran-livetv.com/radio/zamaneh/" title="رادیو زمانه">رادیو زمانه</a><br>
  • Error Line 1985, Column 86: end tag for "br" omitted, but OMITTAG NO was specified
    …f="http://iran-livetv.com/radio/koocheh/" title="رادیو کوچه">رادیو کوچه</a><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 1985, Column 82: start tag was here
    …f="http://iran-livetv.com/radio/koocheh/" title="رادیو کوچه">رادیو کوچه</a><br>
  • Error Line 1986, Column 88: end tag for "br" omitted, but OMITTAG NO was specified
    …"http://iran-livetv.com/radio/hamseda/" title="رادیو همصدا">رادیو همصدا</a><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 1986, Column 84: start tag was here
    …"http://iran-livetv.com/radio/hamseda/" title="رادیو همصدا">رادیو همصدا</a><br>
  • Error Line 1987, Column 81: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://iran-livetv.com/radio/nabz/" title="رادیو نبض">رادیو نبض</a><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 1987, Column 77: start tag was here
    <a href="http://iran-livetv.com/radio/nabz/" title="رادیو نبض">رادیو نبض</a><br>
  • Error Line 1988, Column 93: end tag for "br" omitted, but OMITTAG NO was specified
    …://iran-livetv.com/radio/porchooneh/" title="رادیو پرچونه">رادیو پرچونه</a><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 1988, Column 89: start tag was here
    …://iran-livetv.com/radio/porchooneh/" title="رادیو پرچونه">رادیو پرچونه</a><br>
  • Error Line 1989, Column 89: end tag for "br" omitted, but OMITTAG NO was specified
    …http://iran-livetv.com/radio/hamsafar/" title="رادیو همسفر">رادیو همسفر</a><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 1989, Column 85: start tag was here
    …http://iran-livetv.com/radio/hamsafar/" title="رادیو همسفر">رادیو همسفر</a><br>
  • Error Line 1990, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><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 1990, Column 1: start tag was here
    <br><br><br><br>
  • Error Line 1990, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><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 1990, Column 5: start tag was here
    <br><br><br><br>
  • Error Line 1990, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><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 1990, Column 9: start tag was here
    <br><br><br><br>
  • Error Line 1990, Column 17: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><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 1990, Column 13: start tag was here
    <br><br><br><br>
  • Error Line 1996, Column 135: end tag for "br" omitted, but OMITTAG NO was specified
    …"شاید برای شما هم اتفاق بیفتد فصل-2">شاید برای شما هم اتفاق بیفتد فصل-2</a><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 1996, Column 131: start tag was here
    …"شاید برای شما هم اتفاق بیفتد فصل-2">شاید برای شما هم اتفاق بیفتد فصل-2</a><br>
  • Error Line 1997, Column 107: end tag for "br" omitted, but OMITTAG NO was specified
    ….com/series/dokhtaranhava/" title="سریال دختران حوا ">سریال دختران حوا </a><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 1997, Column 103: start tag was here
    ….com/series/dokhtaranhava/" title="سریال دختران حوا ">سریال دختران حوا </a><br>
  • Error Line 1998, Column 112: end tag for "br" omitted, but OMITTAG NO was specified
    …series/ghalbeyakhi3/" title="سریال قلب یخی فصل-۳ ">سریال قلب یخی فصل-۳ </a><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 1998, Column 108: start tag was here
    …series/ghalbeyakhi3/" title="سریال قلب یخی فصل-۳ ">سریال قلب یخی فصل-۳ </a><br>
  • Error Line 1999, Column 112: end tag for "br" omitted, but OMITTAG NO was specified
    …series/rastashrobegoo/" title="سریال راستش رو بگو ">سریال راستش رو بگو </a><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 1999, Column 108: start tag was here
    …series/rastashrobegoo/" title="سریال راستش رو بگو ">سریال راستش رو بگو </a><br>
  • Error Line 2000, Column 121: end tag for "br" omitted, but OMITTAG NO was specified
    …aliat-125/" title="سریال عملیات 125 فصل سوم ">سریال عملیات 125 فصل سوم </a><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 2000, Column 117: start tag was here
    …aliat-125/" title="سریال عملیات 125 فصل سوم ">سریال عملیات 125 فصل سوم </a><br>
  • Error Line 2001, Column 108: end tag for "br" omitted, but OMITTAG NO was specified
    …com/series/kolahe-pahlavi/" title="سریال کلاه پهلوی ">سریال کلاه پهلوی </a><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 2001, Column 104: start tag was here
    …com/series/kolahe-pahlavi/" title="سریال کلاه پهلوی ">سریال کلاه پهلوی </a><br>
  • Error Line 2002, Column 104: end tag for "br" omitted, but OMITTAG NO was specified
    …etv.com/series/harimsoltan/" title="سریال حریم سلطان">سریال حریم سلطان </a><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 2002, Column 100: start tag was here
    …etv.com/series/harimsoltan/" title="سریال حریم سلطان">سریال حریم سلطان </a><br>
  • Error Line 2003, Column 115: end tag for "br" omitted, but OMITTAG NO was specified
    …ies/azboosetaeshgh/" title="سریال از بوسه تا عشق">سریال از بوسه تا عشق </a><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 2003, Column 111: start tag was here
    …ies/azboosetaeshgh/" title="سریال از بوسه تا عشق">سریال از بوسه تا عشق </a><br>
  • Error Line 2004, Column 106: end tag for "br" omitted, but OMITTAG NO was specified
    …v.com/series/bartarineshgh/" title="سریال برترین عشق">سریال برترین عشق </a><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 2004, Column 102: start tag was here
    …v.com/series/bartarineshgh/" title="سریال برترین عشق">سریال برترین عشق </a><br>
  • Error Line 2005, Column 101: end tag for "br" omitted, but OMITTAG NO was specified
    …livetv.com/series/shamimeeshgh/" title="سریال شمیم عشق">سریال شمیم عشق </a><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 2005, Column 97: start tag was here
    …livetv.com/series/shamimeeshgh/" title="سریال شمیم عشق">سریال شمیم عشق </a><br>
  • Error Line 2006, Column 101: end tag for "br" omitted, but OMITTAG NO was specified
    …livetv.com/series/rooheelina/" title="سریال روح الینا">سریال روح الینا </a><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 2006, Column 97: start tag was here
    …livetv.com/series/rooheelina/" title="سریال روح الینا">سریال روح الینا </a><br>
  • Error Line 2007, Column 109: end tag for "br" omitted, but OMITTAG NO was specified
    …om/series/omregolelale/" title="سریال عمر گل لاله ">سریال عمر گل لاله  </a><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 2007, Column 105: start tag was here
    …om/series/omregolelale/" title="سریال عمر گل لاله ">سریال عمر گل لاله  </a><br>
  • Error Line 2010, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><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 2010, Column 1: start tag was here
    <br><br><br><br>
  • Error Line 2010, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><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 2010, Column 5: start tag was here
    <br><br><br><br>
  • Error Line 2010, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><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 2010, Column 9: start tag was here
    <br><br><br><br>
  • Error Line 2010, Column 17: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><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 2010, Column 13: start tag was here
    <br><br><br><br>
  • Error Line 2017, Column 72: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
          <div style="height: 35px; overflow: hidden; margin-bottom: 4px; "> 

    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 2018, Column 89: required attribute "type" not specified
    …     <div id="google_translate_element" style="margin-top:9px;"></div><script> 

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

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

  • Error Line 2024, Column 112: required attribute "type" not specified
    …late.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>

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

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

  • Error Line 2028, Column 104: end tag for "img" omitted, but OMITTAG NO was specified
    …vetv.com/images/footer_facebookicon.png" width="18">Find us on Facebook</a><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 2028, Column 1: start tag was here
    <img alt="facebook" height="18" src="http://iran-livetv.com/images/footer_faceb…
  • Error Line 2028, Column 131: end tag for "br" omitted, but OMITTAG NO was specified
    …vetv.com/images/footer_facebookicon.png" width="18">Find us on Facebook</a><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 2028, Column 127: start tag was here
    …vetv.com/images/footer_facebookicon.png" width="18">Find us on Facebook</a><br>
  • Error Line 2030, Column 120: end tag for "img" omitted, but OMITTAG NO was specified
    …/iran-livetv.com/images/twitter-icon.png" width="18">Find us on Twitter</a><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 2030, Column 1: start tag was here
    <img style="padding-top:5px" alt="twitter" height="18" src="http://iran-livetv.…
  • Error Line 2030, Column 146: end tag for "br" omitted, but OMITTAG NO was specified
    …/iran-livetv.com/images/twitter-icon.png" width="18">Find us on Twitter</a><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 2030, Column 142: start tag was here
    …/iran-livetv.com/images/twitter-icon.png" width="18">Find us on Twitter</a><br>
  • Error Line 2032, Column 120: end tag for "img" omitted, but OMITTAG NO was specified
    …/iran-livetv.com/images/youtube_icon.png" width="18">Find us on Youtube</a><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 2032, Column 1: start tag was here
    <img style="padding-top:5px" alt="youtube" height="18" src="http://iran-livetv.…
  • Error Line 2032, Column 146: end tag for "br" omitted, but OMITTAG NO was specified
    …/iran-livetv.com/images/youtube_icon.png" width="18">Find us on Youtube</a><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 2032, Column 142: start tag was here
    …/iran-livetv.com/images/youtube_icon.png" width="18">Find us on Youtube</a><br>
  • Error Line 2036, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …leBookmarksIcon.png" alt="Google Bookmarks" width="18">Google Bookmarks</a><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 2036, Column 1: start tag was here
    <img style="padding-top:5px" src="http://iran-livetv.com/images/GoogleBookmarks…
  • Error Line 2036, Column 148: end tag for "br" omitted, but OMITTAG NO was specified
    …leBookmarksIcon.png" alt="Google Bookmarks" width="18">Google Bookmarks</a><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 2036, Column 144: start tag was here
    …leBookmarksIcon.png" alt="Google Bookmarks" width="18">Google Bookmarks</a><br>
  • Error Line 2039, Column 91: duplicate specification of attribute "target"
    …-livetv.com/toolbar/" target="_blank" title="Downlaod Toolbar" target="_blank">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 2040, Column 149: end tag for "img" omitted, but OMITTAG NO was specified
    …src="http://iran-livetv.com/images/toolbar.png" width="18">Downlaod Toolbar</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 2040, Column 1: start tag was here
    <img style="padding-top:5px" alt="Downlaod Toolbar" title="Downlaod Toolbar" he…
  • Error Line 2043, Column 102: end tag for "br" omitted, but OMITTAG NO was specified
    …ivetv.com/ad/" title="Advertise With Iran-livetv.com">Advertise With Us</a><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 2043, Column 98: start tag was here
    …ivetv.com/ad/" title="Advertise With Iran-livetv.com">Advertise With Us</a><br>
  • Error Line 2044, Column 97: end tag for "br" omitted, but OMITTAG NO was specified
    …ran-livetv.com/contact.php/" title="Contact Iran-livetv.com">Contact Us</a><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 2044, Column 93: start tag was here
    …ran-livetv.com/contact.php/" title="Contact Iran-livetv.com">Contact Us</a><br>
  • Error Line 2045, Column 110: end tag for "br" omitted, but OMITTAG NO was specified
    …m/sat.php/" title="List of Persian Satellite TV Frequency">TV Frequency</a><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 2045, Column 106: start tag was here
    …m/sat.php/" title="List of Persian Satellite TV Frequency">TV Frequency</a><br>
  • Error Line 2046, Column 112: end tag for "br" omitted, but OMITTAG NO was specified
    …dmca.php/" title="Copyright Infringement Notice">Copyright Infringement</a><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 2046, Column 108: start tag was here
    …dmca.php/" title="Copyright Infringement Notice">Copyright Infringement</a><br>
  • Error Line 2047, Column 94: end tag for "br" omitted, but OMITTAG NO was specified
    …//iran-livetv.com/terms.php/" title="Terms of Service">Terms of Service</a><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 2047, Column 90: start tag was here
    …//iran-livetv.com/terms.php/" title="Terms of Service">Terms of Service</a><br>
  • Error Line 2048, Column 92: end tag for "br" omitted, but OMITTAG NO was specified
    …p://iran-livetv.com/privacy.php/" title="Privacy policy">Privacy policy</a><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 2048, Column 88: start tag was here
    …p://iran-livetv.com/privacy.php/" title="Privacy policy">Privacy policy</a><br>
  • Error Line 2055, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr>

    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 2055, Column 1: start tag was here
    <hr>
  • Error Line 2060, Column 69: end tag for "br" omitted, but OMITTAG NO was specified
    <strong>Copyright &copy;2012 Iran-livetv.com All rights reserved<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 2060, Column 65: start tag was here
    <strong>Copyright &copy;2012 Iran-livetv.com All rights reserved<br>
  • Error Line 2061, Column 40: end tag for "br" omitted, but OMITTAG NO was specified
    All trademarks acknowledged<br></strong>

    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 2061, Column 28: start tag was here
    All trademarks acknowledged<br></strong>
  • Error Line 2064, Column 115: end tag for "img" omitted, but OMITTAG NO was specified
    …ran-LiveTv.com" src="http://iran-livetv.com/images/logo1.png" width="300"></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 2064, Column 5: start tag was here
    <td><img alt="Iran Live Tv" title="Iran-LiveTv.com" src="http://iran-livetv.com…
  • Error Line 2068, 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 141, Column 1: start tag was here
    <div id="header" >

Visitor Analysis

Daily Visitor
  • 4.667 visits

In Page Analysis