MP3 Music Song Lagu Download Free - MP3crop.com is an Search Engine-Designed for legal entertainment purposes only ...

mp3crop.com
  • Domain Name
    mp3crop.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #55083
  • Page Size
    22.3 KB
  • Ip Address
    216.172.108.244
  • Heading
    H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    MP3 Music Song Lagu Download Free
  • Meta Keyword
    mp3, download, lyrics, music, songs, lagu, lirik, free, gratis, 4shared
  • Meta Description
    MP3 Music Song Lagu Download Free - MP3crop.com is an Search Engine-Designed for legal entertainment purposes only

Technical Analysis

  • Webserver
    nginx admin
  • Ip Address
    216.172.108.244
  • Domain Age
    10 Months, 27 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx admin
  • date: Sun, 17 Feb 2013 11:48:27 GMT
  • content-type: text/html
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.3.21
  • cache-control: max-age=0
  • expires: Sun, 17 Feb 2013 11:48:27 GMT
  • x-cache: HIT from Backend
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: mp3crop.com
Registrar: Name.com LLC

Protected Domain Services Customer ID: NCR-4082251

Expiration Date: 2014-03-27 09:25:34
Creation Date: 2012-03-27 09:25:34

Name Servers:
ns1.name.com
ns2.name.com
ns3.name.com
ns4.name.com

Domain privacy provided by Protected Domain Services. For more information see www.protecteddomainservices.com

REGISTRANT CONTACT INFO
Protected Domain Services - Customer ID: NCR-4082251
P.O. Box 6197
Denver
CO
80206
US
Phone: +1.7202492374
Email Address: email

ADMINISTRATIVE CONTACT INFO
Protected Domain Services - Customer ID: NCR-4082251
P.O. Box 6197
Denver
CO
80206
US
Phone: +1.7202492374
Email Address: email

TECHNICAL CONTACT INFO
Protected Domain Services - Customer ID: NCR-4082251
P.O. Box 6197
Denver
CO
80206
US
Phone: +1.7202492374
Email Address: email

BILLING CONTACT INFO
Protected Domain Services - Customer ID: NCR-4082251
P.O. Box 6197
Denver
CO
80206
US
Phone: +1.7202492374
Email Address: email

DNS Analysis


DNS servers
ns1.crophost.info [184.164.156.114]
ns2.crophost.info [184.164.156.115]


DNS Records

Answer records
mp3crop.com TXT v=spf1 +a +mx +ip4:184.164.156.114 ?all 14400s
mp3crop.com MX
preference: 0
exchange: mp3crop.com
14400s
mp3crop.com SOA
server: ns1.crophost.info
email: mp3crop@gmail.com
serial: 2013020306
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
mp3crop.com NS  ns1.crophost.info 86400s
mp3crop.com NS  ns2.crophost.info 86400s
mp3crop.com A 184.164.156.118 14400s

Authority records

Additional records
mp3crop.com A 184.164.156.118 14400s
ns1.crophost.info A 184.164.156.114 14400s
ns2.crophost.info A 184.164.156.115 14400s

IP 216.172.108.244 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 51 Errors
  • 20 Warnings
Ratio Text/Html
  • 0.6814225099514457
