The official Vuclip internal network. ...

vuclip.com
  • Domain Name
    vuclip.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #20372
  • Page Size
    39.5 KB
  • Ip Address
    66.160.159.106
  • Heading
    H1: 0, H2: 10, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    7 GIF, 1 JPG, 16 PNG

Website Meta Analysis

  • Title
    Vuclip
  • Meta Keyword
  • Meta Description
    The official Vuclip internal network.

Technical Analysis

  • Webserver
    Apache/2.2.3 (Red Hat)
  • Ip Address
    66.160.159.106
  • Domain Age
    9 Years, 3 Months, 1 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 28 Sep 2013 19:39:27 GMT
  • server: Apache/2.2.3 (Red Hat)
  • x-powered-by: PHP/5.3.2
  • p3p: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
  • cache-control: no-cache
  • pragma: no-cache
  • connection: close
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Xinlab
Sreya Krishnamurthy
1551 McCarthy Blvd Suite 213
Milpitas, CA 95035
US
Phone: +1.4086492240
Email: email

Registrar URL: www.register.com

Domain Name: vuclip.com
Created: 2008-06-05
Expires: 2012-06-16

Administrative Contact:
Xinlab
Sreya Krishnamurthy
1551 McCarthy Blvd Suite 213
Milpitas, CA 95035
US
Phone: +1.4083864830
Email: email

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

DNS Servers:
dns019.b.register.com
dns142.a.register.com
dns249.d.register.com
dns220.c.register.com

DNS Analysis


DNS servers
dns249.d.register.com
dns142.a.register.com
dns220.c.register.com
dns019.b.register.com


DNS Records

Answer records
vuclip.com NS  dns220.c.register.com 14400s
vuclip.com SOA
server: dns142.a.register.com
email: root@register.com
serial: 2008060669
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 14400
14400s
vuclip.com MX
preference: 0
exchange: mx.vuclip.com
14400s
vuclip.com A 66.160.159.101 14400s
vuclip.com NS  dns249.d.register.com 14400s
vuclip.com NS  dns142.a.register.com 14400s
vuclip.com MX
preference: 0
exchange: mx1.vuclip.com
14400s
vuclip.com A 66.160.159.106 14400s
vuclip.com NS  dns019.b.register.com 14400s

Authority records

Additional records
mx1.vuclip.com A 65.19.141.132 14400s
mx.vuclip.com A 65.19.141.132 14400s

IP 66.160.159.106 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Milpitas
  • Continent Code
    95035
  • Latitude
    408
  • Longitude
    807
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 66.160.159.106"
    #
    # Use "?" to get help.
    #

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

    Xinlab, Inc. HURRICANE-CE2102-9B1 (NET-66-160-159-0-1) 66.160.159.0 - 66.160.159.127
    Hurricane Electric, Inc. HURRICANE-7 (NET-66-160-128-0-1) 66.160.128.0 - 66.160.207.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
  • 62 Errors
  • 85 Warnings
Ratio Text/Html
  • 0.5439810239177703
