Buscar: Cidades Curiosidades Saúde Habitação Revista Cultura Economia Editorial Educação Empregos Esportes Mundo País Polícia Política Bombeiros buscam jovens que sumiram em praia da RO Amigos entraram no mar de Piratininga para nadar ...

ofluminense.com.br
  • Domain Name
    ofluminense.com.br
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #53847
  • Page Size
    60.7 KB
  • Ip Address
    189.1.132.252
  • Heading
    H1: 1, H2: 2, H3: 17, H4: 21, H5: 1, H6: 0
  • Images
    1 GIF, 28 JPG, 2 PNG

Website Meta Analysis

  • Title
    Jornal O Fluminense
  • Meta Keyword
  • Meta Description
    Buscar: Cidades Curiosidades Saúde Habitação Revista Cultura Economia Editorial Educação Empregos Esportes Mundo País Polícia Política Bombeiros buscam jovens que sumiram em praia da RO Amigos entraram no mar de Piratininga para nadar e foram ...

Technical Analysis

  • Webserver
    ATS/3.2.0
  • Ip Address
    189.1.132.252
  • Domain Age
    16 Years, 4 Months, 20 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 09 Mar 2013 21:03:11 GMT
  • server: ATS/3.2.0
  • x-powered-by: PHP/5.3.5-1ubuntu7.4
  • expires: Sun, 19 Nov 1978 05:00:00 GMT
  • last-modified: Sat, 09 Mar 2013 21:03:11 GMT
  • cache-control: store, no-cache, must-revalidate
  • content-type: text/html; charset=utf-8
  • age: 1
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for ofluminense.com.br

DNS Analysis


DNS servers
ns1.predialnet.com.br [189.1.128.15]
ns2.predialnet.com.br [189.1.128.16]


DNS Records

Answer records
ofluminense.com.br TXT v=spf1 mx ip4:189.1.132.96/29 ip4:189.1.139.151 ip4:189.1.139.152 ip4:189.1.132.240/28 -all 86400s
ofluminense.com.br SOA
server: ns1.predialnet.com.br
email: sistemas@predialnet.com.br
serial: 2010062366
refresh: 900
retry: 600
expire: 300
minimum ttl: 300
300s
ofluminense.com.br NS  ns1.predialnet.com.br 86400s
ofluminense.com.br NS  ns2.predialnet.com.br 86400s
ofluminense.com.br A 189.1.132.252 3600s
ofluminense.com.br MX
preference: 10
exchange: mx.ofluminense.com.br
86400s

Authority records

Additional records
ns1.predialnet.com.br A 189.1.128.15 14400s
ns2.predialnet.com.br A 189.1.128.16 14400s
mx.ofluminense.com.br A 189.1.132.244 86400s

IP 189.1.132.252 Analysis

  • Country Code
    BR
  • Country Code3
    BRA
  • Country Name
    Brazil
  • City
    Niter�i
  • Continent Code
    SA
  • Latitude
    22.8844
  • Longitude
    43.0944
  • No whois ip data for 189.1.132.252

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 67 Errors
  • 0 Warnings
Ratio Text/Html
  • 0.5271668302415008
