Sitio que ofrece a los visitantes la posibilidad de votar el atractivo de las personas, de conocer gente mediante un sistema de mensajeria exclusivo, y de subir sus propias fotos para ser votados ...

sexyono.com
  • Domain Name
    sexyono.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #30611
  • Page Size
    19.9 KB
  • Ip Address
    62.97.138.32
  • Heading
    H1: 0, H2: 1, H3: 1, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 2 JPG, 0 PNG

Website Meta Analysis

  • Title
    SEXY o NO? - Ranking de fotos, conocer gente y hacer amigos
  • Meta Keyword
    conocer, conocer gente, amar, novios, sexys, sexy, sexi, ranking, votacion, compartir, solteros, matrimonio, pareja, amor, romance, amistad, hacer amigos, buscar pareja, citas, foto, fotos, contacto, contactos, buscar pareja, novio, novia
  • Meta Description
    Sitio que ofrece a los visitantes la posibilidad de votar el atractivo de las personas, de conocer gente mediante un sistema de mensajeria exclusivo, y de subir sus propias fotos para ser votados por otros.

Technical Analysis

  • Webserver
    Apache/2.2.15 (CentOS)
  • Ip Address
    62.97.138.32
  • Domain Age
    10 Years, 10 Months, 20 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 09 Oct 2014 06:32:47 GMT
  • server: Apache/2.2.15 (CentOS)
  • x-powered-by: PHP/5.3.3
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • connection: close
  • content-type: text/html; charset=ISO-8859-1
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Kifony S.A.
Edificio Jimenez de Arechaga,Viana&Brause
Zabala, 1504
Montevideo, 11000
Uruguay

Domain Name: SEXYONO.COM
Created on: 09-Nov-02
Expires on: 09-Nov-12
Last Updated on: 22-Oct-10

Administrative Contact:
Pardeza, David email
Kifony S.A.
Edificio Jimenez de Arechaga,Viana&Brause
Zabala, 1504
Montevideo, 11000
Uruguay
+34.912701220

Technical Contact:
Pardeza, David email
Kifony S.A.
Edificio Jimenez de Arechaga,Viana&Brause
Zabala, 1504
Montevideo, 11000
Uruguay
+34.912701220

Domain servers in listed order:
NS1.SEXYONO.COM
NS2.SEXYONO.COM

DNS Analysis


DNS servers
ns1.sexyono.com [62.97.138.17]
ns2.sexyono.com [88.208.230.92]


DNS Records

Answer records
sexyono.com SOA
server: ns1.sexyono.com
email: dnsmaster@sexyono.com
serial: 2012121902
refresh: 14400
retry: 7200
expire: 1728000
minimum ttl: 28800
7200s
sexyono.com NS  ns2.sexyono.com 7200s
sexyono.com NS  ns1.sexyono.com 7200s
sexyono.com A 216.139.209.40 7200s
sexyono.com MX
preference: 30
exchange: aspmx2.googlemail.com
7200s
sexyono.com MX
preference: 30
exchange: aspmx3.googlemail.com
7200s
sexyono.com MX
preference: 30
exchange: aspmx4.googlemail.com
7200s
sexyono.com MX
preference: 30
exchange: aspmx5.googlemail.com
7200s
sexyono.com MX
preference: 10
exchange: aspmx.l.google.com
7200s
sexyono.com MX
preference: 20
exchange: alt1.aspmx.l.google.com
7200s
sexyono.com MX
preference: 20
exchange: alt2.aspmx.l.google.com
7200s
sexyono.com TXT v=spf1 ip4:62.97.139.0/24 ip4:216.139.255.0/25 ip4:216.139.212.0/24 ip4:216.139.221.21 ip4:216.139.210.192/27 mx ~all 7200s

Authority records

Additional records

IP 62.97.138.32 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 81 Errors
  • 11 Warnings
Ratio Text/Html
  • 0.5822529954822235
