Descarga gratis Peliculas, Animes, Documentales, Series, Programas para PC, Portables y mucho mas en Mediafire, Megaupload y mas. ...

hackstore.net
  • Domain Name
    hackstore.net
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #74392
  • Page Size
    61.1 KB
  • Ip Address
    91.121.178.66
  • Heading
    H1: 1, H2: 0, H3: 5, H4: 0, H5: 0, H6: 0
  • Images
    5 GIF, 0 JPG, 101 PNG

Website Meta Analysis

  • Title
    Hackstore.Net - Descargar Gratis, Peliculas, Anime, Juegos, Musica, Series, Videos Por Mediaifre
  • Meta Keyword
    mediafire,descarga,directa,gratis,descargar,2013,1 link,estreno,2012,identi,mf,mu,documentales,portables,online, anime mp4 mediafire, peliculas mediafire, Series de Tv en Mediafire, descargas, dvdrip, mp3, putlocker,audio latino,mega,mega.co.nz
  • Meta Description
    Descarga gratis Peliculas, Animes, Documentales, Series, Programas para PC, Portables y mucho mas en Mediafire, Megaupload y mas.

Technical Analysis

  • Webserver
    LiteSpeed
  • Ip Address
    91.121.178.66
  • Domain Age
    6 Years, 7 Months, 22 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 28 Feb 2013 18:17:22 GMT
  • server: LiteSpeed
  • connection: close
  • x-powered-by: PHP/5.4.12
  • pragma: no-cache
  • cache-control: private
  • expires: Mon, 26 Jul 1997 05:00:00 GMT
  • last-modified: Thu, 28 Feb 2013 18:17:22 GMT
  • content-type: text/html; charset=ISO-8859-1
  • content-encoding: gzip
  • vary: Accept-Encoding
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for hackstore.net

