Ao Vivo Ao Vivo Agora . com. TV Grátis! Ao Vivo Agora| TV Online ...

aovivoagora.com
  • Domain Name
    aovivoagora.com
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #24470
  • Page Size
    94.8 KB
  • Ip Address
    93.115.82.78
  • Heading
    H1: 0, H2: 7, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    19 GIF, 33 JPG, 141 PNG

Website Meta Analysis

  • Title
    Ao Vivo Agora | Assistir TV online, futebol ao vivo , filmes on line, series de tv , radios, grátis na Internet!
  • Meta Keyword
    Ao vivo, televisão, on line, gratis, futebol, series, tv, stream, serie a, serie b, brasileirão, 2012, supernatural, the vampire diaries, the walking dead, house, terra nova, chuck, jogo, corinthians, flamengo, são paulo, santos, botafogo, fluminense, vasco, cruzeiro, inter,atletico, cruzeiro, sport, vitoria, bahia, parana, portuguesa, nautico, santa cruz, fortaleza, gremio, coritiba, paysandu, seleção brasilerira, band, sportv, espn, telecine, hbo, rede tv, record, news, bbb, fazenda, sbt, the big bang theory,
  • Meta Description
    Ao Vivo Ao Vivo Agora . com. TV Grátis! Ao Vivo Agora| TV Online

Technical Analysis

  • Webserver
    nginx/1.2.8
  • Ip Address
    93.115.82.78
  • Domain Age
    2 Years, 4 Months, 22 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.2.8
  • date: Wed, 03 Jul 2013 15:03:16 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.3.20
  • x-pingback: http://aovivoagora.com/xmlrpc.php
  • content-encoding: gzip
  • vary: Accept-Encoding
  • last-modified: Thu, 01 Jan 1970 00:00:00 GMT
  • x-server-cache: EXPIRED
  • nextdns-eu-01: HIT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: aovivoagora.com

Registrant Contact:
Whois Privacy Protection Service, Inc.
Whois Agent ()

Fax:
PMB 368, 14150 NE 20th St - F1
C/O aovivoagora.com
Bellevue, WA 98007
US

Administrative Contact:
Whois Privacy Protection Service, Inc.
Whois Agent ( email )
+1.4252740657
Fax: +1.4259744730
PMB 368, 14150 NE 20th St - F1
C/O aovivoagora.com
Bellevue, WA 98007
US

Technical Contact:
Whois Privacy Protection Service, Inc.
Whois Agent ( email )
+1.4252740657
Fax: +1.4259744730
PMB 368, 14150 NE 20th St - F1
C/O aovivoagora.com
Bellevue, WA 98007
US

Status: Locked

Name Servers:
Cody.NS.cloudflare.com
olga.ns.cloudflare.com

Creation date: 25 Mar 2011 12:36:00
Expiration date: 25 Mar 2013 07:36:00

DNS Analysis


DNS servers
cody.ns.cloudflare.com [173.245.59.107]
olga.ns.cloudflare.com [173.245.58.137]


DNS Records

Answer records
aovivoagora.com NS  cody.ns.cloudflare.com 86400s
aovivoagora.com A 199.27.135.243 30s
aovivoagora.com NS  olga.ns.cloudflare.com 86400s
aovivoagora.com SOA
server: cody.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2013012917
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s
aovivoagora.com A 199.27.134.243 30s

Authority records

Additional records

IP 93.115.82.78 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 81 Errors
  • 11 Warnings
Ratio Text/Html
  • 0.8020922442669415
