official tupperware Web site, food storage, food preservation, plastic containers, tuperware, tupper ware, storage containers, containers, microwave cooking, career, tupperware recipes, tupperware products, tupperware party, tupperware catalog, home business, storage solutions, fresh, produce, ...

tupperware.com
  • Domain Name
    tupperware.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #23593
  • Page Size
    25.5 KB
  • Ip Address
    63.237.248.60
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 7 JPG, 6 PNG

Website Meta Analysis

  • Title
    Tupperware | Tupperware - the official World Web Site for Tupperware Products
  • Meta Keyword
    Tupperware&2018;s official U.S. Web site. Tupperware products are available for sale on-line and information on Tupperware parties is also available. Tupperware.com features innovative food storage containers, microwave cooking products, techniques and recipes, and exciting career opportunities for women.
  • Meta Description
    official tupperware Web site, food storage, food preservation, plastic containers, tuperware, tupper ware, storage containers, containers, microwave cooking, career, tupperware recipes, tupperware products, tupperware party, tupperware catalog, home business, storage solutions, fresh, produce, bowls, household hints, refrigerator, meal preparation, income, time saving, toys, food serving, tupperware corp, www.tupperware.com, tupperware.com, www.tupperware, http://www.tupperware.com, http://www.tupperware, http://tupperware.com

Technical Analysis

  • Webserver
    Oracle-Application-Server-10g/10.1.2.0.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.0.0 (N;ecid=256649778933,0)
  • Ip Address
    63.237.248.60
  • Domain Age
    7 Years, 3 Months, 18 days.
  • Javascript Library
    prototype
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-length: 7737
  • content-type: text/html; charset=US-ASCII
  • server: Oracle-Application-Server-10g/10.1.2.0.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.0.0 (N;ecid=256649778933,0)
  • date: Wed, 11 Sep 2013 12:25:25 GMT
  • vary: Accept-Encoding
  • content-encoding: gzip
  • connection: Keep-Alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for tupperware.com

DNS Analysis


DNS servers
ns1.tupperware.net
ns2.tupperware.net
ns3.tupperware.net


DNS Records

Answer records
tupperware.com A 63.237.248.60 3600s
tupperware.com NS  ns1.tupperware.net 3600s
tupperware.com NS  ns2.tupperware.net 3600s
tupperware.com NS  ns3.tupperware.net 3600s
tupperware.com SOA
server: ns1.tupperware.net
email: dns@tupperware.net
serial: 2004083624
refresh: 1800
retry: 600
expire: 604800
minimum ttl: 3600
3600s
tupperware.com MX
preference: 10
exchange: maila02a.tupperware.com
3600s
tupperware.com MX
preference: 10
exchange: maila03a.tupperware.com
3600s
tupperware.com MX
preference: 20
exchange: maila02b.tupperware.com
3600s
tupperware.com MX
preference: 20
exchange: maila01b.tupperware.com
3600s
tupperware.com TXT MS=ms70041759 3600s
tupperware.com TXT cvq2nJFTJdiKMAhsw2M8r/L4UJMSnIDwjlM5AEVYc9ZY2M633Nh3AU+jXN/Z6SiVsYTatxnU0oQFQfXQX1fE4g== 3600s

Authority records

Additional records
ns1.tupperware.net A 63.237.248.250 3600s
ns2.tupperware.net A 50.123.128.25 3600s
ns3.tupperware.net A 207.224.237.184 3600s
maila02a.tupperware.com A 63.237.248.216 3600s
maila03a.tupperware.com A 63.237.248.217 3600s
maila02b.tupperware.com A 64.220.42.122 3600s
maila01b.tupperware.com A 64.220.42.123 3600s

