busuk.org

Laman perkongsian artikel untuk semua. Ping Busuk menyediakan sistem auto-ping artikel yang pertama di Malaysia. Kongsi artikel anda hari ini! ...

This data was last updated from 31-07-2014 10:34:19  (update).

Overview Info



  • Domain Name
    busuk.org
  • Favicon
  • Alexa Rank
    #7521
  • Google Page Rank
    4
  • Ip Address
    106.186.21.145
  • Page Size
    46.8 KB
  • Images
    15 GIF, 21 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    Ping Busuk | Laman Aggregator Blog Malaysia
  • Meta Keyword
    ping,busuk,aggregator,blog,malaysia,melayu,tips,trick,site,submission,apesal,guablog,pingje,autoping
  • Meta Description
    Laman perkongsian artikel untuk semua. Ping Busuk menyediakan sistem auto-ping artikel yang pertama di Malaysia. Kongsi artikel anda hari ini!

Technical Analysis



  • Webserver
    Apache/2.2.15 (CentOS)
  • Ip Address
    106.186.21.145
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from busuk.org.

HTML Analysis

  • date: Thu, 31 Jul 2014 10:36:34 GMT
  • server: Apache/2.2.15 (CentOS)
  • x-powered-by: PHP/5.3.3
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain ID:D162042291-LROR
Domain Domain Name:BUSUK.ORG
Created:15-Apr-2011 13:20:31 UTC
Updated:14-Jan-2012 19:53:20 UTC
Expires:15-Apr-2012 13:20:31 UTC
Registrar:QuantumPages Technologies Pvt. Ltd. d/b/a OwnRegistrar.com (R1466-LROR)
Domain Status:CLIENT TRANSFER PROHIBITED
Registrant ID:PP-SP-001
Registrant Domain Name:Domain Admin
Registrant Organization:PrivacyProtect.org
Registrant Street1:ID#10760, PO Box 16
Registrant Street2:Note - All Postal Mails Rejected, visit Privacyprotect.org
Registrant Street3:
Registrant City:Nobby Beach
Registrant State/Province:
Registrant Postal Code:QLD 4218
Registrant Country:AU
Registrant Phone:+45.36946676
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant Email: email
Admin ID:PP-SP-001
Admin Domain Name:Domain Admin
Admin Organization:PrivacyProtect.org
Admin Street1:ID#10760, PO Box 16
Admin Street2:Note - All Postal Mails Rejected, visit Privacyprotect.org
Admin Street3:
Admin City:Nobby Beach
Admin State/Province:
Admin Postal Code:QLD 4218
Admin Country:AU
Admin Phone:+45.36946676
Admin Phone Ext.:
Admin FAX:
Admin FAX Ext.:
Admin Email: email
Tech ID:PP-SP-001
Tech Domain Name:Domain Admin
Tech Organization:PrivacyProtect.org
Tech Street1:ID#10760, PO Box 16
Tech Street2:Note - All Postal Mails Rejected, visit Privacyprotect.org
Tech Street3:
Tech City:Nobby Beach
Tech State/Province:
Tech Postal Code:QLD 4218
Tech Country:AU
Tech Phone:+45.36946676
Tech Phone Ext.:
Tech FAX:
Tech FAX Ext.:
Tech Email: email
Name Servers:LARA.NS.CLOUDFLARE.COM
Name Servers:PHIL.NS.CLOUDFLARE.COM
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
DNSSEC:Unsigned

0

IP 106.186.21.145 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 172 Errors
  • 16 Warnings