Message Error
  • Error Line 54, Column 33: there is no attribute "cellspacing"
    <table width="100%" cellspacing="0" cellpadding="0" border="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 54, Column 49: there is no attribute "cellpadding"
    <table width="100%" cellspacing="0" cellpadding="0" border="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 54, Column 60: there is no attribute "border"
    <table width="100%" cellspacing="0" cellpadding="0" border="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 55, Column 17: element "tbody" undefined
              <tbody><tr>

    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 56, Column 26: ID "header" already defined
                <td><div id="header">

    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 53, Column 10: ID "header" first defined here
    <div id="header">
  • Error Line 57, Column 101: end tag for "img" omitted, but OMITTAG NO was specified
    …" height="36" alt="Vuclip Videos" src="im/vuclip_logo_trans_sm.png"></div></td>

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

  • Info Line 57, Column 13: start tag was here
                <img width="148" height="36" alt="Vuclip Videos" src="im/vuclip_log…
  • Error Line 63, Column 24: end tag for "table" which is not finished
            </tbody></table>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Warning Line 92, Column 101: cannot generate system identifier for general entity "z"
    …>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=2675166…

    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 92, Column 101: general entity "z" not defined and no default entity
    …>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=2675166…

    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 92, Column 102: reference not terminated by REFC delimiter
    …&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=26751667…

    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 92, Column 102: reference to external entity in attribute value
    …&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=26751667…

    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 92, Column 102: reference to entity "z" for which no system identifier could be generated
    …&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=26751667…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 93, Column 94: reference not terminated by REFC delimiter
    …s"/>&nbsp;<a href="s?k=Anne Hathaway&z=1005&amp;frm=index.html&amp;bu=26751667…

    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 93, Column 94: reference to external entity in attribute value
    …s"/>&nbsp;<a href="s?k=Anne Hathaway&z=1005&amp;frm=index.html&amp;bu=26751667…

    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 93, Column 94: reference to entity "z" for which no system identifier could be generated
    …s"/>&nbsp;<a href="s?k=Anne Hathaway&z=1005&amp;frm=index.html&amp;bu=26751667…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Error Line 96, Column 32: required attribute "alt" not specified
        <img src="/im/bullet.gif" />&nbsp;<a href="tchlist?channelid=7&z=20092&amp;…

    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 96, Column 69: reference not terminated by REFC delimiter
    …/>&nbsp;<a href="tchlist?channelid=7&z=20092&amp;frm=index.html&amp;bu=2675166…

    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 96, Column 69: reference to external entity in attribute value
    …/>&nbsp;<a href="tchlist?channelid=7&z=20092&amp;frm=index.html&amp;bu=2675166…

    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 96, Column 69: reference to entity "z" for which no system identifier could be generated
    …/>&nbsp;<a href="tchlist?channelid=7&z=20092&amp;frm=index.html&amp;bu=2675166…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Error Line 97, Column 32: required attribute "alt" not specified
        <img src="/im/bullet.gif" />&nbsp;<a href="tchlist?channelid=5&z=20093&amp;…

    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 97, Column 69: reference not terminated by REFC delimiter
    …/>&nbsp;<a href="tchlist?channelid=5&z=20093&amp;frm=index.html&amp;bu=2675166…

    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 97, Column 69: reference to external entity in attribute value
    …/>&nbsp;<a href="tchlist?channelid=5&z=20093&amp;frm=index.html&amp;bu=2675166…

    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 97, Column 69: reference to entity "z" for which no system identifier could be generated
    …/>&nbsp;<a href="tchlist?channelid=5&z=20093&amp;frm=index.html&amp;bu=2675166…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 108, Column 29: cannot generate system identifier for general entity "fid"
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…

    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 108, Column 29: general entity "fid" not defined and no default entity
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…

    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 108, Column 32: reference not terminated by REFC delimiter
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…

    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 108, Column 32: reference to external entity in attribute value
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…

    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 108, Column 32: reference to entity "fid" for which no system identifier could be generated
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…

    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 108, Column 28: entity was defined here
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…
  • Warning Line 108, Column 40: reference not terminated by REFC delimiter
    …p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…

    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 108, Column 40: reference to external entity in attribute value
    …p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…

    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 108, Column 40: reference to entity "z" for which no system identifier could be generated
    …p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 108, Column 46: cannot generate system identifier for general entity "nvar"
    …ref="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267516671…

    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 108, Column 46: general entity "nvar" not defined and no default entity
    …ref="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267516671…

    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 108, Column 50: reference not terminated by REFC delimiter
    …"w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 108, Column 50: reference to external entity in attribute value
    …"w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 108, Column 50: reference to entity "nvar" for which no system identifier could be generated
    …"w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 108, Column 45: entity was defined here
    …href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=26751667…
  • Warning Line 109, Column 33: reference not terminated by REFC delimiter
        <a href="w?cid=577292292&fid=45113&z=1008&nvar&amp;frm=index.html&amp;bu=26…

    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 109, Column 33: reference to external entity in attribute value
        <a href="w?cid=577292292&fid=45113&z=1008&nvar&amp;frm=index.html&amp;bu=26…

    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 109, Column 33: reference to entity "fid" for which no system identifier could be generated
        <a href="w?cid=577292292&fid=45113&z=1008&nvar&amp;frm=index.html&amp;bu=26…

    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 108, Column 28: entity was defined here
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…
  • Warning Line 109, Column 41: reference not terminated by REFC delimiter
    …  <a href="w?cid=577292292&fid=45113&z=1008&nvar&amp;frm=index.html&amp;bu=267…

    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 109, Column 41: reference to external entity in attribute value
    …  <a href="w?cid=577292292&fid=45113&z=1008&nvar&amp;frm=index.html&amp;bu=267…

    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 109, Column 41: reference to entity "z" for which no system identifier could be generated
    …  <a href="w?cid=577292292&fid=45113&z=1008&nvar&amp;frm=index.html&amp;bu=267…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 109, Column 51: reference not terminated by REFC delimiter
    …"w?cid=577292292&fid=45113&z=1008&nvar&amp;frm=index.html&amp;bu=2675166719">T…

    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 109, Column 51: reference to external entity in attribute value
    …"w?cid=577292292&fid=45113&z=1008&nvar&amp;frm=index.html&amp;bu=2675166719">T…

    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 109, Column 51: reference to entity "nvar" for which no system identifier could be generated
    …"w?cid=577292292&fid=45113&z=1008&nvar&amp;frm=index.html&amp;bu=2675166719">T…

    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 108, Column 45: entity was defined here
    …href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=26751667…
  • Warning Line 110, Column 36: reference not terminated by REFC delimiter
        <p><a href="w?cid=572231531&fid=45118&z=1009&nvar&amp;frm=index.html&amp;bu…

    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 110, Column 36: reference to external entity in attribute value
        <p><a href="w?cid=572231531&fid=45118&z=1009&nvar&amp;frm=index.html&amp;bu…

    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 110, Column 36: reference to entity "fid" for which no system identifier could be generated
        <p><a href="w?cid=572231531&fid=45118&z=1009&nvar&amp;frm=index.html&amp;bu…

    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 108, Column 28: entity was defined here
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…
  • Warning Line 110, Column 44: reference not terminated by REFC delimiter
    …p><a href="w?cid=572231531&fid=45118&z=1009&nvar&amp;frm=index.html&amp;bu=267…

    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 110, Column 44: reference to external entity in attribute value
    …p><a href="w?cid=572231531&fid=45118&z=1009&nvar&amp;frm=index.html&amp;bu=267…

    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 110, Column 44: reference to entity "z" for which no system identifier could be generated
    …p><a href="w?cid=572231531&fid=45118&z=1009&nvar&amp;frm=index.html&amp;bu=267…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 110, Column 54: reference not terminated by REFC delimiter
    …"w?cid=572231531&fid=45118&z=1009&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 110, Column 54: reference to external entity in attribute value
    …"w?cid=572231531&fid=45118&z=1009&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 110, Column 54: reference to entity "nvar" for which no system identifier could be generated
    …"w?cid=572231531&fid=45118&z=1009&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 108, Column 45: entity was defined here
    …href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=26751667…
  • Warning Line 111, Column 33: reference not terminated by REFC delimiter
        <a href="w?cid=572231531&fid=45118&z=1010&nvar&amp;frm=index.html&amp;bu=26…

    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 111, Column 33: reference to external entity in attribute value
        <a href="w?cid=572231531&fid=45118&z=1010&nvar&amp;frm=index.html&amp;bu=26…

    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 111, Column 33: reference to entity "fid" for which no system identifier could be generated
        <a href="w?cid=572231531&fid=45118&z=1010&nvar&amp;frm=index.html&amp;bu=26…

    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 108, Column 28: entity was defined here
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…
  • Warning Line 111, Column 41: reference not terminated by REFC delimiter
    …  <a href="w?cid=572231531&fid=45118&z=1010&nvar&amp;frm=index.html&amp;bu=267…

    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 111, Column 41: reference to external entity in attribute value
    …  <a href="w?cid=572231531&fid=45118&z=1010&nvar&amp;frm=index.html&amp;bu=267…

    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 111, Column 41: reference to entity "z" for which no system identifier could be generated
    …  <a href="w?cid=572231531&fid=45118&z=1010&nvar&amp;frm=index.html&amp;bu=267…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 111, Column 51: reference not terminated by REFC delimiter
    …"w?cid=572231531&fid=45118&z=1010&nvar&amp;frm=index.html&amp;bu=2675166719">W…

    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 111, Column 51: reference to external entity in attribute value
    …"w?cid=572231531&fid=45118&z=1010&nvar&amp;frm=index.html&amp;bu=2675166719">W…

    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 111, Column 51: reference to entity "nvar" for which no system identifier could be generated
    …"w?cid=572231531&fid=45118&z=1010&nvar&amp;frm=index.html&amp;bu=2675166719">W…

    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 108, Column 45: entity was defined here
    …href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=26751667…
  • Warning Line 112, Column 36: reference not terminated by REFC delimiter
        <p><a href="w?cid=578660756&fid=45119&z=1011&nvar&amp;frm=index.html&amp;bu…

    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 112, Column 36: reference to external entity in attribute value
        <p><a href="w?cid=578660756&fid=45119&z=1011&nvar&amp;frm=index.html&amp;bu…

    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 112, Column 36: reference to entity "fid" for which no system identifier could be generated
        <p><a href="w?cid=578660756&fid=45119&z=1011&nvar&amp;frm=index.html&amp;bu…

    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 108, Column 28: entity was defined here
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…
  • Warning Line 112, Column 44: reference not terminated by REFC delimiter
    …p><a href="w?cid=578660756&fid=45119&z=1011&nvar&amp;frm=index.html&amp;bu=267…

    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 112, Column 44: reference to external entity in attribute value
    …p><a href="w?cid=578660756&fid=45119&z=1011&nvar&amp;frm=index.html&amp;bu=267…

    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 112, Column 44: reference to entity "z" for which no system identifier could be generated
    …p><a href="w?cid=578660756&fid=45119&z=1011&nvar&amp;frm=index.html&amp;bu=267…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 112, Column 54: reference not terminated by REFC delimiter
    …"w?cid=578660756&fid=45119&z=1011&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 112, Column 54: reference to external entity in attribute value
    …"w?cid=578660756&fid=45119&z=1011&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 112, Column 54: reference to entity "nvar" for which no system identifier could be generated
    …"w?cid=578660756&fid=45119&z=1011&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 108, Column 45: entity was defined here
    …href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=26751667…
  • Warning Line 113, Column 33: reference not terminated by REFC delimiter
        <a href="w?cid=578660756&fid=45119&z=1012&nvar&amp;frm=index.html&amp;bu=26…

    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 113, Column 33: reference to external entity in attribute value
        <a href="w?cid=578660756&fid=45119&z=1012&nvar&amp;frm=index.html&amp;bu=26…

    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 113, Column 33: reference to entity "fid" for which no system identifier could be generated
        <a href="w?cid=578660756&fid=45119&z=1012&nvar&amp;frm=index.html&amp;bu=26…

    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 108, Column 28: entity was defined here
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…
  • Warning Line 113, Column 41: reference not terminated by REFC delimiter
    …  <a href="w?cid=578660756&fid=45119&z=1012&nvar&amp;frm=index.html&amp;bu=267…

    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 113, Column 41: reference to external entity in attribute value
    …  <a href="w?cid=578660756&fid=45119&z=1012&nvar&amp;frm=index.html&amp;bu=267…

    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 113, Column 41: reference to entity "z" for which no system identifier could be generated
    …  <a href="w?cid=578660756&fid=45119&z=1012&nvar&amp;frm=index.html&amp;bu=267…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 113, Column 51: reference not terminated by REFC delimiter
    …"w?cid=578660756&fid=45119&z=1012&nvar&amp;frm=index.html&amp;bu=2675166719">G…

    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 113, Column 51: reference to external entity in attribute value
    …"w?cid=578660756&fid=45119&z=1012&nvar&amp;frm=index.html&amp;bu=2675166719">G…

    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 113, Column 51: reference to entity "nvar" for which no system identifier could be generated
    …"w?cid=578660756&fid=45119&z=1012&nvar&amp;frm=index.html&amp;bu=2675166719">G…

    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 108, Column 45: entity was defined here
    …href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=26751667…
  • Warning Line 114, Column 36: reference not terminated by REFC delimiter
        <p><a href="w?cid=578316499&fid=45116&z=1044&nvar&amp;frm=index.html&amp;bu…

    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 114, Column 36: reference to external entity in attribute value
        <p><a href="w?cid=578316499&fid=45116&z=1044&nvar&amp;frm=index.html&amp;bu…

    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 114, Column 36: reference to entity "fid" for which no system identifier could be generated
        <p><a href="w?cid=578316499&fid=45116&z=1044&nvar&amp;frm=index.html&amp;bu…

    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 108, Column 28: entity was defined here
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…
  • Warning Line 114, Column 44: reference not terminated by REFC delimiter
    …p><a href="w?cid=578316499&fid=45116&z=1044&nvar&amp;frm=index.html&amp;bu=267…

    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 114, Column 44: reference to external entity in attribute value
    …p><a href="w?cid=578316499&fid=45116&z=1044&nvar&amp;frm=index.html&amp;bu=267…

    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 114, Column 44: reference to entity "z" for which no system identifier could be generated
    …p><a href="w?cid=578316499&fid=45116&z=1044&nvar&amp;frm=index.html&amp;bu=267…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 114, Column 54: reference not terminated by REFC delimiter
    …"w?cid=578316499&fid=45116&z=1044&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 114, Column 54: reference to external entity in attribute value
    …"w?cid=578316499&fid=45116&z=1044&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 114, Column 54: reference to entity "nvar" for which no system identifier could be generated
    …"w?cid=578316499&fid=45116&z=1044&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 108, Column 45: entity was defined here
    …href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=26751667…
  • Warning Line 115, Column 33: reference not terminated by REFC delimiter
        <a href="w?cid=578316499&fid=45116&z=1045&nvar&amp;frm=index.html&amp;bu=26…

    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 115, Column 33: reference to external entity in attribute value
        <a href="w?cid=578316499&fid=45116&z=1045&nvar&amp;frm=index.html&amp;bu=26…

    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 115, Column 33: reference to entity "fid" for which no system identifier could be generated
        <a href="w?cid=578316499&fid=45116&z=1045&nvar&amp;frm=index.html&amp;bu=26…

    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 108, Column 28: entity was defined here
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…
  • Warning Line 115, Column 41: reference not terminated by REFC delimiter
    …  <a href="w?cid=578316499&fid=45116&z=1045&nvar&amp;frm=index.html&amp;bu=267…

    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 115, Column 41: reference to external entity in attribute value
    …  <a href="w?cid=578316499&fid=45116&z=1045&nvar&amp;frm=index.html&amp;bu=267…

    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 115, Column 41: reference to entity "z" for which no system identifier could be generated
    …  <a href="w?cid=578316499&fid=45116&z=1045&nvar&amp;frm=index.html&amp;bu=267…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 115, Column 51: reference not terminated by REFC delimiter
    …"w?cid=578316499&fid=45116&z=1045&nvar&amp;frm=index.html&amp;bu=2675166719">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 115, Column 51: reference to external entity in attribute value
    …"w?cid=578316499&fid=45116&z=1045&nvar&amp;frm=index.html&amp;bu=2675166719">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 115, Column 51: reference to entity "nvar" for which no system identifier could be generated
    …"w?cid=578316499&fid=45116&z=1045&nvar&amp;frm=index.html&amp;bu=2675166719">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 108, Column 45: entity was defined here
    …href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=26751667…
  • Warning Line 116, Column 36: reference not terminated by REFC delimiter
        <p><a href="w?cid=458669509&fid=45117&z=1046&nvar&amp;frm=index.html&amp;bu…

    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 116, Column 36: reference to external entity in attribute value
        <p><a href="w?cid=458669509&fid=45117&z=1046&nvar&amp;frm=index.html&amp;bu…

    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 116, Column 36: reference to entity "fid" for which no system identifier could be generated
        <p><a href="w?cid=458669509&fid=45117&z=1046&nvar&amp;frm=index.html&amp;bu…

    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 108, Column 28: entity was defined here
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…
  • Warning Line 116, Column 44: reference not terminated by REFC delimiter
    …p><a href="w?cid=458669509&fid=45117&z=1046&nvar&amp;frm=index.html&amp;bu=267…

    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 116, Column 44: reference to external entity in attribute value
    …p><a href="w?cid=458669509&fid=45117&z=1046&nvar&amp;frm=index.html&amp;bu=267…

    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 116, Column 44: reference to entity "z" for which no system identifier could be generated
    …p><a href="w?cid=458669509&fid=45117&z=1046&nvar&amp;frm=index.html&amp;bu=267…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 116, Column 54: reference not terminated by REFC delimiter
    …"w?cid=458669509&fid=45117&z=1046&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 116, Column 54: reference to external entity in attribute value
    …"w?cid=458669509&fid=45117&z=1046&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 116, Column 54: reference to entity "nvar" for which no system identifier could be generated
    …"w?cid=458669509&fid=45117&z=1046&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 108, Column 45: entity was defined here
    …href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=26751667…
  • Warning Line 117, Column 33: reference not terminated by REFC delimiter
        <a href="w?cid=458669509&fid=45117&z=1047&nvar&amp;frm=index.html&amp;bu=26…

    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 117, Column 33: reference to external entity in attribute value
        <a href="w?cid=458669509&fid=45117&z=1047&nvar&amp;frm=index.html&amp;bu=26…

    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 117, Column 33: reference to entity "fid" for which no system identifier could be generated
        <a href="w?cid=458669509&fid=45117&z=1047&nvar&amp;frm=index.html&amp;bu=26…

    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 108, Column 28: entity was defined here
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…
  • Warning Line 117, Column 41: reference not terminated by REFC delimiter
    …  <a href="w?cid=458669509&fid=45117&z=1047&nvar&amp;frm=index.html&amp;bu=267…

    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 117, Column 41: reference to external entity in attribute value
    …  <a href="w?cid=458669509&fid=45117&z=1047&nvar&amp;frm=index.html&amp;bu=267…

    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 117, Column 41: reference to entity "z" for which no system identifier could be generated
    …  <a href="w?cid=458669509&fid=45117&z=1047&nvar&amp;frm=index.html&amp;bu=267…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 117, Column 51: reference not terminated by REFC delimiter
    …"w?cid=458669509&fid=45117&z=1047&nvar&amp;frm=index.html&amp;bu=2675166719">P…

    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 117, Column 51: reference to external entity in attribute value
    …"w?cid=458669509&fid=45117&z=1047&nvar&amp;frm=index.html&amp;bu=2675166719">P…

    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 117, Column 51: reference to entity "nvar" for which no system identifier could be generated
    …"w?cid=458669509&fid=45117&z=1047&nvar&amp;frm=index.html&amp;bu=2675166719">P…

    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 108, Column 45: entity was defined here
    …href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=26751667…
  • Warning Line 118, Column 36: reference not terminated by REFC delimiter
        <p><a href="w?cid=578774108&fid=45114&z=1048&nvar&amp;frm=index.html&amp;bu…

    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 118, Column 36: reference to external entity in attribute value
        <p><a href="w?cid=578774108&fid=45114&z=1048&nvar&amp;frm=index.html&amp;bu…

    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 118, Column 36: reference to entity "fid" for which no system identifier could be generated
        <p><a href="w?cid=578774108&fid=45114&z=1048&nvar&amp;frm=index.html&amp;bu…

    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 108, Column 28: entity was defined here
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…
  • Warning Line 118, Column 44: reference not terminated by REFC delimiter
    …p><a href="w?cid=578774108&fid=45114&z=1048&nvar&amp;frm=index.html&amp;bu=267…

    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 118, Column 44: reference to external entity in attribute value
    …p><a href="w?cid=578774108&fid=45114&z=1048&nvar&amp;frm=index.html&amp;bu=267…

    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 118, Column 44: reference to entity "z" for which no system identifier could be generated
    …p><a href="w?cid=578774108&fid=45114&z=1048&nvar&amp;frm=index.html&amp;bu=267…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 118, Column 54: reference not terminated by REFC delimiter
    …"w?cid=578774108&fid=45114&z=1048&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 118, Column 54: reference to external entity in attribute value
    …"w?cid=578774108&fid=45114&z=1048&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 118, Column 54: reference to entity "nvar" for which no system identifier could be generated
    …"w?cid=578774108&fid=45114&z=1048&nvar&amp;frm=index.html&amp;bu=2675166719"><…

    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 108, Column 45: entity was defined here
    …href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=26751667…
  • Warning Line 119, Column 33: reference not terminated by REFC delimiter
        <a href="w?cid=578774108&fid=45114&z=1049&nvar&amp;frm=index.html&amp;bu=26…

    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 119, Column 33: reference to external entity in attribute value
        <a href="w?cid=578774108&fid=45114&z=1049&nvar&amp;frm=index.html&amp;bu=26…

    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 119, Column 33: reference to entity "fid" for which no system identifier could be generated
        <a href="w?cid=578774108&fid=45114&z=1049&nvar&amp;frm=index.html&amp;bu=26…

    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 108, Column 28: entity was defined here
    <p><a href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=267…
  • Warning Line 119, Column 41: reference not terminated by REFC delimiter
    …  <a href="w?cid=578774108&fid=45114&z=1049&nvar&amp;frm=index.html&amp;bu=267…

    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 119, Column 41: reference to external entity in attribute value
    …  <a href="w?cid=578774108&fid=45114&z=1049&nvar&amp;frm=index.html&amp;bu=267…

    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 119, Column 41: reference to entity "z" for which no system identifier could be generated
    …  <a href="w?cid=578774108&fid=45114&z=1049&nvar&amp;frm=index.html&amp;bu=267…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Warning Line 119, Column 51: reference not terminated by REFC delimiter
    …"w?cid=578774108&fid=45114&z=1049&nvar&amp;frm=index.html&amp;bu=2675166719">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 119, Column 51: reference to external entity in attribute value
    …"w?cid=578774108&fid=45114&z=1049&nvar&amp;frm=index.html&amp;bu=2675166719">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 119, Column 51: reference to entity "nvar" for which no system identifier could be generated
    …"w?cid=578774108&fid=45114&z=1049&nvar&amp;frm=index.html&amp;bu=2675166719">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 108, Column 45: entity was defined here
    …href="w?cid=577292292&fid=45113&z=1007&nvar&amp;frm=index.html&amp;bu=26751667…
  • Error Line 129, Column 56: there is no attribute "defaultValue"
    …ot.gif" alt="Hot Videos" defaultValue="What's Hot!" />&nbsp;<a href="f?f=18229…

    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 154, Column 78: end tag for element "P" which is not open
    |&nbsp;<a href="sl?z=1001&amp;frm=index.html&amp;bu=2675166719">Log in</a></P>

    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 155, Column 3: document type does not allow element "p" here; assuming missing "object" start-tag
    <p>
  • Warning Line 161, Column 45: reference not terminated by REFC delimiter
    …h&nbsp;l&nbsp;<a href="/locale?lid=2&z=1032&amp;frm=index.html&amp;bu=26751667…

    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 161, Column 45: reference to external entity in attribute value
    …h&nbsp;l&nbsp;<a href="/locale?lid=2&z=1032&amp;frm=index.html&amp;bu=26751667…

    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 161, Column 45: reference to entity "z" for which no system identifier could be generated
    …h&nbsp;l&nbsp;<a href="/locale?lid=2&z=1032&amp;frm=index.html&amp;bu=26751667…

    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 92, Column 100: entity was defined here
    …/>&nbsp;<a href="s?k=Pope Benedict XVI&z=1004&amp;frm=index.html&amp;bu=267516…
  • Error Line 166, Column 6: end tag for "object" omitted, but OMITTAG NO was specified
    </div><!-- footer end-->

    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 155, Column 1: start tag was here
    <p>
  • Error Line 166, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div><!-- footer end-->

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

  • Info Line 152, Column 1: start tag was here
    <p>	

Visitor Analysis

Daily Visitor
  • 6.067 visits