vtotvonline.tv

vtotvonline.tv has Alexa Rank 615.372 and Google Page Rank is 4

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    vtotvonline.tv
  • Favicon
  • Alexa Rank
    #615372
  • Google Page Rank
    PR 4
  • Ip Address
    141.101.118.179
  • Page Size
    32.4 KB
  • Images
    0 GIF, 8 JPG, 7 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 2 1 0 0 0

Technical Analysis



  • Webserver
    cloudflare-nginx
  • Ip Address
    141.101.118.179
  • Domain Age
    1 Years, 0 Months, 23 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: cloudflare-nginx
  • date: Mon, 05 Aug 2013 00:05:41 GMT
  • content-type: text/html
  • connection: keep-alive
  • vary: Accept-Encoding
  • last-modified: Sun, 04 Aug 2013 20:29:29 GMT
  • x-cache: HIT from Backend
  • cf-ray: 98f3cb1e32605a3
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
The data contained in GoDaddy.com, LLC's WhoIs database,
while believed by the company to be reliable, is provided "as is"
with no guarantee or warranties regarding its accuracy. This
information is provided for the sole purpose of assisting you
in obtaining information about domain name registration records.
Any use of this data for any other purpose is expressly forbidden without the prior written
permission of GoDaddy.com, LLC. By submitting an inquiry,
you agree to these terms of usage and limitations of warranty. In particular,
you agree not to use this data to allow, enable, or otherwise make possible,
dissemination or collection of this data, in part or in its entirety, for any
purpose, such as the transmission of unsolicited advertising and
and solicitations of any kind, including spam. You further agree
not to use this data to enable high volume, automated or robotic electronic
processes designed to collect or compile this data for any purpose,
including mining this data for your own personal or commercial purposes.

Please note: the registrant of the domain name is specified
in the "registrant" field. In most cases, GoDaddy.com, LLC
is not the registrant of domain names listed in this database.


