hirufm.lk

Hiru FM,The No 01 online Radio in Sri Lanka.Listen to Live Music Online,Download Sinhala Songs & Sinhala MP3.The Best Live Music streaming in sri Lanka.Request your favorite Sinhala Songs & Sinhala MP3. ...

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

Overview Info

  • Domain Name
    hirufm.lk
  • Favicon
  • Alexa Rank
    #29236
  • Google Page Rank
    PR 4
  • Ip Address
    209.239.127.105
  • Page Size
    36.3 KB
  • Images
    13 GIF, 13 JPG, 14 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 0 1 0 0

Website Meta Analysis



  • Title
    Hiru FM Official Web Site|Sinhala Songs|Free Sinhala Songs|Download Sinhala Songs
  • Meta Keyword
    Hiru,Sinhala Songs,Free Sinhala Songs,Download sinhala songs,Free Sinhala MP3,5gOWOuFYP-eSRKvAnZnL1Q7nuAo
  • Meta Description
    Hiru FM,The No 01 online Radio in Sri Lanka.Listen to Live Music Online,Download Sinhala Songs & Sinhala MP3.The Best Live Music streaming in sri Lanka.Request your favorite Sinhala Songs & Sinhala MP3.

Technical Analysis



  • Webserver
    Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • Ip Address
    209.239.127.105
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from hirufm.lk.

HTML Analysis

  • date: Sat, 02 Feb 2013 00:36:21 GMT
  • server: Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • x-powered-by: PHP/5.3.10
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for hirufm.lk

DNS Analysis


DNS servers
ns2.3csnetworks.net [208.77.101.190]
ns1.3csnetworks.net [69.73.164.14]


DNS Records

Answer records
hirufm.lk MX
preference: 0
exchange: hirufm.lk
300s
hirufm.lk SOA
server: ns1.3csnetworks.net
email: lankanwriter@yahoo.com
serial: 2011042909
refresh: 600
retry: 600
expire: 600
minimum ttl: 600
300s
hirufm.lk NS  ns1.3csnetworks.net 300s
hirufm.lk NS  ns2.3csnetworks.net 300s
hirufm.lk A 209.239.127.105 300s

Authority records

Additional records
hirufm.lk A 209.239.127.105 300s
ns1.3csnetworks.net A 69.73.164.14 300s
ns2.3csnetworks.net A 208.77.101.190 600s

IP 209.239.127.105 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Saint Louis
  • Continent Code
    63101
  • Latitude
    314
  • Longitude
    609
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 209.239.127.105"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=209.239.127.105?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 209.239.112.0 - 209.239.127.255
    CIDR: 209.239.112.0/20
    OriginAS: AS30083
    NetName: HSI-2
    NetHandle: NET-209-239-112-0-1
    Parent: NET-209-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2008-07-10
    Updated: 2012-05-10
    Ref: http://whois.arin.net/rest/net/NET-209-239-112-0-1

    OrgName: Hosting Solutions International, Inc.
    OrgId: SERVE-6
    Address: 210 North Tucker Blvd.
    Address: Suite 910
    City: Saint Louis
    StateProv: MO
    PostalCode: 63101
    Country: US
    RegDate: 2003-04-15
    Updated: 2012-05-10
    Comment: Please forward abuse complaints to abuse@hostingsolutionsint.com
    Ref: http://whois.arin.net/rest/org/SERVE-6

    OrgNOCHandle: SWI19-ARIN
    OrgNOCName: Wintz, Sascha
    OrgNOCPhone: +1-314-480-6840
    OrgNOCEmail: s.wintz@hostingsolutionsinternational.com
    OrgNOCRef: http://whois.arin.net/rest/poc/SWI19-ARIN

    OrgAbuseHandle: HAD15-ARIN
    OrgAbuseName: HSI Abuse Department
    OrgAbusePhone: +1-314-266-3638
    OrgAbuseEmail: abuse@hostingsolutionsint.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/HAD15-ARIN

    OrgTechHandle: SWI19-ARIN
    OrgTechName: Wintz, Sascha
    OrgTechPhone: +1-314-480-6840
    OrgTechEmail: s.wintz@hostingsolutionsinternational.com
    OrgTechRef: http://whois.arin.net/rest/poc/SWI19-ARIN

    RAbuseHandle: HAD15-ARIN
    RAbuseName: HSI Abuse Department
    RAbusePhone: +1-314-266-3638
    RAbuseEmail: abuse@hostingsolutionsint.com
    RAbuseRef: http://whois.arin.net/rest/poc/HAD15-ARIN

    RTechHandle: SWI19-ARIN
    RTechName: Wintz, Sascha
    RTechPhone: +1-314-480-6840
    RTechEmail: s.wintz@hostingsolutionsinternational.com
    RTechRef: http://whois.arin.net/rest/poc/SWI19-ARIN

    RNOCHandle: SWI19-ARIN
    RNOCName: Wintz, Sascha
    RNOCPhone: +1-314-480-6840
    RNOCEmail: s.wintz@hostingsolutionsinternational.com
    RNOCRef: http://whois.arin.net/rest/poc/SWI19-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 63 Errors
  • 10 Warnings
