Free iPhone and Mobile Ringtones, Make your own Ringtone ...

free-ringtones.cc
  • Domain Name
    free-ringtones.cc
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #65621
  • Page Size
    14.5 KB
  • Ip Address
    68.233.252.66
  • Heading
    H1: 1, H2: 2, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 1 JPG, 4 PNG

Website Meta Analysis

  • Title
    Free Ringtones for iPhone and Android. Free Online Ringtone Maker
  • Meta Keyword
    Ringtones, Download, iPhone, Free, MP3, Ring tones, Make ringtone, Nokia, java, games, mobile, Cell, phone, android, wallapers, tones
  • Meta Description
    Free iPhone and Mobile Ringtones, Make your own Ringtone

Technical Analysis

  • Webserver
    nginx/1.0.15
  • Ip Address
    68.233.252.66
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from free-ringtones.cc.

HTML Analysis

  • server: nginx/1.0.15
  • date: Sun, 18 Aug 2013 09:03:24 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.3.18
  • expires: Sun, 18 Aug 2013 10:03:24 GMT
  • cache-control: max-age=3600
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for free-ringtones.cc

DNS Analysis


DNS servers
ns10.dnsmadeeasy.com [208.94.148.4]
ns11.dnsmadeeasy.com [208.80.124.4]
ns12.dnsmadeeasy.com [208.80.126.4]
ns14.dnsmadeeasy.com [208.80.127.4]
ns13.dnsmadeeasy.com [208.80.125.4]
ns15.dnsmadeeasy.com [208.94.149.4]


DNS Records

Answer records
free-ringtones.cc MX
preference: 10
exchange: mail.free-ringtones.cc
600s
free-ringtones.cc A 68.233.252.66 3600s
free-ringtones.cc NS  ns11.dnsmadeeasy.com 86400s
free-ringtones.cc NS  ns13.dnsmadeeasy.com 86400s
free-ringtones.cc NS  ns14.dnsmadeeasy.com 86400s
free-ringtones.cc NS  ns10.dnsmadeeasy.com 86400s
free-ringtones.cc NS  ns15.dnsmadeeasy.com 86400s
free-ringtones.cc NS  ns12.dnsmadeeasy.com 86400s
free-ringtones.cc SOA
server: ns10.dnsmadeeasy.com
email: dns@dnsmadeeasy.com
serial: 2009010133
refresh: 43200
retry: 3600
expire: 1209600
minimum ttl: 180
86400s

Authority records

Additional records

IP 68.233.252.66 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Tampa
  • Continent Code
    33611
  • Latitude
    813
  • Longitude
    539
  • %rwhois V-1.0,V-1.5:00090h:00 manage.hivelocity.net (Ubersmith RWhois Server V-2.3.0)
    autharea=68.233.224.0/19
    xautharea=68.233.224.0/19
    network:Class-Name:network
    network:Auth-Area:68.233.224.0/19
    network:ID:NET-33135.68.233.252.66
    network:Network-Name:68.233.252.66
    network:IP-Network:68.233.252.66
    network:IP-Network-Block:68.233.252.66
    network:Org-Name:zamir, Ehud
    network:Street-Address:Moshe kol 8/7
    network:City:Jerusalem
    network:State:
    network:Postal-Code:93715
    network:Country-Code:IL
    network:Tech-Contact:MAINT-33135.68.233.252.66
    network:Created:20110722183706000
    network:Updated:20120917005424000
    network:Updated-By:ipAdmin@hivelocity.net
    contact:POC-Name:Network Administrator
    contact:POC-Email:ipAdmin@hivelocity.net
    contact:POC-Phone:888-869-4678
    contact:Tech-Name:Network Administrator
    contact:Tech-Email:ipAdmin@hivelocity.net
    contact:Tech-Phone:888-869-4678
    contact:Abuse-Name:Hivelocity Abuse Department
    contact:Abuse-Email:abuse@hivelocity.net
    contact:Abuse-Phone:888-869-4678
    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 32 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.578047138047138
