זימון תורים, בדיקות מעבדה, חיפוש רופאים, מרפאות ובתי מרקחת של שירותי בריאות כללית, כללית סמייל, כללית מושלם ועוד מגוון של שירותים מתקדמים ומידע באתר קופת חולים כללית ...

clalit.co.il
  • Domain Name
    clalit.co.il
  • Favicon
  • Google Page Rank
    7
  • Alexa Rank
    #57349
  • Page Size
    160.7 KB
  • Ip Address
    194.114.146.40
  • Heading
    H1: 0, H2: 4, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    37 GIF, 16 JPG, 1 PNG

Website Meta Analysis

  • Title
    אתר קופ"ח כללית | אתר שירותי בריאות כללית
  • Meta Keyword
    כללית, שירותי בריאות כללית, קופת חולים כללית, קופ
  • Meta Description
    זימון תורים, בדיקות מעבדה, חיפוש רופאים, מרפאות ובתי מרקחת של שירותי בריאות כללית, כללית סמייל, כללית מושלם ועוד מגוון של שירותים מתקדמים ומידע באתר קופת חולים כללית

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    194.114.146.40
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • connection: close
  • date: Sun, 18 Aug 2013 16:38:51 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • x-aspnet-version: 1.1.4322
  • cache-control: private
  • content-type: text/html; charset=utf-8
  • vary: Accept-Encoding
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

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

query: clalit.co.il

reg-name: clalit
domain: clalit.co.il

descr: Kupat Holim Clalit
descr: 115 Arlozorov st.
descr: Tel Aviv
descr: 62098
descr: Israel
phone: +972 3 6945701
fax-no: +972 3 6912794
e-mail: rafhi AT clalit.org.il
admin-c: II-RH9000-IL
tech-c: II-DR4105-IL
zone-c: II-DR4105-IL
nserver: pdns.goldenlines.net.il
nserver: sdns.goldenlines.net.il
validity: N/A
status: Transfer Locked
changed: registrar AT ns.il 19970417 (Assigned)
changed: domain-registrar AT isoc.org.il 20011227 (Changed)
changed: domain-registrar AT isoc.org.il 20030910 (Changed)

person: Rafi Hirsh
address: clalit health services
address: 115 Arlozorov st.
address: Tel Aviv
address: 62098
address: Israel
phone: +972 3 6945701
fax-no: +972 3 6912794
e-mail: rafihi AT clalit.org.il
nic-hdl: II-RH9000-IL
changed: domain-registrar AT isoc.org.il 20030910
changed: domain-registrar AT isoc.org.il 20040922

person: DNS Registration 012 Golden Lines
address: 012 Golden Lines LTD
address: 25 Hasivim St.
address: Petach Tikva Israel
address: 49170
address: Israel
phone: +972 3 9539063
fax-no: +972 3 9274608
e-mail: dns AT 012.net.il
nic-hdl: II-DR4105-IL
changed: domain-registrar AT isoc.org.il 20010902
changed: domain-registrar AT isoc.org.il 20030227
changed: domain-registrar AT isoc.org.il 20030227
changed: domain-registrar AT isoc.org.il 20040425
changed: domain-registrar AT isoc.org.il 20041223
changed: domain-registrar AT isoc.org.il 20041227
changed: domain-registrar AT isoc.org.il 20060130
changed: domain-registrar AT isoc.org.il 20060827
changed: domain-registrar AT isoc.org.il 20080731

registrar name: Israel Internet Association ISOC-IL
registrar info: www.isoc.org.il

% Rights to the data above are restricted by copyright.

DNS Analysis


DNS servers
sdns.goldenlines.net.il [212.117.128.6]
pdns.goldenlines.net.il [212.117.129.3]


DNS Records

Answer records
clalit.co.il SOA
server: pdns.goldenlines.net.il
email: postmaster@goldenlines.net.il
serial: 2012090801
refresh: 28800
retry: 3600
expire: 604800
minimum ttl: 3600
300s
clalit.co.il NS  pdns.goldenlines.net.il 300s
clalit.co.il NS  sdns.goldenlines.net.il 300s
clalit.co.il A 194.114.146.40 300s
clalit.co.il MX
preference: 0
exchange: mail.clalit.co.il
300s
clalit.co.il MX
preference: 100
exchange: etrn.012.net.il
300s

Authority records

