incestuosas.com

incestuosas.com has Alexa Rank 22.154 and Google Page Rank is 0

Display Widget for this domain on your website. Click Here
This data was last updated from 22-07-2013 03:40:20  (update).

Overview Info

  • Domain Name
    incestuosas.com
  • Favicon
  • Alexa Rank
    #22154
  • Google Page Rank
    PR 0
  • Ip Address
    195.78.228.76
  • Page Size
    35.1 KB
  • Images
    25 GIF, 12 JPG, 2 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 3 0 0 0 0

Technical Analysis



  • Webserver
    Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/0.9.8o PHP/5.2.17
  • Ip Address
    195.78.228.76
  • Domain Age
    3 Years, 1 Months, 28 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Mon, 22 Jul 2013 03:40:15 GMT
  • server: Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/0.9.8o PHP/5.2.17
  • x-powered-by: PHP/5.2.17
  • 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
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 8303
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: incestuosas.com

Registrant Contact:
SEDIPRO S.L.
SEDIPRO SL ()

Fax:
CAMPOS CRESPO, 4
VALENCIA, VA 46017
ES

Administrative Contact:
SEDIPRO S.L.
SEDIPRO SL ( email )
+34.687433077
Fax: +1.5555555555
CAMPOS CRESPO, 4
VALENCIA, VA 46017
ES

Technical Contact:
SEDIPRO S.L.
SEDIPRO SL ( email )
+34.687433077
Fax: +1.5555555555
CAMPOS CRESPO, 4
VALENCIA, VA 46017
ES

Status: Locked

Name Servers:
DNS1.HISPALISDNS.COM
DNS2.HISPALISDNS.COM
DNS3.HISPALISDNS.COM

Creation date: 09 Jun 2010 09:48:00
Expiration date: 09 Jun 2015 04:48:00

DNS Analysis


DNS servers
dns1.hispalisdns.com [195.78.228.199]
dns2.hispalisdns.com [67.18.244.114]
dns3.hispalisdns.com [213.186.47.218]


DNS Records

Answer records
incestuosas.com SOA
server: dns1.hispalisdns.com
email: admin@furanet.com
serial: 2011121401
refresh: 3200
retry: 1600
expire: 604800
minimum ttl: 3600
3600s
incestuosas.com A 195.78.228.76 3600s
incestuosas.com MX
preference: 10
exchange: mail.incestuosas.com
3600s
incestuosas.com NS  dns1.hispalisdns.com 3600s
incestuosas.com NS  dns2.hispalisdns.com 3600s
incestuosas.com NS  dns3.hispalisdns.com 3600s
incestuosas.com TXT v=spf1 a mx a:mail.incestuosas.com ip4:195.78.228.0/22 ip4:91.192.108.0/22 ?all 3600s

Authority records

Additional records
mail.incestuosas.com A 195.78.228.76 3600s
dns1.hispalisdns.com A 195.78.228.199 3600s
dns2.hispalisdns.com A 67.18.244.114 3600s
dns3.hispalisdns.com A 213.186.47.218 3600s

IP 195.78.228.76 Analysis

  • Country Code
    ES
  • Country Code3
    ESP
  • Country Name
    Spain
  • City
    EU
  • Continent Code
    40° North
  • Latitude
    4.
  • Longitude
  • No whois ip data for 195.78.228.76

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 74 Errors
  • 91 Warnings
Ratio Text/Html
  • 0.5854609237965309