Ratio Text/Html
  • 0.7508083863565245
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 4, Column 134: NET-enabling start-tag requires SHORTTAG YES
    …ucZyjjI/AAAAAAAAB8s/Vn3Z3rtmQwI/s1600/ico.png' rel='icon' type='image/x-icon'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 5, Column 123: document type does not allow element "LINK" here
    …p.blogspot.com/-zLRK_baCfQw/UaGAucZyjjI/AAAAAAAAB8s/Vn3Z3rtmQwI/s1600/ico.png'>

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

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

  • Warning Line 6, Column 112: NET-enabling start-tag requires SHORTTAG YES
    …ication/atom+xml' title='Ping Busuk - Atom' href='http://pingbusuk.org/feed' />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 6, Column 112: document type does not allow element "LINK" here
    …ication/atom+xml' title='Ping Busuk - Atom' href='http://pingbusuk.org/feed' />

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

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

  • Warning Line 7, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …lication/rss+xml' title='Ping Busuk - RSS' href='http://pingbusuk.org/feed' />	

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 7, Column 110: document type does not allow element "LINK" here
    …lication/rss+xml' title='Ping Busuk - RSS' href='http://pingbusuk.org/feed' />	

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

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

  • Error Line 8, Column 119: document type does not allow element "LINK" here
    …p.blogspot.com/-zLRK_baCfQw/UaGAucZyjjI/AAAAAAAAB8s/Vn3Z3rtmQwI/s1600/ico.png'>

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

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

  • Warning Line 9, Column 76: NET-enabling start-tag requires SHORTTAG YES
    		<meta name='title' content='Ping Busuk : Laman Aggregator Blog Malaysia' />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 9, Column 76: document type does not allow element "META" here
    		<meta name='title' content='Ping Busuk : Laman Aggregator Blog Malaysia' />

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

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

  • Warning Line 10, Column 61: NET-enabling start-tag requires SHORTTAG YES
    		<meta content='IE=EmulateIE7' http-equiv='X-UA-Compatible'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 10, Column 61: document type does not allow element "META" here
    		<meta content='IE=EmulateIE7' http-equiv='X-UA-Compatible'/>

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

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

  • Warning Line 11, Column 69: NET-enabling start-tag requires SHORTTAG YES
    		<meta content='text/html; charset=UTF-8' http-equiv='Content-Type'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 11, Column 69: document type does not allow element "META" here
    		<meta content='text/html; charset=UTF-8' http-equiv='Content-Type'/>

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

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

  • Warning Line 13, Column 95: NET-enabling start-tag requires SHORTTAG YES
    …l yang pertama di Malaysia. Kongsi artikel anda hari ini!' name='description'/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 13, Column 95: document type does not allow element "META" here
    …l yang pertama di Malaysia. Kongsi artikel anda hari ini!' name='description'/>

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

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

  • Warning Line 14, Column 135: NET-enabling start-tag requires SHORTTAG YES
    …ablog,pingje,autoping' name='keywords'/>	<link href="http://pingbusuk.org/src/…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 14, Column 135: document type does not allow element "META" here
    …ablog,pingje,autoping' name='keywords'/>	<link href="http://pingbusuk.org/src/…

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

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

  • Error Line 14, Column 214: document type does not allow element "LINK" here
    …>	<link href="http://pingbusuk.org/src/a.css" rel="stylesheet" type="text/css">

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

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

  • Warning Line 27, Column 97: NET-enabling start-tag requires SHORTTAG YES
    …et" type="text/css" href="http://pingbusuk.org/src/fancy.css" media="screen" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 27, Column 97: document type does not allow element "LINK" here
    …et" type="text/css" href="http://pingbusuk.org/src/fancy.css" media="screen" />

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

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

  • Error Line 29, Column 8: end tag for element "HEAD" which is not open
    	</head>

    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 30, Column 24: document type does not allow element "BODY" here
    <body bgcolor='#EDEDED'>

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

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

  • Error Line 31, Column 8: required attribute "TYPE" not specified
    <script>

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

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

  • Error Line 62, Column 14: invalid comment declaration: found name character outside comment but inside comment declaration
    	<!-- ads 1--->
  • Info Line 62, Column 2: comment declaration started here
    	<!-- ads 1--->
  • Error Line 63, Column 16: "ASYNC" is not a member of a group specified for any attribute
    	<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"><…
  • Error Line 63, Column 78: required attribute "TYPE" not specified
    … async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.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 67, Column 17: there is no attribute "DATA-LANGUAGE"
    	 data-language="id"

    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 68, Column 18: there is no attribute "DATA-AD-CLIENT"
    	 data-ad-client="ca-pub-5691017586059942"

    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 69, Column 16: there is no attribute "DATA-AD-SLOT"
    	 data-ad-slot="4791496671"></ins>

    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 70, Column 8: required attribute "TYPE" not specified
    <script>

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

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

  • Error Line 78, Column 60: there is no attribute "HEIGHT"
    … border='0' cellpadding='0' cellspacing='10' height='100%' bgcolor='white'><tr>

    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 89, Column 64: there is no attribute "ALT"
    …k.org/htm/README.txt' id='framex' alt='BACA SAYA pingbusuk.org' title='BACA SA…

    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 90, Column 49: ID "FRAMEX" already defined
    …http://pingbusuk.org/htm/TOS.txt' id='framex' alt='TERMA DAN SYARAT' title='TE…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 89, Column 52: ID "FRAMEX" first defined here
    …p://pingbusuk.org/htm/README.txt' id='framex' alt='BACA SAYA pingbusuk.org' ti…
  • Warning Line 110, Column 22: NET-enabling start-tag requires SHORTTAG YES
    	<input type="submit"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 117, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 118, Column 260: end tag for "DIV" omitted, but its declaration does not permit this
    …lam kebakaran di Kunak' title='Pasar raya musnah dalam kebakaran di Kunak'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 117, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 120, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>pasar raya musnah …

    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 122, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 123, Column 245: end tag for "DIV" omitted, but its declaration does not permit this
    …endam Amerika Kini Bermula' title='MISI Balas Dendam Amerika Kini Bermula'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 122, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 125, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>misi balas dendam …

    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 127, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 128, Column 379: end tag for "DIV" omitted, but its declaration does not permit this
    …Rakyat Tapi Selepas Apa Yang Kau Buat Selama Ini Adakah Aku Hanya Membisu'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 127, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 130, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>aku sayangkan paka…

    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 132, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 133, Column 380: end tag for "DIV" omitted, but its declaration does not permit this
    …TAS KUBUR DIKUTUK KERAS OLEH RAKYAT DAN DIFATWAKAN HARAM OLEH MUFTI PERAK'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 132, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 135, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>bila gelagat biada…

    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 137, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 138, Column 278: end tag for "DIV" omitted, but its declaration does not permit this
    … title='Cabang PKR Selangor gesa Khalid dikenakan tindakan disiplin parti'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 137, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 140, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>cabang pkr selango…

    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 142, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 143, Column 330: end tag for "DIV" omitted, but its declaration does not permit this
    …='feedback 1 years old thigh scar reduce in 1 month ameryllis herbal balm'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 142, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 145, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>feedback 1 years o…

    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 147, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 148, Column 219: end tag for "DIV" omitted, but its declaration does not permit this
    …Donald s Malaysia Panas Pungkok' title='McDonald s Malaysia Panas Pungkok'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 147, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 150, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>mcdonald s malaysi…

    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 152, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 153, Column 323: end tag for "DIV" omitted, but its declaration does not permit this
    …i Akhirnya Meninggal Selepas 6 Hari Ditarik Dari Rahim Ibunya Yang Syahid'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 152, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 155, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>bayi kecil ini akh…

    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 157, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 158, Column 270: end tag for "DIV" omitted, but its declaration does not permit this
    …S X' title='Aplikasi Pengecaman Lagu Shazam Hadir Untuk Pengguna Mac OS X'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 157, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 160, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>aplikasi pengecama…

    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 162, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 163, Column 259: end tag for "DIV" omitted, but its declaration does not permit this
    …Wan Junaidi' title='Malaysia Tidak Pernah Latih Pejuang Hamas Wan Junaidi'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 162, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 165, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>malaysia tidak per…

    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 167, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 168, Column 214: end tag for "DIV" omitted, but its declaration does not permit this
    …n.jpg' alt='Terkulai bagai kena tembak' title='Terkulai bagai kena tembak'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 167, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 170, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>terkulai bagai ken…

    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 172, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 173, Column 240: end tag for "DIV" omitted, but its declaration does not permit this
    …s Tak Berhati Perut' title='Ambik Kau Balasan Untuk Bos Tak Berhati Perut'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 172, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 175, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>ambik kau balasan …

    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 177, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 178, Column 257: end tag for "DIV" omitted, but its declaration does not permit this
    …napa Zam Sedih Tengok Gambar Ni' title='Kenapa Zam Sedih Tengok Gambar Ni'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 177, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 180, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>kenapa zam sedih t…

    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 182, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 183, Column 245: end tag for "DIV" omitted, but its declaration does not permit this
    …enikmati Hubungan Seks' title='Usia Terbaik untuk Menikmati Hubungan Seks'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 182, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 185, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>usia terbaik untuk…

    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 187, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 188, Column 226: end tag for "DIV" omitted, but its declaration does not permit this
    …ncari Jodoh Di Musim Raya' title='Petua Untuk Mencari Jodoh Di Musim Raya'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 187, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 190, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>petua untuk mencar…

    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 192, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 193, Column 251: end tag for "DIV" omitted, but its declaration does not permit this
    …idlfitri jumpa kereta hantu' title='Kenangan Aidlfitri jumpa kereta hantu'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 192, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 195, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>kenangan aidlfitri…

    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 197, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 198, Column 361: end tag for "DIV" omitted, but its declaration does not permit this
    …M TUNJUK VIDEO MEREKA SERANG PENEMPATAN ISRAEL 10 TENTERA ISRAEL TERBUNUH'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 197, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 200, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>buat pertama kali …

    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 202, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

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

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

  • Error Line 203, Column 224: end tag for "DIV" omitted, but its declaration does not permit this
    …Menarik Foto Lawak Giler vol 193' title='Menarik Foto Lawak Giler vol 193'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 202, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 205, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>menarik foto lawak…

    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 207, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

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

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

  • Error Line 208, Column 243: end tag for "DIV" omitted, but its declaration does not permit this
    …nguasa KASTAM W27' title='Peperiksaan Online Penolong Penguasa KASTAM W27'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 207, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 210, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>peperiksaan online…

    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 212, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 213, Column 216: end tag for "DIV" omitted, but its declaration does not permit this
    …tusan PAS dalam pakatan rakyat' title='Keputusan PAS dalam pakatan rakyat'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 212, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 215, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>keputusan pas dala…

    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 217, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 218, Column 270: end tag for "DIV" omitted, but its declaration does not permit this
    …ersonakan' title='Karya Seni Lukisan Pada Wanita Hamil Yang Mempersonakan'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 217, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 220, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>karya seni lukisan…

    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 222, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 223, Column 268: end tag for "DIV" omitted, but its declaration does not permit this
    …ysia' title='Bagaimana McDonald s Malaysia Memperbodohkan Rakyat Malaysia'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 222, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 225, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>bagaimana mcdonald…

    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 227, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 228, Column 239: end tag for "DIV" omitted, but its declaration does not permit this
    …UKAN RAFIZI DAN DAPigs' title='PAK MUS TAMPIL MEMALUKAN RAFIZI DAN DAPigs'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 227, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 230, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>pak mus tampil mem…

    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 232, Column 79: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>

    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 233, Column 212: end tag for "DIV" omitted, but its declaration does not permit this
    …di negara negara Asia' title='Harimau semakin pupus di negara negara Asia'></a>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 232, Column 3: start tag was here
    		<div class='thumbnail' style='background:#CCCCCC;width:145px;' align='right'>
  • Error Line 235, Column 8: end tag for element "DIV" which is not open
    		</div><div style='padding:5px;width:150px;' align='center'>harimau semakin pu…

    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 236, Column 25: end tag for "TR" which is not finished
    		<br></td></tr><tr></tr></table>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 237, Column 53: there is no attribute "WIDTH"
    …//pingbusuk.org/pg/939839'><div width='100%' style='background:#ECECEC;padding…

    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 237, Column 139: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …rder:#CCCCCC 1px solid' align='center'>ARTIKEL YANG LEBIH LAMA</div></a><br><h…

    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 240, Column 370: there is no attribute "ALLOWTRANSPARENCY"
    …overflow:hidden; width:290px; height:258px;" allowTransparency="true"></iframe>

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

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

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

  • Error Line 251, Column 65: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    ….org'><div width='100%' align='center'><img src='http://pingbusuk.org/img/bing…

    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 251, Column 121: required attribute "ALT" not specified
    …ign='center'><img src='http://pingbusuk.org/img/bing.jpg' border='0'></div></a>

    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 261, Column 146: ID "FRAMEX" already defined
    …://pingbusuk.org/htm/getcode.php' id='framex' alt='code auto ping tanpa papara…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 89, Column 52: ID "FRAMEX" first defined here
    …p://pingbusuk.org/htm/README.txt' id='framex' alt='BACA SAYA pingbusuk.org' ti…
  • Error Line 263, Column 238: end tag for "A" omitted, but its declaration does not permit this
    …eck status domain anda' title='check status domain anda'>Domain Check</td></tr>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 263, Column 74: start tag was here
    …er:1px solid #000;' bgcolor='#EE1B24'><a style='color:white;' href='http://pin…
  • Error Line 268, Column 17: "ASYNC" is not a member of a group specified for any attribute
    		<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js">…
  • Error Line 268, Column 79: required attribute "TYPE" not specified
    … async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.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 275, Column 8: required attribute "TYPE" not specified
    <script>

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

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

  • Error Line 282, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><a href='http://pingbusuk.org/v/939301/ngeri-3-gambar-peluru-terlekat-di-ke…

    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 282, Column 339: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …ru terlekat di kepala ak..</a></li><li><a href='http://pingbusuk.org/v/939760/…

    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 282, Column 557: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …20/m.jpg'>cuba terbalikkan</a></li><li><a href='http://pingbusuk.org/v/939375/…

    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 282, Column 890: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …ll lundang kb rosak akib..</a></li><li><a href='http://pingbusuk.org/v/939688/…

    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 282, Column 1172: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …belakang viva wanita parah</a></li><li><a href='http://pingbusuk.org/v/939276/…

    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 282, Column 1415: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …cara mudah kempiskan perut</a></li><li><a href='http://pingbusuk.org/v/939759/…

    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 282, Column 1709: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …s malaysia memperbodohka..</a></li><li><a href='http://pingbusuk.org/v/939282/…

    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 282, Column 2030: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …l wee wern kalah mengeju..</a></li><li><a href='http://pingbusuk.org/v/939687/…

    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 282, Column 2323: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …unia tawar bayaran balik..</a></li><li><a href='http://pingbusuk.org/v/939284/…

    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 282, Column 2661: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    … untuk ore kelantan sepa..</a></li><li><a href='http://pingbusuk.org/v/939427/…

    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 282, Column 2922: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …melu lukaku sah ke everton</a></li><li><a href='http://pingbusuk.org/v/939600/…

    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 282, Column 3220: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …irection diugut bunuh ke..</a></li><li><a href='http://pingbusuk.org/v/939505/…

    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 283, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><a href='http://pingbusuk.org/v/833184/macam-macam-wau-ada.html'  target='_…

    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 283, Column 249: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …8.jpg'>macam macam wau ada</a></li><li><a href='http://pingbusuk.org/v/916089/…

    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 283, Column 488: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …'>motivasi nak jadi cantik</a></li><li><a href='http://pingbusuk.org/v/914277/…

    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 283, Column 729: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …pg'>kau setan aku malaikat</a></li><li><a href='http://pingbusuk.org/v/914257/…

    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 283, Column 985: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …man pelajar sekolah lelaki</a></li><li><a href='http://pingbusuk.org/v/915762/…

    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 283, Column 1248: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …iri mencari cinta pencipta</a></li><li><a href='http://pingbusuk.org/v/915578/…

    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 283, Column 1516: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …n untuk memperolehi zuriat</a></li><li><a href='http://pingbusuk.org/v/911809/…

    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 283, Column 1802: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …antu jalan raya yang seram</a></li><li><a href='http://pingbusuk.org/v/918115/…

    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 283, Column 2057: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …dang mengajar kita sesuatu</a></li><li><a href='http://pingbusuk.org/v/603051/…

    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 283, Column 2288: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …hicken.jpg'>aku penganggur</a></li><li><a href='http://pingbusuk.org/v/374963/…

    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 283, Column 2527: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …0'>emak abah opah dan atuk</a></li><li><a href='http://pingbusuk.org/v/606000/…

    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 283, Column 2772: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …f'>spisis kawan yang femes</a></li><li><a href='http://pingbusuk.org/v/524726/…

    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 286, Column 4: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    <li><a href='http://pingbusuk.org/domain/izyanshamba.blogspot.com'>izyanshamba.…

    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 287, Column 229: required attribute "ALT" not specified
    …AAAAAAAAB_U/wa_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.…

    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 287, Column 242: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …a_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.org/domain/ry…

    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 288, Column 224: required attribute "ALT" not specified
    …AAAAAAAAB_U/wa_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.…

    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 288, Column 237: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …a_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.org/domain/ca…

    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 289, Column 220: required attribute "ALT" not specified
    …AAAAAAAAB_U/wa_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.…

    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 289, Column 233: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …a_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.org/domain/is…

    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 290, Column 236: required attribute "ALT" not specified
    …AAAAAAAAB_U/wa_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.…

    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 290, Column 249: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …a_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.org/domain/pw…

    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 291, Column 224: required attribute "ALT" not specified
    …AAAAAAAAB_U/wa_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.…

    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 291, Column 237: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …a_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.org/domain/le…

    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 292, Column 238: required attribute "ALT" not specified
    …AAAAAAAAB_U/wa_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.…

    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 292, Column 251: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …a_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.org/domain/ek…

    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 293, Column 228: required attribute "ALT" not specified
    …AAAAAAAAB_U/wa_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.…

    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 293, Column 241: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …a_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.org/domain/mi…

    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 294, Column 227: required attribute "ALT" not specified
    …AAAAAAAAB_U/wa_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.…

    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 294, Column 240: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …a_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.org/domain/un…

    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 295, Column 231: required attribute "ALT" not specified
    …AAAAAAAAB_U/wa_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.…

    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 295, Column 244: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …a_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.org/domain/en…

    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 296, Column 233: required attribute "ALT" not specified
    …AAAAAAAAB_U/wa_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.…

    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 296, Column 246: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …a_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.org/domain/lo…

    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 297, Column 232: required attribute "ALT" not specified
    …AAAAAAAAB_U/wa_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.…

    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 297, Column 245: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    …a_00ipE0pg/s1600/pop.gif'></a></li><li><a href='http://pingbusuk.org/domain/ij…

    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 298, Column 226: required attribute "ALT" not specified
    …t.com/-I2MYFnkzuhM/Ucr9tmmTxhI/AAAAAAAAB_U/wa_00ipE0pg/s1600/pop.gif'></a></li>

    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 304, Column 106: cannot generate system identifier for general entity "dim"
    …et/ajrotator/834443/0/vj?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-b…

    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 304, Column 106: general entity "dim" not defined and no default entity
    …et/ajrotator/834443/0/vj?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-b…

    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.

  • Error Line 304, Column 109: reference to entity "dim" for which no system identifier could be generated
    …ajrotator/834443/0/vj?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-bcf2…

    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 304, Column 105: entity was defined here
    …let/ajrotator/834443/0/vj?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-…
  • Warning Line 304, Column 117: cannot generate system identifier for general entity "pid"
    …r/834443/0/vj?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-bcf2bf061de4…

    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 304, Column 117: general entity "pid" not defined and no default entity
    …r/834443/0/vj?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-bcf2bf061de4…

    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.

  • Error Line 304, Column 120: reference to entity "pid" for which no system identifier could be generated
    …34443/0/vj?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-bcf2bf061de4&as…

    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 304, Column 116: entity was defined here
    …or/834443/0/vj?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-bcf2bf061de…
  • Warning Line 304, Column 158: cannot generate system identifier for general entity "asid"
    …=2e482725-3b94-4afb-bff5-bcf2bf061de4&asid=28393f7a-2437-4329-b2d8-bfc4d2488a9…

    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 304, Column 158: general entity "asid" not defined and no default entity
    …=2e482725-3b94-4afb-bff5-bcf2bf061de4&asid=28393f7a-2437-4329-b2d8-bfc4d2488a9…

    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.

  • Error Line 304, Column 162: reference to entity "asid" for which no system identifier could be generated
    …82725-3b94-4afb-bff5-bcf2bf061de4&asid=28393f7a-2437-4329-b2d8-bfc4d2488a93"><…

    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 304, Column 157: entity was defined here
    …d=2e482725-3b94-4afb-bff5-bcf2bf061de4&asid=28393f7a-2437-4329-b2d8-bfc4d2488a…
  • Error Line 304, Column 200: required attribute "TYPE" not specified
    …=28393f7a-2437-4329-b2d8-bfc4d2488a93"></script><noscript><a href="http://a.ad…

    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 304, Column 300: reference to entity "pid" for which no system identifier could be generated
    …ajrotator/834443/0/cc?z=admaxasia2&pid=2e482725-3b94-4afb-bff5-bcf2bf061de4&as…

    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 304, Column 116: entity was defined here
    …or/834443/0/vj?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-bcf2bf061de…
  • Error Line 304, Column 342: reference to entity "asid" for which no system identifier could be generated
    …82725-3b94-4afb-bff5-bcf2bf061de4&asid=28393f7a-2437-4329-b2d8-bfc4d2488a93"><…

    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 304, Column 157: entity was defined here
    …d=2e482725-3b94-4afb-bff5-bcf2bf061de4&asid=28393f7a-2437-4329-b2d8-bfc4d2488a…
  • Error Line 304, Column 462: reference to entity "dim" for which no system identifier could be generated
    …ajrotator/834443/0/vc?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-bcf2…

    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 304, Column 105: entity was defined here
    …let/ajrotator/834443/0/vj?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-…
  • Error Line 304, Column 473: reference to entity "pid" for which no system identifier could be generated
    …34443/0/vc?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-bcf2bf061de4&as…

    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 304, Column 116: entity was defined here
    …or/834443/0/vj?z=admaxasia2&dim=280733&pid=2e482725-3b94-4afb-bff5-bcf2bf061de…
  • Error Line 304, Column 515: reference to entity "asid" for which no system identifier could be generated
    …82725-3b94-4afb-bff5-bcf2bf061de4&asid=28393f7a-2437-4329-b2d8-bfc4d2488a93&ab…

    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 304, Column 157: entity was defined here
    …d=2e482725-3b94-4afb-bff5-bcf2bf061de4&asid=28393f7a-2437-4329-b2d8-bfc4d2488a…
  • Warning Line 304, Column 553: cannot generate system identifier for general entity "abr"
    …=28393f7a-2437-4329-b2d8-bfc4d2488a93&abr=$imginiframe" width="300" height="25…

    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 304, Column 553: general entity "abr" not defined and no default entity
    …=28393f7a-2437-4329-b2d8-bfc4d2488a93&abr=$imginiframe" width="300" height="25…

    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.

  • Error Line 304, Column 556: reference to entity "abr" for which no system identifier could be generated
    …393f7a-2437-4329-b2d8-bfc4d2488a93&abr=$imginiframe" width="300" height="250" …

    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 304, Column 552: entity was defined here
    …d=28393f7a-2437-4329-b2d8-bfc4d2488a93&abr=$imginiframe" width="300" height="2…
  • Error Line 304, Column 606: required attribute "ALT" not specified
    …4d2488a93&abr=$imginiframe" width="300" height="250" border="0"></a></noscript>

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

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

  • Error Line 315, Column 7: end tag for "CENTER" omitted, but its declaration does not permit this
    </body>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 59, Column 1: start tag was here
    <center>

Visitor Analysis

Daily Visitor
  • 14.700 visits

In Page Analysis