IP 63.237.248.60 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    West Palm Beach
  • Continent Code
    33401
  • Latitude
    561
  • Longitude
    548
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 63.237.248.60"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=63.237.248.60?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 63.236.0.0 - 63.239.255.255
    CIDR: 63.236.0.0/14
    OriginAS:
    NetName: QWEST-INET-9
    NetHandle: NET-63-236-0-0-1
    Parent: NET-63-0-0-0-0
    NetType: Direct Allocation
    Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
    Comment: NOTE: For abuse issues, please email abuse@qwest.net.
    RegDate: 1999-11-19
    Updated: 2012-02-24
    Ref: http://whois.arin.net/rest/net/NET-63-236-0-0-1

    OrgName: Qwest Communications Company, LLC
    OrgId: QCC-18
    Address: 1801 California Street
    City: Denver
    StateProv: CO
    PostalCode: 80202
    Country: US
    RegDate: 2005-05-09
    Updated: 2011-09-08
    Ref: http://whois.arin.net/rest/org/QCC-18

    OrgTechHandle: QIA-ARIN
    OrgTechName: Qwest IP Admin
    OrgTechPhone: +1-877-886-6515
    OrgTechEmail: ipadmin@qwest.com
    OrgTechRef: http://whois.arin.net/rest/poc/QIA-ARIN

    OrgNOCHandle: QIN-ARIN
    OrgNOCName: Qwest IP NOC
    OrgNOCPhone: +1-877-886-6515
    OrgNOCEmail: support@qwestip.net
    OrgNOCRef: http://whois.arin.net/rest/poc/QIN-ARIN

    OrgAbuseHandle: QIA2-ARIN
    OrgAbuseName: Qwest Abuse
    OrgAbusePhone: +1-877-886-6515
    OrgAbuseEmail: abuse@qwest.net
    OrgAbuseRef: http://whois.arin.net/rest/poc/QIA2-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 58 Errors
  • 37 Warnings
Ratio Text/Html
  • 0.7644309955184433
