Insertar aviso La idea es simple Encuentra clasificados en tu región 700.174 avisos disponibles 5.682 productos vendidos en los últimos 7 días Es muy fácil encontrar lo que buscas Busca en tu región ...

yapo.cl
  • Domain Name
    yapo.cl
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #12365
  • Page Size
    15.2 KB
  • Ip Address
    190.215.46.4
  • Heading
    H1: 1, H2: 2, H3: 3, H4: 0, H5: 0, H6: 0
  • Images
    5 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Clasificados yapo.cl - Avisos Clasificados Gratis en Chile: Vehículos, Motos, Casas, Departamentos y otros productos.
  • Meta Keyword
  • Meta Description
    Insertar aviso La idea es simple Encuentra clasificados en tu región 700.174 avisos disponibles 5.682 productos vendidos en los últimos 7 días Es muy fácil encontrar lo que buscas Busca en tu región Contacta con el vendedor Haz un buen negocio ...

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    190.215.46.4
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from yapo.cl.

HTML Analysis

  • date: Thu, 28 Feb 2013 05:54:18 GMT
  • server: Apache
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • p3p: CP='NOI DSP COR PSAo PSDo'
  • content-length: 4061
  • connection: close
  • content-type: text/html; charset=ISO-8859-1
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: yapo.cl (RFC-3490, RFC-3491, RFC-3492)
SCM Ventures AB (CLICMAGIC S A)
Contacto Administrativo (Administrative Contact):
Nombre : Domaininfo Registry
Organización: Domaininfo Ab
Contacto Técnico (Technical Contact):
Nombre : Domaininfo Registry
Organización: Domaininfo Ab
Name Servers:
edns01.ports.net (193.12.211.140)
edns03.ports.net (217.28.206.27)

Updated: 11 de marzo de 2011 (15:30:34 GMT)
Más información (More information):
http://www.nic.cl/cgi-bin/dom-CL?q=yapo
Este mensajes está impreso en ISO-8859-1
(This message is printed in ISO-8859-1)

DNS Analysis


DNS servers
secundario.nic.cl [200.7.5.7]
svr-03.creativa.cl
host-c9eee709.hc.creativa.cl [201.238.231.9]
svr-01.creativa.cl
svr-02.creativa.cl


DNS Records

Answer records
yapo.cl SOA
server: svr-01.creativa.cl
email: hostmaster@excedo.se
serial: 2012101401
refresh: 300
retry: 600
expire: 604800
minimum ttl: 300
300s
yapo.cl NS  svr-02.creativa.cl 86400s
yapo.cl NS  svr-01.creativa.cl 86400s
yapo.cl NS  host-c9eee709.hc.creativa.cl 86400s
yapo.cl NS  secundario.nic.cl 86400s
yapo.cl NS  svr-03.creativa.cl 86400s
yapo.cl A 190.215.46.4 300s
yapo.cl MX
preference: 20
exchange: ALT1.ASPMX.L.GOOGLE.COM
300s
yapo.cl MX
preference: 10
exchange: ASPMX.L.GOOGLE.COM
300s
yapo.cl MX
preference: 30
exchange: ASPMX5.GOOGLEMAIL.COM
300s
yapo.cl MX
preference: 30
exchange: ASPMX4.GOOGLEMAIL.COM
300s
yapo.cl MX
preference: 30
exchange: ASPMX3.GOOGLEMAIL.COM
300s
yapo.cl MX
preference: 30
exchange: ASPMX2.GOOGLEMAIL.COM
300s
yapo.cl MX
preference: 20
exchange: ALT2.ASPMX.L.GOOGLE.COM
300s

Authority records

Additional records
svr-01.creativa.cl A 190.196.9.122 300s
svr-02.creativa.cl A 190.196.9.123 300s
svr-03.creativa.cl A 190.196.9.124 300s
host-c9eee709.hc.creativa.cl A 201.238.231.9 300s
secundario.nic.cl A 200.7.5.7 38498s
ASPMX.L.GOOGLE.COM A 74.125.134.26 21s

IP 190.215.46.4 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 35 Errors
  • 10 Warnings
Ratio Text/Html
  • 0.8237712817218117
