tin-nsdl.com

Tax Information Network of Income Tax Department Font Size : Home    Contact Us    Related Links    Disclaimer    Privacy Policy About TIN Services TIN Facilitation Centers Guided Tour Publications Downloads FAQ ...

Display Widget for this domain on your website. Click Here
This data was last updated from 08-02-2013 10:09:16  (update).

Overview Info

  • Domain Name
    tin-nsdl.com
  • Favicon
  • Alexa Rank
    #34711
  • Google Page Rank
    PR 6
  • Ip Address
    210.210.18.84
  • Page Size
    130.6 KB
  • Images
    31 GIF, 2 JPG, 16 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    TIN
  • Meta Keyword
  • Meta Description
    Tax Information Network of Income Tax Department Font Size : Home    Contact Us    Related Links    Disclaimer    Privacy Policy About TIN Services TIN Facilitation Centers Guided Tour Publications Downloads FAQ Customer Care e-TDS/e-TCS Overview ...

Technical Analysis



  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    210.210.18.84
  • Domain Age
    8 Years, 5 Months, 6 days.
  • Javascript Library
    prototype
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from tin-nsdl.com.

HTML Analysis

  • date: Fri, 08 Feb 2013 10:09:17 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • content-type: text/html
  • content-length: 128296
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: TIN-NSDL.COM

Registrant:
NSDL
Mr. Kishore ( email )
Trade World, 4th floor,
Kamala Mills Compound,
Senapati Bapat Marg, Lower Parel West
Mumbai
null,400013
IN
Tel. +91.2224994200

Creation Date: 18-Aug-2004
Expiration Date: 18-Aug-2018

Domain servers in listed order:
ns1.netcore.co.in
ns2.netcore.co.in

Administrative Contact:
NSDL
Mr. Kishore ( email )
Trade World, 4th floor,
Kamala Mills Compound,
Senapati Bapat Marg, Lower Parel West
Mumbai
null,400013
IN
Tel. +91.2224994200

Technical Contact:
NSDL
Mr. Kishore ( email )
Trade World, 4th floor,
Kamala Mills Compound,
Senapati Bapat Marg, Lower Parel West
Mumbai
null,400013
IN
Tel. +91.2224994200

Billing Contact:
Surebrowse
Sudipta Ghosh ( email )
Vikhroli
Mumbai
,400083
IN
Tel. +91.2234260303

Status:ACTIVE

DNS Analysis


DNS servers
ns1.netcore.co.in [202.162.229.11]
ns2.netcore.co.in [202.162.240.2]


DNS Records

Answer records
tin-nsdl.com SOA
server: tin-nsdl.com
email: Postmaster@tin-nsdl.com
serial: 9903193
refresh: 10800
retry: 3600
expire: 86400
minimum ttl: 600
600s
tin-nsdl.com NS  mumdns.tatanova.com 600s
tin-nsdl.com NS  ns2.netcore.co.in 600s
tin-nsdl.com NS  ns1.netcore.co.in 600s
tin-nsdl.com A 210.210.18.84 600s
tin-nsdl.com MX
preference: 5
exchange: mx1.netcore.co.in
600s
tin-nsdl.com MX
preference: 10
exchange: mx3.netcore.co.in
600s

Authority records

Additional records
ns1.netcore.co.in A 202.162.229.11 86400s
ns2.netcore.co.in A 202.162.240.2 86400s
mx1.netcore.co.in A 202.162.229.17 86400s
mx3.netcore.co.in A 202.162.240.122 86400s

