Sunday, September 08, 2013 - يکشنبه ۱۷ شهريور ۱۳۹۲ | صفحه اصلی | معرفی بنیاد | پست الکترونيک | معرفی و راهنمای خدمات بنیاد | ارتباط با ریاست عالی بنیاد |  جستجو ...

isaar.ir
  • Domain Name
    isaar.ir
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #62218
  • Page Size
    69.6 KB
  • Ip Address
    77.237.95.143
  • Heading
    H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    23 GIF, 4 JPG, 27 PNG

Website Meta Analysis

  • Title
    پورتال اطلاع رسانی بنیاد شهید و امور ایثارگران
  • Meta Keyword
  • Meta Description
      Sunday, September 08, 2013 - يکشنبه ۱۷ شهريور ۱۳۹۲ | صفحه اصلی | معرفی بنیاد | پست الکترونيک | معرفی و راهنمای خدمات بنیاد | ارتباط با ریاست عالی بنیاد |  جستجو ***** اطلاعیه مهم : مهلت اعتبار کارت شناسایی ایثارگران تاریخ 30/10/1392 تمدید ...

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    77.237.95.143
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from isaar.ir.

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • expires: Sun, 08 Sep 2013 00:22:51 GMT
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • date: Sun, 08 Sep 2013 00:22:52 GMT
  • content-length: 80525
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% This is the IRNIC Whois server v1.6.2.
% Available on web at http://whois.nic.ir/
% Find the terms and conditions of use on http://www.nic.ir/
%
% This server uses UTF-8 as the encoding for requests and responses.

% NOTE: This output has been filtered.

% Information related to 'isaar.ir'


domain: isaar.ir
ascii: isaar.ir
remarks: (Domain Holder) BONYAD SHAHID va OMUR ISARGARAN
remarks: (Domain Holder Address) Sq Valiasr , Taleghani AveBonyad Shahid va Omure Isargaran, Tehran, Tehran, IR
holder-c: bo194-irnic
admin-c: ap89-irnic
tech-c: bb98-irnic
nserver: ns1.isaar.ir
nserver: ns2.isaar.ir
last-updated: 2012-01-03
expire-date: 2013-01-25
source: IRNIC # Filtered

nic-hdl: bo194-irnic
org: BONYAD SHAHID va OMUR ISARGARAN
person: MAHMOOD DEHBASHI
e-mail: email
address: Sq Valiasr , Taleghani AveBonyad Shahid va Omure Isargaran, Tehran, Tehran, IR
phone: 88937908
fax-no: 88939733
source: IRNIC # Filtered

nic-hdl: ap89-irnic
person: Amir Poursoltani
e-mail: email
address: Shahrara, No. 163,, Tehran, Tehran, IR
phone: +98 21 8827 1020
fax-no: +98 21 8825 0344
source: IRNIC # Filtered

nic-hdl: bb98-irnic
person: BEHROUZ BAGHI
e-mail: email
source: IRNIC # Filtered

DNS Analysis


DNS servers
ns1.isaar.ir [77.237.95.154]
ns2.isaar.ir [77.237.95.154]


DNS Records

Answer records
isaar.ir A 77.237.95.143 3600s
isaar.ir NS  isaar.ir 3600s
isaar.ir NS  isaar.org.ir 3600s
isaar.ir NS  hostisaar1 3600s
isaar.ir SOA
server: hostisaar1
email: hostmaster
serial: 750
refresh: 900
retry: 600
expire: 3600
minimum ttl: 3600
3600s
isaar.ir MX
preference: 10
exchange: mail.isaar.ir
3600s

Authority records

Additional records
isaar.ir A 77.237.95.143 3600s
mail.isaar.ir A 77.237.95.144 3600s

IP 77.237.95.143 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 107 Errors
  • 13 Warnings
Ratio Text/Html
  • 0.5036665217818034