Message Error
  • Warning Line 10, Column 46: character "&" is the first character of a delimiter but occurred as data
    …ta name="keywords" content="Tupperware&2018;s official U.S. Web site. Tupperwa…

    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 70, Column 76: cannot generate system identifier for general entity "fv_section_name"
    ….show_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=sh…

    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 70, Column 76: general entity "fv_section_name" not defined and no default entity
    ….show_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=sh…

    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 70, Column 91: reference not terminated by REFC delimiter
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"

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

  • Warning Line 70, Column 91: reference to external entity in attribute value
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"

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

  • Error Line 70, Column 91: reference to entity "fv_section_name" for which no system identifier could be generated
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"

    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 70, Column 75: entity was defined here
    …t.show_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=s…
  • Warning Line 70, Column 97: cannot generate system identifier for general entity "fv_category_code"
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"

    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 70, Column 97: general entity "fv_category_code" not defined and no default entity
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"

    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 70, Column 113: reference not terminated by REFC delimiter
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"

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

  • Warning Line 70, Column 113: reference to external entity in attribute value
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"

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

  • Error Line 70, Column 113: reference to entity "fv_category_code" for which no system identifier could be generated
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"

    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 70, Column 96: entity was defined here
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"
  • Warning Line 73, Column 86: reference not terminated by REFC delimiter
    …?fv_page_code=warranty&fv_section_name=help&fv_category_code=search&fv_item_ca…

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

  • Warning Line 73, Column 86: reference to external entity in attribute value
    …?fv_page_code=warranty&fv_section_name=help&fv_category_code=search&fv_item_ca…

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

  • Error Line 73, Column 86: reference to entity "fv_section_name" for which no system identifier could be generated
    …?fv_page_code=warranty&fv_section_name=help&fv_category_code=search&fv_item_ca…

    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 70, Column 75: entity was defined here
    …t.show_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=s…
  • Warning Line 73, Column 108: reference not terminated by REFC delimiter
    …anty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500"

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

  • Warning Line 73, Column 108: reference to external entity in attribute value
    …anty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500"

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

  • Error Line 73, Column 108: reference to entity "fv_category_code" for which no system identifier could be generated
    …anty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500"

    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 70, Column 96: entity was defined here
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"
  • Warning Line 73, Column 116: cannot generate system identifier for general entity "fv_item_category_code"
    …anty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500"

    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 73, Column 116: general entity "fv_item_category_code" not defined and no default entity
    …anty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500"

    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 73, Column 137: reference not terminated by REFC delimiter
    …anty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500"

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

  • Warning Line 73, Column 137: reference to external entity in attribute value
    …anty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500"

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

  • Error Line 73, Column 137: reference to entity "fv_item_category_code" for which no system identifier could be generated
    …anty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500"

    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 73, Column 115: entity was defined here
    …anty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500"
  • Error Line 88, Column 78: "mporgnav" is not a member of a group specified for any attribute
    …://espanol.tupperware.com/enes/" mporgnav onclick="return switchLanguage('es');
  • Error Line 113, Column 130: there is no attribute "autocomplete"
    …tem #" id="sli_search_1" autocomplete="off" size="15" maxlength="1991" class="…

    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 113, Column 189: there is no attribute "onFocus"
    …ngth="1991" class="formInput" onFocus="JavaScript:this.value=''" /><!-- mp_tra…

    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 113, Column 272: S separator in comment declaration
    …move_end --><!-- mp_trans_add="ES"<!-- mp_trans_disable_start --]><input type=…

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 113, Column 273: invalid comment declaration: found name start character outside comment but inside comment declaration
    …ove_end --><!-- mp_trans_add="ES"<!-- mp_trans_disable_start --]><input type="…
  • Info Line 113, Column 246: comment declaration started here
    …lue=''" /><!-- mp_trans_remove_end --><!-- mp_trans_add="ES"<!-- mp_trans_disa…
  • Error Line 113, Column 365: ID "sli_search_1" already defined
    … value="Pal. clave/N&deg; de art" id="sli_search_1" autocomplete="off" size="1…

    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 113, Column 103: ID "sli_search_1" first defined here
    …ame="w" value="Keyword or Item #" id="sli_search_1" autocomplete="off" size="1…
  • Error Line 113, Column 508: invalid comment declaration: found character "]" outside comment but inside comment declaration
    …lue=''" /><!-- mp_trans_disable_end --]>--><input type="hidden" name="asug" />…

    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 113, Column 480: comment declaration started here
    … onFocus="JavaScript:this.value=''" /><!-- mp_trans_disable_end --]>--><input …
  • Error Line 156, Column 110: document type does not allow element "link" here
    …xt/css" href="http://order.tupperware.com/coe-css/featuredcontentglider.css" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 177, Column 43: character "$" not allowed in attribute specification list
    			config.nextslideindex=(selected<config.$contentdivs.length-1)? selected+1 : 0
  • Error Line 177, Column 43: element "config." undefined
    			config.nextslideindex=(selected<config.$contentdivs.length-1)? selected+1 : 0

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 248, Column 28: character "&" is the first character of a delimiter but occurred as data
    			if (config.totalsteps>0 && config.stepcount>=config.totalsteps){

    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 248, Column 29: character "&" is the first character of a delimiter but occurred as data
    			if (config.totalsteps>0 && config.stepcount>=config.totalsteps){

    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 296, Column 49: character "&" is the first character of a delimiter but occurred as data
    …	if (typeof config.remotecontent!="undefined" && config.remotecontent.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 296, Column 50: character "&" is the first character of a delimiter but occurred as data
    …	if (typeof config.remotecontent!="undefined" && config.remotecontent.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.
  • Error Line 314, Column 9: end tag for "config." 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 177, Column 35: start tag was here
    			config.nextslideindex=(selected<config.$contentdivs.length-1)? selected+1 : 0
  • Error Line 343, Column 186: required attribute "alt" not specified
    …s/home/01.24.13_home.jpg" border="0" title="Spread some love" width="850"/></a>

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

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

  • Error Line 355, Column 182: required attribute "alt" not specified
    …="0" title="SmartSteamer" width="850"/></a>                                   …

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

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

  • Error Line 366, Column 214: required attribute "alt" not specified
    ….13_onlineex.jpg" width="850px" border="0" title="Shop Online Exclusives"/></a>

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

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

  • Error Line 377, Column 179: required attribute "alt" not specified
    …ges/home/connect_home.jpg" width="850" height="530" border="0" usemap="#Map" />

    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 393, Column 35: there is no attribute "onMouseOver"
        		<a class="prev" onMouseOver="document.navswap.src='http://order.tupperwar…

    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 393, Column 131: there is no attribute "onMouseOut"
    …ges/home/prev_over2.png';" onMouseOut="document.navswap.src='http://order.tupp…

    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 394, Column 97: required attribute "alt" not specified
    …p://order.tupperware.com/coe-images/home/prev2.png" name="navswap" border="0"> 

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

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

  • Error Line 394, Column 98: end tag for "img" omitted, but OMITTAG NO was specified
    …p://order.tupperware.com/coe-images/home/prev2.png" name="navswap" border="0"> 

    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 394, Column 7: start tag was here
        		<img src="http://order.tupperware.com/coe-images/home/prev2.png" name="na…
  • Error Line 400, Column 98: required attribute "alt" not specified
    …://order.tupperware.com/coe-images/home/next2.png" name="navswap2" border="0"> 

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

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

  • Error Line 400, Column 99: end tag for "img" omitted, but OMITTAG NO was specified
    …://order.tupperware.com/coe-images/home/next2.png" name="navswap2" border="0"> 

    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 400, Column 7: start tag was here
        		<img src="http://order.tupperware.com/coe-images/home/next2.png" name="na…
  • Error Line 415, Column 35: there is no attribute "height"
         		<table width="100%" height="420px"cellspacing="0" cellpadding="0">

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

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

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

  • Error Line 415, Column 73: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
         		<table width="100%" height="420px"cellspacing="0" cellpadding="0">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 436, Column 69: character "&" is the first character of a delimiter but occurred as data
    …	<td><a href="!tw$shop.p_category?pv_ic_code=2001">Cutlery & Cookware </a></td>

    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 472, Column 94: cannot generate system identifier for general entity "storeid"
    …pperware/index.aspx?pagename=shopmain&storeid=1033893">Browse our Catalog</a><…

    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 472, Column 94: general entity "storeid" not defined and no default entity
    …pperware/index.aspx?pagename=shopmain&storeid=1033893">Browse our Catalog</a><…

    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 472, Column 101: reference not terminated by REFC delimiter
    …rware/index.aspx?pagename=shopmain&storeid=1033893">Browse our Catalog</a></td>

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

  • Warning Line 472, Column 101: reference to external entity in attribute value
    …rware/index.aspx?pagename=shopmain&storeid=1033893">Browse our Catalog</a></td>

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

  • Error Line 472, Column 101: reference to entity "storeid" for which no system identifier could be generated
    …rware/index.aspx?pagename=shopmain&storeid=1033893">Browse our Catalog</a></td>

    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 472, Column 93: entity was defined here
    …upperware/index.aspx?pagename=shopmain&storeid=1033893">Browse our Catalog</a>…
  • Error Line 478, Column 22: ID "sidenav-head" already defined
                <div id="sidenav-head">

    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 410, Column 22: ID "sidenav-head" first defined here
                <div id="sidenav-head">
  • Error Line 483, Column 59: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
         		<table width="100%" cellspacing="0" cellpadding="0">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 485, Column 28: "px" is not a member of a group specified for any attribute
           			<td height="28"px><a href="!tw$shop.p_category?pv_ic_code=17000">Modu…
  • Error Line 498, Column 17: there is no attribute "width"
        	<div width="283px" style="float:left;">    	

    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 499, Column 164: required attribute "alt" not specified
    …me/home_bucket_opp.jpg" border="0" title="the opportunity" height="222px"/></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>.

  • Warning Line 504, Column 77: reference not terminated by REFC delimiter
    …page_code=tupperliving&fv_section_name=lifestyle&fv_category_code=lifestyle"><…

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

  • Warning Line 504, Column 77: reference to external entity in attribute value
    …page_code=tupperliving&fv_section_name=lifestyle&fv_category_code=lifestyle"><…

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

  • Error Line 504, Column 77: reference to entity "fv_section_name" for which no system identifier could be generated
    …page_code=tupperliving&fv_section_name=lifestyle&fv_category_code=lifestyle"><…

    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 70, Column 75: entity was defined here
    …t.show_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=s…
  • Warning Line 504, Column 104: reference not terminated by REFC delimiter
    …ection_name=lifestyle&fv_category_code=lifestyle"><img src="http://order.tuppe…

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

  • Warning Line 504, Column 104: reference to external entity in attribute value
    …ection_name=lifestyle&fv_category_code=lifestyle"><img src="http://order.tuppe…

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

  • Error Line 504, Column 104: reference to entity "fv_category_code" for which no system identifier could be generated
    …ection_name=lifestyle&fv_category_code=lifestyle"><img src="http://order.tuppe…

    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 70, Column 96: entity was defined here
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"
  • Error Line 504, Column 233: required attribute "alt" not specified
    …mages/home/home_bucket_rec.jpg" border="0" title="recipes" height="222px"/></a>

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

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

  • Error Line 506, Column 204: required attribute "alt" not specified
    …s/home/home_bucket_party.jpg" border="0" title="the party" height="222px"/></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>.

  • Warning Line 515, Column 82: cannot generate system identifier for general entity "fv_item_number"
    …em_detail?fv_item_category_code=27000&fv_item_number=P10049247000"><img src="h…

    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 515, Column 82: general entity "fv_item_number" not defined and no default entity
    …em_detail?fv_item_category_code=27000&fv_item_number=P10049247000"><img src="h…

    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 515, Column 96: reference not terminated by REFC delimiter
    …tem_category_code=27000&fv_item_number=P10049247000"><img src="http://order.tu…

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

  • Warning Line 515, Column 96: reference to external entity in attribute value
    …tem_category_code=27000&fv_item_number=P10049247000"><img src="http://order.tu…

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

  • Error Line 515, Column 96: reference to entity "fv_item_number" for which no system identifier could be generated
    …tem_category_code=27000&fv_item_number=P10049247000"><img src="http://order.tu…

    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 515, Column 81: entity was defined here
    …tem_detail?fv_item_category_code=27000&fv_item_number=P10049247000"><img src="…
  • Error Line 515, Column 230: required attribute "alt" not specified
    …ges/home/e-gift.jpg" border="0" title="e-gift certificates" width="170px"/></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>.

  • Warning Line 518, Column 92: reference not terminated by REFC delimiter
    …e/index.aspx?pagename=shopmain&storeid=1033893" target="_blank"><img src="http…

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

  • Warning Line 518, Column 92: reference to external entity in attribute value
    …e/index.aspx?pagename=shopmain&storeid=1033893" target="_blank"><img src="http…

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

  • Error Line 518, Column 92: reference to entity "storeid" for which no system identifier could be generated
    …e/index.aspx?pagename=shopmain&storeid=1033893" target="_blank"><img src="http…

    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 472, Column 93: entity was defined here
    …upperware/index.aspx?pagename=shopmain&storeid=1033893">Browse our Catalog</a>…
  • Error Line 518, Column 253: required attribute "alt" not specified
    …catalog_spring13.jpg" border="0" title="browse our catalog" width="170px"/></a>

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

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

  • Error Line 540, Column 84: required attribute "alt" not specified
    …mg src="http://order.tupperware.com/coe-images/home/bottom_grey_bar.jpg"/></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 546, Column 9: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
        <div>

    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 549, Column 35: there is no attribute "text-align"
        	<td width="175px" text-align="left" valign="top">

    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 552, Column 124: reference not terminated by REFC delimiter
    …tem_category_code=27000&fv_item_number=P10049247000">e-Gift Certificates</a></…

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

  • Warning Line 552, Column 124: reference to external entity in attribute value
    …tem_category_code=27000&fv_item_number=P10049247000">e-Gift Certificates</a></…

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

  • Error Line 552, Column 124: reference to entity "fv_item_number" for which no system identifier could be generated
    …tem_category_code=27000&fv_item_number=P10049247000">e-Gift Certificates</a></…

    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 515, Column 81: entity was defined here
    …tem_detail?fv_item_category_code=27000&fv_item_number=P10049247000"><img src="…
  • Warning Line 556, Column 114: reference not terminated by REFC delimiter
    …age_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"><b>Fundrais…

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

  • Warning Line 556, Column 114: reference to external entity in attribute value
    …age_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"><b>Fundrais…

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

  • Error Line 556, Column 114: reference to entity "fv_section_name" for which no system identifier could be generated
    …age_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"><b>Fundrais…

    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 70, Column 75: entity was defined here
    …t.show_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=s…
  • Warning Line 556, Column 136: reference not terminated by REFC delimiter
    …ser_us&fv_section_name=home&fv_category_code=shop"><b>Fundraising</b></a></div>

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

  • Warning Line 556, Column 136: reference to external entity in attribute value
    …ser_us&fv_section_name=home&fv_category_code=shop"><b>Fundraising</b></a></div>

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

  • Error Line 556, Column 136: reference to entity "fv_category_code" for which no system identifier could be generated
    …ser_us&fv_section_name=home&fv_category_code=shop"><b>Fundraising</b></a></div>

    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 70, Column 96: entity was defined here
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"
  • Warning Line 571, Column 105: reference not terminated by REFC delimiter
    …e?fv_page_code=contact&fv_section_name=help&fv_category_code=search&fv_item_ca…

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

  • Warning Line 571, Column 105: reference to external entity in attribute value
    …e?fv_page_code=contact&fv_section_name=help&fv_category_code=search&fv_item_ca…

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

  • Error Line 571, Column 105: reference to entity "fv_section_name" for which no system identifier could be generated
    …e?fv_page_code=contact&fv_section_name=help&fv_category_code=search&fv_item_ca…

    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 70, Column 75: entity was defined here
    …t.show_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=s…
  • Warning Line 571, Column 127: reference not terminated by REFC delimiter
    …&fv_section_name=help&fv_category_code=search&fv_item_category_code=200600">Cu…

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

  • Warning Line 571, Column 127: reference to external entity in attribute value
    …&fv_section_name=help&fv_category_code=search&fv_item_category_code=200600">Cu…

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

  • Error Line 571, Column 127: reference to entity "fv_category_code" for which no system identifier could be generated
    …&fv_section_name=help&fv_category_code=search&fv_item_category_code=200600">Cu…

    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 70, Column 96: entity was defined here
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"
  • Warning Line 571, Column 156: reference not terminated by REFC delimiter
    …v_category_code=search&fv_item_category_code=200600">Customer Service</a></div>

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

  • Warning Line 571, Column 156: reference to external entity in attribute value
    …v_category_code=search&fv_item_category_code=200600">Customer Service</a></div>

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

  • Error Line 571, Column 156: reference to entity "fv_item_category_code" for which no system identifier could be generated
    …v_category_code=search&fv_item_category_code=200600">Customer Service</a></div>

    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 73, Column 115: entity was defined here
    …anty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500"
  • Warning Line 573, Column 106: reference not terminated by REFC delimiter
    …?fv_page_code=warranty&fv_section_name=help&fv_category_code=search&fv_item_ca…

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

  • Warning Line 573, Column 106: reference to external entity in attribute value
    …?fv_page_code=warranty&fv_section_name=help&fv_category_code=search&fv_item_ca…

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

  • Error Line 573, Column 106: reference to entity "fv_section_name" for which no system identifier could be generated
    …?fv_page_code=warranty&fv_section_name=help&fv_category_code=search&fv_item_ca…

    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 70, Column 75: entity was defined here
    …t.show_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=s…
  • Warning Line 573, Column 128: reference not terminated by REFC delimiter
    …&fv_section_name=help&fv_category_code=search&fv_item_category_code=200400">Wa…

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

  • Warning Line 573, Column 128: reference to external entity in attribute value
    …&fv_section_name=help&fv_category_code=search&fv_item_category_code=200400">Wa…

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

  • Error Line 573, Column 128: reference to entity "fv_category_code" for which no system identifier could be generated
    …&fv_section_name=help&fv_category_code=search&fv_item_category_code=200400">Wa…

    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 70, Column 96: entity was defined here
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"
  • Warning Line 573, Column 157: reference not terminated by REFC delimiter
    …e=help&fv_category_code=search&fv_item_category_code=200400">Warranty</a></div>

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

  • Warning Line 573, Column 157: reference to external entity in attribute value
    …e=help&fv_category_code=search&fv_item_category_code=200400">Warranty</a></div>

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

  • Error Line 573, Column 157: reference to entity "fv_item_category_code" for which no system identifier could be generated
    …e=help&fv_category_code=search&fv_item_category_code=200400">Warranty</a></div>

    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 73, Column 115: entity was defined here
    …anty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500"
  • Warning Line 574, Column 106: reference not terminated by REFC delimiter
    …?fv_page_code=shipping&fv_section_name=help&fv_category_code=search&fv_item_ca…

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

  • Warning Line 574, Column 106: reference to external entity in attribute value
    …?fv_page_code=shipping&fv_section_name=help&fv_category_code=search&fv_item_ca…

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

  • Error Line 574, Column 106: reference to entity "fv_section_name" for which no system identifier could be generated
    …?fv_page_code=shipping&fv_section_name=help&fv_category_code=search&fv_item_ca…

    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 70, Column 75: entity was defined here
    …t.show_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=s…
  • Warning Line 574, Column 128: reference not terminated by REFC delimiter
    …&fv_section_name=help&fv_category_code=search&fv_item_category_code=200200">Sh…

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

  • Warning Line 574, Column 128: reference to external entity in attribute value
    …&fv_section_name=help&fv_category_code=search&fv_item_category_code=200200">Sh…

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

  • Error Line 574, Column 128: reference to entity "fv_category_code" for which no system identifier could be generated
    …&fv_section_name=help&fv_category_code=search&fv_item_category_code=200200">Sh…

    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 70, Column 96: entity was defined here
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"
  • Warning Line 574, Column 157: reference not terminated by REFC delimiter
    …e=help&fv_category_code=search&fv_item_category_code=200200">Shipping</a></div>

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

  • Warning Line 574, Column 157: reference to external entity in attribute value
    …e=help&fv_category_code=search&fv_item_category_code=200200">Shipping</a></div>

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

  • Error Line 574, Column 157: reference to entity "fv_item_category_code" for which no system identifier could be generated
    …e=help&fv_category_code=search&fv_item_category_code=200200">Shipping</a></div>

    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 73, Column 115: entity was defined here
    …anty&fv_section_name=help&fv_category_code=search&fv_item_category_code=200500"
  • Warning Line 575, Column 117: reference not terminated by REFC delimiter
    …_code=REPLACEMENT_PART&fv_section_name=help&fv_category_code=search">Replaceme…

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

  • Warning Line 575, Column 117: reference to external entity in attribute value
    …_code=REPLACEMENT_PART&fv_section_name=help&fv_category_code=search">Replaceme…

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

  • Error Line 575, Column 117: reference to entity "fv_section_name" for which no system identifier could be generated
    …_code=REPLACEMENT_PART&fv_section_name=help&fv_category_code=search">Replaceme…

    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 70, Column 75: entity was defined here
    …t.show_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=s…
  • Warning Line 575, Column 139: reference not terminated by REFC delimiter
    …_PART&fv_section_name=help&fv_category_code=search">Replacement Parts</a></div>

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

  • Warning Line 575, Column 139: reference to external entity in attribute value
    …_PART&fv_section_name=help&fv_category_code=search">Replacement Parts</a></div>

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

  • Error Line 575, Column 139: reference to entity "fv_category_code" for which no system identifier could be generated
    …_PART&fv_section_name=help&fv_category_code=search">Replacement Parts</a></div>

    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 70, Column 96: entity was defined here
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"
  • Error Line 592, Column 155: required attribute "alt" not specified
    …://order.tupperware.com/coe-images/home/submit_arrow.png" border="0"/></button>

    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 592, Column 164: end tag for element "button" which is not open
    …://order.tupperware.com/coe-images/home/submit_arrow.png" border="0"/></button>

    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 627, Column 114: reference not terminated by REFC delimiter
    …age_code=fl_healthy100&fv_section_name=shop&fv_category_code=shop"><img src="h…

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

  • Warning Line 627, Column 114: reference to external entity in attribute value
    …age_code=fl_healthy100&fv_section_name=shop&fv_category_code=shop"><img src="h…

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

  • Error Line 627, Column 114: reference to entity "fv_section_name" for which no system identifier could be generated
    …age_code=fl_healthy100&fv_section_name=shop&fv_category_code=shop"><img src="h…

    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 70, Column 75: entity was defined here
    …t.show_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=s…
  • Warning Line 627, Column 136: reference not terminated by REFC delimiter
    …&fv_section_name=shop&fv_category_code=shop"><img src="http://order.tupperware…

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

  • Warning Line 627, Column 136: reference to external entity in attribute value
    …&fv_section_name=shop&fv_category_code=shop"><img src="http://order.tupperware…

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

  • Error Line 627, Column 136: reference to entity "fv_category_code" for which no system identifier could be generated
    …&fv_section_name=shop&fv_category_code=shop"><img src="http://order.tupperware…

    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 70, Column 96: entity was defined here
    …how_page?fv_page_code=fundraiser_us&fv_section_name=home&fv_category_code=shop"
  • Error Line 627, Column 254: required attribute "alt" not specified
    …mages/home/fl_healthy100.jpg" border="0" width="95px" height="50px"/></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 628, Column 209: required attribute "alt" not specified
    …/home/tup_redcross_sandy.jpg" border="0" width="95px" height="60px"/></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 629, Column 179: required attribute "alt" not specified
    …-images/home/coc_home_12.jpg" border="0" width="95px" height="37px"/></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 633, Column 218: required attribute "alt" not specified
    …ges/home/facebook_new.jpg" border="0"/></a>&nbsp;&nbsp;<a href="http://twitter…

    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 633, Column 375: required attribute "alt" not specified
    …order.tupperware.com/coe-images/home/twitter_new.png" 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 634, Column 189: required attribute "alt" not specified
    …e-images/home/g+_home.jpg" border="0"/></a>&nbsp;&nbsp;<a href="http://money.c…

    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 634, Column 413: required attribute "alt" not specified
    …coe-images/home/fortune_new.jpg" border="0" width="68" height="60"/></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 638, Column 15: end tag for "div" omitted, but OMITTAG NO was specified
            </span>

    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 546, Column 5: start tag was here
        <div>
  • Error Line 640, Column 6: end tag for "td" omitted, but OMITTAG NO was specified
    </div><!--End Footer Nav -->

    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 531, Column 5: start tag was here
    		  <td id="mainContentHomeFlexBay">
  • Error Line 640, Column 6: end tag for "tr" omitted, but OMITTAG NO was specified
    </div><!--End Footer Nav -->

    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 530, Column 3: start tag was here
    		<tr>
  • Error Line 640, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div><!--End Footer Nav -->

    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 150, Column 4: start tag was here
    	  <table id="mainContent">
  • Error Line 644, Column 9: end tag for element "td" which is not open
    		  </td>

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

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

  • Error Line 645, Column 7: end tag for element "tr" which is not open
    		</tr>

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

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

  • Error Line 646, Column 11: end tag for element "table" which is not open
    	  </table>

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

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

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

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

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

  • Warning Line 694, Column 159: character "&" is the first character of a delimiter but occurred as data
    …gjzrjx_2z4q/njs.gif?dcsuri=/nojavascript&&amp;WT.js=No&amp;WT.tv=1.1.1"/></div>

    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.

Visitor Analysis

Daily Visitor
  • 4.783 visits