deliverymusic.net has Alexa Rank 49.409 and Google Page Rank is 2

deliverymusic.net
  • Domain Name
    deliverymusic.net
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #49409
  • Page Size
    27.3 KB
  • Ip Address
    108.160.152.65
  • Heading
    H1: 8, H2: 2, H3: 1, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 8 JPG, 1 PNG

Website Meta Analysis

  • Title
    Deliverymusic.net | Descargar Musica | Mp3 Gratis
  • Meta Keyword
    descargar,mp3,gratis,musica,canciones,sueltas
  • Meta Description

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    108.160.152.65
  • Domain Age
    1 Years, 9 Months, 25 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from deliverymusic.net.

HTML Analysis

  • date: Sat, 16 Feb 2013 03:27:14 GMT
  • server: Apache
  • 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
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Robert Oliva Suarez
Manuel M. 100
Piura, -
Peru
Domain Domain Name: DELIVERYMUSIC.NET
Created: 02-May-11
Expires: 02-May-13
Updated: 10-Jan-12
Administrative Contact:
Oliva Suarez, Robert email
Manuel M. 100
Piura, -
Peru
+51.5174978426545 Fax -
Technical Contact:
Oliva Suarez, Robert email
Manuel M. 100
Piura, -
Peru
+51.5174978426545 Fax -
Name Servers:
NS1.DELIVERYMUSIC.NET
NS2.DELIVERYMUSIC.NET

DNS Analysis


DNS servers
ns1.deliverymusic.net [108.160.152.65]
ns2.deliverymusic.net [108.160.153.65]


DNS Records

Answer records
deliverymusic.net TXT v=spf1 +a +mx +ip4:108.160.152.65 ?all 14400s
deliverymusic.net MX
preference: 0
exchange: deliverymusic.net
14400s
deliverymusic.net SOA
server: ns1.deliverymusic.net
email: rickroma@hotmail.es
serial: 2013021102
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
deliverymusic.net NS  ns2.deliverymusic.net 86400s
deliverymusic.net NS  ns1.deliverymusic.net 86400s
deliverymusic.net A 108.160.152.65 14400s

Authority records

Additional records
deliverymusic.net A 108.160.152.65 14400s
ns1.deliverymusic.net A 108.160.152.65 14400s
ns2.deliverymusic.net A 108.160.153.65 14400s

IP 108.160.152.65 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 72 Errors
  • 21 Warnings
Ratio Text/Html
  • 0.5236014612133801