Message Error
  • Error Line 6, Column 16: there is no attribute "PROPERTY"
    <meta property="fb:app_id" content="178759728876899" />

    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 6, Column 54: NET-enabling start-tag requires SHORTTAG YES
    <meta property="fb:app_id" content="178759728876899" />

    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 242: document type does not allow element "META" here
    …ensajeria exclusivo, y de subir sus propias fotos para ser votados por otros.">

    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 8, Column 271: document type does not allow element "META" here
    … pareja, citas, foto, fotos, contacto, contactos, buscar pareja, novio, novia">

    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 9, Column 23: document type does not allow element "STYLE" here
    <style type="text/css">

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

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

  • Warning Line 43, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …href="/js/fancybox/jquery.fancybox-1.3.4.css" type="text/css" media="screen" />

    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 43, Column 101: document type does not allow element "LINK" here
    …href="/js/fancybox/jquery.fancybox-1.3.4.css" type="text/css" media="screen" />

    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 46, Column 54: document type does not allow element "LINK" here
    <link href="/st.css" rel="stylesheet" type="text/css">

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

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

  • Error Line 59, Column 16: end tag for element "HEAD" which is not open
    </script></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 61, Column 6: document type does not allow element "BODY" here
    <body>

    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 87, Column 64: there is no attribute "NAME"
    …class="pa"><div id="HOTWordsTxt" name="HOTWordsTxt"><b>Sube tu foto, y comienz…

    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 128, Column 198: NET-enabling start-tag requires SHORTTAG YES
    …p?zoneid=5898&amp;cb=123456&amp;n=afc4b9d6' border='0' alt='' /></a></noscript>

    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 136, Column 9: required attribute "TYPE" not specified
    	<script>(function(d, s, id) {

    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 143, Column 37: there is no attribute "DATA-HREF"
    	<div class="fb-like-box" data-href="http://www.facebook.com/pages/Sexyono/3180…

    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 143, Column 104: there is no attribute "DATA-WIDTH"
    …s/Sexyono/318006078216660" data-width="292" data-show-faces="true" data-stream…

    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 143, Column 126: there is no attribute "DATA-SHOW-FACES"
    …660" data-width="292" data-show-faces="true" data-stream="false" data-header="…

    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 143, Column 145: there is no attribute "DATA-STREAM"
    …idth="292" data-show-faces="true" data-stream="false" data-header="true"></div>

    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 143, Column 165: there is no attribute "DATA-HEADER"
    …idth="292" data-show-faces="true" data-stream="false" data-header="true"></div>

    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 289, Column 9: document type does not allow element "TR" here
         <tr>

    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 297, Column 26: ID "FB-ROOT" already defined
                    <div id="fb-root"></div>

    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 135, Column 11: ID "FB-ROOT" first defined here
    	<div id="fb-root"></div>
  • Error Line 298, Column 24: required attribute "TYPE" not specified
                    <script>(function(d, s, id) {

    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 305, Column 101: there is no attribute "DATA-SEND"
    …yono.com/r/?uid=pe99643813" data-send="false" data-layout="box_count" data-wid…

    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 305, Column 121: there is no attribute "DATA-LAYOUT"
    …643813" data-send="false" data-layout="box_count" data-width="70" data-show-fa…

    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 310, Column 8: document type does not allow element "TR" here
        <tr>

    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 316, Column 8: document type does not allow element "TR" here
        <tr>

    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 318, Column 22: ID "HOTWORDSTXT" already defined
                <div id="HOTWordsTxt" name="HOTWordsTxt">Por favor mant&eacute;n es…

    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 87, Column 46: ID "HOTWORDSTXT" first defined here
    …td align="center" class="pa"><div id="HOTWordsTxt" name="HOTWordsTxt"><b>Sube …
  • Error Line 323, Column 8: document type does not allow element "TR" here
        <tr>

    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 331, Column 12: "TR" not finished but containing element ended
        </table></td>
  • Warning Line 401, Column 64: cannot generate system identifier for general entity "cor"
    …pt src="http://ads34985.hotwords.com.mx/show.jsp?id=34985&cor=005F00"></script>

    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 401, Column 64: general entity "cor" not defined and no default entity
    …pt src="http://ads34985.hotwords.com.mx/show.jsp?id=34985&cor=005F00"></script>

    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 401, Column 67: reference to entity "cor" for which no system identifier could be generated
    …pt src="http://ads34985.hotwords.com.mx/show.jsp?id=34985&cor=005F00"></script>

    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 401, Column 63: entity was defined here
    …pt src="http://ads34985.hotwords.com.mx/show.jsp?id=34985&cor=005F00"></script>
  • Error Line 401, Column 75: required attribute "TYPE" not specified
    …pt src="http://ads34985.hotwords.com.mx/show.jsp?id=34985&cor=005F00"></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>.

Visitor Analysis

Daily Visitor
  • 3.033 visits