Assistir tv online no melhor e mais completo site para ver tv online gratis, ver tv no pc, futebol ao vivo, filmes, Globo, Fox, Band, Record, Sbt ...

tvonlinegratis.tv
  • Domain Name
    tvonlinegratis.tv
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #33894
  • Page Size
    113.2 KB
  • Ip Address
    146.0.75.18
  • Heading
    H1: 1, H2: 1, H3: 1, H4: 0, H5: 0, H6: 0
  • Images
    4 GIF, 3 JPG, 214 PNG

Website Meta Analysis

  • Title
    Assistir Tv Online - Ver Tv Online Grátis - Futebol Ao Vivo no pc
  • Meta Keyword
    futebol, graça, gratis, bbb 13, filmes, assistir, free, canais, online, hbo, sbt, record, tv, internet, ver, bandeirantes, rede, simpson, series, gratis, fox brasil, supernatural, chaves, cartoon network, nick, mtv, disney, libertadores, ao vivo, assista
  • Meta Description
    Assistir tv online no melhor e mais completo site para ver tv online gratis, ver tv no pc, futebol ao vivo, filmes, Globo, Fox, Band, Record, Sbt

Technical Analysis

  • Webserver
    Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • Ip Address
    146.0.75.18
  • Domain Age
    1 Years, 9 Months, 13 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from tvonlinegratis.tv.

HTML Analysis

  • date: Fri, 28 Jun 2013 11:06:58 GMT
  • server: Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • x-powered-by: PHP/5.3.10
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for tvonlinegratis.tv

DNS Analysis


DNS servers
nserver1.contabo.net [194.126.239.242]
nserver2.contabo.net


DNS Records

Answer records
tvonlinegratis.tv SOA
server: nserver1.contabo.net
email: nameserver@kambach.net
serial: 2013020201
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
86400s
tvonlinegratis.tv A 193.34.145.40 86400s
tvonlinegratis.tv MX
preference: 10
exchange: mail.tvonlinegratis.tv
86400s
tvonlinegratis.tv NS  nserver2.contabo.net 86400s
tvonlinegratis.tv NS  nserver1.contabo.net 86400s

Authority records

Additional records
mail.tvonlinegratis.tv A 193.34.145.40 86400s
nserver1.contabo.net A 91.194.91.216 3600s
nserver2.contabo.net A 91.194.91.216 3600s

IP 146.0.75.18 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 160 Errors
  • 32 Warnings
Ratio Text/Html
  • 0.8755521811154059