Message Error
  • Error Line 22, Column 115: required attribute "alt" not specified
    …://www.ciberguarras.com"><img src="/img/deseoban1107gif.gif" /></a></div></div>

    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 188, Column 15: there is no attribute "width"
    <ilayer width="300" height="434" src="http://recursos.promocionesweb.com/mb/lis…

    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 188, Column 28: there is no attribute "height"
    <ilayer width="300" height="434" src="http://recursos.promocionesweb.com/mb/lis…

    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 188, Column 38: there is no attribute "src"
    <ilayer width="300" height="434" src="http://recursos.promocionesweb.com/mb/lis…

    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 188, Column 104: element "ilayer" undefined
    …web.com/mb/listado_salas.php?id=11606"></ilayer><iframe scrolling="no" framebo…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 229, Column 90: cannot generate system identifier for general entity "login"
    …ion.exoclick.com/ads.php?type=300x250&login=zurri&cat=97&search=&ad_title_colo…

    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 229, Column 90: general entity "login" not defined and no default entity
    …ion.exoclick.com/ads.php?type=300x250&login=zurri&cat=97&search=&ad_title_colo…

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

  • Warning Line 229, Column 95: reference not terminated by REFC delimiter
    …xoclick.com/ads.php?type=300x250&login=zurri&cat=97&search=&ad_title_color=000…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 95: reference to external entity in attribute value
    …xoclick.com/ads.php?type=300x250&login=zurri&cat=97&search=&ad_title_color=000…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 95: reference to entity "login" for which no system identifier could be generated
    …xoclick.com/ads.php?type=300x250&login=zurri&cat=97&search=&ad_title_color=000…

    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 229, Column 89: entity was defined here
    …tion.exoclick.com/ads.php?type=300x250&login=zurri&cat=97&search=&ad_title_col…
  • Warning Line 229, Column 102: cannot generate system identifier for general entity "cat"
    ….com/ads.php?type=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgc…

    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 229, Column 102: general entity "cat" not defined and no default entity
    ….com/ads.php?type=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgc…

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

  • Warning Line 229, Column 105: reference not terminated by REFC delimiter
    …m/ads.php?type=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgcolo…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 105: reference to external entity in attribute value
    …m/ads.php?type=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgcolo…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 105: reference to entity "cat" for which no system identifier could be generated
    …m/ads.php?type=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgcolo…

    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 229, Column 101: entity was defined here
    …k.com/ads.php?type=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bg…
  • Warning Line 229, Column 109: cannot generate system identifier for general entity "search"
    …s.php?type=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgcolor=FF…

    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 229, Column 109: general entity "search" not defined and no default entity
    …s.php?type=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgcolor=FF…

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

  • Warning Line 229, Column 115: reference not terminated by REFC delimiter
    …type=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 115: reference to external entity in attribute value
    …type=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 115: reference to entity "search" for which no system identifier could be generated
    …type=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&b…

    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 229, Column 108: entity was defined here
    …ds.php?type=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgcolor=F…
  • Warning Line 229, Column 117: cannot generate system identifier for general entity "ad_title_color"
    …pe=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

    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 229, Column 117: general entity "ad_title_color" not defined and no default entity
    …pe=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bor…

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

  • Warning Line 229, Column 131: reference not terminated by REFC delimiter
    …in=zurri&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 131: reference to external entity in attribute value
    …in=zurri&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 131: reference to entity "ad_title_color" for which no system identifier could be generated
    …in=zurri&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_c…

    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 229, Column 116: entity was defined here
    …ype=300x250&login=zurri&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&bo…
  • Warning Line 229, Column 139: cannot generate system identifier for general entity "bgcolor"
    …&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000…

    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 229, Column 139: general entity "bgcolor" not defined and no default entity
    …&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000…

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

  • Warning Line 229, Column 146: reference not terminated by REFC delimiter
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 146: reference to external entity in attribute value
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 146: reference to entity "bgcolor" for which no system identifier could be generated
    …&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&fon…

    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 229, Column 138: entity was defined here
    …i&cat=97&search=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=00…
  • Warning Line 229, Column 154: cannot generate system identifier for general entity "border"
    …&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block…

    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 229, Column 154: general entity "border" not defined and no default entity
    …&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block…

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

  • Warning Line 229, Column 160: reference not terminated by REFC delimiter
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 160: reference to external entity in attribute value
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 160: reference to entity "border" for which no system identifier could be generated
    …tle_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywo…

    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 229, Column 153: entity was defined here
    …=&ad_title_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&bloc…
  • Warning Line 229, Column 163: cannot generate system identifier for general entity "border_color"
    …_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords…

    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 229, Column 163: general entity "border_color" not defined and no default entity
    …_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords…

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

  • Warning Line 229, Column 175: reference not terminated by REFC delimiter
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 175: reference to external entity in attribute value
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 175: reference to entity "border_color" for which no system identifier could be generated
    …c&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_co…

    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 229, Column 162: entity was defined here
    …e_color=0000cc&bgcolor=FFFFFF&border=0&border_color=000000&font=&block_keyword…
  • Warning Line 229, Column 183: cannot generate system identifier for general entity "font"
    …r=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=0000…

    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 229, Column 183: general entity "font" not defined and no default entity
    …r=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=0000…

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

  • Warning Line 229, Column 187: reference not terminated by REFC delimiter
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 187: reference to external entity in attribute value
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 187: reference to entity "font" for which no system identifier could be generated
    …FFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&a…

    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 229, Column 182: entity was defined here
    …or=FFFFFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000…
  • Warning Line 229, Column 189: cannot generate system identifier for general entity "block_keywords"
    …FF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad_…

    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 229, Column 189: general entity "block_keywords" not defined and no default entity
    …FF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad_…

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

  • Warning Line 229, Column 203: reference not terminated by REFC delimiter
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 203: reference to external entity in attribute value
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 203: reference to entity "block_keywords" for which no system identifier could be generated
    …rder_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008…

    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 229, Column 188: entity was defined here
    …FFF&border=0&border_color=000000&font=&block_keywords=&ad_text_color=000000&ad…
  • Warning Line 229, Column 205: cannot generate system identifier for general entity "ad_text_color"
    …er_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=00800…

    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 229, Column 205: general entity "ad_text_color" not defined and no default entity
    …er_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=00800…

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

  • Warning Line 229, Column 218: reference not terminated by REFC delimiter
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 218: reference to external entity in attribute value
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 218: reference to entity "ad_text_color" for which no system identifier could be generated
    …00&font=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub…

    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 229, Column 204: entity was defined here
    …der_color=000000&font=&block_keywords=&ad_text_color=000000&ad_durl_color=0080…
  • Warning Line 229, Column 226: cannot generate system identifier for general entity "ad_durl_color"
    …&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_…

    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 229, Column 226: general entity "ad_durl_color" not defined and no default entity
    …&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_…

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

  • Warning Line 229, Column 239: reference not terminated by REFC delimiter
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 239: reference to external entity in attribute value
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 239: reference to entity "ad_durl_color" for which no system identifier could be generated
    …ds=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_t…

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

  • Info Line 229, Column 225: entity was defined here
    …=&block_keywords=&ad_text_color=000000&ad_durl_color=008000&adult=0&sub=0&text…
  • Warning Line 229, Column 247: cannot generate system identifier for general entity "adult"
    …ext_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&i…

    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 229, Column 247: general entity "adult" not defined and no default entity
    …ext_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&i…

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

  • Warning Line 229, Column 252: reference not terminated by REFC delimiter
    …olor=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 252: reference to external entity in attribute value
    …olor=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 252: reference to entity "adult" for which no system identifier could be generated
    …olor=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone…

    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 229, Column 246: entity was defined here
    …text_color=000000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&…
  • Warning Line 229, Column 258: reference not terminated by REFC delimiter
    …00000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=18753…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 261: cannot generate system identifier for general entity "text_only"
    …00&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&i…

    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 229, Column 261: general entity "text_only" not defined and no default entity
    …00&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&i…

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

  • Warning Line 229, Column 270: reference not terminated by REFC delimiter
    …l_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=996…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 270: reference to external entity in attribute value
    …l_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=996…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 270: reference to entity "text_only" for which no system identifier could be generated
    …l_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=996…

    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 229, Column 260: entity was defined here
    …000&ad_durl_color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&…
  • Warning Line 229, Column 273: cannot generate system identifier for general entity "show_thumb"
    …olor=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"…

    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 229, Column 273: general entity "show_thumb" not defined and no default entity
    …olor=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"…

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

  • Warning Line 229, Column 283: reference not terminated by REFC delimiter
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 283: reference to external entity in attribute value
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 283: reference to entity "show_thumb" for which no system identifier could be generated
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></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 229, Column 272: entity was defined here
    …color=008000&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643…
  • Warning Line 229, Column 286: cannot generate system identifier for general entity "idzone"
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></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 229, Column 286: general entity "idzone" not defined and no default entity
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></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.

  • Warning Line 229, Column 292: reference not terminated by REFC delimiter
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 292: reference to external entity in attribute value
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 292: reference to entity "idzone" for which no system identifier could be generated
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></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 229, Column 285: entity was defined here
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></script>
  • Warning Line 229, Column 300: cannot generate system identifier for general entity "idsite"
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></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 229, Column 300: general entity "idsite" not defined and no default entity
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></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.

  • Warning Line 229, Column 306: reference not terminated by REFC delimiter
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 229, Column 306: reference to external entity in attribute value
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 229, Column 306: reference to entity "idsite" for which no system identifier could be generated
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></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 229, Column 299: entity was defined here
    …00&adult=0&sub=0&text_only=0&show_thumb=0&idzone=187537&idsite=99643"></script>
  • Error Line 238, Column 10: ID "topvideos" already defined
    <div id="topvideos">

    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 190, Column 10: ID "topvideos" first defined here
    <div id="topvideos">
  • Error Line 239, Column 10: ID "topvideossup" already defined
    <div id="topvideossup"><h2><span>LINKS AMIGOS</span></h2></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 191, Column 10: ID "topvideossup" first defined here
    <div id="topvideossup"><h2><span>TAGS</span></h2></div>
  • Error Line 240, Column 10: ID "topvideosc" already defined
    <div id="topvideosc"></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 192, Column 10: ID "topvideosc" first defined here
    <div id="topvideosc"></div>
  • Error Line 255, Column 10: ID "topvideosinf" already defined
    <div id="topvideosinf"></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 218, Column 10: ID "topvideosinf" first defined here
    <div id="topvideosinf"></div>
  • Error Line 257, Column 10: ID "topvideos" already defined
    <div id="topvideos">

    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 190, Column 10: ID "topvideos" first defined here
    <div id="topvideos">
  • Error Line 258, Column 10: ID "topvideossup" already defined
    <div id="topvideossup"><h2><span>CHICAS DE TU CIUDAD</span></h2></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 191, Column 10: ID "topvideossup" first defined here
    <div id="topvideossup"><h2><span>TAGS</span></h2></div>
  • Error Line 259, Column 10: ID "topvideosc" already defined
    <div id="topvideosc"></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 192, Column 10: ID "topvideosc" first defined here
    <div id="topvideosc"></div>
  • Error Line 267, Column 10: ID "topvideosinf" already defined
    <div id="topvideosinf"></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 218, Column 10: ID "topvideosinf" first defined here
    <div id="topvideosinf"></div>
  • Error Line 292, Column 104: element "ilayer" undefined
    …sweb.com/mb/listado_salas.php?id=8440"></ilayer><iframe scrolling="no" framebo…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).

Visitor Analysis

Daily Visitor
  • 3.383 visits

In Page Analysis