divxatope.com

Descargas Gratis de DivX, PSP, P2P, Torrents, Torrent y BitTorrent ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    divxatope.com
  • Favicon
  • Alexa Rank
    #11987
  • Google Page Rank
    PR 3
  • Ip Address
    188.95.248.45
  • Page Size
    42.6 KB
  • Images
    0 GIF, 18 JPG, 25 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 4 0 14 0 0

Website Meta Analysis



  • Title
    cine gratis, torrents, peliculas gratis, descargar peliculas, torrent
  • Meta Keyword
    Torrents, Torrent, peliculas torrent, cine gratis, bajar peliculas gratis, peliculas gratis, descargar peliculas gratis, descargar peliculas, BitTorrent, Estrenos Bittorrent, Acelerar BitTorrent, BitComet, Download Torrent, Direct Down, Descargas Directas, Torrents Gratis, Descargar Torrents
  • Meta Description
    Descargas Gratis de DivX, PSP, P2P, Torrents, Torrent y BitTorrent

Technical Analysis



  • Webserver
    - Web acceleration by Rackmarkt.com
  • Ip Address
    188.95.248.45
  • Domain Age
    5 Years, 5 Months, 26 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-type: text/html; charset=UTF-8
  • server: - Web acceleration by Rackmarkt.com
  • x-cacheable: YES
  • content-length: 7923
  • date: Sat, 03 Aug 2013 02:49:16 GMT
  • x-varnish: 1476018585
  • via: 1.1 varnish
  • connection: keep-alive
  • age: 0
  • x-cache: MISS
  • x-google-cache-control: remote-fetch
Servicio de Registro provisto por: RackMarkt
Contacto: email
Visite: http://www.rackmarkt.com

Registration Service Provided By: RackMarkt
Contact: email
Visit: http://www.rackmarkt.com

Domain divxatope.com

Date Registered: 2008-3-5
Date Modified: 2012-8-14
Expiry Date: 2013-3-5

DNS1: ns-canada.topdns.com
DNS2: ns-uk.topdns.com
DNS3: ns-usa.topdns.com

Registrant
Fundacion Private Whois
Domain Administrator
Email: email
Attn: divxatope.com
Aptds. 0850-00056
Zona 15 Panama
Panama
Tel: +507.65995877

Administrative Contact
Fundacion Private Whois
Domain Administrator
Email: email
Attn: divxatope.com
Aptds. 0850-00056
Zona 15 Panama
Panama
Tel: +507.65995877

Technical Contact
Fundacion Private Whois
Domain Administrator
Email: email
Attn: divxatope.com
Aptds. 0850-00056
Zona 15 Panama
Panama
Tel: +507.65995877

RACKMARKT.COM - Servicio y Calidad reales

DNS Analysis


DNS servers
ns-canada.topdns.com [109.201.142.225]
ns-usa.topdns.com [108.61.12.163]
ns-uk.topdns.com [5.199.168.80]


DNS Records

Answer records
divxatope.com SOA
server: ns-canada.topdns.com
email: hostmaster@topdns.com
serial: 2012083004
refresh: 172800
retry: 900
expire: 1209600
minimum ttl: 3600
7200s
divxatope.com NS  ns-canada.topdns.com 3600s
divxatope.com NS  ns-usa.topdns.com 3600s
divxatope.com NS  ns-uk.topdns.com 3600s
divxatope.com A 188.95.248.45 900s

Authority records

Additional records

IP 188.95.248.45 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 183 Errors
  • 205 Warnings
Ratio Text/Html
  • 0.6919621370126745
