آخرین به روزرسانی آمار معاملات:  ۱۳۹۲/۴/۵  ۱۲:۱۴ انتخاب موضوع جستجو كل سايت عنوان خبر و اطلاعيه     » تازه‌ها    » بازار در یک نگاه    آمار معاملات هفتگي تالار شيشه اي در پايان هفته منتهي به ...

irbourse.com
  • Domain Name
    irbourse.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #28272
  • Page Size
    86.3 KB
  • Ip Address
    91.99.101.210
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    36 GIF, 6 JPG, 3 PNG

Website Meta Analysis

  • Title
    بورس اوراق بهادار تهران Tehran Stock Exchange
  • Meta Keyword
  • Meta Description
    آخرین به روزرسانی آمار معاملات:  ۱۳۹۲/۴/۵  ۱۲:۱۴ انتخاب موضوع جستجو كل سايت عنوان خبر و اطلاعيه     » تازه‌ها    » بازار در یک نگاه    آمار معاملات هفتگي تالار شيشه اي در پايان هفته منتهي به ۵ تير ماه، شاخص کل با ۰۴ / ۱ درصد افرايش روبرو شد. ...

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    91.99.101.210
  • Domain Age
    9 Years, 11 Months, 4 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • date: Fri, 28 Jun 2013 09:00:20 GMT
  • content-length: 25624
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
DPI Co.
No.216 Nejatolahi Ave
Tehran, Tehran 11365
IR
Domain Domain Name: IRBOURSE.COM

Administrative Contact:
MohammadMirza, Behzad email
No.216 Nejatolahi Ave
Tehran, Tehran 11365
IR
+98213926311
Technical Contact:
MohammadMirza, Behzad email
No.216 Nejatolahi Ave
Tehran, Tehran 11365
IR
+98213926311

Registrar: TUCOWS, INC.
Updated: 03-Jul-2007.
Expires: 17-Jul-2012.
Created: 17-Jul-2003.
Name Servers:
DNS2.PARSNETWORKS.COM
DNS1.PARSNETWORKS.COM

Domain Domain Status: clientTransferProhibited
clientUpdateProhibited

DNS Analysis


DNS servers
dns1.parsnetworks.com [213.217.40.186]
dns2.parsnetworks.com [213.217.60.3]


DNS Records

Answer records
irbourse.com SOA
server: dns1.parsnetworks.com
email: dns1@parsnetworks.com
serial: 2010091302
refresh: 600
retry: 1800
expire: 864000
minimum ttl: 86400
86400s
irbourse.com NS  dns1.parsnetworks.com 86400s
irbourse.com NS  dns2.parsnetworks.com 86400s
irbourse.com A 91.99.101.210 86400s

Authority records

Additional records

IP 91.99.101.210 Analysis

  • Country Code
    IR
  • Country Code3
    IRN
  • Country Name
    Iran, Islamic Republic of
  • City
    Pars
  • Continent Code
    AS
  • Latitude
    35.7355
  • Longitude
    51.5291
  • No whois ip data for 91.99.101.210

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 437 Errors
  • 90 Warnings
Ratio Text/Html
  • 0.5274196651914567
