Watch Malayalam TV Serials Online and Download free Malayalam TV Shows and Malayalam News, Gossips and daily TV shows ...

keralatv.net
  • Domain Name
    keralatv.net
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #164252
  • Page Size
    90.5 KB
  • Ip Address
    184.168.111.55
  • Heading
    H1: 5, H2: 0, H3: 49, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 40 JPG, 1 PNG

Website Meta Analysis

  • Title
    KeralaTv.net ~ Watch Malayalam TV Serials, Shows, Gossips and News
  • Meta Keyword
    malayalam tv, serials, shows, mp3, watch live, malayalam streaming tv shows, download tv serials, download tv shows, watch harichandanam, watch paarjatham, watch autograph
  • Meta Description
    Watch Malayalam TV Serials Online and Download free Malayalam TV Shows and Malayalam News, Gossips and daily TV shows

Technical Analysis

  • Webserver
    Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • Ip Address
    184.168.111.55
  • Domain Age
    2 Years, 3 Months, 19 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from keralatv.net.

HTML Analysis

  • date: Sun, 28 Jul 2013 23:07:08 GMT
  • server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • x-powered-by: PHP/5.2.17
  • p3p: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
  • content-encoding: gzip
  • x-content-encoded-by: Joomla! 1.5
  • expires: Mon, 1 Jan 2001 00:00:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • last-modified: Sun, 28 Jul 2013 23:07:09 GMT
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for keralatv.net

DNS Analysis


DNS servers
ns1.keralatv.net [184.168.111.55]
ns2.keralatv.net [184.168.111.55]


DNS Records

Answer records
keralatv.net MX
preference: 0
exchange: keralatv.net
14400s
keralatv.net SOA
server: ns2.keralatv.net
email: pradeep@john100.gmail.com
serial: 2011042202
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
keralatv.net NS  ns1.keralatv.net 86400s
keralatv.net NS  ns2.keralatv.net 86400s
keralatv.net A 184.168.111.55 14400s

Authority records

Additional records
keralatv.net A 184.168.111.55 14400s

IP 184.168.111.55 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 27 Errors
  • 8 Warnings
Ratio Text/Html
  • 0.6923508650743111
