free download and wapmaster services ...

koolwap.in
  • Domain Name
    koolwap.in
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #31977
  • Page Size
    6.2 KB
  • Ip Address
    198.1.115.14
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 1, H5: 0, H6: 0
  • Images
    1 GIF, 0 JPG, 3 PNG

Website Meta Analysis

  • Title
    Home - KoolWap.IN - Free Downloads and Wapmaster Tools
  • Meta Keyword
    free,downloads,mp3,wapmaster,games,applications,softwares,nokia,symbian,sony,ericcsson,java,counter,service,guestbook,windows
  • Meta Description
    free download and wapmaster services

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    198.1.115.14
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from koolwap.in.

HTML Analysis

  • date: Wed, 04 Sep 2013 14:54:37 GMT
  • server: Apache
  • x-powered-by: PHP/5.3.17
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 2265
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for koolwap.in

DNS Analysis


DNS servers
ns1.koolwap.in [198.1.107.162]
ns2.koolwap.in [198.1.115.13]


DNS Records

Answer records
koolwap.in MX
preference: 0
exchange: koolwap.in
14400s
koolwap.in SOA
server: ns1.koolwap.in
email: koolwap@gmail.com
serial: 2012093001
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
koolwap.in NS  ns2.koolwap.in 86400s
koolwap.in NS  ns1.koolwap.in 86400s
koolwap.in A 198.1.115.14 14400s

Authority records

Additional records
koolwap.in A 198.1.115.14 14400s
ns1.koolwap.in A 198.1.107.162 14400s
ns2.koolwap.in A 198.1.115.13 14400s

IP 198.1.115.14 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • %rwhois V-1.5:000080:00 rwhois.unifiedlayer.com (by Unified Layer, V-1.0.0)
    network:Class-Name:network
    network:ID: NETBLK-UL.198.1.115.14/32
    network:Auth-Area: 198.1.115.14/32
    network:Network-Name: UL-198.1.115.14/32
    network:IP-Network: 198.1.115.14/32
    network:Organization: websitewelcome.com
    network:Tech-Contact: abuse@websitewelcome.com
    network:Admin-Contact: abuse@websitewelcome.com
    network:Abuse-Contact: abuse@websitewelcome.com
    network:Created: 20130103
    network:Updated: 20130103
    network:Updated-By: abuse@websitewelcome.com

    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 81 Errors
  • 18 Warnings
Ratio Text/Html
  • 0.6721594475831765