IP 210.210.18.84 Analysis

  • Country Code
    IN
  • Country Code3
    IND
  • Country Name
    India
  • City
    Hyderabad
  • Continent Code
    AS
  • Latitude
    17.3753
  • Longitude
    78.4744
  • % [whois.apnic.net node-7]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 210.210.18.0 - 210.210.18.254
    netname: Sifyinfranet
    country: IN
    descr: SIFY INFRASTRUCTURE
    admin-c: HS51-AP
    tech-c: HS51-AP
    status: ASSIGNED NON-PORTABLE
    changed: ipadmin@sifycorp.com 20060718
    mnt-by: MAINT-IN-SIFY
    source: APNIC

    route: 210.210.18.0/24
    descr: Sify ip address space
    origin: AS9583
    mnt-by: MAINT-IN-SIFY
    changed: ipadmin@sifycorp.com 20111021
    source: APNIC

    person: Hostmaster Satyam Infoway
    nic-hdl: HS51-AP
    e-mail: ipadmin@sifycorp.com
    address: Sify Limited,
    address: Second Floor, Tidel Park,
    address: No.4,Canal Bank Road,
    address: Taramani, Chennai - 600113
    phone: +91-44-22540770
    fax-no: +91-44-22540771
    country: IN
    changed: ipadmin@sifycorp.com 20040818
    mnt-by: MAINT-IN-SIFY
    changed: hm-changed@apnic.net 20060117
    source: APNIC


Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 83 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.6758142768503914
Message Error
  • Error Line 25, Column 55: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="shortcut icon" type="image/x-icon" href="">

    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 25, Column 1: start tag was here
    <link rel="shortcut icon" type="image/x-icon" href="">
  • Warning Line 53, Column 27: character "&" is the first character of a delimiter but occurred as data
        else if( window.opera && window.print) 

    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 53, Column 28: character "&" is the first character of a delimiter but occurred as data
        else if( window.opera && window.print) 

    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 96, Column 75: there is no attribute "height"
    				<table cellspacing="0" width="100%" border="0" cellpadding="0" height="520">

    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 394, Column 14: end tag for element "li" which is not open
    									</li>

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

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

  • Error Line 605, Column 215: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …"menu-tl" style="text-decoration:none">eTutorial – TAN Registration</a></div><…

    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 605, Column 247: end tag for "div" omitted, but OMITTAG NO was specified
    …nu-tl" style="text-decoration:none">eTutorial – TAN Registration</a></div></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 605, Column 166: start tag was here
    …th=360,height=150,top=325,left=375')"><div class="menu-tl" style="text-decorat…
  • Error Line 605, Column 253: end tag for "td" omitted, but OMITTAG NO was specified
    …nu-tl" style="text-decoration:none">eTutorial – TAN Registration</a></div></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 605, Column 7: start tag was here
    						<td valign="top"><a href="#" onclick="window.open('https://www.tin-nsdl.c…
  • Error Line 605, Column 253: end tag for "tr" omitted, but OMITTAG NO was specified
    …nu-tl" style="text-decoration:none">eTutorial – TAN Registration</a></div></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 579, Column 6: start tag was here
    					<tr>
  • Error Line 605, Column 253: end tag for "table" omitted, but OMITTAG NO was specified
    …nu-tl" style="text-decoration:none">eTutorial – TAN Registration</a></div></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 578, Column 5: start tag was here
    				<table cellspacing="0" style="width: 100%;" border="0" cellpadding="0">
  • Error Line 605, Column 258: end tag for element "td" which is not open
    …nu-tl" style="text-decoration:none">eTutorial – TAN Registration</a></div></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 609, 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 610, Column 9: document type does not allow element "tr" here; assuming missing "table" start-tag
    					<tr>
  • Error Line 808, Column 123: there is no attribute "onMouseover"
    …ng-bottom:10px;"><marquee onMouseover="this.scrollAmount=0" onMouseout="this.s…

    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 808, Column 156: there is no attribute "onMouseout"
    …over="this.scrollAmount=0" onMouseout="this.scrollAmount=4" scrollAmount="4" w…

    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 808, Column 191: there is no attribute "scrollAmount"
    …ut="this.scrollAmount=4" scrollAmount="4" width="900">Due to maintenance activ…

    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 808, Column 201: there is no attribute "width"
    …crollAmount=4" scrollAmount="4" width="900">Due to maintenance activity, onlin…

    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 808, Column 206: element "marquee" undefined
    …Amount=4" scrollAmount="4" width="900">Due to maintenance activity, online ser…

    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 816, Column 29: required attribute "action" not specified
    						<form name="nsdllogin">

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

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

  • Error Line 819, Column 127: end tag for "input" omitted, but OMITTAG NO was specified
    …t name="radiologin" id="radiologin" type="radio" value="tanregistration"> </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 819, Column 49: start tag was here
    …d width="22" height="20" valign="top"><input name="radiologin" id="radiologin"…
  • Error Line 823, Column 68: ID "radiologin" already defined
    …ht="20" ><input name="radiologin" id="radiologin" type="radio" value="eTDSTCS"…

    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 819, Column 78: ID "radiologin" first defined here
    …gn="top"><input name="radiologin" id="radiologin" type="radio" value="tanregis…
  • Error Line 823, Column 113: end tag for "input" omitted, but OMITTAG NO was specified
    …0" ><input name="radiologin" id="radiologin" type="radio" value="eTDSTCS"></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 823, Column 39: start tag was here
    								<td valign="top" height="20" ><input name="radiologin" id="radiologin" …
  • Error Line 827, Column 68: ID "radiologin" already defined
    …ht="20" ><input name="radiologin" id="radiologin" type="radio" value="vtaxstat…

    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 819, Column 78: ID "radiologin" first defined here
    …gn="top"><input name="radiologin" id="radiologin" type="radio" value="tanregis…
  • Error Line 827, Column 119: end tag for "input" omitted, but OMITTAG NO was specified
    …nput name="radiologin" id="radiologin" type="radio" value="vtaxstatement"></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 827, Column 39: start tag was here
    								<td valign="top" height="20" ><input name="radiologin" id="radiologin" …
  • Error Line 831, Column 68: ID "radiologin" already defined
    …ht="20" ><input name="radiologin" id="radiologin" type="radio" value="tinfc"><…

    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 819, Column 78: ID "radiologin" first defined here
    …gn="top"><input name="radiologin" id="radiologin" type="radio" value="tanregis…
  • Error Line 831, Column 111: end tag for "input" omitted, but OMITTAG NO was specified
    …"20" ><input name="radiologin" id="radiologin" type="radio" value="tinfc"></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 831, Column 39: start tag was here
    								<td valign="top" height="20" ><input name="radiologin" id="radiologin" …
  • Error Line 835, Column 68: ID "radiologin" already defined
    …ht="20" ><input name="radiologin" id="radiologin" type="radio" value="panverfi…

    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 819, Column 78: ID "radiologin" first defined here
    …gn="top"><input name="radiologin" id="radiologin" type="radio" value="tanregis…
  • Error Line 835, Column 116: end tag for "input" omitted, but OMITTAG NO was specified
    …ut name="radiologin" id="radiologin" type="radio" value="panverfication"> </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 835, Column 39: start tag was here
    								<td valign="top" height="20" ><input name="radiologin" id="radiologin" …
  • Error Line 839, Column 68: ID "radiologin" already defined
    …ht="20" ><input name="radiologin" id="radiologin" type="radio" value="AOAccoun…

    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 819, Column 78: ID "radiologin" first defined here
    …gn="top"><input name="radiologin" id="radiologin" type="radio" value="tanregis…
  • Error Line 839, Column 111: end tag for "input" omitted, but OMITTAG NO was specified
    …><input name="radiologin" id="radiologin" type="radio" value="AOAccount"> </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 839, Column 39: start tag was here
    								<td valign="top" height="20" ><input name="radiologin" id="radiologin" …
  • Error Line 843, Column 12: end tag for "form" omitted, but OMITTAG NO was specified
    						</div>

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

  • Info Line 816, Column 7: start tag was here
    						<form name="nsdllogin">
  • Error Line 906, Column 16: element "OPTION" undefined
    								<OPTION>Select</OPTION>

    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 907, Column 16: element "OPTION" undefined
    								<OPTION>Andaman & Nicobar</OPTION>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 907, Column 25: character "&" is the first character of a delimiter but occurred as data
    								<OPTION>Andaman & Nicobar</OPTION>

    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 908, Column 16: element "OPTION" undefined
    								<OPTION>Andhra Pradesh</OPTION>

    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 909, Column 16: element "OPTION" undefined
    								<OPTION>Arunachal Pradesh</OPTION>

    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 910, Column 16: element "OPTION" undefined
    								<OPTION>Assam</OPTION>

    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 911, Column 16: element "OPTION" undefined
    								<OPTION>Bihar</OPTION>

    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 912, Column 16: element "OPTION" undefined
    								<OPTION>Chandigarh</OPTION>

    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 913, Column 16: element "OPTION" undefined
    								<OPTION>Chhattisgarh</OPTION>

    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 914, Column 16: element "OPTION" undefined
    								<OPTION>Delhi</OPTION>

    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 915, Column 16: element "OPTION" undefined
    								<OPTION>Goa</OPTION>

    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 916, Column 16: element "OPTION" undefined
    								<OPTION>Gujarat</OPTION>

    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 917, Column 16: element "OPTION" undefined
    								<OPTION>Haryana</OPTION>

    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 918, Column 16: element "OPTION" undefined
    								<OPTION>Himachal Pradesh</OPTION>

    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 919, Column 16: element "OPTION" undefined
    								<OPTION>Jammu and Kashmir</OPTION>

    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 920, Column 16: element "OPTION" undefined
    								<OPTION>Jharkhand</OPTION>

    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 921, Column 16: element "OPTION" undefined
    								<OPTION>Karnataka</OPTION>

    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 922, Column 16: element "OPTION" undefined
    								<OPTION>Kerala</OPTION>

    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 923, Column 16: element "OPTION" undefined
    								<OPTION>Madhya Pradesh</OPTION>

    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 924, Column 16: element "OPTION" undefined
    								<OPTION>Maharashtra</OPTION>

    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 925, Column 16: element "OPTION" undefined
    								<OPTION>Manipur</OPTION>

    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 926, Column 16: element "OPTION" undefined
    								<OPTION>Meghalaya</OPTION>

    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 927, Column 16: element "OPTION" undefined
    								<OPTION>Mizoram</OPTION>

    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 928, Column 16: element "OPTION" undefined
    								<OPTION>Nagaland</OPTION>

    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 929, Column 16: element "OPTION" undefined
    								<OPTION>Orissa</OPTION>

    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 930, Column 16: element "OPTION" undefined
    								<OPTION>Pondicherry</OPTION>

    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 931, Column 16: element "OPTION" undefined
    								<OPTION>Punjab</OPTION>

    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 932, Column 16: element "OPTION" undefined
    								<OPTION>Rajasthan</OPTION>

    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 933, Column 16: element "OPTION" undefined
    								<OPTION>Tamil Nadu</OPTION>

    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 934, Column 16: element "OPTION" undefined
    								<OPTION>Tripura</OPTION>

    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 935, Column 16: element "OPTION" undefined
    								<OPTION>Uttar Pradesh</OPTION>

    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 936, Column 16: element "OPTION" undefined
    								<OPTION>Uttaranchal</OPTION>

    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 937, Column 16: element "OPTION" undefined
    								<OPTION>West Bengal</OPTION>

    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 938, Column 16: end tag for "select" which is not finished
    							</select>

    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 966, Column 59: end tag for "param" omitted, but OMITTAG NO was specified
                        <param name="movie" value="index.swf">

    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 966, Column 21: start tag was here
                        <param name="movie" value="index.swf">
  • Error Line 967, Column 56: end tag for "param" omitted, but OMITTAG NO was specified
                        <param name="quality" value="high">

    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 967, Column 21: start tag was here
                        <param name="quality" value="high">
  • Error Line 968, Column 32: there is no attribute "src"
                        <embed src="index.swf" quality="high" pluginspage="https://…

    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 968, Column 52: there is no attribute "quality"
    …       <embed src="index.swf" quality="high" pluginspage="https://www.macromed…

    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 968, Column 71: there is no attribute "pluginspage"
    …index.swf" quality="high" pluginspage="https://www.macromedia.com/go/getflashp…

    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 968, Column 123: there is no attribute "type"
    …acromedia.com/go/getflashplayer" type="application/x-shockwave-flash" width="5…

    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 968, Column 161: there is no attribute "width"
    …hplayer" type="application/x-shockwave-flash" width="594" height="166"></embed>

    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 968, Column 174: there is no attribute "height"
    …hplayer" type="application/x-shockwave-flash" width="594" height="166"></embed>

    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 968, Column 179: element "embed" undefined
    …hplayer" type="application/x-shockwave-flash" width="594" height="166"></embed>

    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 1128, Column 91: end tag for "br" omitted, but OMITTAG NO was specified
    …e="font-size:12px">Document Required for Making PAN <br>Application for :</div>

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

  • Info Line 1128, Column 87: start tag was here
    …e="font-size:12px">Document Required for Making PAN <br>Application for :</div>
  • Warning Line 1266, Column 130: character "&" is the first character of a delimiter but occurred as data
    …on4.0_310809.xls">File Format for Form 24Q (1st, 2nd & 3rd Quarters). </option>

    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 1271, Column 102: character "&" is the first character of a delimiter but occurred as data
    …le_File_24Q_new.zip">Sample file for Form 24Q (1st, 2nd & 3rd Quarter)</option>

    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 1330, Column 109: character "&" is the first character of a delimiter but occurred as data
    …n/termsandconditionsonlinefacilityforpan_2_r12.pdf">Terms & Conditions</option>

    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 1404, Column 81: character "&" is the first character of a delimiter but occurred as data
    …t"><a href="e-return/ereturn-responsibility.php">Role & Responsibility</a></td>

    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 1500, Column 88: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … src ="newfeatures.php" width="163" height="202" frameborder="0" scrolling=no> 
  • Error Line 1506, Column 49: there is no attribute "background"
    …e width="167" height="210" background="images/vcb.gif" style="background-repea…

    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 1511, Column 163: end tag for "br" omitted, but OMITTAG NO was specified
    …und-color:#EFEBDC;">Statistics of <br>Form 26AS viewed <!--img src="images/new…

    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 1511, Column 159: start tag was here
    …kground-color:#EFEBDC;">Statistics of <br>Form 26AS viewed <!--img src="images…
  • Error Line 1516, Column 125: element "B" undefined
    …2A; padding: 5px 8px; background-color:#F8F6EE;" width="67"><B>6.75 cr</B></td>

    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 1524, Column 125: element "B" undefined
    …2A; padding: 5px 8px; background-color:#F8F6EE;" width="67"><B>1.54 cr</B></td>

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

    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 1581, Column 6: end tag for element "div" which is not open
    </div>

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

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

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

    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 1593, Column 1: start tag was here
    <script type="text/javascript">
  • Error Line 1660, Column 12: end tag for "body" omitted, but OMITTAG NO was specified
    		</script>

    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 27, Column 1: start tag was here
    <body>
  • Error Line 1660, Column 12: end tag for "html" omitted, but OMITTAG NO was specified
    		</script>

    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 3, Column 1: start tag was here
    <html xmlns="http://www.w3.org/1999/xhtml">
  • Error Line 1660, Column 12: missing marked section end
    		</script>
  • Info Line 1594, Column 4: marked section started here
    // <![CDATA[

Visitor Analysis

Daily Visitor
  • 7.233 visits
Daily Visitor

In Page Analysis