Registered through: GoDaddy.com, LLC (http://www.godaddy.com)
Domain Name: VTOTVONLINE.TV
Created on: 17-Jul-12
Expires on: 17-Jul-13
Last Updated on: 17-Jul-12

Registrant:
carlos perreira
calle americo vezpucio 32 3.9
las palmas, Madrid 28004
Spain

Administrative Contact:
perreira, carlos email
calle americo vezpucio 32 3.9
las palmas, Madrid 28004
Spain
0034680143964

Technical Contact:
perreira, carlos email
calle americo vezpucio 32 3.9
las palmas, Madrid 28004
Spain
0034680143964

Domain servers in listed order:
PAM.NS.CLOUDFLARE.COM
WOZ.NS.CLOUDFLARE.COM

DNS Analysis


DNS servers
woz.ns.cloudflare.com [173.245.59.150]
pam.ns.cloudflare.com [173.245.58.138]


DNS Records

Answer records
vtotvonline.tv A 108.162.205.79 300s
vtotvonline.tv SOA
server: pam.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2013011021
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s
vtotvonline.tv NS  woz.ns.cloudflare.com 86400s
vtotvonline.tv NS  pam.ns.cloudflare.com 86400s
vtotvonline.tv A 108.162.206.79 300s

Authority records

Additional records

IP 141.101.118.179 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 40 Errors
  • 17 Warnings
Ratio Text/Html
  • 0.7131974345849267
Message Error
  • Error Line 5, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta http-equiv=content-type content="text/html;charset=UTF-8"/>
  • Error Line 6, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=verifyownership content=a7e0bfb6fcaca595e1987da1d05d9632 />
  • Error Line 6, Column 36: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=verifyownership content=a7e0bfb6fcaca595e1987da1d05d9632 />
  • Error Line 8, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=description content="Ver Tv Online VTO é o melhor site para assistir…
  • Error Line 8, Column 188: end tag for "meta" omitted, but OMITTAG NO was specified
    …cord, SBT, BBB 13, Fox Sports, Cartoon, Filmes Online, Chaves, Novelas, Espn.">

    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 8, Column 1: start tag was here
    <meta name=description content="Ver Tv Online VTO é o melhor site para assistir…
  • Error Line 9, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=keywords content="Tv Online, Futebol ao vivo, tv de graça, vertv, tv…
  • Error Line 9, Column 630: end tag for "meta" omitted, but OMITTAG NO was specified
    …pa do mundo, copa do mundo ao vivo, sbt ao vivo, record ao vio, vtotv, BBB 13">

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

  • Info Line 9, Column 1: start tag was here
    <meta name=keywords content="Tv Online, Futebol ao vivo, tv de graça, vertv, tv…
  • Error Line 10, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=copyright content="ZoozInternet - 2013">
  • Error Line 10, Column 52: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name=copyright content="ZoozInternet - 2013">

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

  • Info Line 10, Column 1: start tag was here
    <meta name=copyright content="ZoozInternet - 2013">
  • Error Line 11, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=author content="Ricardo Mariano">
  • Error Line 11, Column 45: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name=author content="Ricardo Mariano">

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

  • Info Line 11, Column 1: start tag was here
    <meta name=author content="Ricardo Mariano">
  • Error Line 12, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=email content="rickandana@hotmail.com">
  • Error Line 12, Column 51: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name=email content="rickandana@hotmail.com">

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

  • Info Line 12, Column 1: start tag was here
    <meta name=email content="rickandana@hotmail.com">
  • Error Line 13, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=Charset content=ISO-8859-1>
  • Error Line 13, Column 28: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=Charset content=ISO-8859-1>
  • Error Line 13, Column 39: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name=Charset content=ISO-8859-1>

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

  • Info Line 13, Column 1: start tag was here
    <meta name=Charset content=ISO-8859-1>
  • Error Line 14, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=Distribution content=Global>
  • Error Line 14, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=Distribution content=Global>
  • Error Line 14, Column 40: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name=Distribution content=Global>

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

  • Info Line 14, Column 1: start tag was here
    <meta name=Distribution content=Global>
  • Error Line 15, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=Rating content=General>
  • Error Line 15, Column 27: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=Rating content=General>
  • Error Line 15, Column 35: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name=Rating content=General>

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

  • Info Line 15, Column 1: start tag was here
    <meta name=Rating content=General>
  • Error Line 16, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=Robots content="INDEX,FOLLOW">
  • Error Line 16, Column 42: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name=Robots content="INDEX,FOLLOW">

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

  • Info Line 16, Column 1: start tag was here
    <meta name=Robots content="INDEX,FOLLOW">
  • Error Line 17, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <meta name=Revisit-after content="1 Day">
  • Error Line 17, Column 42: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name=Revisit-after content="1 Day">

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

  • Info Line 17, Column 1: start tag was here
    <meta name=Revisit-after content="1 Day">
  • Error Line 20, Column 78: required attribute "type" not specified
    …src="http://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js"></script>

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

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

  • Error Line 28, Column 8: required attribute "type" not specified
    <script>if(top.location!=self.location){top.location=self.location.href}</scrip…

    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 29, Column 8: required attribute "type" not specified
    <script>function abrir(URL){var width=730;var height=650;var left=240;var top=6…

    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 67, Column 24: end tag for element "li" which is not open
    <li class="empty"/></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.

  • Warning Line 69, Column 79: cannot generate system identifier for general entity "H"
    …/ch46-discheh.htm" title="Discovery H&H" target="Player"><img src="icones/hh.p…

    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 69, Column 79: general entity "H" not defined and no default entity
    …/ch46-discheh.htm" title="Discovery H&H" target="Player"><img src="icones/hh.p…

    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 69, Column 80: reference not terminated by REFC delimiter
    …ch46-discheh.htm" title="Discovery H&H" target="Player"><img src="icones/hh.pn…

    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 69, Column 80: reference to external entity in attribute value
    …ch46-discheh.htm" title="Discovery H&H" target="Player"><img src="icones/hh.pn…

    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 69, Column 80: reference to entity "H" for which no system identifier could be generated
    …ch46-discheh.htm" title="Discovery H&H" target="Player"><img src="icones/hh.pn…

    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 69, Column 78: entity was defined here
    …s/ch46-discheh.htm" title="Discovery H&H" target="Player"><img src="icones/hh.…
  • Warning Line 69, Column 131: reference not terminated by REFC delimiter
    …yer"><img src="icones/hh.png" alt="H&H ao vivo" width="70" height="50"/></a></…

    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 69, Column 131: reference to external entity in attribute value
    …yer"><img src="icones/hh.png" alt="H&H ao vivo" width="70" height="50"/></a></…

    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 69, Column 131: reference to entity "H" for which no system identifier could be generated
    …yer"><img src="icones/hh.png" alt="H&H ao vivo" width="70" height="50"/></a></…

    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 69, Column 78: entity was defined here
    …s/ch46-discheh.htm" title="Discovery H&H" target="Player"><img src="icones/hh.…
  • Error Line 80, Column 24: end tag for element "li" which is not open
    <li class="empty"/></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 93, Column 24: end tag for element "li" which is not open
    <li class="empty"/></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.

  • Warning Line 105, Column 72: cannot generate system identifier for general entity "nome"
    …/players/justin.php?canal=pedro_ozzy3&nome=CHAPOLIN" title="Chapolin" target="…

    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 105, Column 72: general entity "nome" not defined and no default entity
    …/players/justin.php?canal=pedro_ozzy3&nome=CHAPOLIN" title="Chapolin" target="…

    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 105, Column 76: reference not terminated by REFC delimiter
    …yers/justin.php?canal=pedro_ozzy3&nome=CHAPOLIN" title="Chapolin" target="Play…

    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 105, Column 76: reference to external entity in attribute value
    …yers/justin.php?canal=pedro_ozzy3&nome=CHAPOLIN" title="Chapolin" target="Play…

    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 105, Column 76: reference to entity "nome" for which no system identifier could be generated
    …yers/justin.php?canal=pedro_ozzy3&nome=CHAPOLIN" title="Chapolin" target="Play…

    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 105, Column 71: entity was defined here
    …v/players/justin.php?canal=pedro_ozzy3&nome=CHAPOLIN" title="Chapolin" target=…
  • Error Line 106, Column 24: end tag for element "li" which is not open
    <li class="empty"/></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 119, Column 24: end tag for element "li" which is not open
    <li class="empty"/></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.

  • Warning Line 120, Column 65: character "&" is the first character of a delimiter but occurred as data
    ….vto.tv/canais/kenan.html" title="Ken & Kel" target="Player"><img src="images/…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 120, Column 127: character "&" is the first character of a delimiter but occurred as data
    …img src="images/kenan.jpg" alt="Kenan & kel ao vivo" width="70" height="50"/><…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 121, Column 67: character "&" is the first character of a delimiter but occurred as data
    …to.tv/canais/drack.html" title="Drack & Josh" target="Player"><img src="images…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 121, Column 130: character "&" is the first character of a delimiter but occurred as data
    …img src="images/drack.jpg" alt="Drack & Josh ao vivo" width="70" height="50"/>…

    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 132, Column 24: end tag for element "li" which is not open
    <li class="empty"/></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.

  • Warning Line 138, Column 73: cannot generate system identifier for general entity "E"
    …players/master.php?canal=ae" title="A&E" target="Player"><img src="images/ae.j…

    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 138, Column 73: general entity "E" not defined and no default entity
    …players/master.php?canal=ae" title="A&E" target="Player"><img src="images/ae.j…

    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 138, Column 74: reference not terminated by REFC delimiter
    …layers/master.php?canal=ae" title="A&E" target="Player"><img src="images/ae.jp…

    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 138, Column 74: reference to external entity in attribute value
    …layers/master.php?canal=ae" title="A&E" target="Player"><img src="images/ae.jp…

    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 138, Column 74: reference to entity "E" for which no system identifier could be generated
    …layers/master.php?canal=ae" title="A&E" target="Player"><img src="images/ae.jp…

    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 138, Column 72: entity was defined here
    …/players/master.php?canal=ae" title="A&E" target="Player"><img src="images/ae.…
  • Warning Line 138, Column 125: reference not terminated by REFC delimiter
    …yer"><img src="images/ae.jpg" alt="A&E ao vivo" width="70" height="50"/></a></…

    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 138, Column 125: reference to external entity in attribute value
    …yer"><img src="images/ae.jpg" alt="A&E ao vivo" width="70" height="50"/></a></…

    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 138, Column 125: reference to entity "E" for which no system identifier could be generated
    …yer"><img src="images/ae.jpg" alt="A&E ao vivo" width="70" height="50"/></a></…

    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 138, Column 72: entity was defined here
    …/players/master.php?canal=ae" title="A&E" target="Player"><img src="images/ae.…
  • Error Line 145, Column 24: end tag for element "li" which is not open
    <li class="empty"/></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 158, Column 24: end tag for element "li" which is not open
    <li class="empty"/></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 169, Column 46: value of attribute "scrolling" cannot be "No"; must be one of "yes", "no", "auto"
    … id="Player" width="468" scrolling="No" height="386" frameborder="0" src="meio…

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

  • Warning Line 185, Column 78: cannot generate system identifier for general entity "rnd"
    …g.net/ei/3/f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="…

    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 185, Column 78: general entity "rnd" not defined and no default entity
    …g.net/ei/3/f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="…

    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 185, Column 81: reference not terminated by REFC delimiter
    …et/ei/3/f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_bl…

    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 185, Column 81: reference to external entity in attribute value
    …et/ei/3/f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_bl…

    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 185, Column 81: reference to entity "rnd" for which no system identifier could be generated
    …et/ei/3/f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_bl…

    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 185, Column 77: entity was defined here
    …ng.net/ei/3/f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target=…
  • Warning Line 185, Column 90: cannot generate system identifier for general entity "p"
    …188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_blank"><img…

    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 185, Column 90: general entity "p" not defined and no default entity
    …188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_blank"><img…

    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 185, Column 91: reference not terminated by REFC delimiter
    …88/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_blank"><img …

    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 185, Column 91: reference to external entity in attribute value
    …88/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_blank"><img …

    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 185, Column 91: reference to entity "p" for which no system identifier could be generated
    …88/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_blank"><img …

    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 185, Column 89: entity was defined here
    …f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_blank"><im…
  • Warning Line 185, Column 244: reference not terminated by REFC delimiter
    …net/eb/3/f188/e8bb907fbe2485ca?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></…

    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 185, Column 244: reference to external entity in attribute value
    …net/eb/3/f188/e8bb907fbe2485ca?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></…

    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 185, Column 244: reference to entity "rnd" for which no system identifier could be generated
    …net/eb/3/f188/e8bb907fbe2485ca?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></…

    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 185, Column 77: entity was defined here
    …ng.net/ei/3/f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target=…
  • Warning Line 185, Column 254: reference not terminated by REFC delimiter
    …188/e8bb907fbe2485ca?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></a></noscri…

    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 185, Column 254: reference to external entity in attribute value
    …188/e8bb907fbe2485ca?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></a></noscri…

    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 185, Column 254: reference to entity "p" for which no system identifier could be generated
    …188/e8bb907fbe2485ca?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></a></noscri…

    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 185, Column 89: entity was defined here
    …f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_blank"><im…
  • Error Line 185, Column 280: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …8/e8bb907fbe2485ca?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></a></noscript>
  • Error Line 185, Column 285: end tag for "img" omitted, but OMITTAG NO was specified
    …8/e8bb907fbe2485ca?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></a></noscript>

    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 185, Column 126: start tag was here
    …M&p=570fa19b4a48607d" target="_blank"><img width="468" height="60" alt="e-plan…
  • Error Line 191, Column 12: there is no attribute "src"
    <embed src="http://www.xatech.com/web_gear/chat/chat.swf" quality="'high" width…

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

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

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

  • Error Line 191, Column 67: there is no attribute "quality"
    …h.com/web_gear/chat/chat.swf" quality="'high" width="529" height="428" name="c…

    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 191, Column 81: there is no attribute "width"
    …/chat/chat.swf" quality="'high" width="529" height="428" name="chat" flashvars…

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

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

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

  • Error Line 191, Column 94: there is no attribute "height"
    …f" quality="'high" width="529" height="428" name="chat" flashvars="id=18662526…

    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 191, Column 105: there is no attribute "name"
    …"'high" width="529" height="428" name="chat" flashvars="id=186625263&rl=Brazil…

    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 191, Column 122: there is no attribute "flashvars"
    …9" height="428" name="chat" flashvars="id=186625263&rl=Brazilian" align="middl…

    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 191, Column 136: cannot generate system identifier for general entity "rl"
    …" name="chat" flashvars="id=186625263&rl=Brazilian" align="middle" allowscript…

    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 191, Column 136: general entity "rl" not defined and no default entity
    …" name="chat" flashvars="id=186625263&rl=Brazilian" align="middle" allowscript…

    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 191, Column 138: reference not terminated by REFC delimiter
    …name="chat" flashvars="id=186625263&rl=Brazilian" align="middle" allowscriptac…

    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 191, Column 138: reference to external entity in attribute value
    …name="chat" flashvars="id=186625263&rl=Brazilian" align="middle" allowscriptac…

    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 191, Column 138: reference to entity "rl" for which no system identifier could be generated
    …name="chat" flashvars="id=186625263&rl=Brazilian" align="middle" allowscriptac…

    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 191, Column 135: entity was defined here
    …8" name="chat" flashvars="id=186625263&rl=Brazilian" align="middle" allowscrip…
  • Error Line 191, Column 156: there is no attribute "align"
    …ars="id=186625263&rl=Brazilian" align="middle" allowscriptaccess="sameDomain" …

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

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

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

  • Error Line 191, Column 183: there is no attribute "allowscriptaccess"
    …ian" align="middle" allowscriptaccess="sameDomain" wmode="transparent" type="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 191, Column 202: there is no attribute "wmode"
    … allowscriptaccess="sameDomain" wmode="transparent" type="application/x-shockw…

    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 191, Column 221: there is no attribute "type"
    …"sameDomain" wmode="transparent" type="application/x-shockwave-flash" pluginsp…

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

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

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

  • Error Line 191, Column 265: there is no attribute "pluginspage"
    …pplication/x-shockwave-flash" pluginspage="http://xat.com/update_flash.shtml"/>

    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 191, Column 301: element "embed" undefined
    …pplication/x-shockwave-flash" pluginspage="http://xat.com/update_flash.shtml"/>

    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 192, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

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

  • Info Line 192, Column 1: start tag was here
    <br>
  • Error Line 216, Column 69: required attribute "type" not specified
    <script charset="utf-8" src="http://widgets.twimg.com/j/2/widget.js"></script>

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

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

  • Error Line 217, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 286, Column 145: there is no attribute "mce_src"
    …http://i.imgur.com/uDJDK.png" mce_src="banner_morgadao/125x125.jpg" border="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.

  • Warning Line 288, Column 83: cannot generate system identifier for general entity "utm_medium"
    …ttp://www.de-amor.net/?utm_source=VTO&utm_medium=banner_125x125&utm_campaign=m…

    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 288, Column 83: general entity "utm_medium" not defined and no default entity
    …ttp://www.de-amor.net/?utm_source=VTO&utm_medium=banner_125x125&utm_campaign=m…

    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 288, Column 93: reference not terminated by REFC delimiter
    …de-amor.net/?utm_source=VTO&utm_medium=banner_125x125&utm_campaign=midia" targ…

    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 288, Column 93: reference to external entity in attribute value
    …de-amor.net/?utm_source=VTO&utm_medium=banner_125x125&utm_campaign=midia" targ…

    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 288, Column 93: reference to entity "utm_medium" for which no system identifier could be generated
    …de-amor.net/?utm_source=VTO&utm_medium=banner_125x125&utm_campaign=midia" targ…

    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 288, Column 82: entity was defined here
    …http://www.de-amor.net/?utm_source=VTO&utm_medium=banner_125x125&utm_campaign=…
  • Warning Line 288, Column 109: cannot generate system identifier for general entity "utm_campaign"
    …_source=VTO&utm_medium=banner_125x125&utm_campaign=midia" target="_blank"><img…

    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 288, Column 109: general entity "utm_campaign" not defined and no default entity
    …_source=VTO&utm_medium=banner_125x125&utm_campaign=midia" target="_blank"><img…

    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 288, Column 121: reference not terminated by REFC delimiter
    …utm_medium=banner_125x125&utm_campaign=midia" target="_blank"><img src="http:/…

    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 288, Column 121: reference to external entity in attribute value
    …utm_medium=banner_125x125&utm_campaign=midia" target="_blank"><img src="http:/…

    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 288, Column 121: reference to entity "utm_campaign" for which no system identifier could be generated
    …utm_medium=banner_125x125&utm_campaign=midia" target="_blank"><img src="http:/…

    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 288, Column 108: entity was defined here
    …m_source=VTO&utm_medium=banner_125x125&utm_campaign=midia" target="_blank"><im…
  • Warning Line 449, Column 81: reference not terminated by REFC delimiter
    …et/ei/3/f188/11e675b91cfc9b21?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_bl…

    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 449, Column 81: reference to external entity in attribute value
    …et/ei/3/f188/11e675b91cfc9b21?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_bl…

    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 449, Column 81: reference to entity "rnd" for which no system identifier could be generated
    …et/ei/3/f188/11e675b91cfc9b21?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_bl…

    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 185, Column 77: entity was defined here
    …ng.net/ei/3/f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target=…
  • Warning Line 449, Column 91: reference not terminated by REFC delimiter
    …88/11e675b91cfc9b21?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_blank"><img …

    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 449, Column 91: reference to external entity in attribute value
    …88/11e675b91cfc9b21?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_blank"><img …

    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 449, Column 91: reference to entity "p" for which no system identifier could be generated
    …88/11e675b91cfc9b21?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_blank"><img …

    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 185, Column 89: entity was defined here
    …f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_blank"><im…
  • Warning Line 449, Column 245: reference not terminated by REFC delimiter
    …net/eb/3/f188/11e675b91cfc9b21?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></…

    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 449, Column 245: reference to external entity in attribute value
    …net/eb/3/f188/11e675b91cfc9b21?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></…

    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 449, Column 245: reference to entity "rnd" for which no system identifier could be generated
    …net/eb/3/f188/11e675b91cfc9b21?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></…

    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 185, Column 77: entity was defined here
    …ng.net/ei/3/f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target=…
  • Warning Line 449, Column 255: reference not terminated by REFC delimiter
    …188/11e675b91cfc9b21?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></a></noscri…

    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 449, Column 255: reference to external entity in attribute value
    …188/11e675b91cfc9b21?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></a></noscri…

    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 449, Column 255: reference to entity "p" for which no system identifier could be generated
    …188/11e675b91cfc9b21?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></a></noscri…

    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 185, Column 89: entity was defined here
    …f188/e8bb907fbe2485ca?it=i&rnd=$RANDOM&p=570fa19b4a48607d" target="_blank"><im…
  • Error Line 449, Column 281: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …8/11e675b91cfc9b21?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></a></noscript>
  • Error Line 449, Column 286: end tag for "img" omitted, but OMITTAG NO was specified
    …8/11e675b91cfc9b21?o=i&rnd=$RANDOM&p=570fa19b4a48607d" border=0></a></noscript>

    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 449, Column 126: start tag was here
    …M&p=570fa19b4a48607d" target="_blank"><img width="300" height="250" alt="e-pla…
  • Warning Line 468, Column 111: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?2007671&101" alt="contador de visitas gratis" b…

    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 468, Column 164: end tag for "img" omitted, but OMITTAG NO was specified
    …/0.gif?2007671&101" alt="contador de visitas gratis" border="0"></a></noscript>

    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 468, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img src="http://sstatic1.histats.com/0.…
  • Warning Line 470, Column 64: cannot generate system identifier for general entity "cor"
    …pt src="http://ads42120.hotwords.com.br/show.jsp?id=42120&cor=005F00"></script>

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

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

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

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

  • Error Line 470, Column 64: general entity "cor" not defined and no default entity
    …pt src="http://ads42120.hotwords.com.br/show.jsp?id=42120&cor=005F00"></script>

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

  • Warning Line 470, Column 67: reference not terminated by REFC delimiter
    …pt src="http://ads42120.hotwords.com.br/show.jsp?id=42120&cor=005F00"></script>

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

  • Warning Line 470, Column 67: reference to external entity in attribute value
    …pt src="http://ads42120.hotwords.com.br/show.jsp?id=42120&cor=005F00"></script>

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

  • Error Line 470, Column 67: reference to entity "cor" for which no system identifier could be generated
    …pt src="http://ads42120.hotwords.com.br/show.jsp?id=42120&cor=005F00"></script>

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

  • Info Line 470, Column 63: entity was defined here
    …pt src="http://ads42120.hotwords.com.br/show.jsp?id=42120&cor=005F00"></script>
  • Error Line 470, Column 75: required attribute "type" not specified
    …pt src="http://ads42120.hotwords.com.br/show.jsp?id=42120&cor=005F00"></script>

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

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

Visitor Analysis

Daily Visitor
  • 175 visits

In Page Analysis