Message Error
  • Error Line 98, Column 22: there is no attribute "language"
        <script language="javascript">

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

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

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

  • Error Line 98, Column 34: 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 306, Column 121: document type does not allow element "label" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …" id="search-block-form"><label for="edit-search-block-form-1">Buscar: </label>

    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 307, Column 179: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …title="Digite as palavras que você quer procurar no site." class="form-text" />

    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 308, Column 74: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="submit" name="op" id="edit-submit" value="Ir"  class="btn" />

    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 309, Column 134: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …6260e4ac1444d950fdc133105e93" value="form-8f026260e4ac1444d950fdc133105e93"  />

    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 310, Column 93: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …idden" name="form_id" id="edit-search-block-form" value="search_block_form"  />

    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 315, Column 7: required attribute "type" not specified
    <style>

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

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

  • Error Line 315, Column 7: document type does not allow element "style" here
    <style>

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

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

  • Error Line 614, Column 31: end tag for "img" omitted, but OMITTAG NO was specified
    		<img id="img" src="" alt=""> 

    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 614, Column 3: start tag was here
    		<img id="img" src="" alt=""> 
  • Error Line 639, Column 20: there is no attribute "src"
        			<iframe src="http://tvoflu.com.br/tvoflu/_boxtvoflu2.aspx" width="246" h…

    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 639, Column 73: there is no attribute "width"
    …com.br/tvoflu/_boxtvoflu2.aspx" width="246" height="345px" style="margin-left:…

    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 639, Column 86: there is no attribute "height"
    …/_boxtvoflu2.aspx" width="246" height="345px" style="margin-left:-2px;" frameb…

    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 639, Column 100: there is no attribute "style"
    …spx" width="246" height="345px" style="margin-left:-2px;" frameborder="0" SCRO…

    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 639, Column 132: there is no attribute "frameborder"
    …ght="345px" style="margin-left:-2px;" frameborder="0" SCROLLING=NO ></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 639, Column 146: there is no attribute "SCROLLING"
    …ght="345px" style="margin-left:-2px;" frameborder="0" SCROLLING=NO ></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 639, Column 146: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ght="345px" style="margin-left:-2px;" frameborder="0" SCROLLING=NO ></iframe>		
  • Error Line 639, Column 149: element "iframe" undefined
    …ght="345px" style="margin-left:-2px;" frameborder="0" SCROLLING=NO ></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 644, Column 46: there is no attribute "target"
    …ref="http://www.tvoflu.com.br" target="_blank">Outros vídeos  -  Visite o site…

    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 704, Column 113: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …textoradio'>                        <p>Entrevista com o coordenador do Program…

    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 708, Column 7: required attribute "type" not specified
    <style>.boxtextoradio{font-size:12px !important; display:table; font-weight:nor…

    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 708, Column 7: document type does not allow element "style" here
    <style>.boxtextoradio{font-size:12px !important; display:table; font-weight:nor…

    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 715, Column 7: required attribute "type" not specified
    <style>

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

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

  • Error Line 715, Column 7: document type does not allow element "style" here
    <style>

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

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

  • Error Line 734, Column 97: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …quilibrando as energias</a></strong><p>Confira técnicas que têm sido mais usad…

    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 735, Column 3: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><a href="http://flipagem.ofluminense.com.br/flip.asp?iidpublicacao=2">Clique…

    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 945, Column 116: element "iframe" undefined
    …2.aspx" width="246" height="540" frameborder="0" SCROLLING="NO"></iframe></div>

    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 1028, Column 53: there is no attribute "allowtransparency"
    …"margin-left:30px;" allowtransparency="true" marginwidth="0" marginheight="0" …

    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 1028, Column 72: there is no attribute "marginwidth"
    … allowtransparency="true" marginwidth="0" marginheight="0" hspace="0" vspace="…

    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 1028, Column 89: there is no attribute "marginheight"
    …y="true" marginwidth="0" marginheight="0" hspace="0" vspace="0" frameborder="0…

    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 1028, Column 100: there is no attribute "hspace"
    …rginwidth="0" marginheight="0" hspace="0" vspace="0" frameborder="0" scrolling…

    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 1028, Column 111: there is no attribute "vspace"
    …0" marginheight="0" hspace="0" vspace="0" frameborder="0" scrolling="no" 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 1028, Column 141: there is no attribute "scrolling"
    … vspace="0" frameborder="0" scrolling="no" src="http://www.cptec.inpe.br/widge…

    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 1028, Column 263: element "iframe" undefined
    …f=ffffff" height="154px" width="120px"></iframe><noscript>Previs&atilde;o de <…

    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 1028, Column 283: character data is not allowed here
    …4px" width="120px"></iframe><noscript>Previs&atilde;o de <a href="http://www.c…

    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 1028, Column 354: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …//www.cptec.inpe.br/cidades/tempo/241">Rio de Janeiro/RJ</a> oferecido por <a …

    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 1028, Column 377: character data is not allowed here
    …ades/tempo/241">Rio de Janeiro/RJ</a> oferecido por <a href="http://www.cptec.…

    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 1028, Column 425: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …</a> oferecido por <a href="http://www.cptec.inpe.br">CPTEC/INPE</a></noscript>

    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 1113, Column 231: end tag for element "li" which is not open
    …ecache-default imagecache-Edicao_hoje_default" width="176" height="279" /></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 1116, Column 154: document type does not allow element "a" here; missing one of "object", "ins", "del", "span", "bdo", "tt", "i", "b", "big", "small", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label" start-tag
    …argura=&amp;ed=39789&amp;pag=0&amp;pc=#" class="edicao-online" target="_blank">

    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 1130, Column 8: end tag for "a" 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 1111, Column 6: start tag was here
        <a href="http://flipagem.ofluminense.com.br/flip.asp?iidpublicacao=1&amp;f…
  • Error Line 1165, Column 56: element "Tr" undefined
    <table style="margin-top:-12px; margin-bottom:10px"><Tr><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 1175, 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 1176, Column 8: end tag for "Tr" omitted, but OMITTAG NO was specified
    </table>

    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 1165, Column 53: start tag was here
    <table style="margin-top:-12px; margin-bottom:10px"><Tr><br />
  • Error Line 1176, Column 8: end tag for "table" which is not finished
    </table>

    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 1198, Column 10: ID "signo-tit" already defined
    		<p id="signo-tit">Touro <span>21/04 a 20/05</span></p>

    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 1195, Column 10: ID "signo-tit" first defined here
    		<p id="signo-tit">Áries <span>21/03 a 20/04</span></p>
  • Error Line 1199, Column 8: ID "signo-inf" already defined
    <p id="signo-inf"><span>Regente: Vênus</span>Você hoje tem tudo para ser o cent…

    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 1196, Column 8: ID "signo-inf" first defined here
    <p id="signo-inf"><span>Regente: Marte</span>Não dê ouvidos a fofocas, principa…
  • Error Line 1201, Column 10: ID "signo-tit" already defined
    		<p id="signo-tit">Gêmeos <span>21/05 a 20/06</span></p>

    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 1195, Column 10: ID "signo-tit" first defined here
    		<p id="signo-tit">Áries <span>21/03 a 20/04</span></p>
  • Error Line 1202, Column 8: ID "signo-inf" already defined
    <p id="signo-inf"><span>Regente: Mercúrio</span>Você hoje pode precisar de uma …

    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 1196, Column 8: ID "signo-inf" first defined here
    <p id="signo-inf"><span>Regente: Marte</span>Não dê ouvidos a fofocas, principa…
  • Error Line 1204, Column 10: ID "signo-tit" already defined
    		<p id="signo-tit">Câncer <span>21/06 até 21/07</span></p>

    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 1195, Column 10: ID "signo-tit" first defined here
    		<p id="signo-tit">Áries <span>21/03 a 20/04</span></p>
  • Error Line 1205, Column 8: ID "signo-inf" already defined
    <p id="signo-inf"><span>Regente: Lua</span>Não rejeite as idéias de uma pessoa …

    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 1196, Column 8: ID "signo-inf" first defined here
    <p id="signo-inf"><span>Regente: Marte</span>Não dê ouvidos a fofocas, principa…
  • Error Line 1207, Column 10: ID "signo-tit" already defined
    		<p id="signo-tit">Leão <span>23/07 até 22/08</span></p>

    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 1195, Column 10: ID "signo-tit" first defined here
    		<p id="signo-tit">Áries <span>21/03 a 20/04</span></p>
  • Error Line 1208, Column 8: ID "signo-inf" already defined
    <p id="signo-inf"><span>Regente: Sol</span>Sua liderança natural e personalidad…

    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 1196, Column 8: ID "signo-inf" first defined here
    <p id="signo-inf"><span>Regente: Marte</span>Não dê ouvidos a fofocas, principa…
  • Error Line 1210, Column 10: ID "signo-tit" already defined
    		<p id="signo-tit">Virgem <span>23/08 a 22/09</span></p>

    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 1195, Column 10: ID "signo-tit" first defined here
    		<p id="signo-tit">Áries <span>21/03 a 20/04</span></p>
  • Error Line 1211, Column 8: ID "signo-inf" already defined
    <p id="signo-inf"><span>Regente: Mercúrio</span>Quando faz uma promessa, você l…

    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 1196, Column 8: ID "signo-inf" first defined here
    <p id="signo-inf"><span>Regente: Marte</span>Não dê ouvidos a fofocas, principa…
  • Error Line 1213, Column 10: ID "signo-tit" already defined
    		<p id="signo-tit">Libra <span>23/09 até 22/10</span></p>

    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 1195, Column 10: ID "signo-tit" first defined here
    		<p id="signo-tit">Áries <span>21/03 a 20/04</span></p>
  • Error Line 1214, Column 8: ID "signo-inf" already defined
    <p id="signo-inf"><span>Regente: Vênus</span>A Sorte estará ao seu lado em todo…

    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 1196, Column 8: ID "signo-inf" first defined here
    <p id="signo-inf"><span>Regente: Marte</span>Não dê ouvidos a fofocas, principa…
  • Error Line 1216, Column 10: ID "signo-tit" already defined
    		<p id="signo-tit">Escorpião <span>23/10 até 21/11</span></p>

    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 1195, Column 10: ID "signo-tit" first defined here
    		<p id="signo-tit">Áries <span>21/03 a 20/04</span></p>
  • Error Line 1217, Column 8: ID "signo-inf" already defined
    <p id="signo-inf"><span>Regente: Marte e Plutão</span>Tome para si a responsabi…

    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 1196, Column 8: ID "signo-inf" first defined here
    <p id="signo-inf"><span>Regente: Marte</span>Não dê ouvidos a fofocas, principa…
  • Error Line 1219, Column 10: ID "signo-tit" already defined
    		<p id="signo-tit">Sagitário <span>22/11 até 21/12</span></p>

    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 1195, Column 10: ID "signo-tit" first defined here
    		<p id="signo-tit">Áries <span>21/03 a 20/04</span></p>
  • Error Line 1220, Column 8: ID "signo-inf" already defined
    <p id="signo-inf"><span>Regente: Júpiter</span>Faça algo divertido e agradável …

    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 1196, Column 8: ID "signo-inf" first defined here
    <p id="signo-inf"><span>Regente: Marte</span>Não dê ouvidos a fofocas, principa…
  • Error Line 1222, Column 10: ID "signo-tit" already defined
    		<p id="signo-tit">Capricórnio <span>22/12 até 19/01</span></p>

    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 1195, Column 10: ID "signo-tit" first defined here
    		<p id="signo-tit">Áries <span>21/03 a 20/04</span></p>
  • Error Line 1223, Column 8: ID "signo-inf" already defined
    <p id="signo-inf"><span>Regente: Saturno</span>Não é que o mundo esteja contra …

    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 1196, Column 8: ID "signo-inf" first defined here
    <p id="signo-inf"><span>Regente: Marte</span>Não dê ouvidos a fofocas, principa…
  • Error Line 1225, Column 10: ID "signo-tit" already defined
    		<p id="signo-tit">Aquário <span>20/01 até 18/02</span></p>

    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 1195, Column 10: ID "signo-tit" first defined here
    		<p id="signo-tit">Áries <span>21/03 a 20/04</span></p>
  • Error Line 1226, Column 8: ID "signo-inf" already defined
    <p id="signo-inf"><span>Regente: Urano</span>A capacidade de enxergar os dois l…

    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 1196, Column 8: ID "signo-inf" first defined here
    <p id="signo-inf"><span>Regente: Marte</span>Não dê ouvidos a fofocas, principa…
  • Error Line 1228, Column 10: ID "signo-tit" already defined
    		<p id="signo-tit">Peixes <span>19/02 até 20/03</span></p>

    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 1195, Column 10: ID "signo-tit" first defined here
    		<p id="signo-tit">Áries <span>21/03 a 20/04</span></p>
  • Error Line 1229, Column 8: ID "signo-inf" already defined
    <p id="signo-inf"><span>Regente: Netuno</span>É claro que você deve ser educado…

    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 1196, Column 8: ID "signo-inf" first defined here
    <p id="signo-inf"><span>Regente: Marte</span>Não dê ouvidos a fofocas, principa…

Visitor Analysis

Daily Visitor
  • 3.733 visits
Daily Visitor