Additional records
pdns.goldenlines.net.il A 212.117.129.3 3600s
sdns.goldenlines.net.il A 212.117.128.6 3600s
mail.clalit.co.il A 194.114.146.48 300s
etrn.012.net.il A 80.179.52.250 600s

IP 194.114.146.40 Analysis

  • Country Code
    PL
  • Country Code3
    POL
  • Country Name
    Poland
  • City
    EU
  • Continent Code
    52° North
  • Latitude
    20.
  • Longitude
  • No whois ip data for 194.114.146.40

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 106 Errors
  • 36 Warnings
Ratio Text/Html
  • 0.6149965966549981
Message Error
  • Error Line 5, Column 82: character "ח" not allowed in attribute specification list
    …ONTENT="כללית, שירותי בריאות כללית, קופת חולים כללית, קופ"ח כללית, קופח כללית">
  • Error Line 5, Column 84: character data is not allowed here
    …ONTENT="כללית, שירותי בריאות כללית, קופת חולים כללית, קופ"ח כללית, קופח כללית">

    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 8, Column 257: document type does not allow element "SPAN" here
    … mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: HE">

    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 54: NET-enabling start-tag requires SHORTTAG YES
    <link rel="canonical" href="http://www.clalit.co.il/"/>

    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.

  • Warning Line 26, Column 107: cannot generate system identifier for general entity "NRNODEGUID"
    …tes/NeoHomepage.aspx?NRMODE=Published&NRNODEGUID=%7bDAA1778D-E28B-42B7-B56C-CF…

    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 26, Column 107: general entity "NRNODEGUID" not defined and no default entity
    …tes/NeoHomepage.aspx?NRMODE=Published&NRNODEGUID=%7bDAA1778D-E28B-42B7-B56C-CF…

    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.

  • Error Line 26, Column 117: reference to entity "NRNODEGUID" for which no system identifier could be generated
    …epage.aspx?NRMODE=Published&NRNODEGUID=%7bDAA1778D-E28B-42B7-B56C-CF05E1955DEB…

    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 26, Column 106: entity was defined here
    …ates/NeoHomepage.aspx?NRMODE=Published&NRNODEGUID=%7bDAA1778D-E28B-42B7-B56C-C…
  • Warning Line 26, Column 161: cannot generate system identifier for general entity "NRORIGINALURL"
    …A1778D-E28B-42B7-B56C-CF05E1955DEB%7d&NRORIGINALURL=%2fhe-il&NRCACHEHINT=Guest…

    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 26, Column 161: general entity "NRORIGINALURL" not defined and no default entity
    …A1778D-E28B-42B7-B56C-CF05E1955DEB%7d&NRORIGINALURL=%2fhe-il&NRCACHEHINT=Guest…

    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.

  • Error Line 26, Column 174: reference to entity "NRORIGINALURL" for which no system identifier could be generated
    …1778D-E28B-42B7-B56C-CF05E1955DEB%7d&NRORIGINALURL=%2fhe-il&NRCACHEHINT=Guest">

    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 26, Column 160: entity was defined here
    …AA1778D-E28B-42B7-B56C-CF05E1955DEB%7d&NRORIGINALURL=%2fhe-il&NRCACHEHINT=Gues…
  • Warning Line 26, Column 184: cannot generate system identifier for general entity "NRCACHEHINT"
    …1778D-E28B-42B7-B56C-CF05E1955DEB%7d&NRORIGINALURL=%2fhe-il&NRCACHEHINT=Guest">

    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 26, Column 184: general entity "NRCACHEHINT" not defined and no default entity
    …1778D-E28B-42B7-B56C-CF05E1955DEB%7d&NRORIGINALURL=%2fhe-il&NRCACHEHINT=Guest">

    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.

  • Error Line 26, Column 195: reference to entity "NRCACHEHINT" for which no system identifier could be generated
    …1778D-E28B-42B7-B56C-CF05E1955DEB%7d&NRORIGINALURL=%2fhe-il&NRCACHEHINT=Guest">

    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 26, Column 183: entity was defined here
    …1778D-E28B-42B7-B56C-CF05E1955DEB%7d&NRORIGINALURL=%2fhe-il&NRCACHEHINT=Guest">
  • Error Line 30, Column 91: "ENDIF" is not a reserved name
    …INK href="/ClalitCMS/css/neo.css" rel="stylesheet" type="text/css"><![endif]-->
  • Error Line 30, Column 96: character data is not allowed here
    …INK href="/ClalitCMS/css/neo.css" rel="stylesheet" type="text/css"><![endif]-->

    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 33, Column 16: there is no attribute "PROPERTY"
    <meta property="fb:page_id" content="256106150692">

    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 51, Column 52: NET-enabling start-tag requires SHORTTAG YES
    <input type="hidden" name="__EVENTTARGET" value="" />

    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 51, Column 52: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    <input type="hidden" name="__EVENTTARGET" value="" />

    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 51, Column 53: character data is not allowed here
    <input type="hidden" name="__EVENTTARGET" value="" />

    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.
  • Warning Line 52, Column 54: NET-enabling start-tag requires SHORTTAG YES
    <input type="hidden" name="__EVENTARGUMENT" value="" />

    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 52, Column 54: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    <input type="hidden" name="__EVENTARGUMENT" value="" />

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

  • Warning Line 53, Column 95: NET-enabling start-tag requires SHORTTAG YES
    …en" name="__VIEWSTATE_KEY" value="VIEWSTATE_128.30.52.71_634977608210792505" />

    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 53, Column 95: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    …en" name="__VIEWSTATE_KEY" value="VIEWSTATE_128.30.52.71_634977608210792505" />

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

  • Warning Line 54, Column 50: NET-enabling start-tag requires SHORTTAG YES
    <input type="hidden" name="__VIEWSTATE" value="" />

    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 54, Column 50: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    <input type="hidden" name="__VIEWSTATE" value="" />

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

  • Warning Line 55, Column 50: NET-enabling start-tag requires SHORTTAG YES
    <input type="hidden" name="__VIEWSTATE" value="" />

    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 55, Column 50: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    <input type="hidden" name="__VIEWSTATE" value="" />

    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 56, Column 18: there is no attribute "LANGUAGE"
    <script language="javascript" type="text/javascript">

    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 85, Column 11: element "CENTER" undefined
    			<center>

    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 97, Column 29: there is no attribute "WIDTH"
    		<td vAlign="bottom" width="210"><table cellpadding="2" cellspacing="2" border…

    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 97, Column 250: there is no attribute "TARGET"
    …f="http://www.clalit.co.il/ar" target="">عربي</a></td><td>|</td><td align="cen…

    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 100, Column 164: there is no attribute "BORDER"
    …129B6F6E/19319/logo.gif" id="Header1_imgLogo" border="0" alt="logo" /></a></td>

    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 100, Column 179: NET-enabling start-tag requires SHORTTAG YES
    …129B6F6E/19319/logo.gif" id="Header1_imgLogo" border="0" alt="logo" /></a></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.

  • Warning Line 109, Column 230: NET-enabling start-tag requires SHORTTAG YES
    …8/Moshlam_btn.gif" id="Header1_imgMushlam" border="0" alt="mushlam" /></a></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 111, Column 328: required attribute "ALT" not specified
    …itCMS/images/neo/TopmenuSeparator.gif"></td><td align="center"><a onClick="_ga…

    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 111, Column 572: required attribute "ALT" not specified
    …itCMS/images/neo/TopmenuSeparator.gif"></td><td align="center"><a onClick="_ga…

    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 111, Column 819: required attribute "ALT" not specified
    …itCMS/images/neo/TopmenuSeparator.gif"></td><td align="center"><a  href="http:…

    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 111, Column 974: required attribute "ALT" not specified
    …itCMS/images/neo/TopmenuSeparator.gif"></td><td align="center"><a  href="/HE-I…

    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 111, Column 1127: required attribute "ALT" not specified
    …itCMS/images/neo/TopmenuSeparator.gif"></td><td align="center"><a onClick="_ga…

    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 111, Column 1373: required attribute "ALT" not specified
    …itCMS/images/neo/TopmenuSeparator.gif"></td><td align="center"><a onClick="_ga…

    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 112, Column 507: required attribute "ALT" not specified
    …mages/neo/ServicesSearchSeparator.gif"></td><td align="center"><a  href="http:…

    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 112, Column 696: required attribute "ALT" not specified
    …mages/neo/ServicesSearchSeparator.gif"></td><td align="center"><a onClick="_ga…

    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 112, Column 978: required attribute "ALT" not specified
    …mages/neo/ServicesSearchSeparator.gif"></td><td align="center"><a onClick="_ga…

    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 112, Column 1250: required attribute "ALT" not specified
    …mages/neo/ServicesSearchSeparator.gif"></td><td align="center"><a onClick="_ga…

    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 112, Column 1537: required attribute "ALT" not specified
    …mages/neo/ServicesSearchSeparator.gif"></td><td align="center"><a onClick="_ga…

    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 122, Column 218: there is no attribute "BORDER"
    …B3-4D20-4504-A6CF-22F0AB7128DF/14780/Search_btn.gif" alt="" border="0" /></div>

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

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

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

  • Warning Line 122, Column 222: NET-enabling start-tag requires SHORTTAG YES
    …B3-4D20-4504-A6CF-22F0AB7128DF/14780/Search_btn.gif" alt="" border="0" /></div>

    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.

  • Warning Line 123, Column 159: NET-enabling start-tag requires SHORTTAG YES
    …ader1_Search1_txtKeyword" class="neoSearchKeyword" style="height:13px" /></div>

    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.

  • Warning Line 127, Column 269: NET-enabling start-tag requires SHORTTAG YES
    …B6D1E68947/15433/Grab1732700.png" id="Header1_imgMoked" border="0" /></a></div>

    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 127, Column 269: required attribute "ALT" not specified
    …B6D1E68947/15433/Grab1732700.png" id="Header1_imgMoked" border="0" /></a></div>

    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 133, Column 8: required attribute "TYPE" not specified
    <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 209, Column 179: "VIEWASTEXT" is not a member of a group specified for any attribute
    …dth=329 height=158 title="" viewastext><P></P><param name="quality" value="hig…
  • Error Line 211, Column 9: end tag for element "PARAM" which is not open
    	</param><param name="wmode" value="transparent">

    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 213, Column 9: end tag for element "PARAM" which is not open
    	</param><param name="bgcolor" value="Transparent">

    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 215, Column 9: end tag for element "PARAM" which is not open
    	</param><param name="movie" value="/ClalitCMS/AdImages/capitation_PR_329x158.s…

    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 217, Column 9: end tag for element "PARAM" which is not open
    	</param><param name="AdId" value="1172">

    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 219, Column 9: end tag for element "PARAM" which is not open
    	</param></OBJECT>

    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 223, Column 85: required attribute "ALT" not specified
    …es/DAA1778D-E28B-42B7-B56C-CF05E1955DEB/14817/btn_Online_Green2.gif"></a></DIV>

    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 234, Column 71: there is no attribute "HEIGHT"
    <table cellspacing="0" cellpadding="0" width="100%" border="0" height="100%">

    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 311, Column 127: required attribute "ALT" not specified
    … src="../../Images/NEO/arrow_left.gif"><SPAN id="buttonTextIWantDummy">רוצה יו…

    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 382, Column 122: required attribute "ALT" not specified
    …"../../Images/NEO/arrow_left_blue.gif"><SPAN id="buttonTextIWant">רוצה יותר</S…

    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 472, Column 92: required attribute "ALT" not specified
    …onlyres/DAA1778D-E28B-42B7-B56C-CF05E1955DEB/14801/OnlineButton.jpg"></a></DIV>

    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 556, Column 120: required attribute "ALT" not specified
    … src="../../Images/NEO/arrow_left.gif"><SPAN id="buttonTextOnline">שירותים נוס…

    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 568, Column 83: there is no attribute "ALIGN"
    …dding="0" cellspacing="0" border="0" align="center" class="MainTableContainer">

    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 574, Column 178: "VIEWASTEXT" is not a member of a group specified for any attribute
    …idth=552 height=52 title="" viewastext><P></P><param name="quality" value="hig…
  • Error Line 576, Column 11: end tag for element "PARAM" which is not open
    			</param><param name="wmode" value="transparent">

    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 578, Column 11: end tag for element "PARAM" which is not open
    			</param><param name="bgcolor" value="Transparent">

    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 580, Column 11: end tag for element "PARAM" which is not open
    			</param><param name="movie" value="/ClalitCMS/AdImages/babyZone_HP1_552x52.s…

    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 582, Column 11: end tag for element "PARAM" which is not open
    			</param><param name="AdId" value="1167">

    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 584, Column 11: end tag for element "PARAM" which is not open
    			</param></OBJECT>

    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 589, Column 178: "VIEWASTEXT" is not a member of a group specified for any attribute
    …idth=207 height=52 title="" viewastext><P></P><param name="quality" value="hig…
  • Error Line 591, Column 11: end tag for element "PARAM" which is not open
    			</param><param name="wmode" value="transparent">

    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 593, Column 11: end tag for element "PARAM" which is not open
    			</param><param name="bgcolor" value="Transparent">

    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 595, Column 11: end tag for element "PARAM" which is not open
    			</param><param name="movie" value="/ClalitCMS/AdImages/hamodis2_hp2_207x52.s…

    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 597, Column 11: end tag for element "PARAM" which is not open
    			</param><param name="AdId" value="1163">

    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 599, Column 11: end tag for element "PARAM" which is not open
    			</param></OBJECT>

    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 625, Column 175: NET-enabling start-tag requires SHORTTAG YES
    …55DEB/14804/blogs_title.gif" id="ContentCubes1_imgBlogs" border="0" /></a></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 625, Column 175: required attribute "ALT" not specified
    …55DEB/14804/blogs_title.gif" id="ContentCubes1_imgBlogs" border="0" /></a></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 699, Column 164: NET-enabling start-tag requires SHORTTAG YES
    …5DEB/14805/Guide_title.gif" id="ContentCubes1_imgGuides" border="0" /></a></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 699, Column 164: required attribute "ALT" not specified
    …5DEB/14805/Guide_title.gif" id="ContentCubes1_imgGuides" border="0" /></a></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 773, Column 162: NET-enabling start-tag requires SHORTTAG YES
    …55DEB/14814/calc_title1.gif" id="ContentCubes1_imgCalcs" border="0" /></a></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 773, Column 162: required attribute "ALT" not specified
    …55DEB/14814/calc_title1.gif" id="ContentCubes1_imgCalcs" border="0" /></a></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 863, Column 36: there is no attribute "HEIGHT"
    												<td colspan="2" height="1" bgcolor="#b3d6ef"></td>

    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 863, Column 48: there is no attribute "BGCOLOR"
    												<td colspan="2" height="1" bgcolor="#b3d6ef"></td>

    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 868, Column 370: NET-enabling start-tag requires SHORTTAG YES
    …1_imgMainArticle" border="0" alt="אוהבים לשתות? כך תעשו את זה נכון" /></a></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 885, Column 346: ID "TVBUTTON" already defined
    …טוני הכנה לבדיקות"></a></div><div id="tvButton"><a onClick="_gaq.push(['_track…

    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 885, Column 73: ID "TVBUTTON" first defined here
    …es1_ClalitTVImagesContainer"><div id="tvButton"><a onClick="_gaq.push(['_track…
  • Error Line 885, Column 586: ID "TVBUTTON" already defined
    … border="0" alt=""></a></div><div id="tvButton"><a onClick="_gaq.push(['_track…

    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 885, Column 73: ID "TVBUTTON" first defined here
    …es1_ClalitTVImagesContainer"><div id="tvButton"><a onClick="_gaq.push(['_track…
  • Error Line 891, Column 30: 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 925, Column 120: document type does not allow element "TABLE" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
    …ellspacing="0" width="100%" border="0"><tr><td><table cellpadding="0" cellspac…

    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 925, Column 285: there is no attribute "RUNAT"
    …0" width="100%" id="LinksTable" runat="server"><tr><td valign="top" width="100…

    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 925, Column 1591: required attribute "ALT" not specified
    …2C0-80E7-015EB6A95754/0/123510260.jpg"></a></td><td><img src="/ClalitCMS/image…

    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 925, Column 1665: required attribute "ALT" not specified
    …mages/transparent-pixel.gif" width="1"></td><td bgcolor="#dedfde" valign="top"…

    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 925, Column 2328: required attribute "ALT" not specified
    …','HP Bottom','main article','first')">&nbsp;<img src="/ClalitCMS/images/iconR…

    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 925, Column 2453: required attribute "ALT" not specified
    …ick="RemoveRow('Linkeradvanced1','1')"></td></tr></table></td></tr><tr><td cla…

    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 925, Column 2691: ID "LINKSTABLE" already defined
    …="0" cellspacing="0" width="100%" id="LinksTable" runat="server"><tr><td valig…

    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 925, Column 267: ID "LINKSTABLE" first defined here
    …="0" cellspacing="0" width="100%" id="LinksTable" runat="server"><tr><td valig…
  • Error Line 925, Column 4009: required attribute "ALT" not specified
    …2DD-823C-C458A196FF52/0/154959385.jpg"></a></td><td><img src="/ClalitCMS/image…

    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 925, Column 4083: required attribute "ALT" not specified
    …mages/transparent-pixel.gif" width="1"></td><td bgcolor="#dedfde" valign="top"…

    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 925, Column 4743: required attribute "ALT" not specified
    …,'HP Bottom','main article','second')">&nbsp;<img src="/ClalitCMS/images/iconR…

    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 925, Column 4868: required attribute "ALT" not specified
    …ick="RemoveRow('Linkeradvanced1','2')"></td></tr></table></td></tr><tr><td cla…

    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 925, Column 5106: ID "LINKSTABLE" already defined
    …="0" cellspacing="0" width="100%" id="LinksTable" runat="server"><tr><td valig…

    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 925, Column 267: ID "LINKSTABLE" first defined here
    …="0" cellspacing="0" width="100%" id="LinksTable" runat="server"><tr><td valig…
  • Error Line 925, Column 6295: required attribute "ALT" not specified
    …blogs.co.il/nutrition/193"><img src=""></a></td><td><img src="/ClalitCMS/image…

    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 925, Column 6369: required attribute "ALT" not specified
    …mages/transparent-pixel.gif" width="1"></td><td bgcolor="#dedfde" valign="top"…

    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 925, Column 7009: required attribute "ALT" not specified
    …','HP Bottom','main article','third')">&nbsp;<img src="/ClalitCMS/images/iconR…

    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 925, Column 7134: required attribute "ALT" not specified
    …ick="RemoveRow('Linkeradvanced1','4')"></td></tr></table></td></tr><tr><td cla…

    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 925, Column 7372: ID "LINKSTABLE" already defined
    …="0" cellspacing="0" width="100%" id="LinksTable" runat="server"><tr><td valig…

    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 925, Column 267: ID "LINKSTABLE" first defined here
    …="0" cellspacing="0" width="100%" id="LinksTable" runat="server"><tr><td valig…
  • Error Line 925, Column 8551: required attribute "ALT" not specified
    …tblogs.co.il/adiporat/145"><img src=""></a></td><td><img src="/ClalitCMS/image…

    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 925, Column 8625: required attribute "ALT" not specified
    …mages/transparent-pixel.gif" width="1"></td><td bgcolor="#dedfde" valign="top"…

    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 925, Column 9256: required attribute "ALT" not specified
    …,'HP Bottom','main article','fourth')">&nbsp;<img src="/ClalitCMS/images/iconR…

    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 925, Column 9381: required attribute "ALT" not specified
    …ick="RemoveRow('Linkeradvanced1','3')"></td></tr></table></td></tr><tr><td cla…

    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 930, Column 40: there is no attribute "BGCOLOR"
    				width="100%" align="right" bgcolor="#dedfde">

    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 939, Column 165: NET-enabling start-tag requires SHORTTAG YES
    …ext" id="Linkeradvanced1_txtDisplayName" class="LinksSmallTextAdvanced" /></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.

  • Warning Line 946, Column 175: NET-enabling start-tag requires SHORTTAG YES
    … id="Linkeradvanced1_txtLink" class="LinksSmallTextAdvanced" dir="ltr" />&nbsp;

    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 956, Column 171: required attribute "ROWS" not specified
    …advanced1_txtPreview" class="LinksSmallTextAdvanced" dir="ltr"></textarea></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 956, Column 171: required attribute "COLS" not specified
    …advanced1_txtPreview" class="LinksSmallTextAdvanced" dir="ltr"></textarea></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 963, Column 171: NET-enabling start-tag requires SHORTTAG YES
    …e="text" id="Linkeradvanced1_txtToolTip" class="LinksSmallTextAdvanced" /></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.

  • Warning Line 981, Column 129: NET-enabling start-tag requires SHORTTAG YES
    …nkeradvanced1:txtWinWidth" type="text" id="Linkeradvanced1_txtWinWidth" /></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.

  • Warning Line 988, Column 131: NET-enabling start-tag requires SHORTTAG YES
    …eradvanced1:txtWinHeight" type="text" id="Linkeradvanced1_txtWinHeight" /></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.

  • Warning Line 1001, Column 128: NET-enabling start-tag requires SHORTTAG YES
    …="text" id="Linkeradvanced1_txtGA_Category" class="LinksSmallTextBasic" /></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.

  • Warning Line 1010, Column 124: NET-enabling start-tag requires SHORTTAG YES
    …pe="text" id="Linkeradvanced1_txtGA_Action" class="LinksSmallTextBasic" /></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.

  • Warning Line 1019, Column 122: NET-enabling start-tag requires SHORTTAG YES
    …ype="text" id="Linkeradvanced1_txtGA_Label" class="LinksSmallTextBasic" /></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.

  • Warning Line 1029, Column 120: NET-enabling start-tag requires SHORTTAG YES
    …type="text" id="Linkeradvanced1_txtGuid" class="LinksSmallTextAdvanced" /></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.

  • Warning Line 1032, Column 124: NET-enabling start-tag requires SHORTTAG YES
    …pe="text" id="Linkeradvanced1_txtNodeID" class="LinksSmallTextAdvanced" /></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.

  • Warning Line 1043, Column 120: NET-enabling start-tag requires SHORTTAG YES
    …ids" type="text" id="Linkeradvanced1_txtSelectedGuids" style="DISPLAY: none" />

    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.

  • Warning Line 1044, Column 120: NET-enabling start-tag requires SHORTTAG YES
    …Arr" type="text" id="Linkeradvanced1_txtLinksOrderArr" style="DISPLAY: none" />

    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.

  • Warning Line 1045, Column 143: NET-enabling start-tag requires SHORTTAG YES
    …" value="" id="Linkeradvanced1_btnUpdateSelectedLinks" style="DISPLAY: none" />

    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.

  • Warning Line 1046, Column 145: NET-enabling start-tag requires SHORTTAG YES
    … value="" id="Linkeradvanced1_btnChangeLinksSortOrder" style="DISPLAY: none" />

    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 1047, Column 8: required attribute "TYPE" not specified
    <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 1307, Column 183: NET-enabling start-tag requires SHORTTAG YES
    …-B56C-CF05E1955DEB/14806/forumsTitle.jpg" id="imgForums" border="0" /></a></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 1307, Column 183: required attribute "ALT" not specified
    …-B56C-CF05E1955DEB/14806/forumsTitle.jpg" id="imgForums" border="0" /></a></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 1314, Column 188: "VIEWASTEXT" is not a member of a group specified for any attribute
    …dth=193 height=197 title="" viewastext><P></P><param name="quality" value="hig…
  • Error Line 1316, Column 11: end tag for element "PARAM" which is not open
    			</param><param name="wmode" value="transparent">

    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 1318, Column 11: end tag for element "PARAM" which is not open
    			</param><param name="bgcolor" value="Transparent">

    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 1320, Column 11: end tag for element "PARAM" which is not open
    			</param><param name="movie" value="/ClalitCMS/AdImages/app_cell_CSHP_193x197…

    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 1322, Column 11: end tag for element "PARAM" which is not open
    			</param><param name="AdId" value="1088">

    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 1324, Column 11: end tag for element "PARAM" which is not open
    			</param></OBJECT>

    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 2111, Column 204: there is no attribute "HSPACE"
    …/Seal/HONConduct489793_s1.gif" hspace="2" vspace="2" align="left" width="43" h…

    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 2111, Column 215: there is no attribute "VSPACE"
    …nduct489793_s1.gif" hspace="2" vspace="2" align="left" width="43" height="60" …

    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 2111, Column 225: there is no attribute "ALIGN"
    …3_s1.gif" hspace="2" vspace="2" align="left" width="43" height="60" style="bor…

    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 2111, Column 440: NET-enabling start-tag requires SHORTTAG YES
    …te is certified by Health On the Net Foundation. Click to verify." /></a></div>

    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.

  • Warning Line 2113, Column 168: NET-enabling start-tag requires SHORTTAG YES
    …3B-97DF-B728CDC7DBA5/14800/Mako1.jpg" id="NeoFooter1_imgMako" border="0" /></a>

    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 2113, Column 168: required attribute "ALT" not specified
    …3B-97DF-B728CDC7DBA5/14800/Mako1.jpg" id="NeoFooter1_imgMako" border="0" /></a>

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

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

Visitor Analysis

Daily Visitor
  • 3.617 visits