Free shoutcast server hosting. Start your own radio station for free! ...

myradiostream.com
  • Domain Name
    myradiostream.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #44375
  • Page Size
    15.9 KB
  • Ip Address
    94.76.204.112
  • Heading
    H1: 0, H2: 4, H3: 5, H4: 0, H5: 0, H6: 2
  • Images
    1 GIF, 1 JPG, 5 PNG

Website Meta Analysis

  • Title
    MyRadioStream.com (FreeStreamHosting) - Free Shoutcast Servers
  • Meta Keyword
    streaming, free, shoutcast, free server, servers, free shoutcast streams
  • Meta Description
    Free shoutcast server hosting. Start your own radio station for free!

Technical Analysis

  • Webserver
    Apache/2.2.15 (CentOS)
  • Ip Address
    94.76.204.112
  • Domain Age
    4 Years, 10 Months, 19 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 17 Aug 2013 10:41:50 GMT
  • server: Apache/2.2.15 (CentOS)
  • x-powered-by: PHP/5.3.3
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: MYRADIOSTREAM.COM

Registrant:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Creation Date: 24-Sep-2008
Expiration Date: 24-Sep-2013

Domain servers in listed order:
ns1.thisdns.net
ns2.thisdns.net


Administrative Contact:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Technical Contact:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Billing Contact:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Status:LOCKED

DNS Analysis


DNS servers
ns1.thisdns.net
ns2.thisdns.net


DNS Records

Answer records
myradiostream.com MX
preference: 0
exchange: myradiostream.com
14400s
myradiostream.com SOA
server: ns1.thisdns.net
email: gavin@bellonline.co.uk
serial: 2009111944
refresh: 10800
retry: 600
expire: 3600000
minimum ttl: 86400
86400s
myradiostream.com NS  ns2.thisdns.net 86400s
myradiostream.com NS  ns1.thisdns.net 86400s
myradiostream.com A 94.76.204.112 14400s

Authority records

Additional records
myradiostream.com A 94.76.204.112 14400s
ns1.thisdns.net A 94.76.253.129 14400s
ns2.thisdns.net A 85.234.144.187 14400s

IP 94.76.204.112 Analysis

  • Country Code
    GB
  • Country Code3
    GBR
  • Country Name
    United Kingdom
  • City
    London
  • Continent Code
    EU
  • Latitude
    51.5002
  • Longitude
    0.1262
  • No whois ip data for 94.76.204.112

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 67 Errors
  • 26 Warnings
Ratio Text/Html
  • 0.5464816406729707