Message Error
  • Error Line 5, Column 7: element "HEAD" undefined
    	<HEAD><title>

    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 8, Column 58: required attribute "type" not specified
    		<script language="JavaScript" src="../Scripts/farsi.js"></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 9, Column 59: required attribute "type" not specified
    		<script language="JavaScript" src="../Scripts/Public.js"></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 10, Column 57: required attribute "type" not specified
    		<script language="JavaScript" src="../Scripts/Ajax.js"></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 11, Column 65: required attribute "type" not specified
    		<script language="JavaScript" src="../scripts/ComboSitemap.js"></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 12, Column 57: required attribute "type" not specified
    		<script language="JavaScript" src="../scripts/menu.js"></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 13, Column 61: required attribute "type" not specified
    		<script language="JavaScript" src="../scripts/Redirect.js"></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 14, Column 32: required attribute "type" not specified
    		<script language="JavaScript">

    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 32, Column 18: there is no attribute "topmargin"
    	<body topmargin="0" leftmargin="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 32, Column 33: there is no attribute "leftmargin"
    	<body topmargin="0" leftmargin="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 32, Column 36: document type does not allow element "body" here
    	<body topmargin="0" leftmargin="0">

    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 78, Column 80: cannot generate system identifier for general entity "Dynamic"
    …pan> <a href='../WebGenerator/PageView.aspx?src=408&Dynamic=0' class='topMenu'>

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

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

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

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

  • Error Line 78, Column 80: general entity "Dynamic" not defined and no default entity
    …pan> <a href='../WebGenerator/PageView.aspx?src=408&Dynamic=0' class='topMenu'>

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

  • Warning Line 78, Column 87: reference not terminated by REFC delimiter
    …pan> <a href='../WebGenerator/PageView.aspx?src=408&Dynamic=0' class='topMenu'>

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

  • Warning Line 78, Column 87: reference to external entity in attribute value
    …pan> <a href='../WebGenerator/PageView.aspx?src=408&Dynamic=0' class='topMenu'>

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

  • Error Line 78, Column 87: reference to entity "Dynamic" for which no system identifier could be generated
    …pan> <a href='../WebGenerator/PageView.aspx?src=408&Dynamic=0' class='topMenu'>

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

  • Info Line 78, Column 79: entity was defined here
    …pan> <a href='../WebGenerator/PageView.aspx?src=408&Dynamic=0' class='topMenu'>
  • Warning Line 86, Column 87: reference not terminated by REFC delimiter
    …pan> <a href='../WebGenerator/PageView.aspx?src=415&Dynamic=0' class='topMenu'>

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

  • Warning Line 86, Column 87: reference to external entity in attribute value
    …pan> <a href='../WebGenerator/PageView.aspx?src=415&Dynamic=0' class='topMenu'>

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

  • Error Line 86, Column 87: reference to entity "Dynamic" for which no system identifier could be generated
    …pan> <a href='../WebGenerator/PageView.aspx?src=415&Dynamic=0' class='topMenu'>

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

  • Info Line 78, Column 79: entity was defined here
    …pan> <a href='../WebGenerator/PageView.aspx?src=408&Dynamic=0' class='topMenu'>
  • Warning Line 90, Column 87: reference not terminated by REFC delimiter
    …pan> <a href='../WebGenerator/PageView.aspx?src=584&Dynamic=0' class='topMenu'>

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

  • Warning Line 90, Column 87: reference to external entity in attribute value
    …pan> <a href='../WebGenerator/PageView.aspx?src=584&Dynamic=0' class='topMenu'>

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

  • Error Line 90, Column 87: reference to entity "Dynamic" for which no system identifier could be generated
    …pan> <a href='../WebGenerator/PageView.aspx?src=584&Dynamic=0' class='topMenu'>

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

  • Info Line 78, Column 79: entity was defined here
    …pan> <a href='../WebGenerator/PageView.aspx?src=408&Dynamic=0' class='topMenu'>
  • Warning Line 94, Column 87: reference not terminated by REFC delimiter
    …pan> <a href='../WebGenerator/PageView.aspx?src=443&Dynamic=0' class='topMenu'>

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

  • Warning Line 94, Column 87: reference to external entity in attribute value
    …pan> <a href='../WebGenerator/PageView.aspx?src=443&Dynamic=0' class='topMenu'>

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

  • Error Line 94, Column 87: reference to entity "Dynamic" for which no system identifier could be generated
    …pan> <a href='../WebGenerator/PageView.aspx?src=443&Dynamic=0' class='topMenu'>

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

  • Info Line 78, Column 79: entity was defined here
    …pan> <a href='../WebGenerator/PageView.aspx?src=408&Dynamic=0' class='topMenu'>
  • Error Line 117, Column 15: there is no attribute "border"
    <input border="0" src="../images/skin/search.gif" style="cursor:hand" name="sub…

    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 117, Column 98: end tag for "input" omitted, but OMITTAG NO was specified
    …src="../images/skin/search.gif" style="cursor:hand" name="submit" type="image">

    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
    <input border="0" src="../images/skin/search.gif" style="cursor:hand" name="sub…
  • Error Line 120, Column 59: end tag for "input" omitted, but OMITTAG NO was specified
    <input name="_txtSearch" type="text" class="inputGeneral">

    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 120, Column 1: start tag was here
    <input name="_txtSearch" type="text" class="inputGeneral">
  • Error Line 131, Column 78: there is no attribute "scrollamount"
    …                <marquee scrollamount="3" direction="right">در اجرای قانون حما…

    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 131, Column 92: there is no attribute "direction"
    …  <marquee scrollamount="3" direction="right">در اجرای قانون حمایت از آزادگان …

    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 131, Column 99: element "marquee" undefined
    …uee scrollamount="3" direction="right">در اجرای قانون حمایت از آزادگان مورخ 13…

    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 132, Column 61: end tag for "marquee" omitted, but OMITTAG NO was specified
                                                            </tr>

    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 131, Column 56: start tag was here
    <marquee scrollamount="3" direction="rig…
  • Error Line 132, Column 61: end tag for "td" omitted, but OMITTAG NO was specified
                                                            </tr>

    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 130, Column 61: start tag was here
    <td style="width: 650px">
  • Error Line 166, Column 104: required attribute "type" not specified
    …                       <td class="boxContentPic" style="width: 168px"><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>.

  • Warning Line 176, Column 114: character "<" is the first character of a delimiter but occurred as data
    …                                     for (i = 0; i < number_of_slideshows; i++)

    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 179, Column 114: character "<" is the first character of a delimiter but occurred as data
    …                                     for (j = 0; j < number_of_slideshows; j++)

    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 218, Column 118: character "<" is the first character of a delimiter but occurred as data
    …                                     for (i = 0; i < number_of_slideshows; i++)

    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 265, Column 157: document type does not allow element "a" here
    …ite('<a href="javascript:clickredir()"><img alt="گزارش تصویری" border="0" heig…

    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 265, Column 276: duplicate specification of attribute "border"
    …  width="168"  src="' + slideshows[0][0] + '" name="multislide" border=0></a>')

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

  • Error Line 265, Column 276: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …  width="168"  src="' + slideshows[0][0] + '" name="multislide" border=0></a>')
  • Error Line 265, Column 281: end tag for "img" omitted, but OMITTAG NO was specified
    …  width="168"  src="' + slideshows[0][0] + '" name="multislide" border=0></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 265, Column 158: start tag was here
    …te('<a href="javascript:clickredir()"><img alt="گزارش تصویری" border="0" heigh…
  • Error Line 267, Column 235: document type does not allow element "img" here
    … height="112"  width="168"  src="' + slideshows[0][0] + '" name="multislide">')

    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 267, Column 236: end tag for "img" omitted, but OMITTAG NO was specified
    … height="112"  width="168"  src="' + slideshows[0][0] + '" name="multislide">')

    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 267, Column 124: start tag was here
    …                      document.write('<img  alt="گزارش تصویری" border="0" heig…
  • Warning Line 270, Column 125: character "<" is the first character of a delimiter but occurred as data
    …                     subinc = (subinc < slideshows[maininc].length - 1) ? subi…

    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 299, Column 31: required attribute "type" not specified
    	<script language="javascript">

    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 325, Column 138: required attribute "alt" not specified
    …="USkinTop_Image1" src="../images/new.gif" height="25" width="25" border="0" />

    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 330, Column 62: character "%" is not allowed in the value of attribute "align"
    …                             <td align="10%" dir="rtl" rowspan="2" width="10%">

    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 330, Column 63: value of attribute "align" cannot be "10%"; must be one of "left", "center", "right", "justify", "char"
    …                             <td align="10%" dir="rtl" rowspan="2" width="10%">

    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 331, Column 138: required attribute "alt" not specified
    …="USkinTop_Image2" src="../images/new.gif" height="25" width="25" border="0" />

    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 392, Column 137: there is no attribute "border"
    …right: 0px solid" height="400" border="0" src="../News/NewsIframe.aspx?Cat=74&…

    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 520, Column 203: value of attribute "align" cannot be "center"; must be one of "top", "middle", "bottom", "left", "right"
    …:d27cdb6e-ae6d-11cf-96b8-444553540000" width="550" align="center" height="400">

    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 525, Column 12: there is no attribute "src"
    <embed src="/WebFiles/Tab/Flashes/Iranmap.swf" quality="high" bgcolor="#ffffff"…

    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 525, Column 56: there is no attribute "quality"
    …iles/Tab/Flashes/Iranmap.swf" quality="high" bgcolor="#ffffff" width="600" hei…

    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 525, Column 71: there is no attribute "bgcolor"
    …s/Iranmap.swf" quality="high" bgcolor="#ffffff" width="600" height="600" name=…

    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 525, Column 87: there is no attribute "width"
    …uality="high" bgcolor="#ffffff" width="600" height="600" name="mymovie" align=…

    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 525, Column 100: there is no attribute "height"
    … bgcolor="#ffffff" width="600" height="600" name="mymovie" align="center" allo…

    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 525, Column 111: there is no attribute "name"
    …ffffff" width="600" height="600" name="mymovie" align="center" allowscriptacce…

    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 525, Column 127: there is no attribute "align"
    …00" height="600" name="mymovie" align="center" allowscriptaccess="sameDomain" …

    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 525, Column 154: there is no attribute "allowscriptaccess"
    …vie" align="center" allowscriptaccess="sameDomain" type="application/x-shockwa…

    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 525, Column 172: there is no attribute "type"
    …" allowscriptaccess="sameDomain" type="application/x-shockwave-flash" pluginsp…

    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 525, Column 216: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" pluginspage="http://www.adobe.com/go/getflashplayer"…

    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 525, Column 259: element "embed" undefined
    …ve-flash" pluginspage="http://www.adobe.com/go/getflashplayer"  />    </object>

    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 645, Column 17: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                <div></a>

    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 645, Column 21: end tag for "div" omitted, but OMITTAG NO was specified
                <div></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 645, Column 13: start tag was here
                <div></a>
  • Error Line 646, Column 247: end tag for "a" omitted, but OMITTAG NO was specified
    …itle="شرکت ذخیره شاهد" href="http://www.zakhireh.co.ir/" target="_blank"></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 646, Column 148: start tag was here
    …t=1" target="_self">هفته نامه حیات</a><a class="textlink" title="شرکت ذخیره شا…
  • Error Line 647, Column 18: end tag for "td" omitted, but OMITTAG NO was specified
                </div>

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

  • Info Line 644, Column 13: start tag was here
                <td><a class="textlink" title="شرکت ذخیره شاهد" href="http://www.za…
  • Error Line 647, Column 18: end tag for "tr" omitted, but OMITTAG NO was specified
                </div>

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

  • Info Line 643, Column 9: start tag was here
            <tr>
  • Error Line 647, Column 18: end tag for "tbody" omitted, but OMITTAG NO was specified
                </div>

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

  • Info Line 635, Column 5: start tag was here
        <tbody>
  • Error Line 647, Column 18: end tag for "table" omitted, but OMITTAG NO was specified
                </div>

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

  • Info Line 634, Column 4: start tag was here
    			<table style="text-align: center" border="0" cellspacing="0" cellpadding="0">
  • Error Line 648, Column 16: end tag for element "a" which is not open
                </a></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 648, Column 21: end tag for "div" omitted, but OMITTAG NO was specified
                </a></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 390, Column 8: start tag was here
    	</div><div id="_TabMain1_body">
  • Error Line 648, Column 21: end tag for "div" omitted, but OMITTAG NO was specified
                </a></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 387, Column 17: start tag was here
                    <div class="ajax__tab_xp" id="_TabMain1">
  • Error Line 650, Column 17: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                <div></a><a class="textlink" title="نشریه شاهد یاران" href="http://…

    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 650, Column 21: end tag for "div" omitted, but OMITTAG NO was specified
                <div></a><a class="textlink" title="نشریه شاهد یاران" href="http://…

    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 650, Column 13: start tag was here
                <div></a><a class="textlink" title="نشریه شاهد یاران" href="http://…
  • Error Line 650, Column 285: end tag for "a" omitted, but OMITTAG NO was specified
    …ستان خاتم الانبیا" href="http://www.khatamhospital.com/" target="_blank"></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 650, Column 175: start tag was here
    …1" target="_self">نشریه شاهد یاران</a><a class="textlink" title="بیمارستان خات…
  • Error Line 650, Column 285: end tag for "td" omitted, but OMITTAG NO was specified
    …ستان خاتم الانبیا" href="http://www.khatamhospital.com/" target="_blank"></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 649, Column 13: start tag was here
                <td><a class="textlink" title="بیمارستان خاتم الانبیا" href="http:/…
  • Error Line 650, Column 285: end tag for "tr" omitted, but OMITTAG NO was specified
    …ستان خاتم الانبیا" href="http://www.khatamhospital.com/" target="_blank"></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 385, Column 9: start tag was here
            <tr>
  • Error Line 650, Column 285: end tag for "table" omitted, but OMITTAG NO was specified
    …ستان خاتم الانبیا" href="http://www.khatamhospital.com/" target="_blank"></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 373, Column 5: start tag was here
        <table border="0" cellpadding="0" style="border-collapse: collapse" width="…
  • Error Line 650, Column 285: end tag for "form" omitted, but OMITTAG NO was specified
    …ستان خاتم الانبیا" href="http://www.khatamhospital.com/" target="_blank"></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 356, Column 1: start tag was here
    <form name="Form1" method="post" action="index.aspx" id="Form1">
  • Error Line 651, Column 16: end tag for element "a" which is not open
                </a></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 653, Column 17: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                <div></a><a class="textlink" title="نشریه خط زندگی" href="../WebGen…

    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 653, Column 21: end tag for "div" omitted, but OMITTAG NO was specified
                <div></a><a class="textlink" title="نشریه خط زندگی" href="../WebGen…

    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 653, Column 13: start tag was here
                <div></a><a class="textlink" title="نشریه خط زندگی" href="../WebGen…
  • Error Line 653, Column 261: end tag for element "div" which is not open
    …e="بیمارستان ساسان" href="http://www.sasanhospital.com/" target="_blank"></div>

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

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

  • Error Line 659, Column 258: end tag for "a" omitted, but OMITTAG NO was specified
    …itle="شرکت ذخیره شاهد" href="http://www.zakhireh.co.ir/" target="_blank"></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 659, Column 159: start tag was here
    …;dept=1" target="_self">نشریه افضل</a><a class="textlink" title="شرکت ذخیره شا…
  • Error Line 660, Column 16: end tag for element "a" which is not open
                </a></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 749, Column 8: end tag for element "div" which is not open
    		</div><div id="_TabMain1_ctl05" style="display:none;">

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

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

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

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

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

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

  • Error Line 808, Column 12: end tag for "tbody" 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 152, Column 17: start tag was here
                    <tbody>
  • Error Line 810, Column 118: end tag for "img" omitted, but OMITTAG NO was specified
    …د سایت' src='../WebStat/StatCounter.aspx?StatID=T141&amp;img=pagestat.gif'></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 810, Column 9: start tag was here
            <img border='0' alt='آمار بازدید سایت' src='../WebStat/StatCounter.aspx…
  • Error Line 839, Column 7: end tag for element "form" which is not open
    </form>

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

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

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

  • Error Line 857, 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 916, Column 79: there is no attribute "Name"
    … style="text-align: right"><form Name="PrintForm" method="post" target="_blank…

    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 916, Column 153: there is no attribute "ID"
    …intForm" method="post" target="_blank" action="../Print/Print.aspx" ID="Form2">

    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 917, Column 43: there is no attribute "ID"
    	<input name="PrintHtml" type="hidden" ID="Hidden1">

    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 917, Column 53: end tag for "input" omitted, but OMITTAG NO was specified
    	<input name="PrintHtml" type="hidden" ID="Hidden1">

    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 917, Column 2: start tag was here
    	<input name="PrintHtml" type="hidden" ID="Hidden1">
  • Error Line 930, Column 29: end tag for element "td" which is not open
                            </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 931, Column 44: document type does not allow element "td" here
                            <td class="sideBar">

    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 932, Column 36: ID "table3" already defined
                            <table id="table3" style="border-collapse: collapse" ce…

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

  • Info Line 155, Column 36: ID "table3" first defined here
                            <table id="table3" style="border-collapse: collapse" ce…
  • Error Line 1001, Column 49: end tag for "td" omitted, but OMITTAG NO was specified
                                                </tr>

    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 987, Column 49: start tag was here
    <td class="boxContent" valign="top"><img…
  • Error Line 1017, Column 79: syntax of attribute value does not conform to declared value
    …                                         <option selected="" value=""></option>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 1017, Column 79: value of attribute "selected" cannot be ""; must be one of "selected"
    …                                         <option selected="" value=""></option>

    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 1049, Column 48: ID "table2" already defined
    …                           <table id="table2" style="border-collapse: collapse…

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

  • Info Line 151, Column 24: ID "table2" first defined here
                <table id="table2" style="border-collapse: collapse" cellpadding="0…
  • Error Line 1066, Column 62: character "%" is not allowed in the value of attribute "align"
    …                             <td align="10%" dir="rtl" rowspan="2" width="30%">

    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 1066, Column 63: value of attribute "align" cannot be "10%"; must be one of "left", "center", "right", "justify", "char"
    …                             <td align="10%" dir="rtl" rowspan="2" width="30%">

    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 1067, Column 134: required attribute "alt" not specified
    …g id="USkinDown_Image4" src="../images/bookapply.gif" height="40" border="0" />

    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 1080, Column 48: ID "table3" already defined
    …                           <table id="table3" style="border-collapse: collapse…

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

  • Info Line 155, Column 36: ID "table3" first defined here
                            <table id="table3" style="border-collapse: collapse" ce…
  • Error Line 1109, Column 25: end tag for element "tr" which is not open
                        </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.

  • Error Line 1110, Column 24: document type does not allow element "tr" here; assuming missing "table" start-tag
                        <tr>
  • Error Line 1112, Column 100: end tag for element "div" which is not open
    … این سایت محفوظ و متعلق به&nbsp;بنیاد شهید و امور ایثارگران&nbsp;می باشد.</div>

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

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

  • Error Line 1115, Column 24: end tag for element "tbody" which is not open
                    </tbody>

    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 1117, Column 17: end tag for element "td" which is not open
                </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 1118, Column 13: end tag for element "tr" which is not open
            </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.

  • Error Line 1119, Column 12: end tag for element "tbody" which is not open
        </tbody>

    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 1120, Column 8: end tag for element "table" which is not open
    </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 1121, Column 62: required attribute "type" not specified
    <script language="javascript" src="../Scripts/AjaxLoading.js"></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 1123, Column 7: end tag for "html" which is not finished
    </html> 

    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 1126, Column 27: document type does not allow element "div" here
    <div style="display: none"><h1><a Style="color:none"  target="_blank" href="htt…

    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 1126, Column 41: there is no attribute "Style"
    …iv style="display: none"><h1><a Style="color:none"  target="_blank" href="http…

    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.

Visitor Analysis

Daily Visitor
  • 2.450 visits