ibercajadirecto.com

9 Julio 2013 ESTAMOS A SU SERVICIO Consultas Ibercaja Directo Particulares Negocios Teléfonos de Interés Información General Tarjetas Banca a Distancia Otros Red de Cajeros y Oficinas Su oficina más cercana El teléfono ...

Display Widget for this domain on your website. Click Here
This data was last updated from 09-07-2013 12:18:24  (update).

Overview Info

  • Domain Name
    ibercajadirecto.com
  • Favicon
  • Alexa Rank
    #23318
  • Google Page Rank
    PR 0
  • Ip Address
    81.95.64.1
  • Page Size
    34.1 KB
  • Images
    4 GIF, 0 JPG, 9 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    Acceso a la banca online de Ibercaja
  • Meta Keyword
  • Meta Description
    9 Julio 2013 ESTAMOS A SU SERVICIO Consultas Ibercaja Directo Particulares Negocios Teléfonos de Interés Información General Tarjetas Banca a Distancia Otros Red de Cajeros y Oficinas Su oficina más cercana El teléfono de su oficina Cajeros ...

Technical Analysis



  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    81.95.64.1
  • Domain Age
    12 Years, 9 Months, 19 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 09 Jul 2013 12:18:18 GMT
  • server: Microsoft-IIS/6.0
  • pragma: no-cache
  • content-length: 31725
  • content-type: text/html
  • expires: Wed, 10 Jul 2013 12:18:18 GMT
  • cache-control: Private
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: ibercajadirecto.com
Created: 26/09/2000
Expires: 26/09/2015
Updated: 26/12/2009
Organization Contact Id.... PROP-1180-00154927
Organization Name........ Caja de Ahorros de Zaragoza ,Aragon y Rioja
Organization Org......... Caja de Ahorros de Zaragoza ,Aragon y Rioja
Organization Street...... Plaza Basilio Paraiso 2
Organization City........ Zaragoza
Organization State....... Zaragoza
Organization PC.......... E-50008
Organization Country..... ES
Organization Phone....... +34. 976767800
Organization Fax......... +34.97676010
Organization e-mail...... email
Administrative Contact Id.. 16104-00167305
Administrative Name...... Jos? Antonio Lapaz Calvo
Administrative Org....... Caja de Ahorros y Monte de Piedad de Zaragoza, Arag?n y Rioja
Administrative Street.... Plaza Basilio Para?so, 2
Administrative City...... Zaragoza
Administrative State..... Zaragoza
Administrative PC........ 50008
Administrative Country... ES
Administrative Phone..... +34.976767655
Administrative Fax....... +34.976767783
Administrative e-mail.... email
Technical Contact Id....... 4248-00044919
Technical Name........... RESPONSABLE DE DNS
Technical Org............ TELEFONICA SERVICIOS Y CONTENIDOS POR LA RED, S.A.
Technical Street......... JULIAN CAMARILLO, 6
Technical City........... MADRID
Technical State.......... MADRID
Technical PC............. 28013
Technical Country........ ES
Technical Phone.......... +34.913752300
Technical Fax............
Technical e-mail......... email
Domain servers in listed order:
Name Servers: MINERVA.TTD.NET
Name Servers: ARTEMIS.TTD.NET
Name Servers:
Name Servers:
Name Servers:
Name Servers:

Interdomain's WHOIS database is provided by Interdomain for information
purposes only, proving information about or related to a domain name
registration record.
Interdomain makes this information available "as is," and does not guarantee
its accuracy.
By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
(1) allow, enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic mail, or
by telephone; or (2) enable high volume, automated, electronic processes that
apply to Interdomain (or its systems). The compilation, repackaging,
dissemination or other use of this data is expressly prohibited without the
prior written consent of Interdomain.
Interdomain reserves the right to terminate your access to the Interdomain's
WHOIS database in its sole discretion, including without limitation, for excessive
querying of the WHOIS database or for failure to otherwise abide by this policy.
Interdomain reserves the right to modify these terms at any time. By
submitting this query, you agree to abide by these terms.
NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY. LACK OF A DOMAIN RECORD
DOES NOT SIGNIFY DOMAIN AVAILABILITY.

IP 81.95.64.1 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 48 Errors
  • 37 Warnings
Ratio Text/Html
  • 0.48233878591686485