Message Error
  • Error Line 8, Column 103: end tag for "meta" omitted, but OMITTAG NO was specified
    … content="Descargas Gratis de DivX, PSP, P2P, Torrents, Torrent y BitTorrent"> 

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

  • Info Line 8, Column 1: start tag was here
    <meta name="description" content="Descargas Gratis de DivX, PSP, P2P, Torrents,…
  • Error Line 10, Column 326: end tag for "meta" omitted, but OMITTAG NO was specified
    …Torrent, Direct Down, Descargas Directas, Torrents Gratis, Descargar Torrents">

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

  • Info Line 10, Column 1: start tag was here
    <meta name="keywords" content="Torrents, Torrent, peliculas torrent, cine grati…
  • Error Line 12, Column 38: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="revisit" content="1 day">

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

  • Info Line 12, Column 1: start tag was here
    <meta name="revisit" content="1 day">
  • Error Line 13, Column 17: document type does not allow element "html" here
    <html lang="es" >

    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 14, Column 20: document type does not allow element "html" here
    <html xml:lang="es">

    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 15, Column 43: document type does not allow element "meta" here; assuming missing "head" start-tag
    <meta name="revisit-after" content="1 day">
  • Error Line 15, Column 44: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="revisit-after" content="1 day">

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

  • Info Line 15, Column 1: start tag was here
    <meta name="revisit-after" content="1 day">
  • Error Line 16, Column 44: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="robots" content="index,follow">

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

  • Info Line 16, Column 1: start tag was here
    <meta name="robots" content="index,follow">
  • Error Line 23, Column 7: end tag for "head" which is not finished
    </head>

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

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

  • Error Line 36, Column 9: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div id=HOTWordsTxt name=HOTWordsTxt> <div id="page_margins">
  • Error Line 36, Column 26: there is no attribute "name"
    <div id=HOTWordsTxt name=HOTWordsTxt> <div id="page_margins">

    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 36, Column 26: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <div id=HOTWordsTxt name=HOTWordsTxt> <div id="page_margins">
  • Error Line 48, Column 16: end tag for "br" omitted, but OMITTAG NO was specified
    					</div><br><img src="http://www.divxatope.com/images/logo.png" align="left"…

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

  • Info Line 48, Column 12: start tag was here
    					</div><br><img src="http://www.divxatope.com/images/logo.png" align="left"…
  • Error Line 48, Column 80: required attribute "alt" not specified
    …			</div><br><img src="http://www.divxatope.com/images/logo.png" align="left">	

    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 48, Column 81: end tag for "img" omitted, but OMITTAG NO was specified
    …			</div><br><img src="http://www.divxatope.com/images/logo.png" align="left">	

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

  • Info Line 48, Column 16: start tag was here
    					</div><br><img src="http://www.divxatope.com/images/logo.png" align="left"…
  • Warning Line 106, Column 46: cannot generate system identifier for general entity "action"
    …<li><a href='main.php?module=torrents&action=view&id=31206' title='Ted TS-Scre…

    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 106, Column 46: general entity "action" not defined and no default entity
    …<li><a href='main.php?module=torrents&action=view&id=31206' title='Ted TS-Scre…

    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 106, Column 52: reference not terminated by REFC delimiter
    … href='main.php?module=torrents&action=view&id=31206' title='Ted TS-Screener 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 106, Column 52: reference to external entity in attribute value
    … href='main.php?module=torrents&action=view&id=31206' title='Ted TS-Screener 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 106, Column 52: reference to entity "action" for which no system identifier could be generated
    … href='main.php?module=torrents&action=view&id=31206' title='Ted TS-Screener 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 106, Column 45: entity was defined here
    …	<li><a href='main.php?module=torrents&action=view&id=31206' title='Ted TS-Scr…
  • Warning Line 106, Column 58: cannot generate system identifier for general entity "id"
    …'main.php?module=torrents&action=view&id=31206' title='Ted TS-Screener Alto Sp…

    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 106, Column 58: general entity "id" not defined and no default entity
    …'main.php?module=torrents&action=view&id=31206' title='Ted TS-Screener Alto Sp…

    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 106, Column 60: reference not terminated by REFC delimiter
    …ain.php?module=torrents&action=view&id=31206' title='Ted TS-Screener Alto Span…

    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 106, Column 60: reference to external entity in attribute value
    …ain.php?module=torrents&action=view&id=31206' title='Ted TS-Screener Alto Span…

    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 106, Column 60: reference to entity "id" for which no system identifier could be generated
    …ain.php?module=torrents&action=view&id=31206' title='Ted TS-Screener Alto Span…

    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 106, Column 57: entity was defined here
    …='main.php?module=torrents&action=view&id=31206' title='Ted TS-Screener Alto S…
  • Warning Line 106, Column 204: reference not terminated by REFC delimiter
    … href='main.php?module=torrents&action=view&id=28093' title='Los Vengadores TS…

    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 106, Column 204: reference to external entity in attribute value
    … href='main.php?module=torrents&action=view&id=28093' title='Los Vengadores TS…

    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 106, Column 204: reference to entity "action" for which no system identifier could be generated
    … href='main.php?module=torrents&action=view&id=28093' title='Los Vengadores TS…

    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 106, Column 45: entity was defined here
    …	<li><a href='main.php?module=torrents&action=view&id=31206' title='Ted TS-Scr…
  • Warning Line 106, Column 212: reference not terminated by REFC delimiter
    …ain.php?module=torrents&action=view&id=28093' title='Los Vengadores TS-Screene…

    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 106, Column 212: reference to external entity in attribute value
    …ain.php?module=torrents&action=view&id=28093' title='Los Vengadores TS-Screene…

    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 106, Column 212: reference to entity "id" for which no system identifier could be generated
    …ain.php?module=torrents&action=view&id=28093' title='Los Vengadores TS-Screene…

    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 106, Column 57: entity was defined here
    …='main.php?module=torrents&action=view&id=31206' title='Ted TS-Screener Alto S…
  • Warning Line 106, Column 378: reference not terminated by REFC delimiter
    … href='main.php?module=torrents&action=view&id=29861' title='Ice Age 4 La Form…

    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 106, Column 378: reference to external entity in attribute value
    … href='main.php?module=torrents&action=view&id=29861' title='Ice Age 4 La Form…

    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 106, Column 378: reference to entity "action" for which no system identifier could be generated
    … href='main.php?module=torrents&action=view&id=29861' title='Ice Age 4 La Form…

    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 106, Column 45: entity was defined here
    …	<li><a href='main.php?module=torrents&action=view&id=31206' title='Ted TS-Scr…
  • Warning Line 106, Column 386: reference not terminated by REFC delimiter
    …ain.php?module=torrents&action=view&id=29861' title='Ice Age 4 La Formacion De…

    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 106, Column 386: reference to external entity in attribute value
    …ain.php?module=torrents&action=view&id=29861' title='Ice Age 4 La Formacion De…

    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 106, Column 386: reference to entity "id" for which no system identifier could be generated
    …ain.php?module=torrents&action=view&id=29861' title='Ice Age 4 La Formacion De…

    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 106, Column 57: entity was defined here
    …='main.php?module=torrents&action=view&id=31206' title='Ted TS-Screener Alto S…
  • Warning Line 106, Column 606: reference not terminated by REFC delimiter
    … href='main.php?module=torrents&action=view&id=29101' title='Men In Black 3 HD…

    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 106, Column 606: reference to external entity in attribute value
    … href='main.php?module=torrents&action=view&id=29101' title='Men In Black 3 HD…

    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 106, Column 606: reference to entity "action" for which no system identifier could be generated
    … href='main.php?module=torrents&action=view&id=29101' title='Men In Black 3 HD…

    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 106, Column 45: entity was defined here
    …	<li><a href='main.php?module=torrents&action=view&id=31206' title='Ted TS-Scr…
  • Warning Line 106, Column 614: reference not terminated by REFC delimiter
    …ain.php?module=torrents&action=view&id=29101' title='Men In Black 3 HDTS-Scree…

    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 106, Column 614: reference to external entity in attribute value
    …ain.php?module=torrents&action=view&id=29101' title='Men In Black 3 HDTS-Scree…

    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 106, Column 614: reference to entity "id" for which no system identifier could be generated
    …ain.php?module=torrents&action=view&id=29101' title='Men In Black 3 HDTS-Scree…

    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 106, Column 57: entity was defined here
    …='main.php?module=torrents&action=view&id=31206' title='Ted TS-Screener Alto S…
  • Warning Line 106, Column 806: reference not terminated by REFC delimiter
    … href='main.php?module=torrents&action=view&id=30872' title='El Dictador BR-Sc…

    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 106, Column 806: reference to external entity in attribute value
    … href='main.php?module=torrents&action=view&id=30872' title='El Dictador BR-Sc…

    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 106, Column 806: reference to entity "action" for which no system identifier could be generated
    … href='main.php?module=torrents&action=view&id=30872' title='El Dictador BR-Sc…

    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 106, Column 45: entity was defined here
    …	<li><a href='main.php?module=torrents&action=view&id=31206' title='Ted TS-Scr…
  • Warning Line 106, Column 814: reference not terminated by REFC delimiter
    …ain.php?module=torrents&action=view&id=30872' title='El Dictador BR-Screener S…

    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 106, Column 814: reference to external entity in attribute value
    …ain.php?module=torrents&action=view&id=30872' title='El Dictador BR-Screener S…

    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 106, Column 814: reference to entity "id" for which no system identifier could be generated
    …ain.php?module=torrents&action=view&id=30872' title='El Dictador BR-Screener S…

    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 106, Column 57: entity was defined here
    …='main.php?module=torrents&action=view&id=31206' title='Ted TS-Screener Alto S…
  • Error Line 119, Column 194: required attribute "alt" not specified
    …ght='29' border='0' title='Click to see how many people are online' /></a></br>

    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 119, Column 203: end tag for element "br" which is not open
    …ght='29' border='0' title='Click to see how many people are online' /></a></br>

    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 190, 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).

  • Error Line 205, Column 9: end tag for element "script" which is not open
    </script>

    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 477, Column 13: document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<noscript>

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

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

  • Error Line 478, Column 105: end tag for "img" omitted, but OMITTAG NO was specified
    …ademails.com/cgi-bin/contador.cgi?ID=1059957505" border="0" alt="Estadisticas">

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

  • Info Line 478, Column 5: start tag was here
    				<img src="http://www.ademails.com/cgi-bin/contador.cgi?ID=1059957505" borde…
  • Error Line 527, Column 8: required attribute "type" not specified
    <script>section=3769390;popTimes=5;</script><script type="text/javascript" src=…

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

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

  • Warning Line 527, Column 135: cannot generate system identifier for general entity "rotateur"
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=46978"></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 527, Column 135: general entity "rotateur" not defined and no default entity
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=46978"></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 527, Column 143: reference not terminated by REFC delimiter
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=46978"></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 527, Column 143: reference to external entity in attribute value
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=46978"></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 527, Column 143: reference to entity "rotateur" for which no system identifier could be generated
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=46978"></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 527, Column 134: entity was defined here
    …http://www.adcash.com/script/java.php?option=rotateur&rotateur=46978"></script>
  • Error Line 528, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 36, Column 1: start tag was here
    <div id=HOTWordsTxt name=HOTWordsTxt> <div id="page_margins">
  • Error Line 529, Column 8: "html" not finished but document ended
    </html>
  • Error Line 529, Column 8: end tag for "html" omitted, but OMITTAG NO was specified
    </html>

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

  • Info Line 13, Column 1: start tag was here
    <html lang="es" >
  • Error Line 529, Column 8: end tag for "head" omitted, but OMITTAG NO was specified
    </html>

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

  • Info Line 4, Column 1: start tag was here
    <head>
  • Error Line 529, Column 8: "html" not finished but document ended
    </html>
  • Error Line 529, Column 8: end tag for "html" omitted, but OMITTAG NO was specified
    </html>

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

  • Info Line 3, Column 1: start tag was here
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="es" lang="es">

Visitor Analysis

Daily Visitor
  • 9.100 visits

In Page Analysis