Message Error
  • Error Line 6, Column 20: there is no attribute "NAME"
            <META NAME="description" CONTENT="Free iPhone and Mobile Ringtones, Mak…

    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 6, Column 42: there is no attribute "CONTENT"
    …     <META NAME="description" CONTENT="Free iPhone and Mobile Ringtones, Make …

    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 6, Column 102: element "META" undefined
    …cription" CONTENT="Free iPhone and Mobile Ringtones, Make your own Ringtone" />

    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 8, Column 24: there is no attribute "property"
            <meta property="fb:admins" content="594566334" />

    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 13, Column 64: end tag for "link" omitted, but OMITTAG NO was specified
    <link type="text/css" rel="stylesheet" href="/min/?g=head-css">

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

  • Info Line 13, Column 1: start tag was here
    <link type="text/css" rel="stylesheet" href="/min/?g=head-css">
  • Warning Line 15, Column 78: cannot generate system identifier for general entity "v"
    …="text/javascript" src="/min/?f=wimpy_lib/wimpy_button_bridge.js&v=4"></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 15, Column 78: general entity "v" not defined and no default entity
    …="text/javascript" src="/min/?f=wimpy_lib/wimpy_button_bridge.js&v=4"></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 15, Column 79: reference not terminated by REFC delimiter
    …="text/javascript" src="/min/?f=wimpy_lib/wimpy_button_bridge.js&v=4"></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 15, Column 79: reference to external entity in attribute value
    …="text/javascript" src="/min/?f=wimpy_lib/wimpy_button_bridge.js&v=4"></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 15, Column 79: reference to entity "v" for which no system identifier could be generated
    …="text/javascript" src="/min/?f=wimpy_lib/wimpy_button_bridge.js&v=4"></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 15, Column 77: entity was defined here
    …="text/javascript" src="/min/?f=wimpy_lib/wimpy_button_bridge.js&v=4"></script>
  • Error Line 32, Column 18: there is no attribute "http-equiv"
    <META http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 

    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 32, Column 41: there is no attribute "content"
    <META http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 

    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 32, Column 69: element "META" undefined
    <META http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 

    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 35, Column 17: required attribute "type" not specified
            	<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 55, Column 96: cannot generate system identifier for general entity "rnd"
    …ow.location.host + "/ajaxHandler.php?sort=" + sortType + '&rnd=' + d.getTime(),

    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 55, Column 96: general entity "rnd" not defined and no default entity
    …ow.location.host + "/ajaxHandler.php?sort=" + sortType + '&rnd=' + d.getTime(),

    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 55, Column 99: reference not terminated by REFC delimiter
    …ow.location.host + "/ajaxHandler.php?sort=" + sortType + '&rnd=' + d.getTime(),

    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 55, Column 99: reference to entity "rnd" for which no system identifier could be generated
    …ow.location.host + "/ajaxHandler.php?sort=" + sortType + '&rnd=' + d.getTime(),

    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 55, Column 95: entity was defined here
    …ow.location.host + "/ajaxHandler.php?sort=" + sortType + '&rnd=' + d.getTime(),
  • Error Line 119, Column 98: required attribute "alt" not specified
    …c="http://free-ringtones.cc/images/logo_and_text.png" title="Free Ringtones" />

    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 123, Column 43: value of attribute "method" cannot be "GET"; must be one of "get", "post"
    …    <form id="form_search" method="GET" action="http://free-ringtones.cc/ringt…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 124, Column 51: there is no attribute "watermark"
    …<input type="text" name="q" watermark="{html:'Search...',css:{color:'#313131'}…

    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 182, Column 17: there is no attribute "size"
    <g:plusone size="medium" href="http://www.free-ringtones.cc/"></g:plusone>

    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 182, Column 31: there is no attribute "href"
    <g:plusone size="medium" href="http://www.free-ringtones.cc/"></g:plusone>

    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 182, Column 62: element "g:plusone" undefined
    <g:plusone size="medium" href="http://www.free-ringtones.cc/"></g:plusone>

    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 202, Column 56: required attribute "alt" not specified
                            <img src="images/homepage.jpg"/>

    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 204, Column 150: required attribute "alt" not specified
    …ke-ringtone" title="Make your own ringtone!"><img src="images/spacer.png"/></a>

    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 205, Column 151: required attribute "alt" not specified
    …ke-ringtone" title="Make your own ringtone!"><img src="images/spacer.png"/></a>

    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 206, Column 156: required attribute "alt" not specified
    …nes/Category/All" title="Download ringtones"><img src="images/spacer.png"/></a>

    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 236, Column 64: required attribute "alt" not specified
    			    <img src="http://free-ringtones.cc/images/ad_text.gif" />	    

    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 237, Column 99: cannot generate system identifier for general entity "zid"
    …rc="http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></scr…

    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 237, Column 99: general entity "zid" not defined and no default entity
    …rc="http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></scr…

    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 237, Column 102: reference not terminated by REFC delimiter
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 102: reference to external entity in attribute value
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 102: reference to entity "zid" for which no system identifier could be generated
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 98: entity was defined here
    …src="http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></sc…
  • Warning Line 237, Column 109: cannot generate system identifier for general entity "wd"
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 109: general entity "wd" not defined and no default entity
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 111: reference not terminated by REFC delimiter
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 111: reference to external entity in attribute value
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 111: reference to entity "wd" for which no system identifier could be generated
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 108: entity was defined here
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></script>
  • Warning Line 237, Column 115: cannot generate system identifier for general entity "ht"
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 115: general entity "ht" not defined and no default entity
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 117: reference not terminated by REFC delimiter
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 117: reference to external entity in attribute value
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 117: reference to entity "ht" for which no system identifier could be generated
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 114: entity was defined here
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></script>
  • Warning Line 237, Column 121: cannot generate system identifier for general entity "target"
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 121: general entity "target" not defined and no default entity
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 127: reference not terminated by REFC delimiter
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 127: reference to external entity in attribute value
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 127: reference to entity "target" for which no system identifier could be generated
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></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 237, Column 120: entity was defined here
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></script>
  • Error Line 243, Column 276: there is no attribute "allowTransparency"
    … overflow:hidden; width:239px; height:328px" 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 256, Column 98: document type does not allow element "a" here; assuming missing "li" start-tag
    …ttp://free-ringtones.cc/topartists" class="arrow_link">More popular artists</a>
  • Error Line 257, Column 8: end tag for "li" omitted, but OMITTAG NO was specified
    			</ul>

    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 256, Column 8: start tag was here
    			    <a style="margin-top: 17px;" href="http://free-ringtones.cc/topartists" …
  • Error Line 267, Column 41: there is no attribute "data-position"
            <div id="footer"  data-position="fixed">

    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 271, Column 7: end tag for "br" omitted, but OMITTAG NO was specified
    		<br>

    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 271, Column 3: start tag was here
    		<br>
  • Warning Line 272, Column 85: reference not terminated by REFC delimiter
    …"http://g.adspeed.net/ad.php?do=js&zid=30195&wd=-1&ht=-1&target=_top"></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 272, Column 85: reference to external entity in attribute value
    …"http://g.adspeed.net/ad.php?do=js&zid=30195&wd=-1&ht=-1&target=_top"></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 272, Column 85: reference to entity "zid" for which no system identifier could be generated
    …"http://g.adspeed.net/ad.php?do=js&zid=30195&wd=-1&ht=-1&target=_top"></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 237, Column 98: entity was defined here
    …src="http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></sc…
  • Warning Line 272, Column 94: reference not terminated by REFC delimiter
    …"http://g.adspeed.net/ad.php?do=js&zid=30195&wd=-1&ht=-1&target=_top"></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 272, Column 94: reference to external entity in attribute value
    …"http://g.adspeed.net/ad.php?do=js&zid=30195&wd=-1&ht=-1&target=_top"></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 272, Column 94: reference to entity "wd" for which no system identifier could be generated
    …"http://g.adspeed.net/ad.php?do=js&zid=30195&wd=-1&ht=-1&target=_top"></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 237, Column 108: entity was defined here
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></script>
  • Warning Line 272, Column 100: reference not terminated by REFC delimiter
    …"http://g.adspeed.net/ad.php?do=js&zid=30195&wd=-1&ht=-1&target=_top"></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 272, Column 100: reference to external entity in attribute value
    …"http://g.adspeed.net/ad.php?do=js&zid=30195&wd=-1&ht=-1&target=_top"></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 272, Column 100: reference to entity "ht" for which no system identifier could be generated
    …"http://g.adspeed.net/ad.php?do=js&zid=30195&wd=-1&ht=-1&target=_top"></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 237, Column 114: entity was defined here
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></script>
  • Warning Line 272, Column 110: reference not terminated by REFC delimiter
    …"http://g.adspeed.net/ad.php?do=js&zid=30195&wd=-1&ht=-1&target=_top"></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 272, Column 110: reference to external entity in attribute value
    …"http://g.adspeed.net/ad.php?do=js&zid=30195&wd=-1&ht=-1&target=_top"></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 272, Column 110: reference to entity "target" for which no system identifier could be generated
    …"http://g.adspeed.net/ad.php?do=js&zid=30195&wd=-1&ht=-1&target=_top"></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 237, Column 120: entity was defined here
    …"http://g.adspeed.net/ad.php?do=js&zid=27314&wd=-1&ht=-1&target=_top"></script>
  • Warning Line 284, Column 37: character "&" is the first character of a delimiter but occurred as data
                    <li><a title="Terms & conditions" href="http://free-ringtones.c…

    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.

Visitor Analysis

Daily Visitor
  • 4.083 visits