Message Error
  • Warning Line 6, Column 60: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 6, Column 61: character data is not allowed here
    <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 28, Column 8: 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 28, Column 8: document type does not allow element "STYLE" here
    	<style>

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

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

  • Warning Line 36, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …mg src="/img/transparent.gif" class="sprite-logo_new logo sprite-background" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 36, Column 80: required attribute "ALT" not specified
    …mg src="/img/transparent.gif" class="sprite-logo_new logo sprite-background" />

    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 50, Column 83: required attribute "ALT" not specified
    …ss="sprite-square_1 sprite-background"><strong class="OrangeText">Busca</stron…

    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 51, Column 83: required attribute "ALT" not specified
    …ss="sprite-square_2 sprite-background"><strong class="OrangeText">Contacta</st…

    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 52, Column 83: required attribute "ALT" not specified
    …ss="sprite-square_3 sprite-background"><strong class="OrangeText">Haz un buen …

    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 102, Column 408: required attribute "ALT" not specified
    …efault_ca('15_s', '.yapo.cl');" href="http://www.yapo.cl/region_metropolitana">

    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 103, Column 327: required attribute "ALT" not specified
    …set_default_ca('1_s', '.yapo.cl');" href="http://www.yapo.cl/arica_parinacota">

    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 104, Column 356: required attribute "ALT" not specified
    …artpage_set_default_ca('2_s', '.yapo.cl');" href="http://www.yapo.cl/tarapaca">

    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 105, Column 432: required attribute "ALT" not specified
    …page_set_default_ca('3_s', '.yapo.cl');" href="http://www.yapo.cl/antofagasta">

    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 106, Column 369: required attribute "ALT" not specified
    …tartpage_set_default_ca('4_s', '.yapo.cl');" href="http://www.yapo.cl/atacama">

    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 107, Column 403: required attribute "ALT" not specified
    …artpage_set_default_ca('5_s', '.yapo.cl');" href="http://www.yapo.cl/coquimbo">

    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 108, Column 367: required attribute "ALT" not specified
    …tpage_set_default_ca('6_s', '.yapo.cl');" href="http://www.yapo.cl/valparaiso">

    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 109, Column 363: required attribute "ALT" not specified
    …artpage_set_default_ca('7_s', '.yapo.cl');" href="http://www.yapo.cl/ohiggins">

    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 110, Column 373: required attribute "ALT" not specified
    … startpage_set_default_ca('8_s', '.yapo.cl');" href="http://www.yapo.cl/maule">

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

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

  • Error Line 111, Column 413: required attribute "ALT" not specified
    …startpage_set_default_ca('9_s', '.yapo.cl');" href="http://www.yapo.cl/biobio">

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

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

  • Error Line 112, Column 382: required attribute "ALT" not specified
    …tpage_set_default_ca('10_s', '.yapo.cl');" href="http://www.yapo.cl/araucania">

    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 113, Column 365: required attribute "ALT" not specified
    …rtpage_set_default_ca('11_s', '.yapo.cl');" href="http://www.yapo.cl/los_rios">

    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 114, Column 413: required attribute "ALT" not specified
    …tpage_set_default_ca('12_s', '.yapo.cl');" href="http://www.yapo.cl/los_lagos">

    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 115, Column 536: required attribute "ALT" not specified
    …startpage_set_default_ca('13_s', '.yapo.cl');" href="http://www.yapo.cl/aisen">

    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 116, Column 651: required attribute "ALT" not specified
    …efault_ca('14_s', '.yapo.cl');" href="http://www.yapo.cl/magallanes_antartica">

    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 140, Column 8: required attribute "TYPE" not specified
    <script>document.body.oncopy=function(){var ytw=document; if(!('yti' in ytw)) y…

    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 167, Column 8: NET-enabling start-tag requires SHORTTAG YES
        <br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 168, Column 8: NET-enabling start-tag requires SHORTTAG YES
        <br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 200, Column 69: cannot generate system identifier for general entity "s2"
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

    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 200, Column 69: general entity "s2" not defined and no default entity
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

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

  • Error Line 200, Column 71: reference to entity "s2" for which no system identifier could be generated
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

    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 200, Column 68: entity was defined here
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />
  • Warning Line 200, Column 74: cannot generate system identifier for general entity "p"
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

    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 200, Column 74: general entity "p" not defined and no default entity
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

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

  • Error Line 200, Column 75: reference to entity "p" for which no system identifier could be generated
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

    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 200, Column 73: entity was defined here
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />
  • Warning Line 200, Column 86: cannot generate system identifier for general entity "di"
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

    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 200, Column 86: general entity "di" not defined and no default entity
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

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

  • Error Line 200, Column 88: reference to entity "di" for which no system identifier could be generated
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

    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 200, Column 85: entity was defined here
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />
  • Warning Line 200, Column 90: cannot generate system identifier for general entity "ac"
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

    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 200, Column 90: general entity "ac" not defined and no default entity
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

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

  • Error Line 200, Column 92: reference to entity "ac" for which no system identifier could be generated
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

    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 200, Column 89: entity was defined here
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />
  • Warning Line 200, Column 94: cannot generate system identifier for general entity "an"
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

    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 200, Column 94: general entity "an" not defined and no default entity
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

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

  • Error Line 200, Column 96: reference to entity "an" for which no system identifier could be generated
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

    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 200, Column 93: entity was defined here
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />
  • Warning Line 200, Column 100: NET-enabling start-tag requires SHORTTAG YES
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 200, Column 100: required attribute "ALT" not specified
    …="1" src="http://logc213.xiti.com/hit.xiti?s=&s2=1&p=Home_page&di=&ac=&an=&" />

    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 212, Column 7: end tag for "DIV" omitted, but its declaration does not permit this
    </body>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 35, Column 1: start tag was here
    <div class="Container">

Visitor Analysis

Daily Visitor
  • 11.900 visits
Daily Visitor