Message Error
  • Error Line 9, Column 79: required attribute "type" not specified
    …rc="https://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js"></script>

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

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

  • Warning Line 12, Column 84: cannot generate system identifier for general entity "width"
    …n/adbooth_floating.js?section=3582899&width=300&height=250&offsetleft=0&offset…

    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 12, Column 84: general entity "width" not defined and no default entity
    …n/adbooth_floating.js?section=3582899&width=300&height=250&offsetleft=0&offset…

    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 12, Column 89: reference not terminated by REFC delimiter
    …ooth_floating.js?section=3582899&width=300&height=250&offsetleft=0&offsettop=0…

    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 12, Column 89: reference to external entity in attribute value
    …ooth_floating.js?section=3582899&width=300&height=250&offsetleft=0&offsettop=0…

    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 12, Column 89: reference to entity "width" for which no system identifier could be generated
    …ooth_floating.js?section=3582899&width=300&height=250&offsetleft=0&offsettop=0…

    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 12, Column 83: entity was defined here
    …in/adbooth_floating.js?section=3582899&width=300&height=250&offsetleft=0&offse…
  • Warning Line 12, Column 94: cannot generate system identifier for general entity "height"
    …floating.js?section=3582899&width=300&height=250&offsetleft=0&offsettop=0&clos…

    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 12, Column 94: general entity "height" not defined and no default entity
    …floating.js?section=3582899&width=300&height=250&offsetleft=0&offsettop=0&clos…

    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 12, Column 100: reference not terminated by REFC delimiter
    …ng.js?section=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true…

    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 12, Column 100: reference to external entity in attribute value
    …ng.js?section=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true…

    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 12, Column 100: reference to entity "height" for which no system identifier could be generated
    …ng.js?section=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true…

    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 12, Column 93: entity was defined here
    …_floating.js?section=3582899&width=300&height=250&offsetleft=0&offsettop=0&clo…
  • Warning Line 12, Column 105: cannot generate system identifier for general entity "offsetleft"
    …?section=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></s…

    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 12, Column 105: general entity "offsetleft" not defined and no default entity
    …?section=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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.

  • Warning Line 12, Column 115: reference not terminated by REFC delimiter
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 115: reference to external entity in attribute value
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 115: reference to entity "offsetleft" for which no system identifier could be generated
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 104: entity was defined here
    …s?section=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></…
  • Warning Line 12, Column 118: cannot generate system identifier for general entity "offsettop"
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 118: general entity "offsettop" not defined and no default entity
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 127: reference not terminated by REFC delimiter
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 127: reference to external entity in attribute value
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 127: reference to entity "offsettop" for which no system identifier could be generated
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 117: entity was defined here
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></script>
  • Warning Line 12, Column 130: cannot generate system identifier for general entity "close"
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 130: general entity "close" not defined and no default entity
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 135: reference not terminated by REFC delimiter
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 135: reference to external entity in attribute value
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 135: reference to entity "close" for which no system identifier could be generated
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></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 12, Column 129: entity was defined here
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></script>
  • Error Line 12, Column 141: required attribute "type" not specified
    …ion=3582899&width=300&height=250&offsetleft=0&offsettop=0&close=true"></script>

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

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

  • Error Line 14, 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 28, Column 76: there is no attribute "height"
    …	<table width="981px" border="0" cellspacing="0" cellpadding="0" height="40px">

    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 38, Column 80: required attribute "alt" not specified
    …lign="center"><img src="http://deliverymusic.net/images/line.png" /></td>						

    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 44, Column 12: end tag for "tr" omitted, but OMITTAG NO was specified
    							</td>

    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 35, Column 9: start tag was here
    						  <tr>    
  • Error Line 44, Column 12: end tag for "table" omitted, but OMITTAG NO was specified
    							</td>

    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 33, Column 7: start tag was here
    						<table class="nav_text" width="400px" border="0" cellspacing="0" cellpadd…
  • Error Line 46, Column 16: end tag for element "center" which is not open
    							</center>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 58, Column 7: document type does not allow element "title" here
    <title>Deliverymusic.net | Descargar Musica | Mp3 Gratis</title>

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

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

  • Error Line 59, Column 79: document type does not allow element "meta" here
    <meta name="title" content="Deliverymusic.net | Descargar Musica | Mp3 Gratis">

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

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

  • Error Line 59, Column 80: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="title" content="Deliverymusic.net | Descargar Musica | Mp3 Gratis">

    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 59, Column 1: start tag was here
    <meta name="title" content="Deliverymusic.net | Descargar Musica | Mp3 Gratis">
  • Error Line 60, Column 36: "Descargar" is not a member of a group specified for any attribute
    <meta name="description" Descargar musica mp3 gratis, canciones sueltas para ba…
  • Error Line 60, Column 43: "musica" is not a member of a group specified for any attribute
    …a name="description" Descargar musica mp3 gratis, canciones sueltas para bajar…
  • Error Line 60, Column 47: "mp3" is not a member of a group specified for any attribute
    …me="description" Descargar musica mp3 gratis, canciones sueltas para bajar en …
  • Error Line 60, Column 53: "gratis" is not a member of a group specified for any attribute
    …scription" Descargar musica mp3 gratis, canciones sueltas para bajar en linea"…
  • Error Line 60, Column 65: "canciones" is not a member of a group specified for any attribute
    …cription" Descargar musica mp3 gratis, canciones sueltas para bajar en linea"/>
  • Error Line 60, Column 73: "sueltas" is not a member of a group specified for any attribute
    …cription" Descargar musica mp3 gratis, canciones sueltas para bajar en linea"/>
  • Error Line 60, Column 78: "para" is not a member of a group specified for any attribute
    …cription" Descargar musica mp3 gratis, canciones sueltas para bajar en linea"/>
  • Error Line 60, Column 84: "bajar" is not a member of a group specified for any attribute
    …cription" Descargar musica mp3 gratis, canciones sueltas para bajar en linea"/>
  • Error Line 60, Column 87: "en" is not a member of a group specified for any attribute
    …cription" Descargar musica mp3 gratis, canciones sueltas para bajar en linea"/>
  • Error Line 60, Column 92: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …cription" Descargar musica mp3 gratis, canciones sueltas para bajar en linea"/>

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 60, Column 92: document type does not allow element "meta" here
    …cription" Descargar musica mp3 gratis, canciones sueltas para bajar en linea"/>

    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 60, Column 93: end tag for "meta" omitted, but OMITTAG NO was specified
    …cription" Descargar musica mp3 gratis, canciones sueltas para bajar en linea"/>

    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 60, Column 1: start tag was here
    <meta name="description" Descargar musica mp3 gratis, canciones sueltas para ba…
  • Error Line 60, Column 93: character data is not allowed here
    …cription" Descargar musica mp3 gratis, canciones sueltas para bajar en linea"/>

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

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

    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 62, Column 44: document type does not allow element "meta" here
    <meta name="Distribution" content="Global"/>

    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 63, Column 39: document type does not allow element "meta" here
    <meta name="Rating" content="General"/>

    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 64, Column 45: document type does not allow element "meta" here
    <meta name="Revisit-after" content="7 days"/>

    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 65, Column 45: document type does not allow element "meta" here
    <meta name="robots" content="INDEX,FOLLOW" />

    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 66, Column 41: document type does not allow element "meta" here
    <meta name="category" content="Musica" /> 

    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 67, Column 46: document type does not allow element "meta" here
    <meta name="author" content="DeliveryMusic" />

    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 68, Column 50: document type does not allow element "meta" here
    <meta http-equiv="Content-Language" content="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 81, Column 52: document type does not allow element "input" here; missing one of "th", "td" start-tag
    									<input type="hidden" value="1" name="page">

    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 81, Column 53: end tag for "input" omitted, but OMITTAG NO was specified
    									<input type="hidden" value="1" name="page">

    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 81, Column 10: start tag was here
    									<input type="hidden" value="1" name="page">
  • Error Line 84, Column 145: end tag for "input" omitted, but OMITTAG NO was specified
    …ckground-image:url('images/btn-searchBig.png'); height:30px; width:29px;"></td>

    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 84, Column 14: start tag was here
    									<td><input name="submit" type="submit" value="" style="background-imag…
  • Error Line 98, Column 27: end tag for "br" omitted, but OMITTAG NO was specified
    			<td align="center"><br><!-- BEGIN STANDARD TAG - 728 x 90 - 763533 http://ww…

    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 98, Column 23: start tag was here
    			<td align="center"><br><!-- BEGIN STANDARD TAG - 728 x 90 - 763533 http://ww…
  • Error Line 99, Column 21: there is no attribute "FRAMEBORDER"
    <IFRAME FRAMEBORDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="…

    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 99, Column 37: there is no attribute "MARGINWIDTH"
    <IFRAME FRAMEBORDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="…

    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 99, Column 54: there is no attribute "MARGINHEIGHT"
    …RDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="728" HEIGHT="9…

    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 99, Column 68: there is no attribute "SCROLLING"
    …NWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="728" HEIGHT="90" SRC="http:/…

    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 99, Column 79: there is no attribute "WIDTH"
    …MARGINHEIGHT="0" SCROLLING="NO" WIDTH="728" HEIGHT="90" SRC="http://yieldmanag…

    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 99, Column 92: there is no attribute "HEIGHT"
    …"0" SCROLLING="NO" WIDTH="728" HEIGHT="90" SRC="http://yieldmanager.adbooth.ne…

    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 99, Column 101: there is no attribute "SRC"
    …LING="NO" WIDTH="728" HEIGHT="90" SRC="http://yieldmanager.adbooth.net/st?ad_t…

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

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

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

  • Warning Line 99, Column 152: cannot generate system identifier for general entity "ad_size"
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAME…

    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 99, Column 152: general entity "ad_size" not defined and no default entity
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAME…

    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 99, Column 159: reference not terminated by REFC delimiter
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAME>

    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 99, Column 159: reference to external entity in attribute value
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAME>

    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 99, Column 159: reference to entity "ad_size" for which no system identifier could be generated
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAME>

    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 99, Column 151: entity was defined here
    …dmanager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAM…
  • Warning Line 99, Column 167: cannot generate system identifier for general entity "section"
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAME>

    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 99, Column 167: general entity "section" not defined and no default entity
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAME>

    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 99, Column 174: reference not terminated by REFC delimiter
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAME>

    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 99, Column 174: reference to external entity in attribute value
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAME>

    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 99, Column 174: reference to entity "section" for which no system identifier could be generated
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAME>

    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 99, Column 166: entity was defined here
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAME>
  • Error Line 99, Column 183: element "IFRAME" undefined
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3583784"></IFRAME>

    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).
  • Error Line 189, Column 91: end tag for "br" omitted, but OMITTAG NO was specified
    …>Descargar Musica Mp3</h2><center><br>Descargar Mp3 gratis DELIVERYMUSIC.NET w…

    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 189, Column 87: start tag was here
    …><h2>Descargar Musica Mp3</h2><center><br>Descargar Mp3 gratis DELIVERYMUSIC.N…
  • Error Line 189, Column 1066: end tag for "br" omitted, but OMITTAG NO was specified
    …, toda tu musica en un solo lugar.<br><center><h3>Descargar Musica Mp3 Gratis<…

    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 189, Column 1062: start tag was here
    …atis, toda tu musica en un solo lugar.<br><center><h3>Descargar Musica Mp3 Gra…
  • Error Line 189, Column 1122: end tag for "br" omitted, but OMITTAG NO was specified
    …gar Musica Mp3 Gratis</h3><center><br>Descargar Baladas romanticas mp3, Descar…

    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 189, Column 1118: start tag was here
    …scargar Musica Mp3 Gratis</h3><center><br>Descargar Baladas romanticas mp3, De…
  • Error Line 189, Column 1238: end tag for "center" omitted, but OMITTAG NO was specified
    …argar canciones Regueton ultimas 2012, descargar musica mp3 de moda gratis</td>

    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 189, Column 1110: start tag was here
    …r><h3>Descargar Musica Mp3 Gratis</h3><center><br>Descargar Baladas romanticas…
  • Error Line 189, Column 1238: end tag for "center" omitted, but OMITTAG NO was specified
    …argar canciones Regueton ultimas 2012, descargar musica mp3 de moda gratis</td>

    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 189, Column 1066: start tag was here
    …, toda tu musica en un solo lugar.<br><center><h3>Descargar Musica Mp3 Gratis<…
  • Error Line 189, Column 1238: end tag for "center" omitted, but OMITTAG NO was specified
    …argar canciones Regueton ultimas 2012, descargar musica mp3 de moda gratis</td>

    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 189, Column 79: start tag was here
    …><center><h2>Descargar Musica Mp3</h2><center><br>Descargar Mp3 gratis DELIVER…
  • Error Line 189, Column 1238: end tag for "center" omitted, but OMITTAG NO was specified
    …argar canciones Regueton ultimas 2012, descargar musica mp3 de moda gratis</td>

    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 189, Column 42: start tag was here
    …								<td class="recentSearch_text"><center><h2>Descargar Musica Mp3</h2><ce…
  • Error Line 362, Column 8: document type does not allow element "tr" here; assuming missing "table" start-tag
    		  <tr>
  • Error Line 371, Column 266: end tag for "span" omitted, but OMITTAG NO was specified
    …n completa, taringa musica,  para smartphone, bajar  para android en mp3.</div>

    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 371, Column 1: start tag was here
    <span style="font-size:85%;"> mp3 gratis, escuchar y  rapido,  para movil grati…
  • Error Line 382, Column 8: required attribute "type" not specified
    <script>section=3582897;popTimes=3;</script><script src="http://cdn.adbooth.net…

    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 382, Column 8: document type does not allow element "script" here
    <script>section=3582897;popTimes=3;</script><script src="http://cdn.adbooth.net…

    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 382, Column 115: required attribute "type" not specified
    …script src="http://cdn.adbooth.net/src/js/v2/min/adbooth_popunder.js"></script>

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

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

  • Error Line 382, Column 115: document type does not allow element "script" here
    …script src="http://cdn.adbooth.net/src/js/v2/min/adbooth_popunder.js"></script>

    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 384, Column 7: end tag for "table" 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 18, Column 1: start tag was here
    <table width="100%" border="0" cellspacing="0" cellpadding="0">

Visitor Analysis

Daily Visitor
  • 4.900 visits
Daily Visitor