IP 91.121.178.66 Analysis

  • Country Code
    FR
  • Country Code3
    FRA
  • Country Name
    France
  • City
    EU
  • Continent Code
    46° North
  • Latitude
    2.
  • Longitude
  • No whois ip data for 91.121.178.66

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 57 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.7646221511395441
Message Error
  • Error Line 6, Column 63: required attribute "type" not specified
            <script src="http://connect.facebook.net/es_ES/all.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 70, Column 65: required attribute "type" not specified
    …cript src="http://cf.ads.kontextua.com/container/tags/5450.js"></script></head>

    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 157, Column 28: value of attribute "align" cannot be "absMiddle"; must be one of "top", "middle", "bottom", "left", "right"
    						<img align="absMiddle" src="http://hackstore.net/Themes/stilev1/images/me…

    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 162, Column 28: value of attribute "align" cannot be "absMiddle"; must be one of "top", "middle", "bottom", "left", "right"
    						<img align="absMiddle" src="http://hackstore.net/Themes/stilev1/images/me…

    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 167, Column 28: value of attribute "align" cannot be "absMiddle"; must be one of "top", "middle", "bottom", "left", "right"
    						<img align="absMiddle" src="http://hackstore.net/imagenes/mf.ico" alt="Pe…

    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 172, Column 28: value of attribute "align" cannot be "absMiddle"; must be one of "top", "middle", "bottom", "left", "right"
    						<img align="absMiddle" src="http://hackstore.net/Themes/stilev1/images/me…

    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 177, Column 28: value of attribute "align" cannot be "absMiddle"; must be one of "top", "middle", "bottom", "left", "right"
    						<img align="absMiddle" src="http://hackstore.net/Themes/stilev1/images/me…

    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 182, Column 28: value of attribute "align" cannot be "absMiddle"; must be one of "top", "middle", "bottom", "left", "right"
    						<img align="absMiddle" src="http://hackstore.net/Themes/stilev1/images/me…

    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 191, Column 28: value of attribute "align" cannot be "absMiddle"; must be one of "top", "middle", "bottom", "left", "right"
    						<img align="absMiddle" src="http://hackstore.net/imagenes/mf.ico" alt="Se…

    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 196, Column 30: value of attribute "align" cannot be "absMiddle"; must be one of "top", "middle", "bottom", "left", "right"
    								<img align="absMiddle" src="http://hackstore.net/imagenes/mf.ico" alt="…

    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 650, Column 109: there is no attribute "type"
    …/siteinfo/hackstore.net"><SCRIPT type='text/javascript' language='JavaScript' …

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

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

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

  • Error Line 650, Column 136: there is no attribute "language"
    …CRIPT type='text/javascript' language='JavaScript' src='http://xslt.alexa.com/…

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

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

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

  • Error Line 650, Column 153: there is no attribute "src"
    …javascript' language='JavaScript' src='http://xslt.alexa.com/site_stats/js/t/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 650, Column 212: element "SCRIPT" undefined
    …' src='http://xslt.alexa.com/site_stats/js/t/a?url=hackstore.net'></SCRIPT></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).
  • Error Line 650, Column 225: end tag for element "A" which is not open
    …' src='http://xslt.alexa.com/site_stats/js/t/a?url=hackstore.net'></SCRIPT></A>

    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 652, Column 63: end tag for "img" omitted, but OMITTAG NO was specified
    …re.net/imagenes/url.png" alt="Enlace"> <a title="Werevertumorro" href="http://…

    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 652, Column 1: start tag was here
    <img src="http://hackstore.net/imagenes/url.png" alt="Enlace"> <a title="Wereve…
  • Error Line 652, Column 138: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …vertumorro" href="http://werevertumorro.org" target="_blank">Werevertumorro</a>

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

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

  • Error Line 654, Column 71: end tag for "img" omitted, but OMITTAG NO was specified
    …magenes/url.png" alt="Temas para PSP"> <a title="Temas para PSP" href="http://…

    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 654, Column 1: start tag was here
    <img src="http://hackstore.net/imagenes/url.png" alt="Temas para PSP"> <a title…
  • Error Line 654, Column 145: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …as para PSP" href="http://temasparapsp.com"  target="_blank">Temas para PSP</a>

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

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

  • Error Line 656, Column 63: end tag for "img" omitted, but OMITTAG NO was specified
    …re.net/imagenes/url.png" alt="Enlace"> <a href="http://www.ultimatez.net" targ…

    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 656, Column 1: start tag was here
    <img src="http://hackstore.net/imagenes/url.png" alt="Enlace"> <a href="http://…
  • Error Line 656, Column 114: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …alt="Enlace"> <a href="http://www.ultimatez.net" target="_blank">Foro Anime</a>

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

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

  • Error Line 658, Column 63: end tag for "img" omitted, but OMITTAG NO was specified
    …re.net/imagenes/url.png" alt="Enlace"> <a href="http://libroscompletos.com" ta…

    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 658, Column 1: start tag was here
    <img src="http://hackstore.net/imagenes/url.png" alt="Enlace"> <a href="http://…
  • Error Line 658, Column 116: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …t="Enlace"> <a href="http://libroscompletos.com" target="_blank">Libros PDF</a>

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

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

  • Error Line 660, Column 63: end tag for "img" omitted, but OMITTAG NO was specified
    …re.net/imagenes/url.png" alt="Enlace"> <a title="Tiras Cómicas" href="http://t…

    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 660, Column 1: start tag was here
    <img src="http://hackstore.net/imagenes/url.png" alt="Enlace"> <a title="Tiras …
  • Error Line 660, Column 135: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …Tiras Cómicas" href="http://tirascomicas.net" target="_blank">Tiras Cómicas</a>

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

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

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

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

  • Info Line 650, Column 42: start tag was here
    …					<div style="text-align: center;"><a href="http://www.alexa.com/siteinfo/h…
  • Error Line 701, Column 133: there is no attribute "allowtransparency"
    …0px; height: 60px;" allowtransparency="true" src="http://www.facebook.com/plug…

    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 703, Column 17: there is no attribute "size"
    <g:plusone size="tall" href="http://hackstore.net/"></g:plusone></div>

    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 703, Column 29: there is no attribute "href"
    <g:plusone size="tall" href="http://hackstore.net/"></g:plusone></div>

    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 703, Column 52: element "g:plusone" undefined
    <g:plusone size="tall" href="http://hackstore.net/"></g:plusone></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 729, Column 80: end tag for "img" omitted, but OMITTAG NO was specified
    …et/imagenes/users.png" alt="Usuarios"> Total de Usuarios: <a href="http://hack…

    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 729, Column 14: start tag was here
    									<li><img src="http://hackstore.net/imagenes/users.png" alt="Usuarios">…
  • Error Line 730, Column 83: end tag for "img" omitted, but OMITTAG NO was specified
    …store.net/imagenes/mensajes.png" alt="Mensajes"> Total de Mensajes: 374655</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 730, Column 14: start tag was here
    									<li><img src="http://hackstore.net/imagenes/mensajes.png" alt="Mensaje…
  • Error Line 731, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    …tp://hackstore.net/imagenes/temas.png" alt="Temas"> Total de Temas: 172389</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 731, Column 14: start tag was here
    									<li><img src="http://hackstore.net/imagenes/temas.png" alt="Temas"> To…
  • Error Line 732, Column 87: end tag for "img" omitted, but OMITTAG NO was specified
    …tore.net/imagenes/categorias.png" alt="Categorias"> Total de Categorías: 6</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 732, Column 14: start tag was here
    									<li><img src="http://hackstore.net/imagenes/categorias.png" alt="Categ…
  • Error Line 733, Column 77: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://hackstore.net/imagenes/foros.png" alt="Foros"> Total de Foros: 79</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 733, Column 14: start tag was here
    									<li><img src="http://hackstore.net/imagenes/foros.png" alt="Foros"> To…
  • Error Line 734, Column 94: end tag for "img" omitted, but OMITTAG NO was specified
    …et/imagenes/conectados.png" alt="Maximo Conectados"> Max. Conectados: 2649</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 734, Column 14: start tag was here
    									<li><img src="http://hackstore.net/imagenes/conectados.png" alt="Maxim…
  • Error Line 752, Column 21: there is no attribute "FRAMEBORDER"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=120 HEIGH…

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

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

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

  • Error Line 752, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=120 HEIGH…
  • Error Line 752, Column 35: there is no attribute "MARGINWIDTH"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=120 HEIGH…

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

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

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

  • Error Line 752, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=120 HEIGH…
  • Error Line 752, Column 50: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=120 HEIGHT=600 SRC=…

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

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

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

  • Error Line 752, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=120 HEIGHT=600 SRC=…
  • Error Line 752, Column 62: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=120 HEIGHT=600 SRC="http://ad.y…

    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 752, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=120 HEIGHT=600 SRC="http://ad.y…
  • Error Line 752, Column 71: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=120 HEIGHT=600 SRC="http://ad.yieldmanag…

    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 752, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=120 HEIGHT=600 SRC="http://ad.yieldmanag…
  • Error Line 752, Column 82: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=120 HEIGHT=600 SRC="http://ad.yieldmanager.com/st?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 752, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=120 HEIGHT=600 SRC="http://ad.yieldmanager.com/st?a…
  • Error Line 752, Column 90: there is no attribute "SRC"
    …SCROLLING=NO WIDTH=120 HEIGHT=600 SRC="http://ad.yieldmanager.com/st?ad_type=i…

    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 752, Column 136: cannot generate system identifier for general entity "ad_size"
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=…

    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 752, Column 136: general entity "ad_size" not defined and no default entity
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=…

    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 752, Column 143: reference not terminated by REFC delimiter
    …dmanager.com/st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_U…

    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 752, Column 143: reference to external entity in attribute value
    …dmanager.com/st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_U…

    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 752, Column 143: reference to entity "ad_size" for which no system identifier could be generated
    …dmanager.com/st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_U…

    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 752, Column 135: entity was defined here
    …/ad.yieldmanager.com/st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url…
  • Warning Line 752, Column 152: cannot generate system identifier for general entity "section"
    …com/st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></IF…

    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 752, Column 152: general entity "section" not defined and no default entity
    …com/st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></IF…

    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 752, Column 159: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></IFRAME>

    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 752, Column 159: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></IFRAME>

    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 752, Column 159: reference to entity "section" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></IFRAME>

    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 752, Column 151: entity was defined here
    ….com/st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></I…
  • Warning Line 752, Column 168: cannot generate system identifier for general entity "pub_url"
    …st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></IFRAME>

    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 752, Column 168: general entity "pub_url" not defined and no default entity
    …st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></IFRAME>

    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 752, Column 175: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></IFRAME>

    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 752, Column 175: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></IFRAME>

    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 752, Column 175: reference to entity "pub_url" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></IFRAME>

    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 752, Column 167: entity was defined here
    …st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 752, Column 187: element "IFRAME" undefined
    …st?ad_type=iframe&ad_size=120x600&section=3488325&pub_url=${PUB_URL}"></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 791, Column 19: end tag for element "div" which is not open
    	</div></div></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
  • 817 visits
Daily Visitor