Message Error
  • Error Line 5, Column 191: end tag for "meta" omitted, but OMITTAG NO was specified
    …ver tv no pc, futebol ao vivo, filmes, BBB 13, Fox, Band, Record, Sbt, Globo.">

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

  • Info Line 5, Column 1: start tag was here
    <meta name="description" content="Assistir tv online no melhor e mais completo …
  • Error Line 6, Column 602: end tag for "meta" omitted, but OMITTAG NO was specified
    …lubes ao vivo, copa do mundo ao vivo, sbt ao vivo, assista tv online, BBB 13"> 

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

  • Info Line 6, Column 1: start tag was here
    <meta name="keywords" content="Tv Online, Futebol ao vivo, tv de graça, tv onli…
  • Error Line 11, Column 57: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="copyright" content="Grupo Interligado 2013">

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

  • Info Line 11, Column 1: start tag was here
    <meta name="copyright" content="Grupo Interligado 2013">
  • Error Line 12, Column 46: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="author" content="Luciano Junior"> 

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

  • Info Line 12, Column 1: start tag was here
    <meta name="author" content="Luciano Junior"> 
  • Error Line 13, Column 50: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="email" content="foxersites@live.com">

    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="email" content="foxersites@live.com">
  • Error Line 14, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name="Distribution" content=Global>
  • Error Line 14, Column 42: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="Distribution" content=Global>

    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 14, Column 1: start tag was here
    <meta name="Distribution" content=Global>
  • Error Line 15, Column 39: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="rating" content="General">

    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 15, Column 1: start tag was here
    <meta name="rating" content="General">
  • Error Line 16, Column 44: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="Robots" content="INDEX,FOLLOW">

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

  • Info Line 16, Column 1: start tag was here
    <meta name="Robots" content="INDEX,FOLLOW">
  • Error Line 17, Column 44: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="revisit-after" content="1 day">

    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 17, Column 1: start tag was here
    <meta name="revisit-after" content="1 day">
  • Error Line 19, Column 57: end tag for "link" omitted, but OMITTAG NO was specified
    <link type="text/css" rel="stylesheet" href="tipsy.css">

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

  • Info Line 19, Column 1: start tag was here
    <link type="text/css" rel="stylesheet" href="tipsy.css">
  • Error Line 20, Column 68: end tag for "link" omitted, but OMITTAG NO was specified
    <link href="estilo-meuguiatv.css" type="text/css" rel="stylesheet">

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

  • Info Line 20, Column 1: start tag was here
    <link href="estilo-meuguiatv.css" type="text/css" rel="stylesheet">
  • Error Line 27, Column 110: end tag for "link" omitted, but OMITTAG NO was specified
    …eapis.com/css?family=Open+Sans+Condensed:700' rel='stylesheet' type='text/css'>

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

  • Info Line 27, Column 1: start tag was here
    <link href='http://fonts.googleapis.com/css?family=Open+Sans+Condensed:700' rel…
  • Error Line 44, Column 8: required attribute "type" not specified
    <script>var mensagem="";function clickIE(){if(document.all){(mensagem);return f…

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

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

  • Warning Line 46, Column 43: character "&" is the first character of a delimiter but occurred as data
    …ument.layers||(document.getElementById&&!document.all)){if(e.which==2||e.which…

    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 46, Column 44: character "&" is the first character of a delimiter but occurred as data
    …ment.layers||(document.getElementById&&!document.all)){if(e.which==2||e.which=…

    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 51, 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 60, Column 21: there is no attribute "FRAMEBORDER"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGH…

    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 60, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGH…
  • Error Line 60, Column 35: there is no attribute "MARGINWIDTH"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGH…

    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 60, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGH…
  • Error Line 60, Column 50: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="…

    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 60, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="…
  • Error Line 60, Column 62: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://www.a…

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

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

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

  • Error Line 60, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://www.a…
  • Error Line 60, Column 71: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://www.assistatvo…

    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 60, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://www.assistatvo…
  • Error Line 60, Column 82: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://www.assistatvonline.com/a…

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

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

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

  • Error Line 60, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://www.assistatvonline.com/a…
  • Error Line 60, Column 89: there is no attribute "SRC"
    … SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://www.assistatvonline.com/afiliado…

    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 60, Column 141: element "IFRAME" undefined
    …28 HEIGHT=90 SRC="http://www.assistatvonline.com/afiliados/topo.html"></IFRAME>

    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 37: there is no attribute "alt"
    <li><a href="futebol/embed.php" alt="Futebol ao vivo" title="Assistir futebol a…

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

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

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

  • Error Line 79, Column 10: ID "site" already defined
    <div id='site'>

    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 57, Column 10: ID "site" first defined here
    <div id='site'>
  • Error Line 86, Column 12: ID "content" already defined
    <table id='content' width="100%" border="0" cellspacing="7" cellpadding="0">

    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 80, Column 12: ID "content" first defined here
    <table id='content' width="100%" border="0" cellspacing="0" cellpadding="0">
  • Error Line 89, Column 35: there is no attribute "alt"
    <iframe src='index/meio.html' alt="tv online" title="ver tv online" name='Playe…

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

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

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

  • Error Line 92, Column 57: there is no attribute "border"
    …ar" width="468" scrolling="no" border="0" frameborder="0" height="60" src="htt…

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

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

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

  • Error Line 94, Column 6: end tag for "td" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 88, Column 1: start tag was here
    <td valign="top">
  • Error Line 94, Column 6: end tag for "tr" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 87, Column 1: start tag was here
    <tr>
  • Error Line 94, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 86, Column 1: start tag was here
    <table id='content' width="100%" border="0" cellspacing="7" cellpadding="0">
  • Error Line 95, Column 6: end tag for element "div" which is not open
    </div>

    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 96, Column 5: end tag for element "td" which is not open
    </td>

    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 97, Column 17: document type does not allow element "td" here
    <td valign="top">

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

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

  • Error Line 99, Column 12: there is no attribute "src"
    <embed src="http://www.xatech.com/web_gear/chat/chat.swf" quality="high" width=…

    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 99, Column 67: there is no attribute "quality"
    …h.com/web_gear/chat/chat.swf" quality="high" width="468" height="390" name="ch…

    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 99, Column 80: there is no attribute "width"
    …r/chat/chat.swf" quality="high" width="468" height="390" name="chat" FlashVars…

    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 99, Column 93: there is no attribute "height"
    …wf" quality="high" width="468" height="390" name="chat" FlashVars="id=18899384…

    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 99, Column 104: there is no attribute "name"
    …="high" width="468" height="390" name="chat" FlashVars="id=188993848" align="m…

    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 99, Column 121: there is no attribute "FlashVars"
    …8" height="390" name="chat" FlashVars="id=188993848" align="middle" allowScrip…

    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 99, Column 142: there is no attribute "align"
    …"chat" FlashVars="id=188993848" align="middle" allowScriptAccess="sameDomain" …

    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 99, Column 169: there is no attribute "allowScriptAccess"
    …848" align="middle" allowScriptAccess="sameDomain" type="application/x-shockwa…

    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 99, Column 187: there is no attribute "type"
    …" allowScriptAccess="sameDomain" type="application/x-shockwave-flash" pluginsp…

    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 99, Column 231: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" pluginspage="http://xat.com/update_flash.shtml" /><p…

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

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

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

  • Error Line 99, Column 268: element "embed" undefined
    …="http://xat.com/update_flash.shtml" /><param name="wmode" value="transparent"…

    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 99, Column 309: document type does not allow element "param" here; missing one of "object", "applet" start-tag
    …at.com/update_flash.shtml" /><param name="wmode" value="transparent"/></object>

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

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

  • Error Line 99, Column 318: end tag for element "object" which is not open
    …at.com/update_flash.shtml" /><param name="wmode" value="transparent"/></object>

    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 103, Column 17: there is no attribute "href"
    <g:plusone href="http://assistirtvgratisonline.com"></g:plusone>

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

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

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

  • Error Line 103, Column 52: element "g:plusone" undefined
    <g:plusone href="http://assistirtvgratisonline.com"></g:plusone>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 112, Column 74: there is no attribute "data-url"
    …class="twitter-share-button" data-url="http://www.assistirtvgratisonline.com" …

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

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

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

  • Error Line 112, Column 124: there is no attribute "data-text"
    …assistirtvgratisonline.com" data-text="Estou os melhores canais de tv por assi…

    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 112, Column 232: there is no attribute "data-count"
    …e www.assistatvonline.com" data-count="horizontal" data-via="atvon" data-lang=…

    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 112, Column 254: there is no attribute "data-via"
    …com" data-count="horizontal" data-via="atvon" data-lang="pt">Tweet</a><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 112, Column 272: there is no attribute "data-lang"
    …orizontal" data-via="atvon" data-lang="pt">Tweet</a><script type="text/javascr…

    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 113, Column 247: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"
    …&amp;font&amp;height=30" scrolling="No" frameborder="0" style="border:none;ove…

    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 116, Column 109: there is no attribute "scrolling"
    …ivo online" target="Player" scrolling="auto"><img src="images/futebol-ao-vivo.…

    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 116, Column 188: required attribute "alt" not specified
    … src="images/futebol-ao-vivo.png" width="460" height="34" border="0"></a></div>

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

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

  • Error Line 116, Column 192: end tag for "img" omitted, but OMITTAG NO was specified
    … src="images/futebol-ao-vivo.png" width="460" height="34" border="0"></a></div>

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

  • Info Line 116, Column 116: start tag was here
    …ine" target="Player" scrolling="auto"><img src="images/futebol-ao-vivo.png" wi…
  • Error Line 118, Column 5: end tag for element "tr" which is not open
    </tr>

    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 119, Column 8: end tag for element "table" which is not open
    </table>

    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 120, Column 12: ID "content" already defined
    <table id='content' width="100%" border="0" cellspacing="7" cellpadding="0">

    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 80, Column 12: ID "content" first defined here
    <table id='content' width="100%" border="0" cellspacing="0" cellpadding="0">
  • Error Line 123, Column 6: end tag for element "div" which is not open
    </div>

    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 128, Column 5: character data is not allowed here
        Guia da Tv

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 129, Column 7: end tag for "ol" which is not finished
      </ol>

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

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

  • Error Line 134, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <li class=home>
  • Error Line 137, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <span class=metadados>HBOs, Telecines, MGM, TNT, Universal...</span>
  • Error Line 140, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <li class=home>
  • Error Line 143, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <span class=metadados>Sony, Fox, AXN, Warner, People & Arts...</span>
  • Warning Line 143, Column 56: character "&" is the first character of a delimiter but occurred as data
      <span class=metadados>Sony, Fox, AXN, Warner, People & Arts...</span>

    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 146, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <li class=home>
  • Error Line 149, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <span class=metadados>ESPN, SporTV, Band Sport, PFC...</span>
  • Error Line 152, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <li class=home>
  • Error Line 155, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <span class=metadados>Cartoon, Disney XD, Discovery Kids, Nick ...</span>
  • Error Line 157, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <li class=home>
  • Error Line 160, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <span class=metadados>Multishow, GNT, A&E, E! Entertainment TV...</span>
  • Warning Line 160, Column 43: cannot generate system identifier for general entity "E"
      <span class=metadados>Multishow, GNT, A&E, E! Entertainment TV...</span>

    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 160, Column 43: general entity "E" not defined and no default entity
      <span class=metadados>Multishow, GNT, A&E, E! Entertainment TV...</span>

    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 160, Column 44: reference not terminated by REFC delimiter
      <span class=metadados>Multishow, GNT, A&E, E! Entertainment TV...</span>

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

  • Error Line 160, Column 44: reference to entity "E" for which no system identifier could be generated
      <span class=metadados>Multishow, GNT, A&E, E! Entertainment TV...</span>

    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 160, Column 42: entity was defined here
      <span class=metadados>Multishow, GNT, A&E, E! Entertainment TV...</span>
  • Error Line 163, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <li class=home>
  • Error Line 166, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <span class=metadados>Nat Geo, Discovery, History Channel...</span>
  • Error Line 169, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <li class=home>
  • Error Line 172, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <span class=metadados>GloboNews, CNN, BBC, Fox News, Band...</span> </a>
  • Error Line 174, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <li class=home>
  • Error Line 177, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <span class=metadados>Globo, Band, Record, SBT, CNT, Rede TV...</span> </a>
  • Error Line 179, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <li class=home>
  • Error Line 182, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      <span class=metadados>Veja tudo que est&aacute; passando agora na TV!</span>
  • Error Line 191, Column 10: ID "redes" already defined
    <div id='redes'>

    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 102, Column 10: ID "redes" first defined here
    <div id='redes'>
  • Error Line 195, Column 5: character data is not allowed here
        Facebook

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 196, Column 7: end tag for "ol" which is not finished
      </ol>

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

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

  • Error Line 199, Column 375: there is no attribute "allowTransparency"
    …overflow:hidden; width:298px; height:440px;" allowTransparency="true"></iframe>

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

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

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

  • Error Line 202, Column 10: document type does not allow element "center" here; assuming missing "li" start-tag
      <center>
  • Error Line 203, Column 16: end tag for "li" omitted, but OMITTAG NO was specified
      </center></td>

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

  • Info Line 202, Column 3: start tag was here
      <center>
  • Error Line 203, Column 16: end tag for "ul" omitted, but OMITTAG NO was specified
      </center></td>

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

  • Info Line 201, Column 3: start tag was here
      <ul>
  • Error Line 203, Column 16: end tag for "div" omitted, but OMITTAG NO was specified
      </center></td>

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

  • Info Line 198, Column 3: start tag was here
      <div id='facebook_content'>
  • Error Line 207, Column 5: character data is not allowed here
        Enquete

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 208, Column 7: end tag for "ol" which is not finished
      </ol>

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

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

  • Error Line 212, Column 30: 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 260, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <form name=frm910766>
  • Error Line 260, Column 21: required attribute "action" not specified
    <form name=frm910766>

    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 261, Column 3: element "B" undefined
    <B>Qual dos canais voc&#234; gostaria de assistir aqui?</B><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 261, Column 63: element "BR" undefined
    <B>Qual dos canais voc&#234; gostaria de assistir aqui?</B><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 262, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    <input name="opcao" type="radio" value="4890587">Baby TV<br>

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

  • Info Line 262, Column 1: start tag was here
    <input name="opcao" type="radio" value="4890587">Baby TV<br>
  • Error Line 262, Column 61: end tag for "br" omitted, but OMITTAG NO was specified
    <input name="opcao" type="radio" value="4890587">Baby TV<br>

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

  • Info Line 262, Column 57: start tag was here
    <input name="opcao" type="radio" value="4890587">Baby TV<br>
  • Error Line 263, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    <input name="opcao" type="radio" value="4890588">American Dad<br>

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

  • Info Line 263, Column 1: start tag was here
    <input name="opcao" type="radio" value="4890588">American Dad<br>
  • Error Line 263, Column 66: end tag for "br" omitted, but OMITTAG NO was specified
    <input name="opcao" type="radio" value="4890588">American Dad<br>

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

  • Info Line 263, Column 62: start tag was here
    <input name="opcao" type="radio" value="4890588">American Dad<br>
  • Error Line 264, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    <input name="opcao" type="radio" value="5332311">R&#225; Tim Bum<br>

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

  • Info Line 264, Column 1: start tag was here
    <input name="opcao" type="radio" value="5332311">R&#225; Tim Bum<br>
  • Error Line 264, Column 69: end tag for "br" omitted, but OMITTAG NO was specified
    <input name="opcao" type="radio" value="5332311">R&#225; Tim Bum<br>

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

  • Info Line 264, Column 65: start tag was here
    <input name="opcao" type="radio" value="5332311">R&#225; Tim Bum<br>
  • Error Line 265, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    <input name="opcao" type="radio" value="5332324">Serie OZ<br>

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

  • Info Line 265, Column 1: start tag was here
    <input name="opcao" type="radio" value="5332324">Serie OZ<br>
  • Error Line 265, Column 62: end tag for "br" omitted, but OMITTAG NO was specified
    <input name="opcao" type="radio" value="5332324">Serie OZ<br>

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

  • Info Line 265, Column 58: start tag was here
    <input name="opcao" type="radio" value="5332324">Serie OZ<br>
  • Error Line 266, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    <input name="opcao" type="radio" value="5522255">Infinito<br>

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

  • Info Line 266, Column 1: start tag was here
    <input name="opcao" type="radio" value="5522255">Infinito<br>
  • Error Line 266, Column 62: end tag for "br" omitted, but OMITTAG NO was specified
    <input name="opcao" type="radio" value="5522255">Infinito<br>

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

  • Info Line 266, Column 58: start tag was here
    <input name="opcao" type="radio" value="5522255">Infinito<br>
  • Error Line 267, Column 50: end tag for "input" omitted, but OMITTAG NO was specified
    … name="opcao" type="radio" value="5537858">Filmes de anima&#231;&#227;o 24H<br>

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

  • Info Line 267, Column 1: start tag was here
    <input name="opcao" type="radio" value="5537858">Filmes de anima&#231;&#227;o 2…
  • Error Line 267, Column 86: end tag for "br" omitted, but OMITTAG NO was specified
    … name="opcao" type="radio" value="5537858">Filmes de anima&#231;&#227;o 24H<br>

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

  • Info Line 267, Column 82: start tag was here
    … name="opcao" type="radio" value="5537858">Filmes de anima&#231;&#227;o 24H<br>
  • Error Line 268, Column 47: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" name="id" value="910766">

    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 268, Column 1: start tag was here
    <input type="hidden" name="id" value="910766">
  • Error Line 271, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><a href="javascript:Abre('http://www.enquetes.com.br/enquete.asp?id=910766'…

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

  • Info Line 271, Column 1: start tag was here
    <br><a href="javascript:Abre('http://www.enquetes.com.br/enquete.asp?id=910766'…
  • Error Line 272, Column 7: end tag for "BR" omitted, but OMITTAG NO was specified
    </form><br>

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

  • Info Line 261, Column 60: start tag was here
    <B>Qual dos canais voc&#234; gostaria de assistir aqui?</B><BR>
  • Error Line 272, Column 12: end tag for "br" omitted, but OMITTAG NO was specified
    </form><br>

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

  • Info Line 272, Column 8: start tag was here
    </form><br>
  • Error Line 273, Column 38: end tag for "br" omitted, but OMITTAG NO was specified
    <!-- FIM DO CODIGO DA ENQUETE --><br>

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

  • Info Line 273, Column 34: start tag was here
    <!-- FIM DO CODIGO DA ENQUETE --><br>
  • Error Line 276, Column 71: required attribute "type" not specified
      <script charset="utf-8" src="http://widgets.twimg.com/j/2/widget.js"></script>

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

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

  • Error Line 277, Column 10: 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 308, Column 10: document type does not allow element "center" here; assuming missing "li" start-tag
      <center></center>
  • Error Line 309, Column 8: end tag for "li" omitted, but OMITTAG NO was specified
       </td>   

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

  • Info Line 308, Column 3: start tag was here
      <center></center>
  • Error Line 309, Column 8: end tag for "ul" omitted, but OMITTAG NO was specified
       </td>   

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

  • Info Line 307, Column 3: start tag was here
      <ul>
  • Error Line 309, Column 8: end tag for "div" omitted, but OMITTAG NO was specified
       </td>   

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

  • Info Line 275, Column 5: start tag was here
        <div id='twitter_content'>
  • Error Line 312, Column 12: ID "content" already defined
    <table id='content' width="100%" border="0" cellspacing="7" cellpadding="0">

    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 80, Column 12: ID "content" first defined here
    <table id='content' width="100%" border="0" cellspacing="0" cellpadding="0">
  • Error Line 315, Column 90: end tag for "img" omitted, but OMITTAG NO was specified
    …g src="images/separar.png" alt="links" title="espaço de anunciantes" ></center>

    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 315, Column 9: start tag was here
    <center><img src="images/separar.png" alt="links" title="espaço de anunciantes"…
  • Error Line 321, Column 8: document type does not allow element "center" here; assuming missing "li" start-tag
    <center>
  • Error Line 329, Column 169: "1px" is not a member of a group specified for any attribute
    …ck.us/a/img525/7532/pontoperdido.gif" 1px solid #000000" width="120" height="6…
  • Error Line 329, Column 179: "solid" is not a member of a group specified for any attribute
    …g525/7532/pontoperdido.gif" 1px solid #000000" width="120" height="60" border=…
  • Error Line 329, Column 223: required attribute "alt" not specified
    …toperdido.gif" 1px solid #000000" width="120" height="60" border="0"/></a>     

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

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

  • Error Line 332, Column 225: duplicate specification of attribute "border"
    …/br_fl2.png" alt="assistir tv online" width="120" height="60" border="0"/></a> 

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

  • Error Line 333, Column 251: required attribute "alt" not specified
    …roPihEPe4/s1600/fadadosexo120x60.jpg" width="120" height="60" border="0" /></a>

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

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

  • Error Line 334, Column 9: end tag for "p" omitted, but OMITTAG NO was specified
    </center>

    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 327, Column 213: start tag was here
    …ratis" title="Acidez Mental"  width="120" height="60" border="0"/></a></p> <p> 
  • Error Line 335, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

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

  • Info Line 321, Column 1: start tag was here
    <center>
  • Error Line 339, Column 5: end tag for "tr" which is not finished
    </tr>

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

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

  • Warning Line 409, Column 22: unclosed start-tag requires SHORTTAG YES
    <div class='direitos'<a>ASSISTIR</a> <b>TV ONLINE</b> <c>GRATIS</c>&copy; 2012-…

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Error Line 409, Column 57: element "c" undefined
    …os'<a>ASSISTIR</a> <b>TV ONLINE</b> <c>GRATIS</c>&copy; 2012-2013 - Todos Dire…

    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 409, Column 116: end tag for "br" omitted, but OMITTAG NO was specified
    … <b>TV ONLINE</b> <c>GRATIS</c>&copy; 2012-2013 - Todos Direitos Reservados<br>

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

  • Info Line 409, Column 112: start tag was here
    … <b>TV ONLINE</b> <c>GRATIS</c>&copy; 2012-2013 - Todos Direitos Reservados<br>
  • Error Line 413, Column 9: end tag for element "center" which is not open
    </center>                        

    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 415, Column 25: end tag for element "center" which is not open
                    </center>

    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 417, Column 17: end tag for element "center" which is not open
            </center>           

    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.

Visitor Analysis

Daily Visitor
  • 5.250 visits
Daily Visitor