The most extreme and crazy videos you've ever seen. Updated daily with the most hardcore content from all around the web! ...

mentalzero.com
  • Domain Name
    mentalzero.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #25771
  • Page Size
    1.1 KB
  • Ip Address
    208.71.128.21
  • Heading
    H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Extreme Videos & Entertainment from MentalZero
  • Meta Keyword
    keywords
  • Meta Description
    The most extreme and crazy videos you've ever seen. Updated daily with the most hardcore content from all around the web!

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    208.71.128.21
  • Domain Age
    3 Years, 12 Months, 16 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache
  • x-powered-by: PHP/5.4.7
  • content-type: text/html
  • content-length: 1104
  • accept-ranges: bytes
  • date: Tue, 16 Sep 2014 06:50:19 GMT
  • x-varnish: 604310866 604310773
  • age: 59
  • via: 1.1 varnish
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
Domain Name: MENTALZERO.COM
Created on: 09-Sep-09
Expires on: 09-Sep-13
Last Updated on: 08-Sep-11

Registrant:
Elena Paraskeva
PO BOX 30088
Ayia Napa, Famagusta 5340
Cyprus

Administrative Contact:
Paraskeva, Elena email
PO BOX 30088
Ayia Napa, Famagusta 5340
Cyprus
+0.1135799322392

Technical Contact:
Paraskeva, Elena email
PO BOX 30088
Ayia Napa, Famagusta 5340
Cyprus
+0.1135799322392

Domain servers in listed order:
NS1.TECHIEMEDIA.NET
NS2.TECHIEMEDIA.NET

DNS Analysis


DNS servers
ns1.techiemedia.net [208.90.152.52]
ns2.techiemedia.net [208.71.131.77]


DNS Records

Answer records
mentalzero.com SOA
server: ns1.techiemedia.net
email: hostmaster@techiemedia.com
serial: 2011090107
refresh: 3600
retry: 900
expire: 3600000
minimum ttl: 3600
14400s
mentalzero.com A 208.71.128.21 14400s
mentalzero.com MX
preference: 10
exchange: mail.techiemedia.net
14400s
mentalzero.com NS  ns2.techiemedia.net 14400s
mentalzero.com NS  ns1.techiemedia.net 14400s

Authority records

Additional records
mail.techiemedia.net A 208.71.131.82 3600s
ns1.techiemedia.net A 208.90.152.52 3600s
ns2.techiemedia.net A 208.71.131.77 3600s

IP 208.71.128.21 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Newark
  • Continent Code
    07102
  • Latitude
    973
  • Longitude
    501
  • No whois ip data for 208.71.128.21

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 71 Errors
  • 17 Warnings
Ratio Text/Html
  • 0.5773101555352241
