Freekibble Freekibble Kat Freekibble Cares Knews About Contact Totals Kibble Map How to Play: Click on the answer that you think is correct... Right or wrong, you win! Click on an answer, and ...

freekibble.com
  • Domain Name
    freekibble.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #27874
  • Page Size
    21.7 KB
  • Ip Address
    69.20.49.98
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    7 GIF, 2 JPG, 2 PNG

Website Meta Analysis

  • Title
    Freekibble
  • Meta Keyword
  • Meta Description
    Freekibble Freekibble Kat Freekibble Cares Knews About Contact Totals Kibble Map How to Play: Click on the answer that you think is correct... Right or wrong, you win! Click on an answer, and every day you do, we'll provide 10 pieces of kibble ...

Technical Analysis

  • Webserver
    Microsoft-IIS/7.0
  • Ip Address
    69.20.49.98
  • Domain Age
    5 Years, 9 Months, 21 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-length: 23644
  • content-type: text/html
  • server: Microsoft-IIS/7.0
  • x-powered-by: ASP.NET
  • date: Tue, 24 Sep 2013 20:45:38 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:

kelly Ausland
18258 Rock Springs Road
Bend, OR 97701
US
Phone: +1.5413301848
Email: email




Domain Name: freekibble.com
Created on..............: 2007-12-04
Expires on..............: 2014-12-04

Administrative Contact:

kelly Ausland
18258 Rock Springs Road
Bend, OR 97701
US
Phone: +1.5413301848
Email: email


Technical Contact:
Registercom
Domain Registrar
575 8th Avenue
New York, NY 10018
US
Phone: +1.9027492701
Email: email


DNS Servers:
ns2.rackspace.com
ns.rackspace.com

DNS Analysis


DNS servers
ns2.rackspace.com [65.61.188.4]
ns.rackspace.com [69.20.95.4]


DNS Records

Answer records
freekibble.com SOA
server: ns.rackspace.com
email: hostmaster@rackspace.com
serial: 1351577420
refresh: 3600
retry: 300
expire: 1814400
minimum ttl: 300
300s
freekibble.com TXT v=spf1 a mx ~all 86400s
freekibble.com TXT v=spf1 mx a:mail.example.com ip4:66.192.165.128/28 ip4:74.202.227.32/27 ip4:66.162.193.224/28 ip4:64.132.109.48/28 ip4:97.65.130.128/28 include:icpbounce.com ?all 86400s
freekibble.com MX
preference: 10
exchange: mx1.emailsrvr.com
86400s
freekibble.com MX
preference: 20
exchange: mx2.emailsrvr.com
86400s
freekibble.com NS  ns.rackspace.com 86400s
freekibble.com NS  ns2.rackspace.com 86400s
freekibble.com A 69.20.49.98 86400s

Authority records

Additional records

IP 69.20.49.98 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Portland
  • Continent Code
    04112
  • Latitude
    207
  • Longitude
    500
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 69.20.49.98"
    #
    # Use "?" to get help.
    #

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

    Transit Id, LLC RSPC-43404-1081951259 (NET-69-20-49-96-1) 69.20.49.96 - 69.20.49.103
    Rackspace Hosting RSPC-NET-4 (NET-69-20-0-0-1) 69.20.0.0 - 69.20.127.255


    #
    # 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
  • 15 Errors
  • 34 Warnings
Ratio Text/Html
  • 0.6939628065762286
