apspsc.gov.in

Andhra Pradesh Public Service Commission Powered by Centre for Good Governance      Main Website All Mark lists All Interview lists All Selection lists          Notifications Click Here           ...

Display Widget for this domain on your website. Click Here
This data was last updated from 18-01-2013 02:34:22  (update).

Overview Info

  • Domain Name
    apspsc.gov.in
  • Favicon
  • Alexa Rank
    #12612
  • Google Page Rank
    PR 4
  • Ip Address
    115.118.0.147
  • Page Size
    114.3 KB
  • Images
    0 GIF, 1 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    :: Andhra Pradesh Public Service Commission ::
  • Meta Keyword
  • Meta Description
    Andhra Pradesh Public Service Commission Powered by Centre for Good Governance      Main Website All Mark lists All Interview lists All Selection lists          Notifications Click Here                 Press Notes Click Here                        ...

Technical Analysis



  • Webserver
    CGG Web Server
  • Ip Address
    115.118.0.147
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from apspsc.gov.in.

HTML Analysis

  • pragma: No-cache
  • cache-control: no-cache
  • expires: Thu, 01 Jan 1970 05:30:00 IST
  • etag: W/"117341-1358424713000"
  • last-modified: Thu, 17 Jan 2013 12:11:53 GMT
  • content-type: text/html
  • content-length: 117341
  • date: Fri, 18 Jan 2013 14:34:22 GMT
  • server: CGG Web Server
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Access to .IN WHOIS information is provided to assist persons in
determining the contents of a domain name registration record in the
.IN registry database. The data in this record is provided by
.IN Registry for informational purposes only, and .IN does not
guarantee its accuracy. This service is intended only for query-based
access. You agree that you will use this data only for lawful purposes
and that, under no circumstances will you use this data to: (a) allow,
enable, or otherwise support the transmission by e-mail, telephone, or
facsimile of mass unsolicited, commercial advertising or solicitations
to entities other than the data recipient's own existing customers; or
(b) enable high volume, automated, electronic processes that send
queries or data to the systems of Registry Operator, a Registrar, or
Afilias except as reasonably necessary to register domain names or
modify existing registrations. All rights reserved. .IN reserves
the right to modify these terms at any time. By submitting this query,
you agree to abide by this policy.

Domain ID:D3067231-AFIN
Domain Name:APSPSC.GOV.IN
Created On:29-Jul-2008 06:04:56 UTC
Last Updated On:06-Sep-2012 06:05:21 UTC
Expiration Date:29-Jul-2014 06:04:56 UTC
Sponsoring Registrar:National Informatics Centre (R12-AFIN)
Status:OK
Registrant ID:JxL2kZayF3
Registrant Name:Harpreet Singh, I.A.S
Registrant Organization:Andhra Pradesh Public Service Commission
Registrant Street1:O/o APPSC Prathibha Bhavan
Registrant Street2:M.J.Road Nampally
Registrant Street3:
Registrant City:Hyderabad
Registrant State/Province:Andhra Pradesh
Registrant Postal Code:500001
Registrant Country:IN
Registrant Phone:+91.24743405
Registrant Phone Ext.:
Registrant FAX:+91.24601664
Registrant FAX Ext.:
Registrant Email: email
Admin ID:JxL2kZayF3
Admin Name:Harpreet Singh, I.A.S
Admin Organization:Andhra Pradesh Public Service Commission
Admin Street1:O/o APPSC Prathibha Bhavan
Admin Street2:M.J.Road Nampally
Admin Street3:
Admin City:Hyderabad
Admin State/Province:Andhra Pradesh
Admin Postal Code:500001
Admin Country:IN
Admin Phone:+91.24743405
Admin Phone Ext.:
Admin FAX:+91.24601664
Admin FAX Ext.:
Admin Email: email
Tech ID:JxL2kZayF3CJIYXT
Tech Name:Manager Networks
Tech Organization:CGG
Tech Street1:Rd. No 25,
Tech Street2:Jubilee Hills
Tech Street3:
Tech City:Hyderabad
Tech State/Province:Andhra Pradesh
Tech Postal Code:500033
Tech Country:IN
Tech Phone:+91.23541907
Tech Phone Ext.:
Tech FAX:
Tech FAX Ext.:
Tech Email: email
Name Server:NS1.CGG.GOV.IN
Name Server:NS2.CGG.GOV.IN
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
DNSSEC:Unsigned