Message Error
  • Error Line 40, Column 20: there is no attribute "property"
        <meta property="og:title" content=" MP3 Music Song Lagu Download Free" /> 

    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 120, Column 104: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …px 10px 0 15px"><a href="http://mp3crop.com/"><div class="logo"></div></a></td>

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

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

  • Warning Line 125, Column 20: character "<" is the first character of a delimiter but occurred as data
    			for (var i=0; i < 100; i++) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 139, Column 29: character "&" is the first character of a delimiter but occurred as data
    		  if ((evt.keyCode == 13) && (node.type=="text"))  {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 139, Column 30: character "&" is the first character of a delimiter but occurred as data
    		  if ((evt.keyCode == 13) && (node.type=="text"))  {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 152, Column 50: required attribute "action" not specified
              <form name="searchForm" id="searchForm">

    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 155, Column 99: there is no attribute "autofocus"
    …vkatakunci" maxlength="256" autofocus="autofocus" placeholder="type your favou…

    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 155, Column 123: there is no attribute "placeholder"
    …56" autofocus="autofocus" placeholder="type your favourite mp3 song title or a…

    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 155, Column 184: "required" is not a member of a group specified for any attribute
    …cus" placeholder="type your favourite mp3 song title or artist here" required/>
  • Error Line 156, Column 58: there is no attribute "onClick"
    …   <input id="searchSubmit" type="button" onClick="cari_file()" value="Search">

    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 156, Column 87: end tag for "input" omitted, but OMITTAG NO was specified
    …   <input id="searchSubmit" type="button" onClick="cari_file()" value="Search">

    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 156, Column 11: start tag was here
              <input id="searchSubmit" type="button" onClick="cari_file()" value="S…
  • Error Line 157, Column 15: end tag for "form" omitted, but OMITTAG NO was specified
             </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 152, Column 11: start tag was here
              <form name="searchForm" id="searchForm">
  • Error Line 167, Column 16: end tag for element "form" which is not open
             </form>       

    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 186, Column 5: end tag for element "br" which is not open
    </br></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 186, Column 10: end tag for element "br" which is not open
    </br></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 187, Column 185: required attribute "alt" not specified
    …r="0" style="vertical-align:middle;" /></a> <a href="http://www.facebook.com/p…

    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 190, Column 388: there is no attribute "allowTransparency"
    …; overflow:hidden; width:90px; height:21px;" allowTransparency="true"></iframe>

    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 192, Column 85: there is no attribute "data-show-count"
    …crop" class="twitter-follow-button" data-show-count="false">Follow @mp3crop</a>

    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 193, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

    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 195, Column 34: there is no attribute "data-size"
    <div class="g-plusone" data-size="small" data-href="https://plus.google.com/u/0…

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

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

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

  • Error Line 195, Column 52: there is no attribute "data-href"
    …-plusone" data-size="small" data-href="https://plus.google.com/u/0/b/112516958…

    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 213, Column 21: an attribute specification must start with a name or name token
    document.write('<scr'+'ipt src="http://adserver.adreactor.com/servlet/view/bann…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 213, Column 21: element "scr" undefined
    document.write('<scr'+'ipt src="http://adserver.adreactor.com/servlet/view/bann…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 213, Column 105: cannot generate system identifier for general entity "pid"
    …let/view/banner/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Mat…

    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 213, Column 105: general entity "pid" not defined and no default entity
    …let/view/banner/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Mat…

    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 213, Column 108: reference not terminated by REFC delimiter
    …/view/banner/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Math.r…

    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.

  • Error Line 213, Column 108: reference to entity "pid" for which no system identifier could be generated
    …/view/banner/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Math.r…

    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 213, Column 104: entity was defined here
    …vlet/view/banner/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Ma…
  • Warning Line 213, Column 113: cannot generate system identifier for general entity "random"
    …/banner/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Math.random…

    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 213, Column 113: general entity "random" not defined and no default entity
    …/banner/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Math.random…

    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 213, Column 119: reference not terminated by REFC delimiter
    …r/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Math.random()+100…

    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.

  • Error Line 213, Column 119: reference to entity "random" for which no system identifier could be generated
    …r/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Math.random()+100…

    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 213, Column 112: entity was defined here
    …w/banner/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Math.rando…
  • Warning Line 213, Column 168: cannot generate system identifier for general entity "millis"
    …or(89999999*Math.random()+10000000)+'&millis='+new Date().getTime()+'&referrer…

    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 213, Column 168: general entity "millis" not defined and no default entity
    …or(89999999*Math.random()+10000000)+'&millis='+new Date().getTime()+'&referrer…

    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 213, Column 174: reference not terminated by REFC delimiter
    …99999*Math.random()+10000000)+'&millis='+new Date().getTime()+'&referrer='+enc…

    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.

  • Error Line 213, Column 174: reference to entity "millis" for which no system identifier could be generated
    …99999*Math.random()+10000000)+'&millis='+new Date().getTime()+'&referrer='+enc…

    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 213, Column 167: entity was defined here
    …oor(89999999*Math.random()+10000000)+'&millis='+new Date().getTime()+'&referre…
  • Warning Line 213, Column 200: cannot generate system identifier for general entity "referrer"
    …00)+'&millis='+new Date().getTime()+'&referrer='+encodeURIComponent(document.l…

    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 213, Column 200: general entity "referrer" not defined and no default entity
    …00)+'&millis='+new Date().getTime()+'&referrer='+encodeURIComponent(document.l…

    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 213, Column 208: reference not terminated by REFC delimiter
    …llis='+new Date().getTime()+'&referrer='+encodeURIComponent(document.location)…

    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.

  • Error Line 213, Column 208: reference to entity "referrer" for which no system identifier could be generated
    …llis='+new Date().getTime()+'&referrer='+encodeURIComponent(document.location)…

    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 213, Column 199: entity was defined here
    …000)+'&millis='+new Date().getTime()+'&referrer='+encodeURIComponent(document.…
  • Error Line 213, Column 280: delimiter "'" invalid: only S separators and TAGC allowed here
    …encodeURIComponent(document.location)+'" type="text/javascript"></scr'+'ipt>');
  • Error Line 221, Column 34: end tag for element "br" which is not open
         <b>MP3crop SearchBox</b></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 223, Column 86: required attribute "rows" not specified
    … <textarea name="textarea" style="width:300px;height:50px;" onclick="select()">

    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 223, Column 86: required attribute "cols" not specified
    … <textarea name="textarea" style="width:300px;height:50px;" onclick="select()">

    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 232, Column 20: end tag for element "br" which is not open
        </textarea></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 243, Column 110: there is no attribute "alt"
    …lewis_feat_wanz_thrift_shop.html' alt='download macklemore amp ryan lewis feat…

    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 294, Column 21: an attribute specification must start with a name or name token
    document.write('<scr'+'ipt src="http://adserver.adreactor.com/servlet/view/bann…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 294, Column 21: element "scr" undefined
    document.write('<scr'+'ipt src="http://adserver.adreactor.com/servlet/view/bann…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 294, Column 108: reference not terminated by REFC delimiter
    …/view/banner/javascript/zone?zid=9&pid=357&random='+Math.floor(89999999*Math.r…

    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.

  • Error Line 294, Column 108: reference to entity "pid" for which no system identifier could be generated
    …/view/banner/javascript/zone?zid=9&pid=357&random='+Math.floor(89999999*Math.r…

    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 213, Column 104: entity was defined here
    …vlet/view/banner/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Ma…
  • Warning Line 294, Column 119: reference not terminated by REFC delimiter
    …r/javascript/zone?zid=9&pid=357&random='+Math.floor(89999999*Math.random()+100…

    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.

  • Error Line 294, Column 119: reference to entity "random" for which no system identifier could be generated
    …r/javascript/zone?zid=9&pid=357&random='+Math.floor(89999999*Math.random()+100…

    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 213, Column 112: entity was defined here
    …w/banner/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Math.rando…
  • Warning Line 294, Column 174: reference not terminated by REFC delimiter
    …99999*Math.random()+10000000)+'&millis='+new Date().getTime()+'&referrer='+enc…

    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.

  • Error Line 294, Column 174: reference to entity "millis" for which no system identifier could be generated
    …99999*Math.random()+10000000)+'&millis='+new Date().getTime()+'&referrer='+enc…

    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 213, Column 167: entity was defined here
    …oor(89999999*Math.random()+10000000)+'&millis='+new Date().getTime()+'&referre…
  • Warning Line 294, Column 208: reference not terminated by REFC delimiter
    …llis='+new Date().getTime()+'&referrer='+encodeURIComponent(document.location)…

    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.

  • Error Line 294, Column 208: reference to entity "referrer" for which no system identifier could be generated
    …llis='+new Date().getTime()+'&referrer='+encodeURIComponent(document.location)…

    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 213, Column 199: entity was defined here
    …000)+'&millis='+new Date().getTime()+'&referrer='+encodeURIComponent(document.…
  • Error Line 294, Column 280: delimiter "'" invalid: only S separators and TAGC allowed here
    …encodeURIComponent(document.location)+'" type="text/javascript"></scr'+'ipt>');
  • Error Line 299, Column 35: end tag for element "br" which is not open
    <strong>Last Search :</strong></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 304, Column 21: an attribute specification must start with a name or name token
    document.write('<scr'+'ipt src="http://adserver.adreactor.com/servlet/view/bann…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 304, Column 21: element "scr" undefined
    document.write('<scr'+'ipt src="http://adserver.adreactor.com/servlet/view/bann…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 304, Column 109: reference not terminated by REFC delimiter
    …view/banner/javascript/zone?zid=34&pid=357&random='+Math.floor(89999999*Math.r…

    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.

  • Error Line 304, Column 109: reference to entity "pid" for which no system identifier could be generated
    …view/banner/javascript/zone?zid=34&pid=357&random='+Math.floor(89999999*Math.r…

    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 213, Column 104: entity was defined here
    …vlet/view/banner/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Ma…
  • Warning Line 304, Column 120: reference not terminated by REFC delimiter
    …/javascript/zone?zid=34&pid=357&random='+Math.floor(89999999*Math.random()+100…

    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.

  • Error Line 304, Column 120: reference to entity "random" for which no system identifier could be generated
    …/javascript/zone?zid=34&pid=357&random='+Math.floor(89999999*Math.random()+100…

    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 213, Column 112: entity was defined here
    …w/banner/javascript/zone?zid=6&pid=357&random='+Math.floor(89999999*Math.rando…
  • Warning Line 304, Column 175: reference not terminated by REFC delimiter
    …99999*Math.random()+10000000)+'&millis='+new Date().getTime()+'&referrer='+enc…

    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.

  • Error Line 304, Column 175: reference to entity "millis" for which no system identifier could be generated
    …99999*Math.random()+10000000)+'&millis='+new Date().getTime()+'&referrer='+enc…

    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 213, Column 167: entity was defined here
    …oor(89999999*Math.random()+10000000)+'&millis='+new Date().getTime()+'&referre…
  • Warning Line 304, Column 209: reference not terminated by REFC delimiter
    …llis='+new Date().getTime()+'&referrer='+encodeURIComponent(document.location)…

    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.

  • Error Line 304, Column 209: reference to entity "referrer" for which no system identifier could be generated
    …llis='+new Date().getTime()+'&referrer='+encodeURIComponent(document.location)…

    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 213, Column 199: entity was defined here
    …000)+'&millis='+new Date().getTime()+'&referrer='+encodeURIComponent(document.…
  • Error Line 304, Column 281: delimiter "'" invalid: only S separators and TAGC allowed here
    …encodeURIComponent(document.location)+'" type="text/javascript"></scr'+'ipt>');
  • Error Line 330, Column 6: end tag for element "div" which is not open
    </div>

    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.

  • Warning Line 343, Column 112: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?1871886&101" alt="free stats" border="0"></a></…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 343, Column 149: end tag for "img" omitted, but OMITTAG NO was specified
    …tic1.histats.com/0.gif?1871886&101" alt="free stats" border="0"></a></noscript>

    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 343, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/0…

Visitor Analysis

Daily Visitor
  • 2.333 visits
Daily Visitor