Ratio Text/Html
  • 0.616520125836896
Message Error
  • Error Line 42, Column 192: document type does not allow element "img" here
    …="Click to stop" title="Click to stop" onclick="javascript: player_play();"/>';

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

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

  • Error Line 47, Column 193: document type does not allow element "img" here
    …="Click to stop" title="Click to stop" onclick="javascript: player_stop();"/>';

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

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

  • Error Line 85, Column 75: document type does not allow element "span" here
    … $('#vote'+id).replaceWith('<span class="liked"> You VOTED for this. </span>');

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

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

  • Error Line 99, Column 38: required attribute "type" not specified
    <script src="js/jquery.roundabout.js"></script>

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

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

  • Error Line 100, Column 38: required attribute "type" not specified
    <script src="js/jquery.easing.1.3.js"></script>

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

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

  • Error Line 197, Column 8: 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>.

  • Error Line 262, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 312, Column 108: required attribute "alt" not specified
    …fm.lk/images/icons_03.png" width="429" height="115" usemap="#Map" border="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 314, Column 90: required attribute "alt" not specified
    … shape="rect" coords="88,68,128,104" href="http://hirutv.lk" target="_blank" />

    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 315, Column 90: required attribute "alt" not specified
    … shape="rect" coords="133,68,175,106" href="http://hirufm.lk" target="_blank"/>

    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 316, Column 90: required attribute "alt" not specified
    … shape="rect" coords="181,69,247,104" href="http://goldfm.lk" target="_blank"/>

    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 317, Column 89: required attribute "alt" not specified
    …a shape="rect" coords="253,69,321,103" href="http://sunfm.lk" target="_blank"/>

    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 318, Column 94: required attribute "alt" not specified
    …pe="rect" coords="325,68,382,101" href="http://sooriyanfm.lk" target="_blank"/>

    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 319, Column 90: required attribute "alt" not specified
    … shape="rect" coords="389,64,418,102" href="http://shaafm.lk" target="_blank"/>

    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 322, Column 105: required attribute "alt" not specified
    … src="images/icons_13.png" width="217" height="51" usemap="#Map2" border="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 324, Column 107: required attribute "alt" not specified
    …rds="117,10,149,46" href="http://twitter.com/hirufmsrilanka"  target="_blank"/>

    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 325, Column 107: required attribute "alt" not specified
    …rds="150,10,183,44" href="http://www.facebook.com/Hiru.FM.1"  target="_blank"/>

    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 326, Column 125: required attribute "alt" not specified
    …" href="https://plus.google.com/111534197799103704258/posts" target="_blank" />

    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 329, Column 103: required attribute "alt" not specified
    …rc="http://www.hirufm.lk/images/icons_06.png" width="412" height="110" /></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 330, Column 102: required attribute "alt" not specified
    …img src="http://www.hirufm.lk/images/hiru_frequency2.gif" width="518" /> </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 368, Column 35: there is no attribute "alt"
          	<li><a href="sandesha" alt="Click Here"><img src="images/sandeshaya_03.p…

    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 368, Column 110: required attribute "alt" not specified
    … Here"><img src="images/sandeshaya_03.png" width="276" height="374" /></a></li>

    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 369, Column 98: required attribute "alt" not specified
    …lt="Click Here"><img src="images/maco.jpg" width="276" height="374" /></a></li>

    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 377, Column 88: cannot generate system identifier for general entity "lightbox"
    …hirufmlvmeter.swf?lightbox[width]=550&lightbox[height]=416" class="lightbox"><…

    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 377, Column 88: general entity "lightbox" not defined and no default entity
    …hirufmlvmeter.swf?lightbox[width]=550&lightbox[height]=416" class="lightbox"><…

    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 377, Column 96: reference not terminated by REFC delimiter
    …meter.swf?lightbox[width]=550&lightbox[height]=416" class="lightbox"><img src=…

    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 377, Column 96: reference to external entity in attribute value
    …meter.swf?lightbox[width]=550&lightbox[height]=416" class="lightbox"><img src=…

    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 377, Column 96: reference to entity "lightbox" for which no system identifier could be generated
    …meter.swf?lightbox[width]=550&lightbox[height]=416" class="lightbox"><img src=…

    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 377, Column 87: entity was defined here
    …/hirufmlvmeter.swf?lightbox[width]=550&lightbox[height]=416" class="lightbox">…
  • Error Line 382, Column 73: there is no attribute "wmode"
    …v class="content_left_ad"><object width="276" height="173" wmode="transparent">

    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 385, Column 32: there is no attribute "src"
                        <embed src="images/boc.swf" width="276" height="173" wmode=…

    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 385, Column 55: there is no attribute "width"
    …    <embed src="images/boc.swf" width="276" height="173" wmode="transparent"><…

    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 385, Column 68: there is no attribute "height"
    …mbed src="images/boc.swf" width="276" height="173" wmode="transparent"></embed>

    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 385, Column 80: there is no attribute "wmode"
    …mbed src="images/boc.swf" width="276" height="173" wmode="transparent"></embed>

    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 385, Column 93: element "embed" undefined
    …mbed src="images/boc.swf" width="276" height="173" wmode="transparent"></embed>

    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 421, Column 58: required attribute "alt" not specified
      <img src="images/top_40.png" width="277" height="250" />

    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 424, Column 41: character "&" is the first character of a delimiter but occurred as data
    …             <li>ඊළඟ වස්සානේ - තීක්ෂණ & ප්‍රතිභා                       <a href…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 430, Column 36: character "&" is the first character of a delimiter but occurred as data
                  <li>නිහඬ ගමනේ - බාචි & ශානිකා                       <a href="#" 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.
  • Warning Line 452, Column 39: character "&" is the first character of a delimiter but occurred as data
                  <li>රත්තරං මාගේ - දම්ත් & අශාන්ති                       <a href="…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 460, Column 52: character "&" is the first character of a delimiter but occurred as data
    … <li>ඔබගේ දෑසින් (තේරී මේරී) - විරාජ් & දිල්රුක්ෂි                       <a hr…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 478, Column 50: character "&" is the first character of a delimiter but occurred as data
    …   <li>මේ සෞම්‍ය රාත්‍රී - ලතා වල්පොල & චමින්ද                       <a href="…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 490, Column 46: character "&" is the first character of a delimiter but occurred as data
    …       <li>පැතු සෙනෙහේ - පූර්ණ සචින්ත & කුෂානි Ft. Thilina R.                 …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 498, Column 46: character "&" is the first character of a delimiter but occurred as data
    …       <li>හිනාවෙන්න බැරිතරමට - උරේෂා & ධම්මික                       <a href="…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 517, Column 137: required attribute "alt" not specified
    … src="images/unusum_puwath.jpg" width="411" height="50" border="0" /></a></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 532, Column 64: required attribute "alt" not specified
            <a href="sandesha"><img src="images/main-slide_03.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 539, Column 118: there is no attribute "widht"
    …w.hirufm.lk/data/banners/2.gif" widht="240px" height="175px" /></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 539, Column 142: required attribute "alt" not specified
    …/2.gif" widht="240px" height="175px" /></a>        <!--<a href="gossips" targe…

    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 541, Column 14: ID "promotion_banner" already defined
        <div id="promotion_banner" style="margin-top:10px;"> <a href="wallpapers.ph…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 538, Column 14: ID "promotion_banner" first defined here
        <div id="promotion_banner">
  • Error Line 584, Column 103: document type does not allow element "link" here
    ….googleapis.com/css?family=Delius+Swash+Caps' rel='stylesheet' type='text/css'>

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

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

  • Error Line 584, Column 104: end tag for "link" omitted, but OMITTAG NO was specified
    ….googleapis.com/css?family=Delius+Swash+Caps' rel='stylesheet' type='text/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 584, Column 1: start tag was here
    <link href='http://fonts.googleapis.com/css?family=Delius+Swash+Caps' rel='styl…
  • Error Line 585, Column 7: required attribute "type" not specified
    <style>

    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 585, Column 7: document type does not allow element "style" here
    <style>

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

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

  • Error Line 653, Column 14: there is no attribute "onLoad"
    <body onLoad="setInterval( 'updateShouts()',120000 )">

    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 653, Column 54: document type does not allow element "body" here
    <body onLoad="setInterval( 'updateShouts()',120000 )">

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

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

  • Error Line 654, Column 14: ID "small_banners" already defined
        <div id="small_banners" style="text-align: justify;background: #b1db8f; pad…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 525, Column 10: ID "small_banners" first defined here
    <div id="small_banners">
  • Error Line 654, Column 191: required attribute "alt" not specified
    …ght="18" style="margin:5px 0 0 10px;"/>&nbsp;&nbsp;&nbsp;<img src="ajax-loader…

    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 654, Column 237: required attribute "alt" not specified
    …nbsp;&nbsp;<img src="ajax-loader.gif"/><div id="dj"><a href="#" onclick="javas…

    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 654, Column 400: required attribute "alt" not specified
    …0')"><img src="images/click_chat.png" width="167" height="18"/></a></div></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 656, Column 96: required attribute "alt" not specified
    …ading" style="text-align:center;margin-top: 200px;"><img src="ajax.gif"/></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 660, Column 10: ID "small_banners" already defined
    <div id="small_banners" style="text-align: justify;margin-left: 40px;"><h1>Hiru…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 525, Column 10: ID "small_banners" first defined here
    <div id="small_banners">
  • Error Line 664, Column 10: ID "small_banners" already defined
    <div id="small_banners" style="text-align: justify;margin-left: 110px;"><script…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 525, Column 10: ID "small_banners" first defined here
    <div id="small_banners">
  • Error Line 675, Column 10: ID "small_banners" already defined
    <div id="small_banners" style="text-align: justify;margin-left: 110px;"><script…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 525, Column 10: ID "small_banners" first defined here
    <div id="small_banners">
  • Error Line 686, Column 10: ID "news_letters" already defined
    <div id="news_letters" style="margin-top:5px;margin-left: 40px;">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 551, Column 10: ID "news_letters" first defined here
    <div id="news_letters">
  • Error Line 692, Column 181: required attribute "alt" not specified
    …f="promo.php" target="_blank"><img src="images/sallithamahiru.jpg" /></a></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 697, Column 10: ID "main_content" already defined
    <div id="main_content">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 419, Column 10: ID "main_content" first defined here
    <div id="main_content">
  • Error Line 698, Column 10: ID "small_banners" already defined
    <div id="small_banners" style="text-align: justify;"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 525, Column 10: ID "small_banners" first defined here
    <div id="small_banners">
  • Error Line 703, Column 15: there is no attribute "nclick"
        <a nclick="getDJs()" href="djs.php">

    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 705, Column 117: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …; position: absolute; margin-top: 10px; margin-left: 30px; z-index: 99;"></div>

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

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

  • Error Line 714, Column 3: "DOCTYPE" declaration not allowed in instance
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.o…
  • Error Line 715, Column 43: document type does not allow element "html" here
    <html xmlns="http://www.w3.org/1999/xhtml">

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

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

  • Error Line 729, Column 7: end tag for "head" which is not finished
    </head>

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

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

  • Error Line 777, Column 192: required attribute "alt" not specified
    …t:void(0)"><img src="images/transparent.gif" width="95" height="62"/></a></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 780, Column 177: required attribute "alt" not specified
    …le="margin: -33px 0px 0pt 60px;" src="images/request_song.gif"></a></div></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 780, Column 181: end tag for "img" omitted, but OMITTAG NO was specified
    …le="margin: -33px 0px 0pt 60px;" src="images/request_song.gif"></a></div></div>

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

  • Info Line 780, Column 96: start tag was here
    …dule_div"><a class="contact" href="#"><img width="70" style="margin: -33px 0px…

Visitor Analysis

Daily Visitor
  • 9.800 visits
Daily Visitor

In Page Analysis