Message Error
  • Error Line 9, 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 28, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <script language=JavaScript>
  • Error Line 28, Column 28: required attribute "type" not specified
    <script language=JavaScript>

    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 83, Column 73: there is no attribute "TYPE"
    …et" href="http://keralatv.net/utils/tabber.css" TYPE="text/css" MEDIA="screen">

    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 83, Column 90: there is no attribute "MEDIA"
    …et" href="http://keralatv.net/utils/tabber.css" TYPE="text/css" MEDIA="screen">

    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 83, Column 99: end tag for "link" omitted, but OMITTAG NO was specified
    …et" href="http://keralatv.net/utils/tabber.css" TYPE="text/css" MEDIA="screen">

    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 83, Column 1: start tag was here
    <link rel="stylesheet" href="http://keralatv.net/utils/tabber.css" TYPE="text/c…
  • Error Line 128, Column 47: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="shortcut icon" href="/favicon.ico">

    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 128, Column 1: start tag was here
    <link rel="shortcut icon" href="/favicon.ico">
  • Error Line 212, Column 11: element "g:plusone" undefined
    <g:plusone></g:plusone>&nbsp;&nbsp;&nbsp;

    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 273, Column 69: character "&" is the first character of a delimiter but occurred as data
    …a-me.html"  id="menu143" title="Mummy & Me"><span class="menu-title">Mummy & M…

    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 273, Column 106: character "&" is the first character of a delimiter but occurred as data
    …enu143" title="Mummy & Me"><span class="menu-title">Mummy & Me</span></a></li> 

    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 320, Column 1: character "<" is the first character of a delimiter but occurred as data
    <! ---- begin added 01/17 --->

    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 323, Column 36: duplicate specification of attribute "class"
    		  <div class="ja-box-full" class="clearfix">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 325, Column 53: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …	<img src="/images/top-image-banner.jpg" border=0 alt="" usemap="#topbanner" />
  • Error Line 327, Column 22: required attribute "id" not specified
    <map name="topbanner"> 

    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 341, Column 31: character "/" is not allowed in the value of attribute "nohref"
    <area shape="default" nohref="/nohref" title="Default" alt="Default"/> 

    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 341, Column 38: value of attribute "nohref" cannot be "/nohref"; must be one of "nohref"
    <area shape="default" nohref="/nohref" title="Default" alt="Default"/> 

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

  • Warning Line 346, Column 3: character "<" is the first character of a delimiter but occurred as data
    		<! ---- end 01/17 --->

    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 353, Column 25: 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 353, Column 25: 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 356, Column 168: end tag for element "ul" which is not open
    …?layout=seccat">TV Serials</a></h1></div></ul><ul class="tabshow clearfix"><li>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 584, Column 12: end tag for "ul" omitted, but OMITTAG NO was specified
          </div><div style="height:10px;margin:10px 0 0 0;"><a href="/component/con…

    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 508, Column 12: start tag was here
          </ul><ul class="tabshow clearfix"><li>
  • Error Line 584, Column 360: end tag for element "ul" which is not open
    …ml?layout=seccat">TV Shows</a></h1></div></ul><ul class="tabshow clearfix"><li>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 812, Column 12: end tag for "ul" omitted, but OMITTAG NO was specified
          </div><div style="height:10px;margin:10px 0 0 0;"><a href="/component/con…

    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 736, Column 12: start tag was here
          </ul><ul class="tabshow clearfix"><li>
  • Warning Line 812, Column 343: character "&" is the first character of a delimiter but occurred as data
    …-and-gossips.html?layout=seccat">News & Gossips</a></h1></div></ul><ul class="…

    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 812, Column 371: end tag for element "ul" which is not open
    …out=seccat">News & Gossips</a></h1></div></ul><ul class="tabshow clearfix"><li>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 834, Column 305: "Bharya" is not a member of a group specified for any attribute
    …ebrates 25 years in acting in "Bharya athra pora" location" width="130" height…
  • Error Line 834, Column 311: "athra" is not a member of a group specified for any attribute
    …s 25 years in acting in "Bharya athra pora" location" width="130" height="85" …
  • Error Line 834, Column 315: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    … years in acting in "Bharya athra pora" location" width="130" height="85"  /><…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 834, Column 316: end tag for "img" omitted, but OMITTAG NO was specified
    …years in acting in "Bharya athra pora" location" width="130" height="85"  /></…

    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 834, Column 135: start tag was here
    …in-qbharya-athra-poraq-location.html"><img src="https://encrypted-tbn3.gstatic…
  • Error Line 872, Column 245: "Natholi" is not a member of a group specified for any attribute
    …nch function of VK Prakash's "Natholi Oru Cheriya Meenalla"" width="130" heigh…
  • Error Line 872, Column 249: "Oru" is not a member of a group specified for any attribute
    …function of VK Prakash's "Natholi Oru Cheriya Meenalla"" width="130" height="8…
  • Error Line 872, Column 257: "Cheriya" is not a member of a group specified for any attribute
    … of VK Prakash's "Natholi Oru Cheriya Meenalla"" width="130" height="85"  /></…
  • Error Line 872, Column 265: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …of VK Prakash's "Natholi Oru Cheriya Meenalla"" width="130" height="85"  /></a>

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 872, Column 266: end tag for "img" omitted, but OMITTAG NO was specified
    …of VK Prakash's "Natholi Oru Cheriya Meenalla"" width="130" height="85"  /></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 872, Column 133: start tag was here
    …-qnatholi-oru-cheriya-meenallaq.html"><img src="http://i3.ytimg.com/vi/nLuD9Qt…
  • Error Line 948, Column 296: "Neelakurinji" is not a member of a group specified for any attribute
    …direct a Malayalam Movie "Neelakurinji Poothu"" width="130" height="85"  /></a>
  • Error Line 948, Column 302: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …direct a Malayalam Movie "Neelakurinji Poothu"" width="130" height="85"  /></a>

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 948, Column 303: end tag for "img" omitted, but OMITTAG NO was specified
    …direct a Malayalam Movie "Neelakurinji Poothu"" width="130" height="85"  /></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 948, Column 152: start tag was here
    …lam-movie-qneelakurinji-poothuq.html"><img src="http://i1.ytimg.com/vi/4HwBHhb…
  • Error Line 967, Column 168: "My" is not a member of a group specified for any attribute
    …i/-ZTl295pXaU/mqdefault.jpg" alt=""My Fan Ramu" movie audio release" width="13…
  • Error Line 967, Column 172: "Fan" is not a member of a group specified for any attribute
    …Tl295pXaU/mqdefault.jpg" alt=""My Fan Ramu" movie audio release" width="130" h…
  • Error Line 967, Column 176: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …5pXaU/mqdefault.jpg" alt=""My Fan Ramu" movie audio release" width="130" heigh…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 967, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …pXaU/mqdefault.jpg" alt=""My Fan Ramu" movie audio release" width="130" height…

    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 967, Column 99: start tag was here
    …y-fan-ramuq-movie-audio-release.html"><img src="http://i2.ytimg.com/vi/-ZTl295…
  • Error Line 986, Column 212: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …alt="Pooja Function Of Malayalam Movie" Gamer"" width="130" height="85"  /></a>

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 986, Column 213: end tag for "img" omitted, but OMITTAG NO was specified
    …alt="Pooja Function Of Malayalam Movie" Gamer"" width="130" height="85"  /></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 986, Column 107: start tag was here
    …tion-of-malayalam-movieq-gamerq.html"><img src="http://i1.ytimg.com/vi/hvTN0PC…
  • Error Line 1040, Column 12: end tag for "ul" omitted, but OMITTAG NO was specified
          </div><div style="height:10px;margin:10px 0 0 0;"><a href="/component/con…

    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 964, Column 12: start tag was here
          </ul><ul class="tabshow clearfix"><li>
  • Warning Line 1040, Column 159: character "&" is the first character of a delimiter but occurred as data
    …out=seccat" class="morebtn">More News & Gossips</a></div></div><div class="sec…

    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 1040, Column 363: end tag for element "ul" which is not open
    …s.html?layout=seccat">News</a></h1></div></ul><ul class="tabshow clearfix"><li>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1268, Column 12: end tag for "ul" omitted, but OMITTAG NO was specified
          </div><div style="height:10px;margin:10px 0 0 0;"><a href="/component/con…

    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 1192, Column 12: start tag was here
          </ul><ul class="tabshow clearfix"><li>
  • Error Line 1290, Column 14: there is no attribute "TYPE"
    <SCRIPT TYPE="text/javascript" SRC="http://ad.xtendmedia.com/st?ad_type=ad&ad_s…

    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 1290, Column 36: there is no attribute "SRC"
    <SCRIPT TYPE="text/javascript" SRC="http://ad.xtendmedia.com/st?ad_type=ad&ad_s…

    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 1290, Column 76: cannot generate system identifier for general entity "ad_size"
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></SCRIP…

    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 1290, Column 76: general entity "ad_size" not defined and no default entity
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></SCRIP…

    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 1290, Column 83: reference not terminated by REFC delimiter
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1290, Column 83: reference to external entity in attribute value
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1290, Column 83: reference to entity "ad_size" for which no system identifier could be generated
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1290, Column 75: entity was defined here
    …http://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></SCRI…
  • Warning Line 1290, Column 92: cannot generate system identifier for general entity "section"
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></SCRIPT>

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

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

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

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

  • Error Line 1290, Column 92: general entity "section" not defined and no default entity
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></SCRIPT>

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

  • Warning Line 1290, Column 99: reference not terminated by REFC delimiter
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1290, Column 99: reference to external entity in attribute value
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1290, Column 99: reference to entity "section" for which no system identifier could be generated
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1290, Column 91: entity was defined here
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></SCRIPT>
  • Error Line 1290, Column 108: element "SCRIPT" undefined
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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).
  • Warning Line 1356, Column 83: reference not terminated by REFC delimiter
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1356, Column 83: reference to external entity in attribute value
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1356, Column 83: reference to entity "ad_size" for which no system identifier could be generated
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1290, Column 75: entity was defined here
    …http://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></SCRI…
  • Warning Line 1356, Column 99: reference not terminated by REFC delimiter
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1356, Column 99: reference to external entity in attribute value
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1356, Column 99: reference to entity "section" for which no system identifier could be generated
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1290, Column 91: entity was defined here
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></SCRIPT>
  • Error Line 1356, Column 108: element "SCRIPT" undefined
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1359, Column 106: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …imageshack.us/img694/7691/tvserialslist.jpg" border=0 alt="" usemap="#logos" />
  • Error Line 1361, Column 18: required attribute "id" not specified
    <map name="logos"> 

    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 1393, Column 31: character "/" is not allowed in the value of attribute "nohref"
    <area shape="default" nohref="/nohref" title="Default" alt="Default"/> 

    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 1393, Column 38: value of attribute "nohref" cannot be "/nohref"; must be one of "nohref"
    <area shape="default" nohref="/nohref" title="Default" alt="Default"/> 

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

  • Error Line 1399, Column 100: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …g9.imageshack.us/img9/8731/tvshowslist.jpg" border=0 alt="" usemap="#logos1" />
  • Error Line 1401, Column 19: required attribute "id" not specified
    <map name="logos1"> 

    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 1427, Column 31: character "/" is not allowed in the value of attribute "nohref"
    <area shape="default" nohref="/nohref" title="Default" alt="Default"/> 

    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 1427, Column 38: value of attribute "nohref" cannot be "/nohref"; must be one of "nohref"
    <area shape="default" nohref="/nohref" title="Default" alt="Default"/> 

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

  • Warning Line 1431, Column 83: reference not terminated by REFC delimiter
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1431, Column 83: reference to external entity in attribute value
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1431, Column 83: reference to entity "ad_size" for which no system identifier could be generated
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1290, Column 75: entity was defined here
    …http://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></SCRI…
  • Warning Line 1431, Column 99: reference not terminated by REFC delimiter
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1431, Column 99: reference to external entity in attribute value
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1431, Column 99: reference to entity "section" for which no system identifier could be generated
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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 1290, Column 91: entity was defined here
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></SCRIPT>
  • Error Line 1431, Column 108: element "SCRIPT" undefined
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></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).
  • Warning Line 1461, Column 83: reference not terminated by REFC delimiter
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=2620445"></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 1461, Column 83: reference to external entity in attribute value
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=2620445"></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 1461, Column 83: reference to entity "ad_size" for which no system identifier could be generated
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=2620445"></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 1290, Column 75: entity was defined here
    …http://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></SCRI…
  • Warning Line 1461, Column 98: reference not terminated by REFC delimiter
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=2620445"></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 1461, Column 98: reference to external entity in attribute value
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=2620445"></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 1461, Column 98: reference to entity "section" for which no system identifier could be generated
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=2620445"></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 1290, Column 91: entity was defined here
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2620445"></SCRIPT>
  • Error Line 1461, Column 107: element "SCRIPT" undefined
    …ttp://ad.xtendmedia.com/st?ad_type=ad&ad_size=728x90&section=2620445"></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).

Visitor Analysis

Daily Visitor
  • 1.470 visits
Daily Visitor