mynyp.org

Your myNYP.org session is about to expire. Your myNYP.org session is about to expire, and you will automatically be signed out. To prevent expiration, please take action on the site.   Close   ...

Display Widget for this domain on your website. Click Here
This data was last updated from 22-08-2013 11:35:49  (update).

Overview Info

  • Domain Name
    mynyp.org
  • Favicon
  • Alexa Rank
    #4170334
  • Google Page Rank
    PR 6
  • Ip Address
    143.104.20.91
  • Page Size
    38 KB
  • Images
    0 GIF, 0 JPG, 2 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 2 0 0 0

Website Meta Analysis



  • Title
    myNYP.org - Your Personal Health Connection to NewYork-Presbyterian Hospital
  • Meta Keyword
    HealthVault,New York,Presbyterian,Hospital,Weill,Cornell,Columbia,university,medicine,specialists,physician,cancer,cardiovascular,cardiology,heart,digestive diseases,geriatrics,neuroscience,pediatrics,psychiatry,transplantation,vascular,immunizations,mynyp,NYP,mynyp.org,Hospital Visits,Hospital Records,Health,NewYork-Presbyterian,New York Presbyterian,Personal Health Connection,medical visits,medical visit
  • Meta Description
    Your myNYP.org session is about to expire. Your myNYP.org session is about to expire, and you will automatically be signed out. To prevent expiration, please take action on the site.   Close   Click me! Health Education| Health Tools| Our Doctors| ...

Technical Analysis



  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    143.104.20.91
  • Domain Age
    4 Years, 4 Months, 24 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from mynyp.org.

HTML Analysis

  • date: Thu, 22 Aug 2013 11:35:42 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • x-aspnet-version: 4.0.30319
  • cache-control: no-cache
  • pragma: no-cache
  • expires: -1
  • content-type: text/html; charset=utf-8
  • content-length: 39557
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for mynyp.org

DNS Analysis


DNS servers
dns1.med.cornell.edu [140.251.2.18]
lex-dns1.med.cornell.edu [157.139.3.53]


DNS Records

Answer records
mynyp.org SOA
server: dns-master.med.cornell.edu
email: hostmaster@med.cornell.edu
serial: 19
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
86400s
mynyp.org NS  dns1.med.cornell.edu 86400s
mynyp.org NS  lex-dns1.med.cornell.edu 86400s
mynyp.org A 143.104.20.91 86400s

Authority records

Additional records
dns1.med.cornell.edu A 140.251.2.18 86400s
lex-dns1.med.cornell.edu A 157.139.3.53 86400s

IP 143.104.20.91 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 42 Errors
  • 94 Warnings
Ratio Text/Html
  • 0.3162948319683705