DNS Analysis


DNS servers
ns2.cgg.gov.in [115.118.0.132]
ns1.cgg.gov.in [196.12.55.2]
Query for DNS records for apspsc.gov.in failed: Timed out

DNS Records

IP 115.118.0.147 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 133 Errors
  • 22 Warnings
Ratio Text/Html
  • 0.4001503939295541
Message Error
  • Error Line 135, Column 31: there is no attribute "bordercolor"
    		cellspacing="0" bordercolor="#F3F3F3" bgcolor="#FFFFFF">

    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 142, Column 57: there is no attribute "height"
    					<table align="right" border="0" width="95%" height="58%"

    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 148, Column 64: required attribute "alt" not specified
    										src="http://apspsc.gov.in/APPSCLOGO.jpg" border="0" /> </a></td>

    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 172, Column 10: S separator in comment declaration
    					<!-- Google translate -->

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 172, Column 11: invalid comment declaration: found name start character outside comment but inside comment declaration
    					<!-- Google translate -->
  • Info Line 171, Column 5: comment declaration started here
    				<!--<td align="right" bgcolor="white" valign="middle">
  • Error Line 172, Column 12: character data is not allowed here
    					<!-- Google translate -->

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 261, Column 66: document type does not allow element "td" here; assuming missing "tr" start-tag
    						<td width="100%" valign="top" align="justify" colspan="2" />
  • Error Line 263, Column 28: document type does not allow element "table" here; missing one of "th", "td" start-tag
    						<table width="100%" />

    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 263, Column 28: end tag for "table" which is not finished
    						<table width="100%" />

    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 263, Column 28: end tag for "table" which is not finished
    						<table width="100%" />

    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 284, Column 43: document type does not allow element "tr" here
    						<tr align="center" bgcolor="#e4e8f0">

    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 302, Column 25: document type does not allow element "tr" here
    						<tr align="center">

    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 303, Column 42: there is no attribute "size"
    							<td align="left" colspan="5" size="2"></td>

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

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

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

  • Warning Line 529, Column 72: multiple comments in comment declaration
    													<font style="font-family: Arial;" color="RED" size="2"><b>-----</b>
  • Warning Line 562, Column 72: multiple comments in comment declaration
    													<font style="font-family: Arial;" color="RED" size="2"><b>-----</b>
  • Warning Line 596, Column 72: multiple comments in comment declaration
    													<font style="font-family: Arial;" color="RED" size="2"><b>-----</b>
  • Warning Line 628, Column 72: multiple comments in comment declaration
    													<font style="font-family: Arial;" color="RED" size="2"><b>-----</b>
  • Warning Line 635, Column 16: multiple comments in comment declaration
    									</tr> -->
  • Error Line 641, Column 12: character data is not allowed here
    					&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 650, Column 20: document type does not allow element "a" here; missing one of "th", "td" start-tag
    					target="blank"> <font size="2" style="font-family: Arial;"

    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 651, Column 22: element "B" undefined
    						color="blue"><B>All Mark lists </B></font> </a> &nbsp;&nbsp; <a

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 651, Column 61: character data is not allowed here
    						color="blue"><B>All Mark lists </B></font> </a> &nbsp;&nbsp; <a

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 652, Column 81: cannot generate system identifier for general entity "type"
    …f="http://website.apspsc.gov.in/listreport.appsc?flag=Interview%20Lists&type=1"

    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 652, Column 81: general entity "type" not defined and no default entity
    …f="http://website.apspsc.gov.in/listreport.appsc?flag=Interview%20Lists&type=1"

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

  • Warning Line 652, Column 85: reference not terminated by REFC delimiter
    …f="http://website.apspsc.gov.in/listreport.appsc?flag=Interview%20Lists&type=1"

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

  • Warning Line 652, Column 85: reference to external entity in attribute value
    …f="http://website.apspsc.gov.in/listreport.appsc?flag=Interview%20Lists&type=1"

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

  • Error Line 652, Column 85: reference to entity "type" for which no system identifier could be generated
    …f="http://website.apspsc.gov.in/listreport.appsc?flag=Interview%20Lists&type=1"

    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 652, Column 80: entity was defined here
    …f="http://website.apspsc.gov.in/listreport.appsc?flag=Interview%20Lists&type=1"
  • Error Line 653, Column 20: document type does not allow element "a" here; missing one of "th", "td" start-tag
    					target="blank"> <font size="2" style="font-family: Arial;"

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

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

  • Error Line 654, Column 22: element "B" undefined
    						color="blue"><B>All Interview lists </B></font> </a>&nbsp;&nbsp; <a

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 654, Column 65: character data is not allowed here
    						color="blue"><B>All Interview lists </B></font> </a>&nbsp;&nbsp; <a

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 655, Column 85: reference not terminated by REFC delimiter
    …f="http://website.apspsc.gov.in/listreport.appsc?flag=Selection%20Lists&type=1"

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

  • Warning Line 655, Column 85: reference to external entity in attribute value
    …f="http://website.apspsc.gov.in/listreport.appsc?flag=Selection%20Lists&type=1"

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

  • Error Line 655, Column 85: reference to entity "type" for which no system identifier could be generated
    …f="http://website.apspsc.gov.in/listreport.appsc?flag=Selection%20Lists&type=1"

    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 652, Column 80: entity was defined here
    …f="http://website.apspsc.gov.in/listreport.appsc?flag=Interview%20Lists&type=1"
  • Error Line 656, Column 20: document type does not allow element "a" here; missing one of "th", "td" start-tag
    					target="blank"> <font size="2" style="font-family: Arial;"

    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 657, Column 22: element "B" undefined
    						color="blue"><B>All Selection lists </B></font> </a> <font size="2"

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 658, Column 46: document type does not allow element "font" here; missing one of "th", "td" start-tag
    …yle="font-family: Arial;" color="blue"><b>&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;…

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

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

  • Error Line 660, Column 11: end tag for "b" omitted, but OMITTAG NO was specified
    				</font></td>

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

  • Info Line 658, Column 47: start tag was here
    …le="font-family: Arial;" color="blue"><b>&nbsp;&nbsp;&nbsp;<br />&nbsp;&nbsp;&…
  • Error Line 660, Column 16: end tag for "tr" omitted, but OMITTAG NO was specified
    				</font></td>

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

  • Info Line 261, Column 7: start tag was here
    						<td width="100%" valign="top" align="justify" colspan="2" />
  • Error Line 660, Column 16: end tag for "table" omitted, but OMITTAG NO was specified
    				</font></td>

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

  • Info Line 211, Column 6: start tag was here
    					<table align="center" border="0" cellpadding="1" cellspacing="0"
  • Error Line 670, Column 16: end tag for "b" omitted, but OMITTAG NO was specified
    									</font>

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

  • Info Line 669, Column 66: start tag was here
    …				<font size="2" style="font-family: Arial;" color="blue"><b>&nbsp;Results : 
  • Error Line 676, Column 10: document type does not allow element "tr" here
    						<tr>

    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 702, Column 10: end tag for "table" omitted, but OMITTAG NO was specified
    					</tr>

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

  • Info Line 680, Column 9: start tag was here
    								<table width="100%">
  • Error Line 702, Column 10: end tag for "td" omitted, but OMITTAG NO was specified
    					</tr>

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

  • Info Line 678, Column 8: start tag was here
    							<td width="100%" colspan="2">
  • Error Line 703, Column 30: there is no attribute "height"
    <tr bgcolor="#e4e8f0" height="10">

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

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

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

  • Error Line 703, Column 34: document type does not allow element "tr" here
    <tr bgcolor="#e4e8f0" height="10">

    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 709, Column 50: document type does not allow element "td" here
    													<td align="center" bgcolor="#d7e2f4"><a

    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 713, Column 28: end tag for "b" omitted, but OMITTAG NO was specified
    																							</td>

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

  • Info Line 711, Column 38: start tag was here
    															color="red" size="2"> <b>Selection List
  • Error Line 713, Column 28: end tag for "font" omitted, but OMITTAG NO was specified
    																							</td>

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

  • Info Line 710, Column 83: start tag was here
    …						href="http://website.apspsc.gov.in/Documents/SELECTIONLIST/194.pdf"><font
  • Error Line 713, Column 28: end tag for "a" omitted, but OMITTAG NO was specified
    																							</td>

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

  • Info Line 709, Column 51: start tag was here
    													<td align="center" bgcolor="#d7e2f4"><a
  • Error Line 714, Column 5: end tag for "font" omitted, but OMITTAG NO was specified
    </tr>

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

  • Info Line 706, Column 16: start tag was here
    															<font color="black" size="2">Noti.No. 50/2011, Assistant Social …
  • Error Line 714, Column 5: end tag for "span" omitted, but OMITTAG NO was specified
    </tr>

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

  • Info Line 705, Column 46: start tag was here
    													<td align="center" height="25"> <span class="style2">
  • Error Line 714, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

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

  • Info Line 705, Column 14: start tag was here
    													<td align="center" height="25"> <span class="style2">
  • Error Line 715, Column 34: document type does not allow element "tr" here
    <tr bgcolor="#e4e8f0" height="10">

    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 718, Column 63: character "&" is the first character of a delimiter but occurred as data
    …or="black" size="2">Noti. No. 18/2011 &15/2011 Group-I Services Main Examinati…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 718, Column 115: cannot generate system identifier for general entity "GENERAL"
    …011 &15/2011 Group-I Services Main Examination(LIMITED &GENERAL RECRUITMENT)   

    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 718, Column 115: general entity "GENERAL" not defined and no default entity
    …011 &15/2011 Group-I Services Main Examination(LIMITED &GENERAL RECRUITMENT)   

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

  • Warning Line 718, Column 122: reference not terminated by REFC delimiter
    …011 &15/2011 Group-I Services Main Examination(LIMITED &GENERAL RECRUITMENT)   

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

  • Error Line 718, Column 122: reference to entity "GENERAL" for which no system identifier could be generated
    …011 &15/2011 Group-I Services Main Examination(LIMITED &GENERAL RECRUITMENT)   

    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 718, Column 114: entity was defined here
    …011 &15/2011 Group-I Services Main Examination(LIMITED &GENERAL RECRUITMENT)   
  • Error Line 721, Column 50: document type does not allow element "td" here
    													<td align="center" bgcolor="#d7e2f4"><a

    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 730, Column 34: element "BR" undefined
    																	</b> </font><BR/><BR/>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 730, Column 39: element "BR" undefined
    																	</b> </font><BR/><BR/>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 731, Column 74: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    							<a href="http://website.apspsc.gov.in/Documents/PRESSNOTE/390.pdf"><font

    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 732, Column 59: end tag for "font" omitted, but OMITTAG NO was specified
    															color="red" size="2"> <b>Press Note</b> </a></font> </a>

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

  • Info Line 731, Column 75: start tag was here
    							<a href="http://website.apspsc.gov.in/Documents/PRESSNOTE/390.pdf"><font
  • Error Line 732, Column 66: end tag for "a" omitted, but OMITTAG NO was specified
    															color="red" size="2"> <b>Press Note</b> </a></font> </a>

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

  • Info Line 721, Column 51: start tag was here
    													<td align="center" bgcolor="#d7e2f4"><a
  • Error Line 732, Column 66: end tag for "td" omitted, but OMITTAG NO was specified
    															color="red" size="2"> <b>Press Note</b> </a></font> </a>

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

  • Info Line 721, Column 14: start tag was here
    													<td align="center" bgcolor="#d7e2f4"><a
  • Error Line 732, Column 71: end tag for element "a" which is not open
    															color="red" size="2"> <b>Press Note</b> </a></font> </a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 734, Column 12: end tag for "span" omitted, but OMITTAG NO was specified
    							</td>

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

  • Info Line 717, Column 46: start tag was here
    													<td align="center" height="25"> <span class="style2">
  • Error Line 736, Column 34: document type does not allow element "tr" here
    <tr bgcolor="#e4e8f0" height="10">

    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 742, Column 50: document type does not allow element "td" here
    													<td align="center" bgcolor="#d7e2f4"><a

    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 746, Column 28: end tag for "b" omitted, but OMITTAG NO was specified
    																							</td>

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

  • Info Line 744, Column 38: start tag was here
    															color="red" size="2"> <b>Marks List
  • Error Line 746, Column 28: end tag for "font" omitted, but OMITTAG NO was specified
    																							</td>

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

  • Info Line 743, Column 80: start tag was here
    …									href="http://website.apspsc.gov.in/Documents/MARKSLIST1/180.pdf"><font
  • Error Line 746, Column 28: end tag for "a" omitted, but OMITTAG NO was specified
    																							</td>

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

  • Info Line 742, Column 51: start tag was here
    													<td align="center" bgcolor="#d7e2f4"><a
  • Error Line 747, Column 5: end tag for "font" omitted, but OMITTAG NO was specified
    </tr>

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

  • Info Line 739, Column 16: start tag was here
    															<font color="black" size="2">Noti.No.11/2009 TO 38/2008 Group-II…
  • Error Line 747, Column 5: end tag for "span" omitted, but OMITTAG NO was specified
    </tr>

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

  • Info Line 738, Column 46: start tag was here
    													<td align="center" height="25"> <span class="style2">
  • Error Line 747, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

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

  • Info Line 738, Column 14: start tag was here
    													<td align="center" height="25"> <span class="style2">
  • Error Line 873, Column 8: end tag for "tr" omitted, but OMITTAG NO was specified
    </table>

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

  • Info Line 665, Column 6: start tag was here
    					<tr>
  • Error Line 873, Column 8: end tag for "tbody" omitted, but OMITTAG NO was specified
    </table>

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

  • Info Line 137, Column 3: start tag was here
    		<tbody>
  • Error Line 918, Column 7: document type does not allow element "tr" here; assuming missing "table" start-tag
    			<tr>
  • Error Line 1261, Column 15: invalid comment declaration: found character "<" outside comment but inside comment declaration
    										<!--<tr bgcolor="#E6E6E6">

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1172, Column 7: comment declaration started here
    						<!--<tr bgcolor="#E6E6E6">
  • Error Line 1261, Column 16: character data is not allowed here
    										<!--<tr bgcolor="#E6E6E6">

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 1263, Column 58: document type does not allow element "td" here; assuming missing "tr" start-tag
    											<td align="center" rowspan="5" valign="middle"><a
  • Error Line 1274, Column 20: there is no attribute "align"
    													align="right" valign="top" /> <br />Exam Dates:29/07/2012

    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 1274, Column 35: there is no attribute "valign"
    													align="right" valign="top" /> <br />Exam Dates:29/07/2012

    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 1276, Column 16: end tag for "font" omitted, but OMITTAG NO was specified
    											</td>

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

  • Info Line 1269, Column 55: start tag was here
    											<td width="170" align="center" rowspan="5"><font
  • Error Line 1308, Column 22: document type does not allow element "tr" here
    <tr bgcolor="#E6E6E6">

    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 1323, Column 16: end tag for "font" omitted, but OMITTAG NO was specified
    											</td>

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

  • Info Line 1317, Column 55: start tag was here
    											<td width="170" align="center" rowspan="5"><font
  • Error Line 1354, Column 32: document type does not allow element "tr" here
    										<tr bgcolor="#3162B5">

    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 1360, Column 32: document type does not allow element "tr" here
    										<tr bgcolor="#E6E6E6">

    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 1910, Column 5: S separator in comment declaration
    <!--

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 1911, Column 1: S separator in comment declaration

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 1912, Column 1: S separator in comment declaration
    				<tr bgcolor="#E6E6E6">

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 1912, Column 2: S separator in comment declaration
    				<tr bgcolor="#E6E6E6">

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 1912, Column 3: S separator in comment declaration
    				<tr bgcolor="#E6E6E6">

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 1912, Column 4: S separator in comment declaration
    				<tr bgcolor="#E6E6E6">

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 1912, Column 5: invalid comment declaration: found character "<" outside comment but inside comment declaration
    				<tr bgcolor="#E6E6E6">

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 1679, Column 7: comment declaration started here
    						<!--   <tr bgcolor="#E6E6E6">
  • Error Line 1914, Column 58: document type does not allow element "td" here
    											<td align="center" rowspan="5" valign="middle">

    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 1923, Column 54: document type does not allow element "td" here
    											<td width="170" align="center" rowspan="5">

    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 1933, Column 16: end tag for "font" omitted, but OMITTAG NO was specified
    											</td>

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

  • Info Line 1925, Column 13: start tag was here
    												<font style="font-family: Arial;" size="2"><b>
  • Error Line 1935, Column 42: document type does not allow element "td" here
    											<td align="center" rowspan="5">

    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 1943, Column 42: document type does not allow element "td" here
    											<td align="center" rowspan="5">

    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 1951, Column 42: document type does not allow element "td" here
    											<td align="center" rowspan="5">

    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 1958, Column 48: document type does not allow element "td" here
    											<td align="center" bgcolor="#E6E6E6">

    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 1971, Column 15: end tag for "div" omitted, but OMITTAG NO was specified
    										</tr>

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

  • Info Line 1364, Column 13: start tag was here
    												<div align="center">
  • Error Line 1971, Column 15: end tag for "td" omitted, but OMITTAG NO was specified
    										</tr>

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

  • Info Line 1362, Column 12: start tag was here
    											<td align="center">
  • Error Line 1973, Column 32: document type does not allow element "tr" here
    										<tr bgcolor="#3162B5">

    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 1981, Column 32: document type does not allow element "tr" here
    										<tr bgcolor="#E6E6E6">

    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 1999, Column 32: document type does not allow element "tr" here
    										<tr bgcolor="#3162B5">

    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 2006, Column 32: document type does not allow element "tr" here
    										<tr bgcolor="#E6E6E6">

    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 2026, Column 23: document type does not allow element "tr" here
     <tr bgcolor="#E6E6E6">

    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 2046, Column 16: end tag for "font" omitted, but OMITTAG NO was specified
    											</td>

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

  • Info Line 2039, Column 13: start tag was here
    												<font style="font-family: Arial;" size="2"><b>
  • Error Line 2086, Column 32: document type does not allow element "tr" here
    										<tr bgcolor="#3162B5">

    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 2094, Column 32: document type does not allow element "tr" here
    										<tr bgcolor="#E6E6E6">

    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 2112, Column 32: document type does not allow element "tr" here
    										<tr bgcolor="#3162B5">

    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 2119, Column 32: document type does not allow element "tr" here
    										<tr bgcolor="#E6E6E6">

    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 2136, Column 16: character data is not allowed here
    										</tr>-->

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 3202, Column 13: "tr" not finished but containing element ended
    					</table></td>
  • Error Line 3202, Column 13: end tag for "tr" omitted, but OMITTAG NO was specified
    					</table></td>

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

  • Info Line 1307, Column 11: start tag was here
    										<tr bgcolor="#3162B5">
  • Error Line 3396, Column 39: document type does not allow element "table" here; missing one of "th", "td" start-tag
    				<table width="100%" align="center">

    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 3405, Column 13: end tag for "b" omitted, but OMITTAG NO was specified
    						</font></td>

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

  • Info Line 3400, Column 67: start tag was here
    …d><font size="2" style="font-family: Arial;" color="blue"><b>&nbsp;&nbsp;&nbsp;
  • Error Line 3408, Column 10: end tag for "table" omitted, but OMITTAG NO was specified
    					</tr>

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

  • Info Line 3396, Column 5: start tag was here
    				<table width="100%" align="center">
  • Error Line 3408, Column 10: end tag for "tr" which is not finished
    					</tr>

    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 3609, Column 16: ID "dateformat" already defined
    											id="dateformat" target="_blank"><font color="#3367be"><b>CLICK

    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 3568, Column 53: ID "dateformat" first defined here
    											href="http://website.apspsc.gov.in/" id="dateformat"
  • Error Line 3622, Column 16: ID "dateformat" already defined
    											id="dateformat" target="_blank"><font color="#3367be"><b>CLICK

    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 3568, Column 53: ID "dateformat" first defined here
    											href="http://website.apspsc.gov.in/" id="dateformat"
  • Error Line 3635, Column 16: ID "dateformat" already defined
    											id="dateformat" target="_blank"><font color="#3367be"><strong>CLICK

    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 3568, Column 53: ID "dateformat" first defined here
    											href="http://website.apspsc.gov.in/" id="dateformat"
  • Error Line 3648, Column 16: ID "dateformat" already defined
    											id="dateformat" target="_blank"><font color="#3367be"><strong>CLICK

    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 3568, Column 53: ID "dateformat" first defined here
    											href="http://website.apspsc.gov.in/" id="dateformat"
  • Error Line 3660, Column 16: ID "dateformat" already defined
    											id="dateformat" target="_blank"><font color="#3367be"><strong>CLICK

    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 3568, Column 53: ID "dateformat" first defined here
    											href="http://website.apspsc.gov.in/" id="dateformat"
  • Error Line 3673, Column 16: ID "dateformat" already defined
    											id="dateformat" target="_blank"><font color="#3367be"><strong>CLICK

    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 3568, Column 53: ID "dateformat" first defined here
    											href="http://website.apspsc.gov.in/" id="dateformat"
  • Error Line 3686, Column 16: ID "dateformat" already defined
    											id="dateformat" target="_blank"><font color="#3367be"><strong>CLICK

    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 3568, Column 53: ID "dateformat" first defined here
    											href="http://website.apspsc.gov.in/" id="dateformat"
  • Error Line 3699, Column 16: ID "dateformat" already defined
    											id="dateformat" target="_blank"><font color="#3367be"><strong>CLICK

    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 3568, Column 53: ID "dateformat" first defined here
    											href="http://website.apspsc.gov.in/" id="dateformat"
  • Error Line 3711, Column 16: ID "dateformat" already defined
    											id="dateformat" target="_blank"><font color="#3367be"><b>CLICK

    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 3568, Column 53: ID "dateformat" first defined here
    											href="http://website.apspsc.gov.in/" id="dateformat"
  • Error Line 3726, Column 16: ID "dateformat" already defined
    											id="dateformat" target="_blank"><font color="#3367be"><strong>CLICK

    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 3568, Column 53: ID "dateformat" first defined here
    											href="http://website.apspsc.gov.in/" id="dateformat"
  • Error Line 3732, Column 72: document type does not allow element "td" here; assuming missing "tr" start-tag
    									<td class="style2" align="right" bgcolor="#e6e6e6" height="25">
  • Error Line 3739, Column 15: ID "dateformat" already defined
    										id="dateformat" target="_blank"><font color="#3367be"><strong>CLICK

    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 3568, Column 53: ID "dateformat" first defined here
    											href="http://website.apspsc.gov.in/" id="dateformat"
  • Error Line 3763, Column 15: end tag for "font" omitted, but OMITTAG NO was specified
    										</td>

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

  • Info Line 3760, Column 62: start tag was here
    										<td class="style2" align="right" bgcolor="#3162b5"><font
  • Error Line 3767, Column 16: ID "dateformat" already defined
    											id="dateformat" target="_blank"><font color="#3367be"><b>CLICK

    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 3568, Column 53: ID "dateformat" first defined here
    											href="http://website.apspsc.gov.in/" id="dateformat"
  • Error Line 3797, Column 14: end tag for "tbody" omitted, but OMITTAG NO was specified
    									</tr>

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

  • Info Line 3559, Column 9: start tag was here
    								<tbody>
  • Error Line 3797, Column 14: end tag for "table" omitted, but OMITTAG NO was specified
    									</tr>

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

  • Info Line 3557, Column 8: start tag was here
    							<table width="95%" align="center">
  • Error Line 3797, Column 14: end tag for "td" omitted, but OMITTAG NO was specified
    									</tr>

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

  • Info Line 3555, Column 7: start tag was here
    						<td width="70%" valign="top">
  • Error Line 3953, Column 16: end tag for element "tbody" which is not open
    								</tbody>

    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 3955, Column 20: end tag for element "td" which is not open
    							</table></td>

    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 3963, Column 50: document type does not allow element "td" here
    						<td width="35%" align="center" valign="top">

    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 3998, Column 37: character "&" is the first character of a delimiter but occurred as data
    												: 10.30 A.M to 1.00 P.M & 1.30 P.M to 5 P.M on working days)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 4054, Column 10: end tag for element "tr" which is not open
    					</tr>

    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 4061, Column 12: end tag for element "table" which is not open
    				</table>

    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 4062, Column 9: end tag for element "td" which is not open
    				</td>

    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 4064, Column 8: end tag for element "tr" which is not open
    			</tr>

    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 4065, Column 9: end tag for element "table" which is not open
    	</table>

    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 4066, Column 10: end tag for "table" which is not finished
    	<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 4066, Column 10: end tag for "table" which is not finished
    	<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 4068, Column 15: there is no attribute "align"
    	<TABLE align="center">

    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 4068, Column 23: element "TABLE" undefined
    	<TABLE align="center">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 4099, Column 7: end tag for "td" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 4084, Column 4: start tag was here
    			<td align="center" height="16" colspan="3">
  • Error Line 4099, Column 7: end tag for "tr" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 4082, Column 3: start tag was here
    		<tr>
  • Error Line 4099, Column 7: end tag for "TABLE" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 4068, Column 2: start tag was here
    	<TABLE align="center">

Visitor Analysis

Daily Visitor
  • 14.350 visits
Daily Visitor

In Page Analysis