Message Error
  • Warning Line 4, Column 20: NET-enabling start-tag requires SHORTTAG YES
    <META content=http://schemas.microsoft.com/intellisense/ie5 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 5, Column 73: document type does not allow element "LINK" here
    name=vs_targetSchema><LINK href="themes/images/style.css" rel=stylesheet>

    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 6, Column 65: document type does not allow element "META" here
    <META http-equiv=Content-Type content="text/html; charset=utf-8">

    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 7, Column 39: document type does not allow element "META" here
    <META content=fa name=Content-Language>

    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).

  • Warning Line 9, Column 51: NET-enabling start-tag requires SHORTTAG YES
    href="themes/images/myfreetemplates.css" type=text/css rel=stylesheet>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 9, Column 51: document type does not allow element "LINK" here
    href="themes/images/myfreetemplates.css" type=text/css rel=stylesheet>

    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).

  • Warning Line 10, Column 46: NET-enabling start-tag requires SHORTTAG YES
    <LINK href="themes/skin1/style.css" type=text/css rel=stylesheet>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 10, Column 46: document type does not allow element "LINK" here
    <LINK href="themes/skin1/style.css" type=text/css rel=stylesheet>

    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 11, Column 54: document type does not allow element "LINK" here
    <LINK href="themes/css/style.css" rel='vstylesheet"/'>

    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 12, Column 50: document type does not allow element "LINK" here
    <LINK href="themes/skin1/text.css" rel=stylesheet>

    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).

  • Warning Line 13, Column 52: NET-enabling start-tag requires SHORTTAG YES
    <link href="themes/css/style.css" rel="stylesheet" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 13, Column 52: document type does not allow element "LINK" here
    <link href="themes/css/style.css" rel="stylesheet" />

    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).

  • Warning Line 14, Column 17: NET-enabling start-tag requires SHORTTAG YES
    <STYLE type=text/css>BODY {

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 14, Column 17: document type does not allow element "STYLE" here
    <STYLE type=text/css>BODY {

    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 31, Column 7: end tag for element "HEAD" which is not open
    </HEAD>

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

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

  • Error Line 32, Column 18: there is no attribute "LEFTMARGIN"
    <BODY leftMargin=0 topMargin=0 marginheight="0" marginwidth="0" bgcolor=#D0D0D0>

    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 32, Column 30: there is no attribute "TOPMARGIN"
    <BODY leftMargin=0 topMargin=0 marginheight="0" marginwidth="0" bgcolor=#D0D0D0>

    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 32, Column 45: there is no attribute "MARGINHEIGHT"
    <BODY leftMargin=0 topMargin=0 marginheight="0" marginwidth="0" bgcolor=#D0D0D0>

    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 32, Column 61: there is no attribute "MARGINWIDTH"
    <BODY leftMargin=0 topMargin=0 marginheight="0" marginwidth="0" bgcolor=#D0D0D0>

    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 32, Column 73: an attribute value must be a literal unless it contains only name characters
    <BODY leftMargin=0 topMargin=0 marginheight="0" marginwidth="0" bgcolor=#D0D0D0>

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

  • Error Line 32, Column 80: document type does not allow element "BODY" here
    <BODY leftMargin=0 topMargin=0 marginheight="0" marginwidth="0" bgcolor=#D0D0D0>

    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 35, Column 45: an attribute value must be a literal unless it contains only name characters
    <TABLE class=grayBack align=center  bgcolor=#D0D0D0>

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

  • Error Line 56, Column 88: invalid comment declaration: found name character outside comment but inside comment declaration
    …0></TD></TR></TBODY></TABLE></DIV><!--- ------------TopBar end-------------- /…
  • Info Line 38, Column 9: comment declaration started here
        <TD><!---------------TopBar Begin------------>
  • Error Line 59, Column 20: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
            <TR vAlign=center align=middle width="900">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 59, Column 33: value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
            <TR vAlign=center align=middle width="900">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 59, Column 46: there is no attribute "WIDTH"
            <TR vAlign=center align=middle width="900">

    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 60, Column 60: required attribute "ALT" not specified
              <TD><IMG src="themes/images/bigHeader_right2.png"></TD>

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

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

  • Error Line 61, Column 39: there is no attribute "BACKGROUND"
              <TD width="100%" background=themes/images/bigHeader_center2.png>

    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 61, Column 45: NET-enabling start-tag requires SHORTTAG YES
              <TD width="100%" background=themes/images/bigHeader_center2.png>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 61, Column 53: character data is not allowed here
              <TD width="100%" background=themes/images/bigHeader_center2.png>

    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 62, Column 56: document type does not allow element "TABLE" here; missing one of "TH", "TD" start-tag
                <TABLE cellSpacing=0 cellPadding=0 border=0>

    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 72, Column 34: required attribute "ALT" not specified
                            width=445></TD>

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

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

  • Warning Line 73, Column 53: NET-enabling start-tag requires SHORTTAG YES
                          <TD width=30 background=themes/images/header2.gif 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 73, Column 61: character data is not allowed here
                          <TD width=30 background=themes/images/header2.gif 

    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 74, Column 38: end tag for "TABLE" omitted, but its declaration does not permit this
                          height=115></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 68, Column 19: start tag was here
                      <TABLE cellSpacing=0 cellPadding=0 border=0>
  • Error Line 76, Column 34: required attribute "ALT" not specified
                            width=496></TD></TR></TBODY></TABLE></TD></TR>

    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 76, Column 65: end tag for "TABLE" omitted, but its declaration does not permit this
                            width=496></TD></TR></TBODY></TABLE></TD></TR>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 57, Column 7: start tag was here
          <TABLE cellSpacing=0 cellPadding=0 width=900 border=0>
  • Error Line 78, Column 61: end tag for element "TD" which is not open
                    <TD height=20></TD></TR></TBODY></TABLE></TD>

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

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

  • Error Line 79, Column 26: document type does not allow element "TD" here
              <TD align=right><IMG 

    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 80, Column 48: required attribute "ALT" not specified
    …rc="themes/images/bigHeader_left2.png"></TD></TR></TBODY></TABLE><!--- -------…

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

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

  • Error Line 80, Column 58: end tag for element "TR" which is not open
    …/images/bigHeader_left2.png"></TD></TR></TBODY></TABLE><!--- ------------Heade…

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

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

  • Error Line 80, Column 66: end tag for element "TBODY" which is not open
    …bigHeader_left2.png"></TD></TR></TBODY></TABLE><!--- ------------Header end---…

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

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

  • Error Line 80, Column 74: end tag for element "TABLE" which is not open
    …r_left2.png"></TD></TR></TBODY></TABLE><!--- ------------Header end-----------…

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

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

  • Error Line 80, Column 118: invalid comment declaration: found character "/" outside comment but inside comment declaration
    …png"></TD></TR></TBODY></TABLE><!--- ------------Header end-------------- //-->

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 80, Column 75: comment declaration started here
    …_left2.png"></TD></TR></TBODY></TABLE><!--- ------------Header end------------…
  • Error Line 82, Column 21: there is no attribute "HEIGHT"
          <TABLE height=588 cellSpacing=0 cellPadding=0 width=600 border=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 86, Column 69: invalid comment declaration: found name start character outside comment but inside comment declaration
    …TABLE cellSpacing=0 cellPadding=0 border=0><!--- ------Modul  Begin------ //-->
  • Info Line 86, Column 57: comment declaration started here
    …TABLE cellSpacing=0 cellPadding=0 border=0><!--- ------Modul  Begin------ //-->
  • Error Line 86, Column 70: character data is not allowed here
    …TABLE cellSpacing=0 cellPadding=0 border=0><!--- ------Modul  Begin------ //-->

    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 90, Column 26: required attribute "ALT" not specified
                      width=1></TD></TR>

    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 96, Column 39: invalid comment declaration: found name start character outside comment but inside comment declaration
                          <TD><!--- ------Modul  header Begin------ //-->
  • Info Line 96, Column 27: comment declaration started here
                          <TD><!--- ------Modul  header Begin------ //-->
  • Error Line 103, Column 90: invalid comment declaration: found name start character outside comment but inside comment declaration
    …</TD></TR></TBODY></TABLE><!--- ------Modul  header end-------- //--></TD></TR…
  • Info Line 103, Column 78: comment declaration started here
    …eft dir=rtl></TD></TR></TBODY></TABLE><!--- ------Modul  header end-------- //…
  • Error Line 105, Column 71: invalid comment declaration: found name start character outside comment but inside comment declaration
    …  <TD style="HEIGHT: auto" vAlign=top><!--- ------Modul  body Begin------ //-->
  • Info Line 105, Column 59: comment declaration started here
    …  <TD style="HEIGHT: auto" vAlign=top><!--- ------Modul  body Begin------ //--…
  • Error Line 110, Column 63: value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
                                <TD class=center vAlign=top align=middle 

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 137, Column 80: invalid comment declaration: found name start character outside comment but inside comment declaration
    …</TD></TR></TBODY></TABLE><!--- ------Modul  body end-------- //--></TD></TR><…
  • Info Line 137, Column 68: comment declaration started here
    …TD class=BL></TD></TR></TBODY></TABLE><!--- ------Modul  body end-------- //--…
  • Error Line 137, Column 157: invalid comment declaration: found name start character outside comment but inside comment declaration
    …</TBODY></TABLE></TD></TR><!--- ------Modul  end-------- //--></TBODY></TABLE>…
  • Info Line 137, Column 145: comment declaration started here
    …-></TD></TR></TBODY></TABLE></TD></TR><!--- ------Modul  end-------- //--></TB…
  • Error Line 137, Column 158: character data is not allowed here
    …/TBODY></TABLE></TD></TR><!--- ------Modul  end-------- //--></TBODY></TABLE><…

    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 138, Column 10: value of attribute "ID" invalid: "_" cannot start a name
          id=__EVENTVALIDATION type=hidden 

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 139, Column 13: an attribute value must be a literal unless it contains only name characters
          value=/wEWPwKI+dbQBQLegqvABQLJv+3mBQLXhK7vCALUhK7vCALVhK7vCALShK7vCALThK7…

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

  • Error Line 140, Column 36: end tag for element "FORM" which is not open
          name=__EVENTVALIDATION></FORM><!--- ------------Footer Begin------------ …

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

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

  • Error Line 141, Column 45: an attribute value must be a literal unless it contains only name characters
          <TABLE width=969 align=center bgColor=#9a9a9a >

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

  • Warning Line 148, Column 46: NET-enabling start-tag requires SHORTTAG YES
                    <TD width=6 background=themes/images/footerBG_TR.png 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 148, Column 54: character data is not allowed here
                    <TD width=6 background=themes/images/footerBG_TR.png 

    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 149, Column 30: end tag for "TABLE" omitted, but its declaration does not permit this
                    height=6></TD>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 145, Column 13: start tag was here
                <TABLE class=footer1 cellSpacing=0 cellPadding=0>
  • Warning Line 150, Column 38: NET-enabling start-tag requires SHORTTAG YES
                    <TD background=themes/images/footerBG_Top.png height=6></TD>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 150, Column 46: character data is not allowed here
                    <TD background=themes/images/footerBG_Top.png height=6></TD>

    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 150, Column 76: end tag for element "TD" which is not open
                    <TD background=themes/images/footerBG_Top.png height=6></TD>

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

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

  • Warning Line 151, Column 46: NET-enabling start-tag requires SHORTTAG YES
                    <TD width=6 background=themes/images/footerBG_TL.png 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 151, Column 54: character data is not allowed here
                    <TD width=6 background=themes/images/footerBG_TL.png 

    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 152, Column 30: end tag for element "TD" which is not open
                    height=6></TD></TR>

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

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

  • Warning Line 154, Column 46: NET-enabling start-tag requires SHORTTAG YES
                    <TD width=6 background=themes/images/footerBG_Right.png></TD>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 154, Column 54: character data is not allowed here
                    <TD width=6 background=themes/images/footerBG_Right.png></TD>

    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 154, Column 77: end tag for element "TD" which is not open
                    <TD width=6 background=themes/images/footerBG_Right.png></TD>

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

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

  • Error Line 155, Column 40: value of attribute "ALIGN" cannot be "MIDDLE"; must be one of "LEFT", "CENTER", "RIGHT", "JUSTIFY", "CHAR"
                    <TD class=center align=middle bgColor=#737373><BR><A 

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 155, Column 55: an attribute value must be a literal unless it contains only name characters
                    <TD class=center align=middle bgColor=#737373><BR><A 

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

  • Error Line 156, Column 64: an attribute value must be a literal unless it contains only name characters
    …             href="default.aspx">صفحه نخست</A><font color=#FF6600> |</font> <A 

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

  • Error Line 158, Column 40: an attribute value must be a literal unless it contains only name characters
                      رایج </A><font color=#FF6600>|</font>  <A 

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

  • Error Line 160, Column 43: an attribute value must be a literal unless it contains only name characters
                      با شرکت </A><font color=#FF6600>| </font><A 

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

  • Error Line 164, Column 29: there is no attribute "HEIGHT"
                      <P height="15"><font color=#FFffff>Copyright 2009 All right r…

    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 164, Column 46: an attribute value must be a literal unless it contains only name characters
    …           <P height="15"><font color=#FFffff>Copyright 2009 All right reserve…

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

  • Error Line 164, Column 90: end tag for "FONT" omitted, but its declaration does not permit this
    …       <P height="15"><font color=#FFffff>Copyright 2009 All right reserved</P>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 164, Column 34: start tag was here
                      <P height="15"><font color=#FFffff>Copyright 2009 All right r…
  • Error Line 165, Column 71: end tag for element "FONT" which is not open
                      <P height="15">Powered By IT Department Of TSE</font></P></TD>

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

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

  • Warning Line 166, Column 46: NET-enabling start-tag requires SHORTTAG YES
    …              <TD width=6 background=themes/images/footerBG_Left.png></TD></TR>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 166, Column 54: character data is not allowed here
    …              <TD width=6 background=themes/images/footerBG_Left.png></TD></TR>

    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 166, Column 76: end tag for element "TD" which is not open
    …              <TD width=6 background=themes/images/footerBG_Left.png></TD></TR>

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

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

  • Warning Line 168, Column 46: NET-enabling start-tag requires SHORTTAG YES
                    <TD width=6 background=themes/images/footerBG_BR.png 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 168, Column 54: character data is not allowed here
                    <TD width=6 background=themes/images/footerBG_BR.png 

    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 169, Column 30: end tag for element "TD" which is not open
                    height=6></TD>

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

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

  • Warning Line 170, Column 38: NET-enabling start-tag requires SHORTTAG YES
                    <TD background=themes/images/footerBG_Bottom.png height=6></TD>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 170, Column 46: character data is not allowed here
                    <TD background=themes/images/footerBG_Bottom.png height=6></TD>

    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 170, Column 79: end tag for element "TD" which is not open
                    <TD background=themes/images/footerBG_Bottom.png height=6></TD>

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

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

  • Warning Line 171, Column 46: NET-enabling start-tag requires SHORTTAG YES
                    <TD width=6 background=themes/images/footerBG_BL.png 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 171, Column 54: character data is not allowed here
                    <TD width=6 background=themes/images/footerBG_BL.png 

    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 172, Column 30: end tag for element "TD" which is not open
                    height=6></TD></TR></TBODY></TABLE>

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

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

  • Error Line 175, Column 21: end tag for element "TD" which is not open
                </P></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE></DIV></BOD…

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

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

  • Error Line 175, Column 26: end tag for element "TR" which is not open
                </P></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE></DIV></BOD…

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

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

  • Error Line 175, Column 34: end tag for element "TBODY" which is not open
                </P></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE></DIV></BOD…

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

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

  • Error Line 175, Column 42: end tag for element "TABLE" which is not open
    …         </P></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE></DIV></BODY>…

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

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

  • Error Line 175, Column 47: end tag for element "TD" which is not open
    …    </P></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE></DIV></BODY></HTM…

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

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

  • Error Line 175, Column 52: end tag for element "TR" which is not open
    …   </P></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE></DIV></BODY></HTML>

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

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

  • Error Line 175, Column 60: end tag for element "TBODY" which is not open
    …   </P></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE></DIV></BODY></HTML>

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

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

  • Error Line 175, Column 68: end tag for element "TABLE" which is not open
    …   </P></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE></DIV></BODY></HTML>

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

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

Visitor Analysis

Daily Visitor
  • 6.883 visits
Daily Visitor