Message Error
  • Warning Line 7, Column 59: 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 7, Column 60: 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 17, Column 8: required attribute "TYPE" not specified
    <script>

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

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

  • Warning Line 324, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …nk rel="stylesheet" href="../css/jquery-ui.css" type="text/css" media="all" /> 

    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 325, Column 7: end tag for element "HEAD" which is not open
    </head>

    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 326, Column 52: there is no attribute "SCROLL"
    …background-color:transparent;" scroll="auto" onload="createKeyboards();ajustaP…

    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 326, Column 103: document type does not allow element "BODY" here
    …color:transparent;" scroll="auto" onload="createKeyboards();ajustaPantalla();">

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

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

  • Error Line 327, Column 68: there is no attribute "AUTOCOMPLETE"
    …name="Formulario" method="post" autocomplete="off" action="Modulodirector.asp">

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

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

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

  • Warning Line 354, Column 73: NET-enabling start-tag requires SHORTTAG YES
    						<a href="/ibercaja/"><img src="../images/logo_directo2.png" alt=""/></a>

    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 357, Column 35: there is no attribute "NAME"
    					<center><div id="fecha" name="fecha">31 Enero 2013</div></center>

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

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

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

  • Warning Line 361, Column 89: NET-enabling start-tag requires SHORTTAG YES
    …gan"><a href="#"><img src="../images/pajarico.png" alt="" height="35px"/></div>

    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 361, Column 96: end tag for "A" omitted, but its declaration does not permit this
    …gan"><a href="#"><img src="../images/pajarico.png" alt="" height="35px"/></div>
    • 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 361, Column 23: start tag was here
    					<div id="slogan"><a href="#"><img src="../images/pajarico.png" alt="" heig…
  • Warning Line 365, Column 68: NET-enabling start-tag requires SHORTTAG YES
    …<img src="../images/reloj.png" alt="" /><!--<img src="../imagenes/NuevoFormato…

    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 370, Column 47: ID "MENUTOP" already defined
    			<!-- menutop --><div id="menutop"><div id="menutop">

    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 370, Column 29: ID "MENUTOP" first defined here
    			<!-- menutop --><div id="menutop"><div id="menutop">
  • Warning Line 378, Column 86: NET-enabling start-tag requires SHORTTAG YES
    …erior.php">--><img src="../images/bann1cortado.png"  usemap="#map"/><!--</a>-->

    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 378, Column 86: required attribute "ALT" not specified
    …erior.php">--><img src="../images/bann1cortado.png"  usemap="#map"/><!--</a>-->

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

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

  • Warning Line 380, Column 170: NET-enabling start-tag requires SHORTTAG YES
    …ja.es/formularios/ibercajadirecto/solicitud_alta_ibd.php?home=1', 650, 600)" />

    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 380, Column 170: required attribute "ALT" not specified
    …ja.es/formularios/ibercajadirecto/solicitud_alta_ibd.php?home=1', 650, 600)" />

    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 380, Column 171: character data is not allowed here
    …ja.es/formularios/ibercajadirecto/solicitud_alta_ibd.php?home=1', 650, 600)" />

    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.
  • Warning Line 381, Column 120: NET-enabling start-tag requires SHORTTAG YES
    …5" href="javascript:createPopup('../Html/IncidenciasClaves.html', 700, 500)" />

    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 381, Column 120: required attribute "ALT" not specified
    …5" href="javascript:createPopup('../Html/IncidenciasClaves.html', 700, 500)" />

    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 382, Column 171: NET-enabling start-tag requires SHORTTAG YES
    …rcaja.es/formularios/ibercajadirecto/solicitud_contacta_ibd.php', 650, 400)" />

    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 382, Column 171: required attribute "ALT" not specified
    …rcaja.es/formularios/ibercajadirecto/solicitud_contacta_ibd.php', 650, 400)" />

    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 383, Column 171: NET-enabling start-tag requires SHORTTAG YES
    …rcaja.es/formularios/ibercajadirecto/solicitud_contacta_ibd.php', 650, 400)" />

    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 383, Column 171: required attribute "ALT" not specified
    …rcaja.es/formularios/ibercajadirecto/solicitud_contacta_ibd.php', 650, 400)" />

    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 384, Column 118: NET-enabling start-tag requires SHORTTAG YES
    …,261" href="javascript:createPopup('../Html/recomendacionesSeguridad.html')" />

    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 384, Column 118: required attribute "ALT" not specified
    …,261" href="javascript:createPopup('../Html/recomendacionesSeguridad.html')" />

    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 385, Column 158: NET-enabling start-tag requires SHORTTAG YES
    …://play.google.com/store/apps/details?id=es.ibercaja.ibercajaapp',1024,768)" />

    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 385, Column 158: required attribute "ALT" not specified
    …://play.google.com/store/apps/details?id=es.ibercaja.ibercajaapp',1024,768)" />

    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 386, Column 135: cannot generate system identifier for general entity "ls"
    …tp://itunes.apple.com/us/app/ibercaja/id515972019?l=es&ls=1&mt=8',1024,768)" />

    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 386, Column 135: general entity "ls" not defined and no default entity
    …tp://itunes.apple.com/us/app/ibercaja/id515972019?l=es&ls=1&mt=8',1024,768)" />

    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 386, Column 137: reference to entity "ls" for which no system identifier could be generated
    …tp://itunes.apple.com/us/app/ibercaja/id515972019?l=es&ls=1&mt=8',1024,768)" />

    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 386, Column 134: entity was defined here
    …tp://itunes.apple.com/us/app/ibercaja/id515972019?l=es&ls=1&mt=8',1024,768)" />
  • Warning Line 386, Column 140: cannot generate system identifier for general entity "mt"
    …tp://itunes.apple.com/us/app/ibercaja/id515972019?l=es&ls=1&mt=8',1024,768)" />

    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 386, Column 140: general entity "mt" not defined and no default entity
    …tp://itunes.apple.com/us/app/ibercaja/id515972019?l=es&ls=1&mt=8',1024,768)" />

    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 386, Column 142: reference to entity "mt" for which no system identifier could be generated
    …tp://itunes.apple.com/us/app/ibercaja/id515972019?l=es&ls=1&mt=8',1024,768)" />

    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 386, Column 139: entity was defined here
    …tp://itunes.apple.com/us/app/ibercaja/id515972019?l=es&ls=1&mt=8',1024,768)" />
  • Warning Line 386, Column 157: NET-enabling start-tag requires SHORTTAG YES
    …tp://itunes.apple.com/us/app/ibercaja/id515972019?l=es&ls=1&mt=8',1024,768)" />

    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 386, Column 157: required attribute "ALT" not specified
    …tp://itunes.apple.com/us/app/ibercaja/id515972019?l=es&ls=1&mt=8',1024,768)" />

    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 392, Column 150: required attribute "TYPE" not specified
    …om&amp;size=M&amp;use_flash=YES&amp;use_transparent=NO&amp;lang=es"></script>		

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

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

  • Warning Line 399, Column 231: NET-enabling start-tag requires SHORTTAG YES
    …ario de Solicitud',800);" class="underline">Consultas Ibercaja Directo</a><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 409, Column 54: NET-enabling start-tag requires SHORTTAG YES
    					  <img src="../images/icoRedCajeros.png" alt="" /><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 409, Column 59: NET-enabling start-tag requires SHORTTAG YES
    					  <img src="../images/icoRedCajeros.png" alt="" /><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 410, Column 185: NET-enabling start-tag requires SHORTTAG YES
    …nas/oficinas.php?ibd=1');" class="underline">Red de Cajeros y Oficinas</a><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 411, Column 33: NET-enabling start-tag requires SHORTTAG YES
    					  Su oficina más cercana<br/>El teléfono de su oficina<br/>Cajeros con ven…

    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 411, Column 63: NET-enabling start-tag requires SHORTTAG YES
    …ina más cercana<br/>El teléfono de su oficina<br/>Cajeros con venta de entradas

    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 418, Column 77: there is no attribute "ALLOWTRANSPARENCY"
    …"#" scrolling="yes" allowtransparency="true" marginwidth="0" marginheight="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 418, Column 140: there is no attribute "VSPACE"
    …rginheight="0" frameborder="0" vspace="0" hspace="0" style="border-top-width: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 418, Column 151: there is no attribute "HSPACE"
    …"0" frameborder="0" vspace="0" hspace="0" style="border-top-width:0px;border-t…

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

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

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

  • Warning Line 422, Column 178: NET-enabling start-tag requires SHORTTAG YES
    …le="display: block; top: 36px; left: 626px; position: absolute; cursor:hand;"/>

    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 430, Column 167: NET-enabling start-tag requires SHORTTAG YES
    …inas();" style="display: block; top: 57px; left: 626px; position: absolute; "/>

    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 447, Column 42: there is no attribute "TABINDEX"
    … <li class="TabbedPanelsTab" tabindex="0" onclick="javascript:cambiar_estilo('…

    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 450, Column 88: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …:visualizar_texto('ibd');" href="#"><p>Acceso <br/><font size="2px">Ibercaja D…

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

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

  • Warning Line 450, Column 99: NET-enabling start-tag requires SHORTTAG YES
    …_texto('ibd');" href="#"><p>Acceso <br/><font size="2px">Ibercaja Directo</fon…

    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 453, Column 9: end tag for "DIV" omitted, but its declaration does not permit this
        </li>
    • 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 452, Column 9: start tag was here
            <div id="capaibdend" class="TabbedPanelsTabSelectedEnd" style="width:6p…
  • Error Line 457, Column 20: ID "APARTADOS" already defined
                <a id="apartados" onclick="javascript:visualizar_texto('tar');" hre…

    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 450, Column 20: ID "APARTADOS" first defined here
                <a id="apartados" onclick="javascript:visualizar_texto('ibd');" hre…
  • Error Line 457, Column 88: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …:visualizar_texto('tar');" href="#"><p>Acceso<br/><font size="2px">Tarjetas</f…

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

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

  • Warning Line 457, Column 98: NET-enabling start-tag requires SHORTTAG YES
    …r_texto('tar');" href="#"><p>Acceso<br/><font size="2px">Tarjetas</font></p></…

    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 460, Column 10: end tag for "DIV" omitted, but its declaration does not permit this
         </li>
    • 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 459, Column 8: start tag was here
           <div id="capatarjetasend" class="" style="width:6px;display:block;">
  • Error Line 464, Column 20: ID "APARTADOS" already defined
                <a id="apartados" onclick="javascript:visualizar_textoDNIE();" href…

    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 450, Column 20: ID "APARTADOS" first defined here
                <a id="apartados" onclick="javascript:visualizar_texto('ibd');" hre…
  • Error Line 464, Column 87: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …t:visualizar_textoDNIE();" href="#"><p>Acceso <br/><font size="2px">DNI electr…

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

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

  • Warning Line 464, Column 98: NET-enabling start-tag requires SHORTTAG YES
    …r_textoDNIE();" href="#"><p>Acceso <br/><font size="2px">DNI electr&oacute;nic…

    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 467, Column 10: end tag for "DIV" omitted, but its declaration does not permit this
         </li>
    • 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 466, Column 3: start tag was here
    		<div id="capadnieend" class="" style="width:6px;display:block;">
  • Warning Line 477, Column 61: NET-enabling start-tag requires SHORTTAG YES
    								  <p>C&oacute;digo Identificaci&oacute;n Usuario <br/><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 477, Column 66: NET-enabling start-tag requires SHORTTAG YES
    								  <p>C&oacute;digo Identificaci&oacute;n Usuario <br/><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 481, Column 12: 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.

  • Error Line 482, Column 119: there is no attribute "AUTOCOMPLETE"
    …e="codeibd" id="codeibd" autocomplete="off" onfocus='determinarFocus("codeibd"…

    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 482, Column 161: character ";" not allowed in attribute specification list
    …d" id="codeibd" autocomplete="off" onfocus='determinarFocus("codeibd")';></div>
  • Error Line 483, Column 177: character ";" not allowed in attribute specification list
    … id="claveibd" autocomplete="off" onfocus='determinarFocus("claveibd")';></div>
  • Error Line 491, Column 16: ID "AYUDAACCESO" already defined
    								<a id="ayudaacceso" style="font-size:10px;" href="javascript:createPopu…

    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 490, Column 16: ID "AYUDAACCESO" first defined here
    								<a id="ayudaacceso" style="font-size:10px;" href="javascript:createPopu…
  • Error Line 502, Column 9: end tag for "CENTER" omitted, but its declaration does not permit this
    			</div>
    • 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 497, Column 5: start tag was here
    				<center>
  • Error Line 511, Column 14: ID "ACCESOFORM" already defined
    				<div id="accesoform" style="padding:20px;height:95px;">

    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 474, Column 14: ID "ACCESOFORM" first defined here
    				<div id="accesoform" style="padding:20px;height:95px;">
  • Warning Line 514, Column 35: NET-enabling start-tag requires SHORTTAG YES
    								  <p>D.N.I (sin letra) <br/><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 514, Column 40: NET-enabling start-tag requires SHORTTAG YES
    								  <p>D.N.I (sin letra) <br/><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.

  • Error Line 518, Column 161: character ";" not allowed in attribute specification list
    …r" id="codetar" autocomplete="off" onfocus='determinarFocus("codetar")';></div>
  • Error Line 519, Column 177: character ";" not allowed in attribute specification list
    … id="clavetar" autocomplete="off" onfocus='determinarFocus("clavetar")';></div>
  • Warning Line 544, 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 545, 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 546, 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 584, 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 588, Column 137: NET-enabling start-tag requires SHORTTAG YES
    …99319030. Domicilio Social: Pza. Basilio Para&iacute;so, 2. 50008-Zaragoza<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 601, Column 6: 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.

  • Error Line 602, Column 6: end tag for element "DIV" which is not open
    </div><!-- /all --></center>

    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 614, Column 16: there is no attribute "TABINDEX"
    	<div tabindex="-1" class="simplemodal-wrap" style="height: 100%; outline: 0px;…

    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 617, Column 196: required attribute "ALT" not specified
    …t="_blank">FOLLETO OFICIAL DE COMISIONES <img src="../images/pdf_icon.gif"></a>

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

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

  • Error Line 619, Column 211: required attribute "ALT" not specified
    …rget="_blank">TARIFAS CAJAS DE SEGURIDAD <img src="../images/pdf_icon.gif"></a>

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

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

Visitor Analysis

Daily Visitor
  • 7.233 visits

In Page Analysis