Message Error
  • Error Line 6, Column 11: there is no attribute "REL"
    <link REL="SHORTCUT ICON" HREF="http://koolwap.in/favicon.ico" />

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

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

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

  • Error Line 6, Column 32: there is no attribute "HREF"
    <link REL="SHORTCUT ICON" HREF="http://koolwap.in/favicon.ico" />

    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 8, Column 12: there is no attribute "name"
    <META name="y_key" content="56d139d495e39324" />

    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 8, Column 28: there is no attribute "content"
    <META name="y_key" content="56d139d495e39324" />

    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 8, Column 48: element "META" undefined
    <META name="y_key" content="56d139d495e39324" />

    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 11, Column 12: there is no attribute "NAME"
    <META NAME="Keywords" CONTENT="free,downloads,mp3,wapmaster,games,applications,…

    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 11, Column 31: there is no attribute "CONTENT"
    <META NAME="Keywords" CONTENT="free,downloads,mp3,wapmaster,games,applications,…

    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 11, Column 160: element "META" undefined
    …ftwares,nokia,symbian,sony,ericcsson,java,counter,service,guestbook,windows" />

    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 12, Column 74: element "META" undefined
    <META NAME="Description" CONTENT="free download and wapmaster services" />

    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 13, Column 82: end tag for "meta" omitted, but OMITTAG NO was specified
    …eta name="inmobi-site-verification" content="7f39ad807639e16b0d53c90fb193dcb8">

    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="inmobi-site-verification" content="7f39ad807639e16b0d53c90fb193dcb8…
  • Error Line 14, Column 54: element "META" undefined
    <META NAME="Author" CONTENT="arpan2c0ool@gmail.com" />

    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 15, Column 16: there is no attribute "property"
    <meta property="og:image" content="http://koolwap.in/logo.png"/>

    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 20, Column 14: there is no attribute "type"
    <script type="text/javascript">

    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 20, Column 31: element "script" undefined
    <script type="text/javascript">

    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 31, Column 48: element "center" undefined
    …headerdat"><div id="container"><center><img src="img/logo.png" class="img" alt…

    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 40, Column 59: there is no attribute "color"
    …cebook.com/koolwap.in"><b><font color="purple"><u>Like us On Facebook.</u></fo…

    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 40, Column 67: element "font" undefined
    …om/koolwap.in"><b><font color="purple"><u>Like us On Facebook.</u></font></b><…

    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 40, Column 70: element "u" undefined
    …koolwap.in"><b><font color="purple"><u>Like us On Facebook.</u></font></b></a>…

    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 43, Column 10: ID "menua" already defined
    <div id="menua"><div id="menu">

    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 39, Column 11: ID "menua" first defined here
     <div id="menua"><div id="menu">
  • Error Line 43, Column 26: ID "menu" already defined
    <div id="menua"><div id="menu">

    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 39, Column 27: ID "menu" first defined here
     <div id="menua"><div id="menu">
  • Error Line 45, Column 22: an attribute value must be a literal unless it contains only name characters
    <div id="odd"><a rel=\"follow\" href="http://zwaper.com">Download Center</a><br…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 45, Column 22: character "\" is not allowed in the value of attribute "rel"
    <div id="odd"><a rel=\"follow\" href="http://zwaper.com">Download Center</a><br…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 46, Column 23: an attribute value must be a literal unless it contains only name characters
    <div id="even"><a rel=\"follow\" href="mp3/index.php">MP3 Zone</a><br/>Latest m…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 46, Column 23: character "\" is not allowed in the value of attribute "rel"
    <div id="even"><a rel=\"follow\" href="mp3/index.php">MP3 Zone</a><br/>Latest m…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 47, Column 10: ID "odd" already defined
    <div id="odd"><a rel=\"follow\" href="vid/index.php">Video Zone</a><br/>Search …

    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 45, Column 10: ID "odd" first defined here
    <div id="odd"><a rel=\"follow\" href="http://zwaper.com">Download Center</a><br…
  • Error Line 47, Column 22: an attribute value must be a literal unless it contains only name characters
    <div id="odd"><a rel=\"follow\" href="vid/index.php">Video Zone</a><br/>Search …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 47, Column 22: character "\" is not allowed in the value of attribute "rel"
    <div id="odd"><a rel=\"follow\" href="vid/index.php">Video Zone</a><br/>Search …

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 48, Column 10: ID "even" already defined
    <div id="even"><a rel=\"follow\" href="ring/index.php">Ringtone Zone</a><br/>Do…

    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 46, Column 10: ID "even" first defined here
    <div id="even"><a rel=\"follow\" href="mp3/index.php">MP3 Zone</a><br/>Latest m…
  • Error Line 48, Column 23: an attribute value must be a literal unless it contains only name characters
    <div id="even"><a rel=\"follow\" href="ring/index.php">Ringtone Zone</a><br/>Do…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 48, Column 23: character "\" is not allowed in the value of attribute "rel"
    <div id="even"><a rel=\"follow\" href="ring/index.php">Ringtone Zone</a><br/>Do…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 49, Column 10: ID "odd" already defined
    <div id="odd"><a rel=\"follow\" href="games_app/index.php">Game/App Search</a><…

    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 45, Column 10: ID "odd" first defined here
    <div id="odd"><a rel=\"follow\" href="http://zwaper.com">Download Center</a><br…
  • Error Line 49, Column 22: an attribute value must be a literal unless it contains only name characters
    <div id="odd"><a rel=\"follow\" href="games_app/index.php">Game/App Search</a><…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 49, Column 22: character "\" is not allowed in the value of attribute "rel"
    <div id="odd"><a rel=\"follow\" href="games_app/index.php">Game/App Search</a><…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 50, Column 10: ID "even" already defined
    <div id="even"><a rel=\"follow\" href="books/index.php">Ebook/Document Download…

    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 46, Column 10: ID "even" first defined here
    <div id="even"><a rel=\"follow\" href="mp3/index.php">MP3 Zone</a><br/>Latest m…
  • Error Line 50, Column 23: an attribute value must be a literal unless it contains only name characters
    <div id="even"><a rel=\"follow\" href="books/index.php">Ebook/Document Download…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 50, Column 23: character "\" is not allowed in the value of attribute "rel"
    <div id="even"><a rel=\"follow\" href="books/index.php">Ebook/Document Download…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 51, Column 10: ID "odd" already defined
    <div id="odd"><a rel=\"follow\" href="http://koolwall.in">Wallpaper Download</a…

    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 45, Column 10: ID "odd" first defined here
    <div id="odd"><a rel=\"follow\" href="http://zwaper.com">Download Center</a><br…
  • Error Line 51, Column 22: an attribute value must be a literal unless it contains only name characters
    <div id="odd"><a rel=\"follow\" href="http://koolwall.in">Wallpaper Download</a…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 51, Column 22: character "\" is not allowed in the value of attribute "rel"
    <div id="odd"><a rel=\"follow\" href="http://koolwall.in">Wallpaper Download</a…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 52, Column 10: ID "even" already defined
    <div id="even"><a rel=\"follow\" href="http://vdowap.com">Movies Zone</a><br/>D…

    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 46, Column 10: ID "even" first defined here
    <div id="even"><a rel=\"follow\" href="mp3/index.php">MP3 Zone</a><br/>Latest m…
  • Error Line 52, Column 23: an attribute value must be a literal unless it contains only name characters
    <div id="even"><a rel=\"follow\" href="http://vdowap.com">Movies Zone</a><br/>D…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 52, Column 23: character "\" is not allowed in the value of attribute "rel"
    <div id="even"><a rel=\"follow\" href="http://vdowap.com">Movies Zone</a><br/>D…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 55, Column 10: ID "menua" already defined
    <div id="menua"><div id="menu">

    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 39, Column 11: ID "menua" first defined here
     <div id="menua"><div id="menu">
  • Error Line 55, Column 26: ID "menu" already defined
    <div id="menua"><div id="menu">

    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 39, Column 27: ID "menu" first defined here
     <div id="menua"><div id="menu">
  • Error Line 56, Column 10: ID "section" already defined
    <div id="section">Special</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 44, Column 10: ID "section" first defined here
    <div id="section">Downloads</div>
  • Error Line 57, Column 10: ID "even" already defined
    <div id="even"><a rel=\"follow\" href="http://chat.koolwap.in">Chat on KoolWap<…

    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 46, Column 10: ID "even" first defined here
    <div id="even"><a rel=\"follow\" href="mp3/index.php">MP3 Zone</a><br/>Latest m…
  • Error Line 57, Column 23: an attribute value must be a literal unless it contains only name characters
    <div id="even"><a rel=\"follow\" href="http://chat.koolwap.in">Chat on KoolWap<…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 57, Column 23: character "\" is not allowed in the value of attribute "rel"
    <div id="even"><a rel=\"follow\" href="http://chat.koolwap.in">Chat on KoolWap<…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 58, Column 10: ID "odd" already defined
    <div id="odd"><a rel=\"follow\" href="#">Send Free SMS</a><br/>Send free sms Wo…

    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 45, Column 10: ID "odd" first defined here
    <div id="odd"><a rel=\"follow\" href="http://zwaper.com">Download Center</a><br…
  • Error Line 58, Column 22: an attribute value must be a literal unless it contains only name characters
    <div id="odd"><a rel=\"follow\" href="#">Send Free SMS</a><br/>Send free sms Wo…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 58, Column 22: character "\" is not allowed in the value of attribute "rel"
    <div id="odd"><a rel=\"follow\" href="#">Send Free SMS</a><br/>Send free sms Wo…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 59, Column 10: ID "even" already defined
    <div id="even"><a rel=\"follow\" href="http://koolwap.in/advertise.php">Adverti…

    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 46, Column 10: ID "even" first defined here
    <div id="even"><a rel=\"follow\" href="mp3/index.php">MP3 Zone</a><br/>Latest m…
  • Error Line 59, Column 23: an attribute value must be a literal unless it contains only name characters
    <div id="even"><a rel=\"follow\" href="http://koolwap.in/advertise.php">Adverti…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 59, Column 23: character "\" is not allowed in the value of attribute "rel"
    <div id="even"><a rel=\"follow\" href="http://koolwap.in/advertise.php">Adverti…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 60, Column 10: ID "odd" already defined
    <div id="odd"><a rel=\"follow\" href="http://koolwap.in/live_tv/">Live Tv</a><b…

    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 45, Column 10: ID "odd" first defined here
    <div id="odd"><a rel=\"follow\" href="http://zwaper.com">Download Center</a><br…
  • Error Line 60, Column 22: an attribute value must be a literal unless it contains only name characters
    <div id="odd"><a rel=\"follow\" href="http://koolwap.in/live_tv/">Live Tv</a><b…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 60, Column 22: character "\" is not allowed in the value of attribute "rel"
    <div id="odd"><a rel=\"follow\" href="http://koolwap.in/live_tv/">Live Tv</a><b…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 61, Column 10: ID "even" already defined
    <div id="even"><a rel=\"follow\" href="http://koolwap.in/gbs/gb.php?id=admin">G…

    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 46, Column 10: ID "even" first defined here
    <div id="even"><a rel=\"follow\" href="mp3/index.php">MP3 Zone</a><br/>Latest m…
  • Error Line 61, Column 23: an attribute value must be a literal unless it contains only name characters
    <div id="even"><a rel=\"follow\" href="http://koolwap.in/gbs/gb.php?id=admin">G…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 61, Column 23: character "\" is not allowed in the value of attribute "rel"
    <div id="even"><a rel=\"follow\" href="http://koolwap.in/gbs/gb.php?id=admin">G…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 62, Column 10: ID "odd" already defined
    <div id="odd"><a rel=\"follow\" href="http://mobizza.in/">More free downloads</…

    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 45, Column 10: ID "odd" first defined here
    <div id="odd"><a rel=\"follow\" href="http://zwaper.com">Download Center</a><br…
  • Error Line 62, Column 22: an attribute value must be a literal unless it contains only name characters
    <div id="odd"><a rel=\"follow\" href="http://mobizza.in/">More free downloads</…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 62, Column 22: character "\" is not allowed in the value of attribute "rel"
    <div id="odd"><a rel=\"follow\" href="http://mobizza.in/">More free downloads</…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 64, Column 10: ID "menua" already defined
    <div id="menua"><div id="menu">

    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 39, Column 11: ID "menua" first defined here
     <div id="menua"><div id="menu">
  • Error Line 64, Column 26: ID "menu" already defined
    <div id="menua"><div id="menu">

    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 39, Column 27: ID "menu" first defined here
     <div id="menua"><div id="menu">
  • Error Line 66, Column 18: there is no attribute "LANGUAGE"
    <SCRIPT LANGUAGE="JavaScript1.1" SRC="http://bdv.bidvertiser.com/BidVertiser.db…

    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 66, Column 38: there is no attribute "SRC"
    <SCRIPT LANGUAGE="JavaScript1.1" SRC="http://bdv.bidvertiser.com/BidVertiser.db…

    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 66, Column 93: cannot generate system identifier for general entity "bid"
    …rtiser.com/BidVertiser.dbm?pid=386882&bid=958120" type="text/javascript"></SCR…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 66, Column 93: general entity "bid" not defined and no default entity
    …rtiser.com/BidVertiser.dbm?pid=386882&bid=958120" type="text/javascript"></SCR…

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

  • Warning Line 66, Column 96: reference not terminated by REFC delimiter
    …ser.com/BidVertiser.dbm?pid=386882&bid=958120" type="text/javascript"></SCRIPT…

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

  • Warning Line 66, Column 96: reference to external entity in attribute value
    …ser.com/BidVertiser.dbm?pid=386882&bid=958120" type="text/javascript"></SCRIPT…

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

  • Error Line 66, Column 96: reference to entity "bid" for which no system identifier could be generated
    …ser.com/BidVertiser.dbm?pid=386882&bid=958120" type="text/javascript"></SCRIPT…

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

  • Info Line 66, Column 92: entity was defined here
    …ertiser.com/BidVertiser.dbm?pid=386882&bid=958120" type="text/javascript"></SC…
  • Error Line 66, Column 110: there is no attribute "type"
    …ser.com/BidVertiser.dbm?pid=386882&bid=958120" type="text/javascript"></SCRIPT>

    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 66, Column 127: element "SCRIPT" undefined
    …ser.com/BidVertiser.dbm?pid=386882&bid=958120" type="text/javascript"></SCRIPT>

    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 67, Column 10: element "noscript" undefined
    <noscript><a href="http://www.bidvertiser.com">pay per click</a></noscript>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 70, Column 55: cannot generate system identifier for general entity "pub"
    …down3.ucweb.com/ucbrowser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UC…

    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 70, Column 55: general entity "pub" not defined and no default entity
    …down3.ucweb.com/ucbrowser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UC…

    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 70, Column 58: reference not terminated by REFC delimiter
    …n3.ucweb.com/ucbrowser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB…

    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 70, Column 58: reference to external entity in attribute value
    …n3.ucweb.com/ucbrowser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB…

    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 70, Column 58: reference to entity "pub" for which no system identifier could be generated
    …n3.ucweb.com/ucbrowser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB…

    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 70, Column 54: entity was defined here
    …/down3.ucweb.com/ucbrowser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download U…
  • Warning Line 70, Column 71: cannot generate system identifier for general entity "title"
    …ucbrowser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G<…

    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 70, Column 71: general entity "title" not defined and no default entity
    …ucbrowser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G<…

    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 70, Column 76: reference not terminated by REFC delimiter
    …wser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G</a><b…

    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 70, Column 76: reference to external entity in attribute value
    …wser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G</a><b…

    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 70, Column 76: reference to entity "title" for which no system identifier could be generated
    …wser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G</a><b…

    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 70, Column 70: entity was defined here
    …/ucbrowser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G…
  • Warning Line 70, Column 78: cannot generate system identifier for general entity "url"
    …er/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G</a><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 70, Column 78: general entity "url" not defined and no default entity
    …er/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G</a><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 70, Column 81: reference not terminated by REFC delimiter
    …er/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G</a><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 70, Column 81: reference to external entity in attribute value
    …er/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G</a><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 70, Column 81: reference to entity "url" for which no system identifier could be generated
    …er/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G</a><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 70, Column 77: entity was defined here
    …ser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G</a><br…
  • Error Line 74, Column 10: ID "menua" already defined
    <div id="menua"><div id="menu">

    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 39, Column 11: ID "menua" first defined here
     <div id="menua"><div id="menu">
  • Error Line 74, Column 26: ID "menu" already defined
    <div id="menua"><div id="menu">

    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 39, Column 27: ID "menu" first defined here
     <div id="menua"><div id="menu">
  • Warning Line 76, Column 74: cannot generate system identifier for general entity "t"
    …arer.php?u=http%3A%2F%2Fkoolwap.in%2F&t=Home%20-%20Koolwap.in%20-%20Free%20Dow…

    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 76, Column 74: general entity "t" not defined and no default entity
    …arer.php?u=http%3A%2F%2Fkoolwap.in%2F&t=Home%20-%20Koolwap.in%20-%20Free%20Dow…

    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 76, Column 75: reference not terminated by REFC delimiter
    …rer.php?u=http%3A%2F%2Fkoolwap.in%2F&t=Home%20-%20Koolwap.in%20-%20Free%20Down…

    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 76, Column 75: reference to external entity in attribute value
    …rer.php?u=http%3A%2F%2Fkoolwap.in%2F&t=Home%20-%20Koolwap.in%20-%20Free%20Down…

    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 76, Column 75: reference to entity "t" for which no system identifier could be generated
    …rer.php?u=http%3A%2F%2Fkoolwap.in%2F&t=Home%20-%20Koolwap.in%20-%20Free%20Down…

    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 76, Column 73: entity was defined here
    …harer.php?u=http%3A%2F%2Fkoolwap.in%2F&t=Home%20-%20Koolwap.in%20-%20Free%20Do…
  • Error Line 76, Column 189: required attribute "alt" not specified
    …g src="http://koolwap.in/facebook.png"></a> <a href="http://twitter.com/share?…

    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 76, Column 193: end tag for "img" omitted, but OMITTAG NO was specified
    …c="http://koolwap.in/facebook.png"></a> <a href="http://twitter.com/share?_=12…

    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 76, Column 148: start tag was here
    …0Downloads%20and%20Wapmaster%20Tools"><img src="http://koolwap.in/facebook.png…
  • Warning Line 76, Column 245: cannot generate system identifier for general entity "count"
    …p://twitter.com/share?_=1294236808542&count=none&original_referer=http%3A%2F%2…

    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 76, Column 245: general entity "count" not defined and no default entity
    …p://twitter.com/share?_=1294236808542&count=none&original_referer=http%3A%2F%2…

    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 76, Column 250: reference not terminated by REFC delimiter
    …witter.com/share?_=1294236808542&count=none&original_referer=http%3A%2F%2Fkool…

    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 76, Column 250: reference to external entity in attribute value
    …witter.com/share?_=1294236808542&count=none&original_referer=http%3A%2F%2Fkool…

    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 76, Column 250: reference to entity "count" for which no system identifier could be generated
    …witter.com/share?_=1294236808542&count=none&original_referer=http%3A%2F%2Fkool…

    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 76, Column 244: entity was defined here
    …tp://twitter.com/share?_=1294236808542&count=none&original_referer=http%3A%2F%…
  • Warning Line 76, Column 256: cannot generate system identifier for general entity "original_referer"
    ….com/share?_=1294236808542&count=none&original_referer=http%3A%2F%2Fkoolwap.in…

    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 76, Column 256: general entity "original_referer" not defined and no default entity
    ….com/share?_=1294236808542&count=none&original_referer=http%3A%2F%2Fkoolwap.in…

    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 76, Column 272: reference not terminated by REFC delimiter
    …4236808542&count=none&original_referer=http%3A%2F%2Fkoolwap.in%2F&text=Home%20…

    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 76, Column 272: reference to external entity in attribute value
    …4236808542&count=none&original_referer=http%3A%2F%2Fkoolwap.in%2F&text=Home%20…

    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 76, Column 272: reference to entity "original_referer" for which no system identifier could be generated
    …4236808542&count=none&original_referer=http%3A%2F%2Fkoolwap.in%2F&text=Home%20…

    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 76, Column 255: entity was defined here
    …r.com/share?_=1294236808542&count=none&original_referer=http%3A%2F%2Fkoolwap.i…
  • Warning Line 76, Column 300: cannot generate system identifier for general entity "text"
    …al_referer=http%3A%2F%2Fkoolwap.in%2F&text=Home%20-%20Koolwap.in%20-%20Free%20…

    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 76, Column 300: general entity "text" not defined and no default entity
    …al_referer=http%3A%2F%2Fkoolwap.in%2F&text=Home%20-%20Koolwap.in%20-%20Free%20…

    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 76, Column 304: reference not terminated by REFC delimiter
    …eferer=http%3A%2F%2Fkoolwap.in%2F&text=Home%20-%20Koolwap.in%20-%20Free%20Down…

    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 76, Column 304: reference to external entity in attribute value
    …eferer=http%3A%2F%2Fkoolwap.in%2F&text=Home%20-%20Koolwap.in%20-%20Free%20Down…

    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 76, Column 304: reference to entity "text" for which no system identifier could be generated
    …eferer=http%3A%2F%2Fkoolwap.in%2F&text=Home%20-%20Koolwap.in%20-%20Free%20Down…

    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 76, Column 299: entity was defined here
    …nal_referer=http%3A%2F%2Fkoolwap.in%2F&text=Home%20-%20Koolwap.in%20-%20Free%2…
  • Warning Line 76, Column 379: reference not terminated by REFC delimiter
    …ownloads%20and%20Wapmaster%20Tools&url=http%3A%2F%2Fkoolwap.in%2F"><img src="h…

    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 76, Column 379: reference to external entity in attribute value
    …ownloads%20and%20Wapmaster%20Tools&url=http%3A%2F%2Fkoolwap.in%2F"><img src="h…

    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 76, Column 379: reference to entity "url" for which no system identifier could be generated
    …ownloads%20and%20Wapmaster%20Tools&url=http%3A%2F%2Fkoolwap.in%2F"><img src="h…

    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 70, Column 77: entity was defined here
    …ser/en/?bid=354&pub=xyj@koolwap&title=&url=">Download UCWEB for FAST 3G</a><br…
  • Error Line 76, Column 466: end tag for "img" omitted, but OMITTAG NO was specified
    …2F%2Fkoolwap.in%2F"><img src="http://koolwap.in/twitter.png" alt="twitter"></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 76, Column 408: start tag was here
    …Tools&url=http%3A%2F%2Fkoolwap.in%2F"><img src="http://koolwap.in/twitter.png"…
  • Error Line 79, Column 24: there is no attribute "align"
    <div id="footer" align="center"><center><b>Contact Us:<br/>koolwap@gmail.com<br…

    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 79, Column 40: element "center" undefined
    …div id="footer" align="center"><center><b>Contact Us:<br/>koolwap@gmail.com<br…

    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 79, Column 128: element "font" undefined
    …"../disclaimer.php"><font color="#F6F">Disclaimer</font></a></b><br/>&copy;201…

    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).

Visitor Analysis

Daily Visitor
  • 8.517 visits