Message Error
  • Error Line 5, Column 59: end tag for "link" omitted, but OMITTAG NO was specified
    <link href="../assets/css/bootstrap.css" rel="stylesheet">

    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 5, Column 1: start tag was here
    <link href="../assets/css/bootstrap.css" rel="stylesheet">
  • Error Line 6, Column 63: end tag for "link" omitted, but OMITTAG NO was specified
    <link href="../assets/css/myradiostream.css" rel="stylesheet">

    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 6, Column 1: start tag was here
    <link href="../assets/css/myradiostream.css" rel="stylesheet">
  • Error Line 7, Column 70: end tag for "link" omitted, but OMITTAG NO was specified
    <link href="../assets/css/bootstrap-responsive.css" rel="stylesheet">

    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 7, Column 1: start tag was here
    <link href="../assets/css/bootstrap-responsive.css" rel="stylesheet">
  • Error Line 9, Column 106: end tag for "meta" omitted, but OMITTAG NO was specified
    …ontent="Free shoutcast server hosting. Start your own radio station for free!">

    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 9, Column 1: start tag was here
    <meta name="description" content="Free shoutcast server hosting. Start your own…
  • Error Line 10, Column 56: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="abstract" content="Free streaming servers">

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

  • Info Line 10, Column 1: start tag was here
    <meta name="abstract" content="Free streaming servers">
  • Error Line 11, Column 78: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="classification" content="web services, free, hosting, streaming">

    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 11, Column 1: start tag was here
    <meta name="classification" content="web services, free, hosting, streaming">
  • Error Line 12, Column 106: end tag for "meta" omitted, but OMITTAG NO was specified
    …ent="streaming, free, shoutcast, free server, servers, free shoutcast streams">

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

  • Info Line 12, Column 1: start tag was here
    <meta name="keywords" content="streaming, free, shoutcast, free server, servers…
  • Error Line 13, Column 44: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="robots" content="index,follow">

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

  • Info Line 13, Column 1: start tag was here
    <meta name="robots" content="index,follow">
  • Error Line 66, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 81, Column 104: there is no attribute "placeholder"
    …xt" id="username" maxlength="50" class="search-query" placeholder="Username" />

    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 90, Column 50: value of attribute "valign" cannot be "center"; must be one of "top", "middle", "bottom", "baseline"
    … <td class="textcenter" valign="center" style="padding: 3px; margin: 0;"><a hr…

    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 90, Column 159: there is no attribute "data-url"
    …class="twitter-share-button" data-url="http://myradiostream.com" data-text="I'…

    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 90, Column 196: there is no attribute "data-text"
    …="http://myradiostream.com" data-text="I'm using a free SHOUTcast server from"…

    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 90, Column 246: there is no attribute "data-via"
    …ext="I'm using a free SHOUTcast server from" data-via="FreeShoutcast">Tweet</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 91, Column 22: required attribute "type" not specified
                  <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0]…

    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 92, Column 81: there is no attribute "data-href"
    …n: 0;"><div class="fb-like" data-href="https://www.facebook.com/bellonlineuk" …

    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 92, Column 131: there is no attribute "data-send"
    ….facebook.com/bellonlineuk" data-send="true" data-layout="button_count" data-w…

    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 92, Column 150: there is no attribute "data-layout"
    …nlineuk" data-send="true" data-layout="button_count" data-width="100" data-sho…

    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 92, Column 176: there is no attribute "data-width"
    …data-layout="button_count" data-width="100" data-show-faces="false"></div></td…

    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 92, Column 198: there is no attribute "data-show-faces"
    …data-layout="button_count" data-width="100" data-show-faces="false"></div></td>

    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 93, Column 50: value of attribute "valign" cannot be "center"; must be one of "top", "middle", "bottom", "baseline"
    … <td class="textcenter" valign="center" style="padding: 3px; margin: 0;"><g:pl…

    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 93, Column 101: there is no attribute "size"
    …ing: 3px; margin: 0;"><g:plusone size="medium" href="http://myradiostream.com"…

    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 93, Column 115: there is no attribute "href"
    …in: 0;"><g:plusone size="medium" href="http://myradiostream.com"></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 93, Column 141: element "g:plusone" undefined
    … 0;"><g:plusone size="medium" href="http://myradiostream.com"></g:plusone></td>

    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 94, Column 50: value of attribute "valign" cannot be "center"; must be one of "top", "middle", "bottom", "baseline"
    … <td class="textcenter" valign="center" style="padding: 3px; margin: 0;"><su:b…

    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 94, Column 102: there is no attribute "layout"
    …"center" style="padding: 3px; margin: 0;"><su:badge layout="1"></su:badge></td>

    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 94, Column 105: element "su:badge" undefined
    …"center" style="padding: 3px; margin: 0;"><su:badge layout="1"></su:badge></td>

    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 97, Column 96: end tag for "img" omitted, but OMITTAG NO was specified
    …s/myradiostream-large.png" alt="My Radio Stream" width="774" height="100"> </p>

    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 97, Column 6: start tag was here
      <p><img src="/images/myradiostream-large.png" alt="My Radio Stream" width="77…
  • Error Line 140, Column 92: there is no attribute "data-widget-id"
    …ter.com/FreeShoutcast" data-widget-id="281440810736689153">Tweets by @FreeShou…

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

    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 150, Column 88: end tag for "br" omitted, but OMITTAG NO was specified
    …streamer - Fox FM 97.9 MHz - Kumasi.</strong></strong><br><small> </small></td>

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

  • Info Line 150, Column 84: start tag was here
    …streamer - Fox FM 97.9 MHz - Kumasi.</strong></strong><br><small> </small></td>
  • Warning Line 151, Column 96: cannot generate system identifier for general entity "q"
    …<a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br><…

    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 151, Column 96: general entity "q" not defined and no default entity
    …<a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br><…

    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 151, Column 97: reference not terminated by REFC delimiter
    …a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br><s…

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

  • Warning Line 151, Column 97: reference to external entity in attribute value
    …a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br><s…

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

  • Error Line 151, Column 97: reference to entity "q" for which no system identifier could be generated
    …a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br><s…

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

  • Info Line 151, Column 95: entity was defined here
    …><a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br>…
  • Error Line 151, Column 135: end tag for "br" omitted, but OMITTAG NO was specified
    …=World">World</a> </span></strong><br><span class="small">679 Listeners, 24kbp…

    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 151, Column 131: start tag was here
    …=1&q=World">World</a> </span></strong><br><span class="small">679 Listeners, 2…
  • Error Line 155, Column 87: end tag for "br" omitted, but OMITTAG NO was specified
    …estreamer - Hot FM 93.9 MHz - Accra.</strong></strong><br><small> </small></td>

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

  • Info Line 155, Column 83: start tag was here
    …estreamer - Hot FM 93.9 MHz - Accra.</strong></strong><br><small> </small></td>
  • Warning Line 156, Column 97: reference not terminated by REFC delimiter
    …a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br><s…

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

  • Warning Line 156, Column 97: reference to external entity in attribute value
    …a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br><s…

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

  • Error Line 156, Column 97: reference to entity "q" for which no system identifier could be generated
    …a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br><s…

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

  • Info Line 151, Column 95: entity was defined here
    …><a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br>…
  • Error Line 156, Column 135: end tag for "br" omitted, but OMITTAG NO was specified
    …=World">World</a> </span></strong><br><span class="small">374 Listeners, 24kbp…

    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 131: start tag was here
    …=1&q=World">World</a> </span></strong><br><span class="small">374 Listeners, 2…
  • Error Line 160, Column 100: end tag for "br" omitted, but OMITTAG NO was specified
    …hat Doesn't Suck</strong></strong><br><small>Five Finger Death Punch - Hard to…

    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 160, Column 96: start tag was here
    …ic That Doesn't Suck</strong></strong><br><small>Five Finger Death Punch - Har…
  • Error Line 160, Column 289: required attribute "alt" not specified
    …et="_blank"><img src="/images/buy.png" width="50" height="16"></a></small></td>

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

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

  • Error Line 160, Column 293: end tag for "img" omitted, but OMITTAG NO was specified
    …et="_blank"><img src="/images/buy.png" width="50" height="16"></a></small></td>

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

  • Info Line 160, Column 240: start tag was here
    …ch%20Hard%20to%20See" target="_blank"><img src="/images/buy.png" width="50" he…
  • Warning Line 161, Column 121: reference not terminated by REFC delimiter
    …a href="/browse/stations.php?genre=1&q=Metal">Metal</a> <a href="/browse/stati…

    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 161, Column 121: reference to external entity in attribute value
    …a href="/browse/stations.php?genre=1&q=Metal">Metal</a> <a href="/browse/stati…

    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 161, Column 121: reference to entity "q" for which no system identifier could be generated
    …a href="/browse/stations.php?genre=1&q=Metal">Metal</a> <a href="/browse/stati…

    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 151, Column 95: entity was defined here
    …><a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br>…
  • Warning Line 161, Column 178: reference not terminated by REFC delimiter
    …a href="/browse/stations.php?genre=1&q=Hard">Hard</a> <a href="/browse/station…

    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 161, Column 178: reference to external entity in attribute value
    …a href="/browse/stations.php?genre=1&q=Hard">Hard</a> <a href="/browse/station…

    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 161, Column 178: reference to entity "q" for which no system identifier could be generated
    …a href="/browse/stations.php?genre=1&q=Hard">Hard</a> <a href="/browse/station…

    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 151, Column 95: entity was defined here
    …><a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br>…
  • Warning Line 161, Column 233: reference not terminated by REFC delimiter
    …a href="/browse/stations.php?genre=1&q=Rock">Rock</a> <a href="/browse/station…

    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 161, Column 233: reference to external entity in attribute value
    …a href="/browse/stations.php?genre=1&q=Rock">Rock</a> <a href="/browse/station…

    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 161, Column 233: reference to entity "q" for which no system identifier could be generated
    …a href="/browse/stations.php?genre=1&q=Rock">Rock</a> <a href="/browse/station…

    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 151, Column 95: entity was defined here
    …><a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br>…
  • Warning Line 161, Column 288: reference not terminated by REFC delimiter
    …a href="/browse/stations.php?genre=1&q=Heavy">Heavy</a> </span></strong><br><s…

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

  • Warning Line 161, Column 288: reference to external entity in attribute value
    …a href="/browse/stations.php?genre=1&q=Heavy">Heavy</a> </span></strong><br><s…

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

  • Error Line 161, Column 288: reference to entity "q" for which no system identifier could be generated
    …a href="/browse/stations.php?genre=1&q=Heavy">Heavy</a> </span></strong><br><s…

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

  • Info Line 151, Column 95: entity was defined here
    …><a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br>…
  • Error Line 161, Column 326: end tag for "br" omitted, but OMITTAG NO was specified
    …=Heavy">Heavy</a> </span></strong><br><span class="small">246 Listeners, 128kb…

    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 161, Column 322: start tag was here
    …=1&q=Heavy">Heavy</a> </span></strong><br><span class="small">246 Listeners, 1…
  • Error Line 165, Column 61: end tag for "br" omitted, but OMITTAG NO was specified
    …g>Al Islah Radio</strong></strong><br><small>MICR - : : : L I V E   C H A R C …

    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 165, Column 57: start tag was here
    …trong>Al Islah Radio</strong></strong><br><small>MICR - : : : L I V E   C H A …
  • Error Line 165, Column 334: required attribute "alt" not specified
    …et="_blank"><img src="/images/buy.png" width="50" height="16"></a></small></td>

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

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

  • Error Line 165, Column 338: end tag for "img" omitted, but OMITTAG NO was specified
    …et="_blank"><img src="/images/buy.png" width="50" height="16"></a></small></td>

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

  • Info Line 165, Column 285: start tag was here
    …AM%20alislahradiocom" target="_blank"><img src="/images/buy.png" width="50" he…
  • Warning Line 166, Column 96: reference not terminated by REFC delimiter
    …a href="/browse/stations.php?genre=1&q=Talk">Talk</a> </span></strong><br><spa…

    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 166, Column 96: reference to external entity in attribute value
    …a href="/browse/stations.php?genre=1&q=Talk">Talk</a> </span></strong><br><spa…

    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 166, Column 96: reference to entity "q" for which no system identifier could be generated
    …a href="/browse/stations.php?genre=1&q=Talk">Talk</a> </span></strong><br><spa…

    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 151, Column 95: entity was defined here
    …><a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br>…
  • Error Line 166, Column 132: end tag for "br" omitted, but OMITTAG NO was specified
    …&q=Talk">Talk</a> </span></strong><br><span class="small">200 Listeners, 24kbp…

    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 166, Column 128: start tag was here
    …re=1&q=Talk">Talk</a> </span></strong><br><span class="small">200 Listeners, 2…
  • Error Line 170, Column 95: end tag for "br" omitted, but OMITTAG NO was specified
    …e best new music</strong></strong><br><small>BBE - Seven Days And One Week <a …

    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 170, Column 91: start tag was here
    …d the best new music</strong></strong><br><small>BBE - Seven Days And One Week…
  • Error Line 170, Column 266: required attribute "alt" not specified
    …et="_blank"><img src="/images/buy.png" width="50" height="16"></a></small></td>

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

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

  • Error Line 170, Column 270: end tag for "img" omitted, but OMITTAG NO was specified
    …et="_blank"><img src="/images/buy.png" width="50" height="16"></a></small></td>

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

  • Info Line 170, Column 217: start tag was here
    …s%20And%20One%20Week" target="_blank"><img src="/images/buy.png" width="50" he…
  • Warning Line 171, Column 128: reference not terminated by REFC delimiter
    …a href="/browse/stations.php?genre=1&q=house">house</a> <a href="/browse/stati…

    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 171, Column 128: reference to external entity in attribute value
    …a href="/browse/stations.php?genre=1&q=house">house</a> <a href="/browse/stati…

    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 171, Column 128: reference to entity "q" for which no system identifier could be generated
    …a href="/browse/stations.php?genre=1&q=house">house</a> <a href="/browse/stati…

    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 151, Column 95: entity was defined here
    …><a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br>…
  • Warning Line 171, Column 185: reference not terminated by REFC delimiter
    …a href="/browse/stations.php?genre=1&q=trance">trance</a> <a href="/browse/sta…

    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 171, Column 185: reference to external entity in attribute value
    …a href="/browse/stations.php?genre=1&q=trance">trance</a> <a href="/browse/sta…

    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 171, Column 185: reference to entity "q" for which no system identifier could be generated
    …a href="/browse/stations.php?genre=1&q=trance">trance</a> <a href="/browse/sta…

    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 151, Column 95: entity was defined here
    …><a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br>…
  • Warning Line 171, Column 244: reference not terminated by REFC delimiter
    …a href="/browse/stations.php?genre=1&q=techno">techno</a> </span></strong><br>…

    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 171, Column 244: reference to external entity in attribute value
    …a href="/browse/stations.php?genre=1&q=techno">techno</a> </span></strong><br>…

    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 171, Column 244: reference to entity "q" for which no system identifier could be generated
    …a href="/browse/stations.php?genre=1&q=techno">techno</a> </span></strong><br>…

    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 151, Column 95: entity was defined here
    …><a href="/browse/stations.php?genre=1&q=World">World</a> </span></strong><br>…
  • Error Line 171, Column 284: end tag for "br" omitted, but OMITTAG NO was specified
    …echno">techno</a> </span></strong><br><span class="small">193 Listeners, 128kb…

    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 171, Column 280: start tag was here
    …&q=techno">techno</a> </span></strong><br><span class="small">193 Listeners, 1…
  • Warning Line 176, Column 88: cannot generate system identifier for general entity "ref"
    …pacialaudio.com/?page=sam-broadcaster&ref=A1100&redirect=SAM_Broadcaster" alt=…

    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 176, Column 88: general entity "ref" not defined and no default entity
    …pacialaudio.com/?page=sam-broadcaster&ref=A1100&redirect=SAM_Broadcaster" alt=…

    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 176, Column 91: reference not terminated by REFC delimiter
    …ialaudio.com/?page=sam-broadcaster&ref=A1100&redirect=SAM_Broadcaster" alt="Sp…

    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 176, Column 91: reference to external entity in attribute value
    …ialaudio.com/?page=sam-broadcaster&ref=A1100&redirect=SAM_Broadcaster" alt="Sp…

    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 176, Column 91: reference to entity "ref" for which no system identifier could be generated
    …ialaudio.com/?page=sam-broadcaster&ref=A1100&redirect=SAM_Broadcaster" alt="Sp…

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

  • Info Line 176, Column 87: entity was defined here
    …spacialaudio.com/?page=sam-broadcaster&ref=A1100&redirect=SAM_Broadcaster" alt…
  • Warning Line 176, Column 98: cannot generate system identifier for general entity "redirect"
    …o.com/?page=sam-broadcaster&ref=A1100&redirect=SAM_Broadcaster" alt="Spacial -…

    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 176, Column 98: general entity "redirect" not defined and no default entity
    …o.com/?page=sam-broadcaster&ref=A1100&redirect=SAM_Broadcaster" alt="Spacial -…

    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 176, Column 106: reference not terminated by REFC delimiter
    …age=sam-broadcaster&ref=A1100&redirect=SAM_Broadcaster" alt="Spacial - SAM Bro…

    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 176, Column 106: reference to external entity in attribute value
    …age=sam-broadcaster&ref=A1100&redirect=SAM_Broadcaster" alt="Spacial - SAM Bro…

    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 176, Column 106: reference to entity "redirect" for which no system identifier could be generated
    …age=sam-broadcaster&ref=A1100&redirect=SAM_Broadcaster" alt="Spacial - SAM Bro…

    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 176, Column 97: entity was defined here
    …io.com/?page=sam-broadcaster&ref=A1100&redirect=SAM_Broadcaster" alt="Spacial …
  • Error Line 176, Column 128: there is no attribute "alt"
    …f=A1100&redirect=SAM_Broadcaster" alt="Spacial - SAM Broadcaster" target="_bla…

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

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

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

  • Warning Line 178, Column 97: cannot generate system identifier for general entity "autoplay"
    …w.youtube.com/embed/0UlQwkb4kk0?rel=0&autoplay=0" frameborder="0" allowfullscr…

    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 178, Column 97: general entity "autoplay" not defined and no default entity
    …w.youtube.com/embed/0UlQwkb4kk0?rel=0&autoplay=0" frameborder="0" allowfullscr…

    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 178, Column 105: reference not terminated by REFC delimiter
    …e.com/embed/0UlQwkb4kk0?rel=0&autoplay=0" frameborder="0" allowfullscreen></if…

    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 178, Column 105: reference to external entity in attribute value
    …e.com/embed/0UlQwkb4kk0?rel=0&autoplay=0" frameborder="0" allowfullscreen></if…

    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 178, Column 105: reference to entity "autoplay" for which no system identifier could be generated
    …e.com/embed/0UlQwkb4kk0?rel=0&autoplay=0" frameborder="0" allowfullscreen></if…

    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 178, Column 96: entity was defined here
    …ww.youtube.com/embed/0UlQwkb4kk0?rel=0&autoplay=0" frameborder="0" allowfullsc…
  • Error Line 178, Column 140: "allowfullscreen" is not a member of a group specified for any attribute
    …m/embed/0UlQwkb4kk0?rel=0&autoplay=0" frameborder="0" allowfullscreen></iframe>
  • Error Line 192, Column 84: required attribute "alt" not specified
    …ss="span4"> <img src="/images/shoutcast.gif" width="339" height="233" /> </div>

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

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

  • Error Line 238, Column 37: required attribute "type" not specified
    <script src="../assets/js/jquery.js"></script>

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

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

Visitor Analysis

Daily Visitor
  • 4.783 visits