Message Error
  • Error Line 46, Column 72: required attribute "type" not specified
    …cript src="http://cdn.jquerytools.org/1.2.7/full/jquery.tools.min.js"></script>

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

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

  • Error Line 49, Column 7: required attribute "type" not specified
    <style>

    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 97, Column 44: there is no attribute "ice:editable"
            <div id="how-to-play" ice:editable="*">

    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 187, Column 95: required attribute "alt" not specified
    … src="images/products/left2.png" style="border-width:0;  padding-bottom:0px;"/>

    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 207, Column 108: cannot generate system identifier for general entity "slotName"
    …lickToGive/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName…

    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 207, Column 108: general entity "slotName" not defined and no default entity
    …lickToGive/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName…

    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 207, Column 116: reference not terminated by REFC delimiter
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekib…

    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 207, Column 116: reference to external entity in attribute value
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekib…

    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 207, Column 116: reference to entity "slotName" for which no system identifier could be generated
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekib…

    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 207, Column 107: entity was defined here
    …clickToGive/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageNam…
  • Warning Line 207, Column 140: cannot generate system identifier for general entity "pageName"
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"

    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 207, Column 140: general entity "pageName" not defined and no default entity
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"

    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 207, Column 148: reference not terminated by REFC delimiter
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"

    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 207, Column 148: reference to external entity in attribute value
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"

    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 207, Column 148: reference to entity "pageName" for which no system identifier could be generated
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"

    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 207, Column 139: entity was defined here
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"
  • Warning Line 221, Column 116: reference not terminated by REFC delimiter
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_02&pageName=freekib…

    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 221, Column 116: reference to external entity in attribute value
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_02&pageName=freekib…

    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 221, Column 116: reference to entity "slotName" for which no system identifier could be generated
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_02&pageName=freekib…

    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 207, Column 107: entity was defined here
    …clickToGive/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageNam…
  • Warning Line 221, Column 148: reference not terminated by REFC delimiter
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_02&pageName=freekibble"

    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 221, Column 148: reference to external entity in attribute value
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_02&pageName=freekibble"

    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 221, Column 148: reference to entity "pageName" for which no system identifier could be generated
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_02&pageName=freekibble"

    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 207, Column 139: entity was defined here
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"
  • Warning Line 235, Column 116: reference not terminated by REFC delimiter
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_03&pageName=freekib…

    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 235, Column 116: reference to external entity in attribute value
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_03&pageName=freekib…

    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 235, Column 116: reference to entity "slotName" for which no system identifier could be generated
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_03&pageName=freekib…

    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 207, Column 107: entity was defined here
    …clickToGive/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageNam…
  • Warning Line 235, Column 148: reference not terminated by REFC delimiter
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_03&pageName=freekibble"

    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 235, Column 148: reference to external entity in attribute value
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_03&pageName=freekibble"

    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 235, Column 148: reference to entity "pageName" for which no system identifier could be generated
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_03&pageName=freekibble"

    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 207, Column 139: entity was defined here
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"
  • Warning Line 249, Column 116: reference not terminated by REFC delimiter
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_04&pageName=freekib…

    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 249, Column 116: reference to external entity in attribute value
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_04&pageName=freekib…

    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 249, Column 116: reference to entity "slotName" for which no system identifier could be generated
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_04&pageName=freekib…

    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 207, Column 107: entity was defined here
    …clickToGive/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageNam…
  • Warning Line 249, Column 148: reference not terminated by REFC delimiter
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_04&pageName=freekibble"

    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 249, Column 148: reference to external entity in attribute value
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_04&pageName=freekibble"

    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 249, Column 148: reference to entity "pageName" for which no system identifier could be generated
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_04&pageName=freekibble"

    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 207, Column 139: entity was defined here
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"
  • Warning Line 269, Column 116: reference not terminated by REFC delimiter
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_05&pageName=freekib…

    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 269, Column 116: reference to external entity in attribute value
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_05&pageName=freekib…

    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 269, Column 116: reference to entity "slotName" for which no system identifier could be generated
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_05&pageName=freekib…

    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 207, Column 107: entity was defined here
    …clickToGive/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageNam…
  • Warning Line 269, Column 148: reference not terminated by REFC delimiter
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_05&pageName=freekibble"

    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 269, Column 148: reference to external entity in attribute value
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_05&pageName=freekibble"

    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 269, Column 148: reference to entity "pageName" for which no system identifier could be generated
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_05&pageName=freekibble"

    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 207, Column 139: entity was defined here
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"
  • Warning Line 283, Column 116: reference not terminated by REFC delimiter
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_06&pageName=freekib…

    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 283, Column 116: reference to external entity in attribute value
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_06&pageName=freekib…

    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 283, Column 116: reference to entity "slotName" for which no system identifier could be generated
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_06&pageName=freekib…

    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 207, Column 107: entity was defined here
    …clickToGive/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageNam…
  • Warning Line 283, Column 148: reference not terminated by REFC delimiter
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_06&pageName=freekibble"

    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 283, Column 148: reference to external entity in attribute value
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_06&pageName=freekibble"

    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 283, Column 148: reference to entity "pageName" for which no system identifier could be generated
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_06&pageName=freekibble"

    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 207, Column 139: entity was defined here
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"
  • Warning Line 297, Column 116: reference not terminated by REFC delimiter
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_07&pageName=freekib…

    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 297, Column 116: reference to external entity in attribute value
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_07&pageName=freekib…

    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 297, Column 116: reference to entity "slotName" for which no system identifier could be generated
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_07&pageName=freekib…

    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 207, Column 107: entity was defined here
    …clickToGive/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageNam…
  • Warning Line 297, Column 148: reference not terminated by REFC delimiter
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_07&pageName=freekibble"

    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 297, Column 148: reference to external entity in attribute value
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_07&pageName=freekibble"

    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 297, Column 148: reference to entity "pageName" for which no system identifier could be generated
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_07&pageName=freekibble"

    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 207, Column 139: entity was defined here
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"
  • Warning Line 311, Column 116: reference not terminated by REFC delimiter
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_08&pageName=freekib…

    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 311, Column 116: reference to external entity in attribute value
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_08&pageName=freekib…

    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 311, Column 116: reference to entity "slotName" for which no system identifier could be generated
    …ve/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_08&pageName=freekib…

    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 207, Column 107: entity was defined here
    …clickToGive/satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageNam…
  • Warning Line 311, Column 148: reference not terminated by REFC delimiter
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_08&pageName=freekibble"

    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 311, Column 148: reference to external entity in attribute value
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_08&pageName=freekibble"

    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 311, Column 148: reference to entity "pageName" for which no system identifier could be generated
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_08&pageName=freekibble"

    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 207, Column 139: entity was defined here
    …satellitead.faces?siteId=3&slotName=Freekibble_Carousel_01&pageName=freekibble"
  • Error Line 335, Column 96: required attribute "alt" not specified
    …src="images/products/right2.png" style="border-width:0; padding-bottom:0px; "/>

    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 347, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 374, Column 172: there is no attribute "onClick"
    …<a href="#" class="TextBlack" onClick="javascript:window.open('happymessage.as…

    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 462, Column 26: there is no attribute "src"
                  <embed src="../system/multimedia/thanks-sponsors2.swf" quality="h…

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

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

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

  • Error Line 462, Column 78: there is no attribute "quality"
    …timedia/thanks-sponsors2.swf" quality="high" pluginspage="http://www.adobe.com…

    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 462, Column 97: there is no attribute "pluginspage"
    …sors2.swf" quality="high" pluginspage="http://www.adobe.com/shockwave/download…

    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 462, Column 188: there is no attribute "type"
    …?P1_Prod_Version=ShockwaveFlash" type="application/x-shockwave-flash" width="1…

    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 462, Column 226: there is no attribute "width"
    …veFlash" type="application/x-shockwave-flash" width="116" height="125"></embed>

    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 462, Column 239: there is no attribute "height"
    …veFlash" type="application/x-shockwave-flash" width="116" height="125"></embed>

    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 462, Column 244: element "embed" undefined
    …veFlash" type="application/x-shockwave-flash" width="116" height="125"></embed>

    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 474, Column 332: there is no attribute "allowTransparency"
    …overflow:hidden; width:300px; height:255px;" allowTransparency="true"></iframe>

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

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

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

Visitor Analysis

Daily Visitor
  • 8.167 visits