Message Error
  • Error Line 17, 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 17, Column 1: start tag was here
    <link href='http://fonts.googleapis.com/css?family=Open+Sans+Condensed:700' rel…
  • Error Line 177, Column 102: element "blink" undefined
    …om/AoVivo/apostar-jogos-de-futebol/"><strong> <blink>APOSTAR</blink> </a> </li>

    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 177, Column 122: end tag for "strong" omitted, but OMITTAG NO was specified
    …om/AoVivo/apostar-jogos-de-futebol/"><strong> <blink>APOSTAR</blink> </a> </li>

    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 177, Column 87: start tag was here
    …com/AoVivo/apostar-jogos-de-futebol/"><strong> <blink>APOSTAR</blink> </a> </l…
  • Error Line 188, Column 25: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="seriesonline"><a href="http://www.aovivoagora.com/AoVivo/assistir-fi…

    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 203, Column 78: there is no attribute "re"
    …voagora.com/categoria/series/" rel="nofollow" re="nofollow" >+ Series</a></li>

    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 203, Column 88: non SGML character number 28
    …voagora.com/categoria/series/" rel="nofollow" re="nofollow" >+ Series</a></li>

    You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.

    Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.

    This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.

  • Error Line 206, Column 30: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    	            <li class="chat"><a href="http://www.aovivoagora.com/AoVivo/chat-f…

    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 207, Column 26: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    								<li class="ajuda"><a href="http://www.aovivoagora.com/AoVivo/14899/" re…

    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 208, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    				<li class="privacidade"><a href="http://www.aovivoagora.com/politica-de-pri…

    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 209, Column 8: 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 178, Column 1: start tag was here
    <li class="futebol"><a href="http://www.aovivoagora.com/AoVivo/futebol-2012-ao-…
  • Error Line 219, Column 70: there is no attribute "annotation"
    …gin:0 0 12px 0;"><g:plusone annotation="inline" width="300"></g:plusone></span>

    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 219, Column 85: there is no attribute "width"
    …gin:0 0 12px 0;"><g:plusone annotation="inline" width="300"></g:plusone></span>

    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 219, Column 90: element "g:plusone" undefined
    …gin:0 0 12px 0;"><g:plusone annotation="inline" width="300"></g:plusone></span>

    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 223, Column 140: there is no attribute "data-via"
    …" rel="nofollow"  class="twitter-share-button" data-via="celsojunior">Tweet</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 224, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

    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 234, Column 94: there is no attribute "hspace"
    …ht="250" 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 234, Column 105: there is no attribute "vspace"
    …ht="250" 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 235, Column 28: there is no attribute "bordercolor"
    scrolling="no" bordercolor="#000000" src="http://www.webstats.com.br/iframes/ao…

    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 235, Column 110: end tag for element "IFRAME" which is not open
    …0000" src="http://www.webstats.com.br/iframes/aovivoagora/index.html"></IFRAME>

    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 241, Column 5: there is no attribute "src"
    src="http://imstore.bet365affiliates.com/365_080307-507-72-2-149-22-46296.aspx" 

    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 242, Column 9: there is no attribute "quality"
    quality="high" 

    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 243, Column 19: there is no attribute "allowScriptAccess"
    allowScriptAccess="always" 

    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 244, Column 17: there is no attribute "allowNetworking"
    allowNetworking="external"  

    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 245, Column 15: there is no attribute "swLiveConnect"
    swLiveConnect="false" 

    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 246, Column 7: there is no attribute "width"
    width="300" 

    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 247, Column 8: there is no attribute "height"
    height="250" 

    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 248, Column 6: there is no attribute "name"
    name="755602a3f497429f8edace67fa3c23d2" 

    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 249, Column 6: there is no attribute "type"
    type="application/x-shockwave-flash" 

    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 250, Column 13: there is no attribute "pluginspage"
    pluginspage="https://www.macromedia.com/go/getflashplayer" 

    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 251, Column 7: there is no attribute "wmode"
    wmode="transparent">

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

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

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

  • Error Line 251, Column 20: element "embed" undefined
    wmode="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 308, Column 38: there is no attribute "alt"
    <a href="http://www.histats.com" alt="page hit counter" target="_blank" >

    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 309, Column 55: there is no attribute "flashvars"
    …://s10.histats.com/29.swf"  flashvars="jver=1&acsid=2039668&domi=4"  quality="…

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

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

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

  • Warning Line 309, Column 63: cannot generate system identifier for general entity "acsid"
    …istats.com/29.swf"  flashvars="jver=1&acsid=2039668&domi=4"  quality="high"  w…

    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 309, Column 63: general entity "acsid" not defined and no default entity
    …istats.com/29.swf"  flashvars="jver=1&acsid=2039668&domi=4"  quality="high"  w…

    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 309, Column 68: reference not terminated by REFC delimiter
    …s.com/29.swf"  flashvars="jver=1&acsid=2039668&domi=4"  quality="high"  width=…

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

  • Warning Line 309, Column 68: reference to external entity in attribute value
    …s.com/29.swf"  flashvars="jver=1&acsid=2039668&domi=4"  quality="high"  width=…

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

  • Error Line 309, Column 68: reference to entity "acsid" for which no system identifier could be generated
    …s.com/29.swf"  flashvars="jver=1&acsid=2039668&domi=4"  quality="high"  width=…

    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 309, Column 62: entity was defined here
    …histats.com/29.swf"  flashvars="jver=1&acsid=2039668&domi=4"  quality="high"  …
  • Warning Line 309, Column 77: cannot generate system identifier for general entity "domi"
    …swf"  flashvars="jver=1&acsid=2039668&domi=4"  quality="high"  width="115" hei…

    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 309, Column 77: general entity "domi" not defined and no default entity
    …swf"  flashvars="jver=1&acsid=2039668&domi=4"  quality="high"  width="115" hei…

    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 309, Column 81: reference not terminated by REFC delimiter
    …  flashvars="jver=1&acsid=2039668&domi=4"  quality="high"  width="115" height=…

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

  • Warning Line 309, Column 81: reference to external entity in attribute value
    …  flashvars="jver=1&acsid=2039668&domi=4"  quality="high"  width="115" height=…

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

  • Error Line 309, Column 81: reference to entity "domi" for which no system identifier could be generated
    …  flashvars="jver=1&acsid=2039668&domi=4"  quality="high"  width="115" height=…

    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 309, Column 76: entity was defined here
    ….swf"  flashvars="jver=1&acsid=2039668&domi=4"  quality="high"  width="115" he…
  • Error Line 309, Column 147: there is no attribute "align"
    …115" height="60" name="29.swf"  align="middle" type="application/x-shockwave-f…

    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 309, Column 272: element "embed" undefined
    …nspage="http://www.macromedia.com/go/getflashplayer" wmode="transparent" /></a>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 310, Column 53: character "&" is the first character of a delimiter but occurred as data
    …tp://sstatic1.histats.com/0.gif?2039668&101" alt="hit counter code" border="0">

    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 310, Column 93: end tag for "img" omitted, but OMITTAG NO was specified
    …tp://sstatic1.histats.com/0.gif?2039668&101" alt="hit counter code" border="0">

    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 310, Column 1: start tag was here
    <img  src="http://sstatic1.histats.com/0.gif?2039668&101" alt="hit counter code…
  • Error Line 334, Column 6: end tag for "iframe" 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 234, Column 1: start tag was here
    <iframe name="flagrasreais" width="300" height="250" marginwidth="0" marginheig…
  • Error Line 361, Column 208: duplicate specification of attribute "rel"
    …"nofollow"  title="Ver todos os posts em UFC" rel="category tag">UFC</a></span>

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

  • Error Line 395, Column 107: duplicate specification of attribute "rel"
    …/ufc-146-ao-vivo/"rel="nofollow"  rel="bookmark" title="UFC 156 &#8211; Ao Viv…

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

  • Error Line 400, Column 57: there is no attribute "fb:like:layout"
    	<a class="addthis_button_facebook_like" fb:like:layout="button_count"></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 402, Column 58: there is no attribute "g:plusone:size"
    	<a class="addthis_button_google_plusone" g:plusone:size="medium"></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 424, Column 226: duplicate specification of attribute "rel"
    …"Ver todos os posts em Futebol 2013" rel="category tag">Futebol 2013</a></span>

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

  • Error Line 437, Column 131: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"
    …width="0" marginheight="0" scrolling="No" width="468" height="60"></iframe></p>

    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 514, Column 112: duplicate specification of attribute "rel"
    …bol-2012-ao-vivo/"rel="nofollow"  rel="bookmark" title="Futebol 2013 &#8211; A…

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

  • Error Line 543, Column 216: duplicate specification of attribute "rel"
    …w"  title="Ver todos os posts em Futebol" rel="category tag">Futebol</a></span>

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

  • Error Line 555, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><a href="http://record.betboopartners.com/_fjNQpVlqHPktlCf1B-F0h2Nd7…

    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 559, Column 116: duplicate specification of attribute "rel"
    …rao-2011-ao-vivo/"rel="nofollow"  rel="bookmark" title="Flamengo x Nova Iguaçu…

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

  • Error Line 588, Column 216: duplicate specification of attribute "rel"
    …w"  title="Ver todos os posts em Futebol" rel="category tag">Futebol</a></span>

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

  • Error Line 601, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><a href="http://record.betboopartners.com/_fjNQpVlqHPktlCf1B-F0h2Nd7…

    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 605, Column 111: duplicate specification of attribute "rel"
    …inthians-ao-vivo/"rel="nofollow"  rel="bookmark" title="Corinthians x Oeste &#…

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

  • Error Line 634, Column 216: duplicate specification of attribute "rel"
    …w"  title="Ver todos os posts em Futebol" rel="category tag">Futebol</a></span>

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

  • Error Line 646, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><br />

    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 650, Column 109: duplicate specification of attribute "rel"
    …ao-paulo-ao-vivo/"rel="nofollow"  rel="bookmark" title="Santos x São Paulo &#8…

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

  • Error Line 679, Column 216: duplicate specification of attribute "rel"
    …w"  title="Ver todos os posts em Futebol" rel="category tag">Futebol</a></span>

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

  • Error Line 690, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><br />

    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 694, Column 108: duplicate specification of attribute "rel"
    …cruzeiro-ao-vivo/"rel="nofollow"  rel="bookmark" title="Atlético-MG x Cruzeiro…

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

  • Error Line 723, Column 216: duplicate specification of attribute "rel"
    …w"  title="Ver todos os posts em Futebol" rel="category tag">Futebol</a></span>

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

  • Error Line 735, Column 11: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><center><br />

    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 739, Column 105: duplicate specification of attribute "rel"
    …vo/inter-ao-vivo/"rel="nofollow"  rel="bookmark" title="Internacional x Grêmio…

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

  • Error Line 768, 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 775, Column 71: non SGML character number 28
    …/politica-de-privacidade"re="nofollow"  title="Política de Privacidade">Polít…

    You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.

    Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.

    This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.

  • Error Line 776, Column 53: non SGML character number 28
    …://aovivoagora.com/sobre"re="nofollow"  title="Saiba mais sobre este site">Qu…

    You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.

    Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.

    This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.

  • Error Line 777, Column 55: non SGML character number 28
    …//aovivoagora.com/contato"re="nofollow"  title="Fale Conosco">Fale Conosco</a>

    You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.

    Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.

    This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.

  • Error Line 780, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>&copy; 2012 <strong>Ao Vivo Agora . com</strong>: Tema desenvolvido e otimiz…

    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 785, Column 6: end tag for "p" 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 772, Column 1: start tag was here
    <p>
  • Error Line 786, 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.

Visitor Analysis

Daily Visitor
  • 12.833 visits