Message Error
  • Error Line 11, Column 120: end tag for "link" omitted, but OMITTAG NO was specified
    …m/css?family=Open+Sans:400,600,700,600italic" rel="stylesheet" type="text/css">

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

  • Info Line 11, Column 3: start tag was here
      <link href="http://fonts.googleapis.com/css?family=Open+Sans:400,600,700,600i…
  • Warning Line 28, Column 127: cannot generate system identifier for general entity "o"
    …newsfilter.org/network_click.php?i=nf&o=nf'; return false;" id="network_newsfi…

    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 28, Column 127: general entity "o" not defined and no default entity
    …newsfilter.org/network_click.php?i=nf&o=nf'; return false;" id="network_newsfi…

    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 28, Column 128: reference not terminated by REFC delimiter
    …ewsfilter.org/network_click.php?i=nf&o=nf'; return false;" id="network_newsfil…

    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 28, Column 128: reference to external entity in attribute value
    …ewsfilter.org/network_click.php?i=nf&o=nf'; return false;" id="network_newsfil…

    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 28, Column 128: reference to entity "o" for which no system identifier could be generated
    …ewsfilter.org/network_click.php?i=nf&o=nf'; return false;" id="network_newsfil…

    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 28, Column 126: entity was defined here
    ….newsfilter.org/network_click.php?i=nf&o=nf'; return false;" id="network_newsf…
  • Error Line 28, Column 177: there is no attribute "alt"
    …n false;" id="network_newsfilter" alt="Free Porn Videos" title="Free Porn Vide…

    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 29, Column 128: reference not terminated by REFC delimiter
    …ewsfilter.org/network_click.php?i=nf&o=mz'; return false;" id="network_mentalz…

    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 29, Column 128: reference to external entity in attribute value
    …ewsfilter.org/network_click.php?i=nf&o=mz'; return false;" id="network_mentalz…

    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 29, Column 128: reference to entity "o" for which no system identifier could be generated
    …ewsfilter.org/network_click.php?i=nf&o=mz'; return false;" id="network_mentalz…

    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 28, Column 126: entity was defined here
    ….newsfilter.org/network_click.php?i=nf&o=nf'; return false;" id="network_newsf…
  • Warning Line 30, Column 129: reference not terminated by REFC delimiter
    …ewsfilter.org/network_click.php?i=nf&o=ef'; return false;" id="network_extreme…

    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 30, Column 129: reference to external entity in attribute value
    …ewsfilter.org/network_click.php?i=nf&o=ef'; return false;" id="network_extreme…

    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 30, Column 129: reference to entity "o" for which no system identifier could be generated
    …ewsfilter.org/network_click.php?i=nf&o=ef'; return false;" id="network_extreme…

    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 28, Column 126: entity was defined here
    ….newsfilter.org/network_click.php?i=nf&o=nf'; return false;" id="network_newsf…
  • Warning Line 31, Column 121: reference not terminated by REFC delimiter
    …ewsfilter.org/network_click.php?i=nf&o=m9'; return false;" id="network_m90" al…

    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 31, Column 121: reference to external entity in attribute value
    …ewsfilter.org/network_click.php?i=nf&o=m9'; return false;" id="network_m90" al…

    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 31, Column 121: reference to entity "o" for which no system identifier could be generated
    …ewsfilter.org/network_click.php?i=nf&o=m9'; return false;" id="network_m90" al…

    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 28, Column 126: entity was defined here
    ….newsfilter.org/network_click.php?i=nf&o=nf'; return false;" id="network_newsf…
  • Error Line 36, Column 24: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    					<form method="POST" action="/members.php?action=login">

    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 38, Column 38: there is no attribute "placeholder"
    						<input type="text" placeholder="Username" class="text" name="username" />

    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 38, Column 79: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    						<input type="text" placeholder="Username" class="text" name="username" />

    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 39, Column 79: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    						<input type="password" placeholder="Password" class="text" name="pass" />

    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 40, Column 56: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    						<input type="submit" value="LOGIN" class="submit">

    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 40, Column 57: end tag for "input" omitted, but OMITTAG NO was specified
    						<input type="submit" value="LOGIN" class="submit">

    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 40, Column 7: start tag was here
    						<input type="submit" value="LOGIN" class="submit">
  • Error Line 67, Column 144: end tag for "input" omitted, but OMITTAG NO was specified
    …lass="text" name="search" /><input type="submit" value="Search" class="submit">

    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 67, Column 93: start tag was here
    … VIDEOS" class="text" name="search" /><input type="submit" value="Search" clas…
  • Error Line 86, Column 43: there is no attribute "target"
    …<a href="/refererout.php?id=8" target="_blank" rel="nofollow">theync.com</a></…

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

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

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

  • Error Line 139, Column 23: there is no attribute "campaign"
    	<pmd:search campaign="newsfilter-search"></pmd:search>

    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 139, Column 42: element "pmd:search" undefined
    	<pmd:search campaign="newsfilter-search"></pmd:search>

    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 700, Column 10: there is no attribute "align"
    <p align="center" style="padding:10px"></p>				<div class="clear"></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 704, Column 27: there is no attribute "align"
    				<div class="ad" align="center"><iframe id="BR_adbucks_880" title="BR_adbuck…

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

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

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

  • Error Line 704, Column 47: there is no attribute "id"
    … class="ad" align="center"><iframe id="BR_adbucks_880" title="BR_adbucks_880" …

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

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

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

  • Error Line 704, Column 70: there is no attribute "title"
    …er"><iframe id="BR_adbucks_880" title="BR_adbucks_880" width="300" scrolling="…

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

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

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

  • Error Line 704, Column 93: there is no attribute "width"
    …cks_880" title="BR_adbucks_880" width="300" scrolling="no" height="250" frameb…

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

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

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

  • Error Line 704, Column 109: there is no attribute "scrolling"
    …BR_adbucks_880" width="300" scrolling="no" height="250" frameborder="0" allowt…

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

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

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

  • Error Line 704, Column 121: there is no attribute "height"
    …80" width="300" scrolling="no" height="250" frameborder="0" allowtransparency=…

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

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

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

  • Error Line 704, Column 139: there is no attribute "frameborder"
    …rolling="no" height="250" frameborder="0" allowtransparency="true" marginheigh…

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

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

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

  • Error Line 704, Column 161: there is no attribute "allowtransparency"
    …50" frameborder="0" allowtransparency="true" marginheight="0" marginwidth="0" …

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

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

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

  • Error Line 704, Column 181: there is no attribute "marginheight"
    …allowtransparency="true" marginheight="0" marginwidth="0" src="http://adbucks.…

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

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

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

  • Error Line 704, Column 197: there is no attribute "marginwidth"
    …y="true" marginheight="0" marginwidth="0" src="http://adbucks.brandreachsys.co…

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

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

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

  • Error Line 704, Column 205: there is no attribute "src"
    … marginheight="0" marginwidth="0" src="http://adbucks.brandreachsys.com/www/de…

    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 704, Column 272: cannot generate system identifier for general entity "loc"
    …hsys.com/www/delivery/amz.php?zoneids=880&loc={encodedtargetingdata}"></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 704, Column 272: general entity "loc" not defined and no default entity
    …hsys.com/www/delivery/amz.php?zoneids=880&loc={encodedtargetingdata}"></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 704, Column 275: reference not terminated by REFC delimiter
    …hsys.com/www/delivery/amz.php?zoneids=880&loc={encodedtargetingdata}"></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 704, Column 275: reference to external entity in attribute value
    …hsys.com/www/delivery/amz.php?zoneids=880&loc={encodedtargetingdata}"></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 704, Column 275: reference to entity "loc" for which no system identifier could be generated
    …hsys.com/www/delivery/amz.php?zoneids=880&loc={encodedtargetingdata}"></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 704, Column 271: entity was defined here
    …hsys.com/www/delivery/amz.php?zoneids=880&loc={encodedtargetingdata}"></iframe>
  • Error Line 704, Column 299: element "iframe" undefined
    …hsys.com/www/delivery/amz.php?zoneids=880&loc={encodedtargetingdata}"></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).
  • Warning Line 707, Column 216: cannot generate system identifier for general entity "p"
    …src="http://syndication.traffichaus.com/adserve.php?z=129&p=4"></iframe></div> 

    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 707, Column 216: general entity "p" not defined and no default entity
    …src="http://syndication.traffichaus.com/adserve.php?z=129&p=4"></iframe></div> 

    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 707, Column 217: reference not terminated by REFC delimiter
    …src="http://syndication.traffichaus.com/adserve.php?z=129&p=4"></iframe></div> 

    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 707, Column 217: reference to external entity in attribute value
    …src="http://syndication.traffichaus.com/adserve.php?z=129&p=4"></iframe></div> 

    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 707, Column 217: reference to entity "p" for which no system identifier could be generated
    …src="http://syndication.traffichaus.com/adserve.php?z=129&p=4"></iframe></div> 

    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 707, Column 215: entity was defined here
    …src="http://syndication.traffichaus.com/adserve.php?z=129&p=4"></iframe></div> 
  • Error Line 707, Column 220: element "iframe" undefined
    …src="http://syndication.traffichaus.com/adserve.php?z=129&p=4"></iframe></div> 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 736, Column 121: required attribute "alt" not specified
    …><img src="/user_images/thumbs/dd8eb9f23fbd362da0e3f4e70b878c16.jpg"></a></div>

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

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

  • Error Line 736, Column 125: end tag for "img" omitted, but OMITTAG NO was specified
    …><img src="/user_images/thumbs/dd8eb9f23fbd362da0e3f4e70b878c16.jpg"></a></div>

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

  • Info Line 736, Column 54: start tag was here
    …ss="thumb"><a href="/users/JDFROMMZ/"><img src="/user_images/thumbs/dd8eb9f23f…
  • Error Line 738, Column 34: there is no attribute "alt"
    							<div class="comments" alt="Comments" title="Comments">0</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 742, Column 124: required attribute "alt" not specified
    …><img src="/user_images/thumbs/705f2172834666788607efbfca35afb3.jpg"></a></div>

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

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

  • Error Line 742, Column 128: end tag for "img" omitted, but OMITTAG NO was specified
    …><img src="/user_images/thumbs/705f2172834666788607efbfca35afb3.jpg"></a></div>

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

  • Info Line 742, Column 57: start tag was here
    …"thumb"><a href="/users/AussiePride/"><img src="/user_images/thumbs/705f217283…
  • Error Line 748, Column 122: required attribute "alt" not specified
    …><img src="/user_images/thumbs/a516a87cfcaef229b342c437fe2b95f7.jpg"></a></div>

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

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

  • Error Line 748, Column 126: end tag for "img" omitted, but OMITTAG NO was specified
    …><img src="/user_images/thumbs/a516a87cfcaef229b342c437fe2b95f7.jpg"></a></div>

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

  • Info Line 748, Column 55: start tag was here
    …s="thumb"><a href="/users/kysersoso/"><img src="/user_images/thumbs/a516a87cfc…
  • Error Line 754, Column 120: required attribute "alt" not specified
    …><img src="/user_images/thumbs/3cef96dcc9b8035d23f69e30bb19218a.jpg"></a></div>

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

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

  • Error Line 754, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …><img src="/user_images/thumbs/3cef96dcc9b8035d23f69e30bb19218a.jpg"></a></div>

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

  • Info Line 754, Column 53: start tag was here
    …ass="thumb"><a href="/users/grechka/"><img src="/user_images/thumbs/3cef96dcc9…
  • Error Line 760, Column 122: required attribute "alt" not specified
    …><img src="/user_images/thumbs/2a9d121cd9c3a1832bb6d2cc6bd7a8a7.jpg"></a></div>

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

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

  • Error Line 760, Column 126: end tag for "img" omitted, but OMITTAG NO was specified
    …><img src="/user_images/thumbs/2a9d121cd9c3a1832bb6d2cc6bd7a8a7.jpg"></a></div>

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

  • Info Line 760, Column 55: start tag was here
    …s="thumb"><a href="/users/INFAMOUS1/"><img src="/user_images/thumbs/2a9d121cd9…
  • Error Line 766, Column 123: required attribute "alt" not specified
    …><img src="/user_images/thumbs/c5ab0bc60ac7929182aadd08703f1ec6.jpg"></a></div>

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

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

  • Error Line 766, Column 127: end tag for "img" omitted, but OMITTAG NO was specified
    …><img src="/user_images/thumbs/c5ab0bc60ac7929182aadd08703f1ec6.jpg"></a></div>

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

  • Info Line 766, Column 56: start tag was here
    …="thumb"><a href="/users/mytrapboom/"><img src="/user_images/thumbs/c5ab0bc60a…
  • Error Line 772, Column 128: required attribute "alt" not specified
    …><img src="/user_images/thumbs/b73dfe25b4b8714c029b37a6ad3006fa.jpg"></a></div>

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

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

  • Error Line 772, Column 132: end tag for "img" omitted, but OMITTAG NO was specified
    …><img src="/user_images/thumbs/b73dfe25b4b8714c029b37a6ad3006fa.jpg"></a></div>

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

  • Info Line 772, Column 61: start tag was here
    …mb"><a href="/users/yangdongqaz1975/"><img src="/user_images/thumbs/b73dfe25b4…
  • Error Line 778, Column 123: required attribute "alt" not specified
    …><img src="/user_images/thumbs/df7f28ac89ca37bf1abd2f6c184fe1cf.jpg"></a></div>

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

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

  • Error Line 778, Column 127: end tag for "img" omitted, but OMITTAG NO was specified
    …><img src="/user_images/thumbs/df7f28ac89ca37bf1abd2f6c184fe1cf.jpg"></a></div>

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

  • Info Line 778, Column 56: start tag was here
    …="thumb"><a href="/users/Oboy+Blend/"><img src="/user_images/thumbs/df7f28ac89…
  • Error Line 784, Column 122: required attribute "alt" not specified
    …er/"><img src="http://media.mentalzero.com/images/head_portrait.jpg"></a></div>

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

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

  • Error Line 784, Column 126: end tag for "img" omitted, but OMITTAG NO was specified
    …er/"><img src="http://media.mentalzero.com/images/head_portrait.jpg"></a></div>

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

  • Info Line 784, Column 59: start tag was here
    …humb"><a href="/users/Throatguzzler/"><img src="http://media.mentalzero.com/im…
  • Error Line 790, Column 120: required attribute "alt" not specified
    …><img src="/user_images/thumbs/0d7de1aca9299fe63f3e0041f02638a3.jpg"></a></div>

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

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

  • Error Line 790, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …><img src="/user_images/thumbs/0d7de1aca9299fe63f3e0041f02638a3.jpg"></a></div>

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

  • Info Line 790, Column 53: start tag was here
    …ass="thumb"><a href="/users/Symerka/"><img src="/user_images/thumbs/0d7de1aca9…
  • Error Line 822, Column 24: document type does not allow element "div" here; assuming missing "li" start-tag
    					<div class="clear"></div>
  • Error Line 823, Column 10: end tag for "li" 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 822, Column 6: start tag was here
    					<div class="clear"></div>
  • Error Line 823, Column 10: end tag for "ul" 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 801, Column 6: start tag was here
    					<ul>
  • Error Line 835, Column 8: end tag for "div" omitted, but OMITTAG NO was specified
    			</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 834, Column 86: start tag was here
    …ass="plug_title"><a href="/more-extreme/5/" target="_blank">Bad daddy!</a><div>
  • Error Line 835, Column 8: end tag for "div" omitted, but OMITTAG NO was specified
    			</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 834, Column 5: start tag was here
    				<div class="plug_title"><a href="/more-extreme/5/" target="_blank">Bad dadd…
  • Error Line 840, Column 8: end tag for "div" omitted, but OMITTAG NO was specified
    			</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 839, Column 99: start tag was here
    …le"><a href="/more-extreme/2/" target="_blank">UNHOLY FUCKING HELL!!!!</a><div>
  • Error Line 840, Column 8: end tag for "div" omitted, but OMITTAG NO was specified
    			</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 839, Column 5: start tag was here
    				<div class="plug_title"><a href="/more-extreme/2/" target="_blank">UNHOLY F…
  • Error Line 867, 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>.

  • Warning Line 869, Column 89: cannot generate system identifier for general entity "welcome"
    …asmin.com/freechat.php?psid=ncnewsfpu&welcome";var popunderWidth=1100;var popu…

    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 869, Column 89: general entity "welcome" not defined and no default entity
    …asmin.com/freechat.php?psid=ncnewsfpu&welcome";var popunderWidth=1100;var popu…

    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 869, Column 96: reference not terminated by REFC delimiter
    …om/freechat.php?psid=ncnewsfpu&welcome";var popunderWidth=1100;var popunderHei…

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

  • Error Line 869, Column 96: reference to entity "welcome" for which no system identifier could be generated
    …om/freechat.php?psid=ncnewsfpu&welcome";var popunderWidth=1100;var popunderHei…

    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 869, Column 88: entity was defined here
    …jasmin.com/freechat.php?psid=ncnewsfpu&welcome";var popunderWidth=1100;var pop…
  • Warning Line 875, Column 98: cannot generate system identifier for general entity "AFNO"
    …mad/imad-v1.2.js?domain=streamate.com&AFNO=1-0-614784-341541&UHNSMTY=303&volum…

    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 875, Column 98: general entity "AFNO" not defined and no default entity
    …mad/imad-v1.2.js?domain=streamate.com&AFNO=1-0-614784-341541&UHNSMTY=303&volum…

    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 875, Column 102: reference not terminated by REFC delimiter
    …imad-v1.2.js?domain=streamate.com&AFNO=1-0-614784-341541&UHNSMTY=303&volume=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 875, Column 102: reference to external entity in attribute value
    …imad-v1.2.js?domain=streamate.com&AFNO=1-0-614784-341541&UHNSMTY=303&volume=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 875, Column 102: reference to entity "AFNO" for which no system identifier could be generated
    …imad-v1.2.js?domain=streamate.com&AFNO=1-0-614784-341541&UHNSMTY=303&volume=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 875, Column 97: entity was defined here
    …imad/imad-v1.2.js?domain=streamate.com&AFNO=1-0-614784-341541&UHNSMTY=303&volu…
  • Warning Line 875, Column 121: cannot generate system identifier for general entity "UHNSMTY"
    …=streamate.com&AFNO=1-0-614784-341541&UHNSMTY=303&volume=0" text/javascript" c…

    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 875, Column 121: general entity "UHNSMTY" not defined and no default entity
    …=streamate.com&AFNO=1-0-614784-341541&UHNSMTY=303&volume=0" text/javascript" c…

    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 875, Column 128: reference not terminated by REFC delimiter
    …ate.com&AFNO=1-0-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset=…

    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 875, Column 128: reference to external entity in attribute value
    …ate.com&AFNO=1-0-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset=…

    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 875, Column 128: reference to entity "UHNSMTY" for which no system identifier could be generated
    …ate.com&AFNO=1-0-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset=…

    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 875, Column 120: entity was defined here
    …n=streamate.com&AFNO=1-0-614784-341541&UHNSMTY=303&volume=0" text/javascript" …
  • Warning Line 875, Column 133: cannot generate system identifier for general entity "volume"
    …om&AFNO=1-0-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset="utf-…

    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 875, Column 133: general entity "volume" not defined and no default entity
    …om&AFNO=1-0-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset="utf-…

    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 875, Column 139: reference not terminated by REFC delimiter
    …O=1-0-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset="utf-8"></s…

    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 875, Column 139: reference to external entity in attribute value
    …O=1-0-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset="utf-8"></s…

    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 875, Column 139: reference to entity "volume" for which no system identifier could be generated
    …O=1-0-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset="utf-8"></s…

    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 875, Column 132: entity was defined here
    …com&AFNO=1-0-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset="utf…
  • Error Line 875, Column 148: NET-enabling start-tag not immediately followed by null end-tag
    …-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset="utf-8"></script>

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 875, Column 148: "text" is not a member of a group specified for any attribute
    …-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset="utf-8"></script>
  • Error Line 875, Column 148: required attribute "type" not specified
    …-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset="utf-8"></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 875, Column 184: end tag for element "script" which is not open
    …-614784-341541&UHNSMTY=303&volume=0" text/javascript" charset="utf-8"></script>

    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
  • 4.783 visits