Message Error
  • Warning Line 59, Column 16: character "<" is the first character of a delimiter but occurred as data
          if(start < 0) return null;

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 62, Column 14: character "<" is the first character of a delimiter but occurred as data
          if(end < 0) end=document.cookie.length;

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 80, Column 34: character "&" is the first character of a delimiter but occurred as data
          } else if(lang==MP.SrcLang && MP.UrlLang!=MP.SrcLang){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 80, Column 35: character "&" is the first character of a delimiter but occurred as data
          } else if(lang==MP.SrcLang && MP.UrlLang!=MP.SrcLang){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 122, Column 68: there is no attribute "autocomplete"
        <form method="post" action="MyNYP.aspx" id="form" autocomplete="off">

    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 163, Column 56: element "B" undefined
    …<li><a href="https://nyp.ixt.com/Login.aspx"><B>Pay Hospital Bill</B></a></li> 

    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 208, Column 37: "mporgnav" is not a member of a group specified for any attribute
                            <a mporgnav href="http://espstage.mynyp.org/?1" onclick…
  • Warning Line 547, Column 14: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 547, Column 18: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 547, Column 22: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 547, Column 26: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 547, Column 30: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 547, Column 34: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 547, Column 38: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 547, Column 42: multiple comments in comment declaration
    … <!-- ------------------------------------------------------------------------…
  • Warning Line 547, Column 46: multiple comments in comment declaration
    …- ----------------------------------------------------------------------------…
  • Warning Line 547, Column 50: multiple comments in comment declaration
    …------------------------------------------------------------------------------…
  • Warning Line 547, Column 54: multiple comments in comment declaration
    …----------------------------------------------------------------------------- …
  • Warning Line 547, Column 58: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 547, Column 62: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 547, Column 66: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 547, Column 70: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 547, Column 74: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 547, Column 78: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 547, Column 82: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 547, Column 86: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 547, Column 90: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Error Line 547, Column 92: invalid comment declaration: found name character outside comment but inside comment declaration
    …--------------------------------------------------------------------------- -->
  • Info Line 547, Column 5: comment declaration started here
        <!-- ----------------------------------------------------------------------…
  • Warning Line 550, Column 14: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 550, Column 18: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 550, Column 22: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 550, Column 26: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 550, Column 30: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 550, Column 34: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 550, Column 38: multiple comments in comment declaration
        <!-- ----------------------------------------------------------------------…
  • Warning Line 550, Column 42: multiple comments in comment declaration
    … <!-- ------------------------------------------------------------------------…
  • Warning Line 550, Column 46: multiple comments in comment declaration
    …- ----------------------------------------------------------------------------…
  • Warning Line 550, Column 50: multiple comments in comment declaration
    …------------------------------------------------------------------------------…
  • Warning Line 550, Column 54: multiple comments in comment declaration
    …----------------------------------------------------------------------------- …
  • Warning Line 550, Column 58: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 550, Column 62: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 550, Column 66: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 550, Column 70: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 550, Column 74: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 550, Column 78: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 550, Column 82: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 550, Column 86: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Warning Line 550, Column 90: multiple comments in comment declaration
    …--------------------------------------------------------------------------- -->
  • Error Line 550, Column 92: invalid comment declaration: found name character outside comment but inside comment declaration
    …--------------------------------------------------------------------------- -->
  • Info Line 550, Column 5: comment declaration started here
        <!-- ----------------------------------------------------------------------…
  • Error Line 620, Column 36: invalid comment declaration: found character ")" outside comment but inside comment declaration
                   for(var i=10;i>0;i--){

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

  • Info Line 563, Column 36: comment declaration started here
        <script type="text/javascript"><!--
  • Warning Line 631, Column 34: character "&" is the first character of a delimiter but occurred as data
           else if (navigator.plugins&&navigator.plugins.length){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 631, Column 36: cannot generate system identifier for general entity "navigator.plugins.length"
           else if (navigator.plugins&&navigator.plugins.length){

    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 631, Column 36: general entity "navigator.plugins.length" not defined and no default entity
           else if (navigator.plugins&&navigator.plugins.length){

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

  • Warning Line 631, Column 60: reference not terminated by REFC delimiter
           else if (navigator.plugins&&navigator.plugins.length){

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

  • Error Line 631, Column 60: reference to entity "navigator.plugins.length" for which no system identifier could be generated
           else if (navigator.plugins&&navigator.plugins.length){

    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 631, Column 35: entity was defined here
           else if (navigator.plugins&&navigator.plugins.length){
  • Error Line 632, Column 55: character ";" not allowed in attribute specification list
                   for (var i=0;i<navigator.plugins.length;i++){
  • Error Line 632, Column 55: element "navigator.plugins.length" undefined
                   for (var i=0;i<navigator.plugins.length;i++){

    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 659, Column 49: character ";" not allowed in attribute specification list
                           for (var i=0;i<gQP.length;i++){
  • Error Line 659, Column 49: element "gQP.length" undefined
                           for (var i=0;i<gQP.length;i++){

    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).
  • Warning Line 669, Column 42: character "&" is the first character of a delimiter but occurred as data
           if ((window.document.referrer!="")&&(window.document.referrer!="-")){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 669, Column 43: character "&" is the first character of a delimiter but occurred as data
           if ((window.document.referrer!="")&&(window.document.referrer!="-")){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 670, Column 70: character "&" is the first character of a delimiter but occurred as data
    …tor.appName=="Microsoft Internet Explorer"&&parseInt(navigator.appVersion)<4)){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 670, Column 72: cannot generate system identifier for general entity "parseInt"
    …tor.appName=="Microsoft Internet Explorer"&&parseInt(navigator.appVersion)<4)){

    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 670, Column 72: general entity "parseInt" not defined and no default entity
    …tor.appName=="Microsoft Internet Explorer"&&parseInt(navigator.appVersion)<4)){

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

  • Warning Line 670, Column 80: reference not terminated by REFC delimiter
    …tor.appName=="Microsoft Internet Explorer"&&parseInt(navigator.appVersion)<4)){

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

  • Error Line 670, Column 80: reference to entity "parseInt" for which no system identifier could be generated
    …tor.appName=="Microsoft Internet Explorer"&&parseInt(navigator.appVersion)<4)){

    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 670, Column 71: entity was defined here
    …tor.appName=="Microsoft Internet Explorer"&&parseInt(navigator.appVersion)<4)){
  • Warning Line 670, Column 102: character "<" is the first character of a delimiter but occurred as data
    …tor.appName=="Microsoft Internet Explorer"&&parseInt(navigator.appVersion)<4)){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 677, Column 17: character "&" is the first character of a delimiter but occurred as data
           if (gI18n&&!EXRE.test(N)){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 677, Column 18: character "&" is the first character of a delimiter but occurred as data
           if (gI18n&&!EXRE.test(N)){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 680, Column 57: character "&" is the first character of a delimiter but occurred as data
                           var params=V.substring(1).split("&");

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 681, Column 52: character ";" not allowed in attribute specification list
                           for (var i=0;i<params.length;i++){
  • Error Line 681, Column 52: element "params.length" undefined
                           for (var i=0;i<params.length;i++){

    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).
  • Warning Line 688, Column 55: character "&" is the first character of a delimiter but occurred as data
                                                   newV+="&";

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 699, Column 16: character "&" is the first character of a delimiter but occurred as data
           return "&"+N+"="+dcsEscape(V, RE);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 726, Column 41: there is no attribute "ALT"
    …             document.write('<IMG ALT="" BORDER="0" NAME="DCSIMG" WIDTH="1" HE…

    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 726, Column 51: there is no attribute "BORDER"
    …   document.write('<IMG ALT="" BORDER="0" NAME="DCSIMG" WIDTH="1" HEIGHT="1" S…

    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 726, Column 60: there is no attribute "NAME"
    …nt.write('<IMG ALT="" BORDER="0" NAME="DCSIMG" WIDTH="1" HEIGHT="1" SRC="'+dcs…

    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 726, Column 75: there is no attribute "WIDTH"
    …'<IMG ALT="" BORDER="0" NAME="DCSIMG" WIDTH="1" HEIGHT="1" SRC="'+dcsSrc+'">');

    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 726, Column 86: there is no attribute "HEIGHT"
    …'<IMG ALT="" BORDER="0" NAME="DCSIMG" WIDTH="1" HEIGHT="1" SRC="'+dcsSrc+'">');

    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 726, Column 94: there is no attribute "SRC"
    …'<IMG ALT="" BORDER="0" NAME="DCSIMG" WIDTH="1" HEIGHT="1" SRC="'+dcsSrc+'">');

    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 726, Column 106: element "IMG" undefined
    …'<IMG ALT="" BORDER="0" NAME="DCSIMG" WIDTH="1" HEIGHT="1" SRC="'+dcsSrc+'">');

    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 740, Column 37: character ";" not allowed in attribute specification list
                   for (var i=0;i<length;i++){
  • Error Line 740, Column 37: element "length" undefined
                   for (var i=0;i<length;i++){

    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 773, Column 34: character ";" not allowed in attribute specification list
           for (var i=0;i<keys.length;i++){
  • Error Line 773, Column 34: element "keys.length" undefined
           for (var i=0;i<keys.length;i++){

    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).
  • Warning Line 793, Column 17: character "&" is the first character of a delimiter but occurred as data
           if (gI18n&&(WT.dep.length>0)){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 793, Column 18: character "&" is the first character of a delimiter but occurred as data
           if (gI18n&&(WT.dep.length>0)){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 796, Column 25: character "&" is the first character of a delimiter but occurred as data
           if (P.length>2048&&navigator.userAgent.indexOf('MSIE')>=0){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 796, Column 27: cannot generate system identifier for general entity "navigator.userAgent.indexOf"
           if (P.length>2048&&navigator.userAgent.indexOf('MSIE')>=0){

    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 796, Column 27: general entity "navigator.userAgent.indexOf" not defined and no default entity
           if (P.length>2048&&navigator.userAgent.indexOf('MSIE')>=0){

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

  • Warning Line 796, Column 54: reference not terminated by REFC delimiter
           if (P.length>2048&&navigator.userAgent.indexOf('MSIE')>=0){

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

  • Error Line 796, Column 54: reference to entity "navigator.userAgent.indexOf" for which no system identifier could be generated
           if (P.length>2048&&navigator.userAgent.indexOf('MSIE')>=0){

    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 796, Column 26: entity was defined here
           if (P.length>2048&&navigator.userAgent.indexOf('MSIE')>=0){
  • Warning Line 797, Column 40: cannot generate system identifier for general entity "WT.tu"
                   P=P.substring(0,2040)+"&WT.tu=1";

    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 797, Column 40: general entity "WT.tu" not defined and no default entity
                   P=P.substring(0,2040)+"&WT.tu=1";

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

  • Warning Line 797, Column 45: reference not terminated by REFC delimiter
                   P=P.substring(0,2040)+"&WT.tu=1";

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

  • Error Line 797, Column 45: reference to entity "WT.tu" for which no system identifier could be generated
                   P=P.substring(0,2040)+"&WT.tu=1";

    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 797, Column 39: entity was defined here
                   P=P.substring(0,2040)+"&WT.tu=1";
  • Warning Line 810, Column 21: character "&" is the first character of a delimiter but occurred as data
           var ff2up=(ff&&!ff0&&!ff10&!ff15);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 810, Column 22: character "&" is the first character of a delimiter but occurred as data
           var ff2up=(ff&&!ff0&&!ff10&!ff15);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 810, Column 27: character "&" is the first character of a delimiter but occurred as data
           var ff2up=(ff&&!ff0&&!ff10&!ff15);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 810, Column 28: character "&" is the first character of a delimiter but occurred as data
           var ff2up=(ff&&!ff0&&!ff10&!ff15);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 810, Column 34: character "&" is the first character of a delimiter but occurred as data
           var ff2up=(ff&&!ff0&&!ff10&!ff15);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 811, Column 19: character "&" is the first character of a delimiter but occurred as data
           var nn=(!ff&&(agt.indexOf("mozilla")!=-1)&&(agt.indexOf("compatible")==-…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 811, Column 20: character "&" is the first character of a delimiter but occurred as data
           var nn=(!ff&&(agt.indexOf("mozilla")!=-1)&&(agt.indexOf("compatible")==-…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 811, Column 49: character "&" is the first character of a delimiter but occurred as data
    …   var nn=(!ff&&(agt.indexOf("mozilla")!=-1)&&(agt.indexOf("compatible")==-1));

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 811, Column 50: character "&" is the first character of a delimiter but occurred as data
    …   var nn=(!ff&&(agt.indexOf("mozilla")!=-1)&&(agt.indexOf("compatible")==-1));

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 812, Column 19: character "&" is the first character of a delimiter but occurred as data
           var nn4=(nn&&(major==4));

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 812, Column 20: character "&" is the first character of a delimiter but occurred as data
           var nn4=(nn&&(major==4));

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 813, Column 21: character "&" is the first character of a delimiter but occurred as data
           var nn6up=(nn&&(major>=5));

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 813, Column 22: character "&" is the first character of a delimiter but occurred as data
           var nn6up=(nn&&(major>=5));

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 814, Column 41: character "&" is the first character of a delimiter but occurred as data
           var ie=((agt.indexOf("msie")!=-1)&&(agt.indexOf("opera")==-1));

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 814, Column 42: character "&" is the first character of a delimiter but occurred as data
           var ie=((agt.indexOf("msie")!=-1)&&(agt.indexOf("opera")==-1));

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 815, Column 19: character "&" is the first character of a delimiter but occurred as data
           var ie4=(ie&&(major==4)&&(agt.indexOf("msie 4")!=-1));

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 815, Column 20: character "&" is the first character of a delimiter but occurred as data
           var ie4=(ie&&(major==4)&&(agt.indexOf("msie 4")!=-1));

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 815, Column 31: character "&" is the first character of a delimiter but occurred as data
           var ie4=(ie&&(major==4)&&(agt.indexOf("msie 4")!=-1));

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 815, Column 32: character "&" is the first character of a delimiter but occurred as data
           var ie4=(ie&&(major==4)&&(agt.indexOf("msie 4")!=-1));

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 816, Column 21: character "&" is the first character of a delimiter but occurred as data
           var ie5up=(ie&&!ie4);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 816, Column 22: character "&" is the first character of a delimiter but occurred as data
           var ie5up=(ie&&!ie4);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 820, Column 21: character "&" is the first character of a delimiter but occurred as data
           var op7up=(op&&!op5&&!op6);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 820, Column 22: character "&" is the first character of a delimiter but occurred as data
           var op7up=(op&&!op5&&!op6);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 820, Column 27: character "&" is the first character of a delimiter but occurred as data
           var op7up=(op&&!op5&&!op6);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 820, Column 28: character "&" is the first character of a delimiter but occurred as data
           var op7up=(op&&!op5&&!op6);

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 831, Column 21: character "&" is the first character of a delimiter but occurred as data
           else if ((mac&&ie5up)||op6){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 831, Column 23: cannot generate system identifier for general entity "ie5up"
           else if ((mac&&ie5up)||op6){

    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 831, Column 23: general entity "ie5up" not defined and no default entity
           else if ((mac&&ie5up)||op6){

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

  • Warning Line 831, Column 28: reference not terminated by REFC delimiter
           else if ((mac&&ie5up)||op6){

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

  • Error Line 831, Column 28: reference to entity "ie5up" for which no system identifier could be generated
           else if ((mac&&ie5up)||op6){

    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 831, Column 22: entity was defined here
           else if ((mac&&ie5up)||op6){
  • Error Line 854, Column 13: end tag for "keys.length" omitted, but OMITTAG NO was specified
        </script>

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

  • Info Line 773, Column 22: start tag was here
           for (var i=0;i<keys.length;i++){
  • Error Line 854, Column 13: end tag for "length" omitted, but OMITTAG NO was specified
        </script>

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

  • Info Line 740, Column 30: start tag was here
                   for (var i=0;i<length;i++){
  • Error Line 854, Column 13: end tag for "IMG" omitted, but OMITTAG NO was specified
        </script>

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

  • Info Line 726, Column 32: start tag was here
                   document.write('<IMG ALT="" BORDER="0" NAME="DCSIMG" WIDTH="1" H…
  • Error Line 854, Column 13: end tag for "params.length" omitted, but OMITTAG NO was specified
        </script>

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

  • Info Line 681, Column 38: start tag was here
                           for (var i=0;i<params.length;i++){
  • Error Line 854, Column 13: end tag for "gQP.length" omitted, but OMITTAG NO was specified
        </script>

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

  • Info Line 659, Column 38: start tag was here
                           for (var i=0;i<gQP.length;i++){
  • Error Line 854, Column 13: end tag for "navigator.plugins.length" omitted, but OMITTAG NO was specified
        </script>

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

  • Info Line 632, Column 30: start tag was here
                   for (var i=0;i<navigator.plugins.length;i++){
  • Error Line 857, Column 182: end tag for "img" omitted, but OMITTAG NO was specified
    …000gwn4yndn5kf_3d6u/njs.gif?dcsuri=/nojavascript&amp;WT.js=No&amp;WT.tv=8.0.3">

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

  • Info Line 857, Column 9: start tag was here
            <img alt="" border="0" name="DCSIMG" width="1" height="1" src="https://…

Visitor Analysis

Daily Visitor
  • 28 visits

In Page Analysis