Sun Aug 25 2013 04:30:43 GMT+0530 (IST) Consumer Login Forgot password?      Register Now? Home Distributor Login IndianOil Login HOME PRODUCTS INITIATIVES TRANSPARENCY PORTAL HOW DO I? Get a New Connection ? Register ...

indane.co.in
  • Domain Name
    indane.co.in
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #22163
  • Page Size
    70.1 KB
  • Ip Address
    111.118.213.60
  • Heading
    H1: 0, H2: 1, H3: 6, H4: 13, H5: 0, H6: 0
  • Images
    1 GIF, 30 JPG, 1 PNG

Website Meta Analysis

  • Title
    Indane Online : Online Gas Booking and Services
  • Meta Keyword
  • Meta Description
    Sun Aug 25 2013 04:30:43 GMT+0530 (IST) Consumer Login Forgot password?      Register Now? Home Distributor Login IndianOil Login HOME PRODUCTS INITIATIVES TRANSPARENCY PORTAL HOW DO I? Get a New Connection ? Register for Preferred Time ? How ...

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    111.118.213.60
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from indane.co.in.

HTML Analysis

  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-type: text/html
  • content-encoding: gzip
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-powered-by: ASP.NET
  • x-powered-by-plesk: PleskWin
  • date: Sat, 24 Aug 2013 23:00:43 GMT
  • connection: close
  • content-length: 20982
  • 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:D3577286-AFIN
Domain Name:INDANE.CO.IN
Created On:23-Apr-2009 12:30:20 UTC
Last Updated On:29-Jul-2012 04:49:17 UTC
Expiration Date:23-Apr-2019 12:30:20 UTC
Sponsoring Registrar:Net4India (R7-AFIN)
Status:CLIENT TRANSFER PROHIBITED
Registrant ID:N5R-1356842
Registrant Name:Deepak Singh Gehlot
Registrant Organization:C G Technosoft Pvt Ltd
Registrant Street1:Techno Centre Mandore Road Paota
Registrant Street2:
Registrant Street3:
Registrant City:Jodhpur
Registrant State/Province:Rajhasthan
Registrant Postal Code:342006
Registrant Country:IN
Registrant Phone:+91.9829021066
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant Email: email
Admin ID:N4R-697638697638
Admin Name:SHEETAL
Admin Organization:IOCL
Admin Street1:801-A,Anukampa Apartments,Malviya Nagar
Admin Street2:
Admin Street3:
Admin City:Jaipur
Admin State/Province:Rajhasthan
Admin Postal Code:302017
Admin Country:IN
Admin Phone:+91.12345678
Admin Phone Ext.:
Admin FAX:
Admin FAX Ext.:
Admin Email: email
Tech ID:N4R-697638697638
Tech Name:SHEETAL
Tech Organization:IOCL
Tech Street1:801-A,Anukampa Apartments,Malviya Nagar
Tech Street2:
Tech Street3:
Tech City:Jaipur
Tech State/Province:Rajhasthan
Tech Postal Code:302017
Tech Country:IN
Tech Phone:+91.12345678
Tech Phone Ext.:
Tech FAX:
Tech FAX Ext.:
Tech Email: email
Name Server:NS1.INDANE.CO.IN
Name Server:NS2.INDANE.CO.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
ns1.indane.co.in [111.118.215.61]
ns2.indane.co.in [111.118.215.61]


DNS Records

Answer records
indane.co.in A 111.118.215.211 86400s
indane.co.in NS  ns1.indane.co.in 86400s
indane.co.in NS  ns2.indane.co.in 86400s
indane.co.in SOA
server: ns1.indane.co.in
email: puneet@cgt.co.in
serial: 1349877834
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
86400s
indane.co.in MX
preference: 10
exchange: mail.indane.co.in
86400s
indane.co.in TXT v=spf1 +all 86400s

Authority records

Additional records
ns1.indane.co.in A 111.118.215.211 86400s
ns2.indane.co.in A 111.118.215.61 86400s
mail.indane.co.in A 111.118.215.211 86400s

IP 111.118.213.60 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 130 Errors
  • 46 Warnings
Ratio Text/Html
  • 0.4360178347498955
Message Error
  • Error Line 5, Column 40: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv='expires' content='0'>

    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 5, Column 1: start tag was here
    <meta http-equiv='expires' content='0'>
  • Error Line 6, Column 18: there is no attribute "HTTP-EQUIV"
    <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">

    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 6, Column 42: there is no attribute "CONTENT"
    <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">

    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 6, Column 52: element "META" undefined
    <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">

    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 7, Column 45: element "META" undefined
    <META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">

    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 11, Column 57: required attribute "type" not specified
    <script src="http://indane.co.in/js/jquery-1.3.2.min.js"></script>

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

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

  • Error Line 12, Column 18: there is no attribute "language"
    <script language="javascript" type="text/javascript">

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

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

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

  • Warning Line 19, Column 16: character "<" is the first character of a delimiter but occurred as data
       if(IEversion<=6)

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

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

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

  • Error Line 64, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 7, Column 1: start tag was here
    <META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">
  • Error Line 64, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 6, Column 1: start tag was here
    <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">
  • Error Line 64, Column 7: end tag for "head" which is not finished
    </head>

    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 107, Column 71: there is no attribute "target"
    …oat:right"><a href="hindi.php" target="_blank"><img src="images/indane-hindi.j…

    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 107, Column 145: there is no attribute "border"
    …di.jpg" style="cursor:pointer" border="0" alt="Hindi" title="Hindi" /></a></di…

    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 188, Column 24: there is no attribute "name"
                <form name="f" action="http://indane.co.in/login.php" method="post"…

    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 192, Column 28: there is no attribute "align"
                    <div align="left" style="padding-left:10px;">

    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 198, Column 66: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                    <input type="hidden" name="mode" value="login"  />

    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 258, Column 60: there is no attribute "onMouseOver"
    …ref="javascript:void(0)"  onMouseOver="mopen('m0')"  onClick="mopen('m0')" onM…

    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 258, Column 83: there is no attribute "onClick"
    …"  onMouseOver="mopen('m0')"  onClick="mopen('m0')" onMouseOut="mclosetime()">…

    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 258, Column 108: there is no attribute "onMouseOut"
    …er="mopen('m0')"  onClick="mopen('m0')" onMouseOut="mclosetime()">HOW DO I?</a>

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

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

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

  • Error Line 259, Column 46: there is no attribute "onMouseOver"
    …             <div id="m0" onMouseOver="mcancelclosetime()" onMouseOut="mcloset…

    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 259, Column 78: there is no attribute "onMouseOut"
    …eOver="mcancelclosetime()" onMouseOut="mclosetime()" style="text-transform:upp…

    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 303, Column 46: there is no attribute "direction"
    …     	             <marquee direction="left" scrollamount="3" onmouseover="thi…

    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 303, Column 66: there is no attribute "scrollamount"
    …marquee direction="left" scrollamount="3" onmouseover="this.stop();" onmouseou…

    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 303, Column 82: there is no attribute "onmouseover"
    …n="left" scrollamount="3" onmouseover="this.stop();" onmouseout="this.start();…

    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 303, Column 108: there is no attribute "onmouseout"
    …onmouseover="this.stop();" onmouseout="this.start();">Please submit your Aadha…

    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 303, Column 123: element "marquee" undefined
    …is.stop();" onmouseout="this.start();">Please submit your Aadhaar Letter witho…

    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 309, Column 7: required attribute "type" not specified
    <style>

    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 309, Column 7: document type does not allow element "style" here
    <style>

    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 368, Column 84: required attribute "alt" not specified
    …nt.getElementById(div_id).innerHTML = '<img src="images/ajax_small_load.gif">';

    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 368, Column 84: document type does not allow element "img" here
    …nt.getElementById(div_id).innerHTML = '<img src="images/ajax_small_load.gif">';

    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 368, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …nt.getElementById(div_id).innerHTML = '<img src="images/ajax_small_load.gif">';

    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 368, Column 47: start tag was here
    …nt.getElementById(div_id).innerHTML = '<img src="images/ajax_small_load.gif">';
  • Warning Line 377, Column 15: character "<" is the first character of a delimiter but occurred as data
    	if(val.length<=3)

    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 420, Column 35: character "&" is the first character of a delimiter but occurred as data
    	if (page_request.readyState == 4 && (page_request.status==200 || window.locati…

    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 420, Column 36: character "&" is the first character of a delimiter but occurred as data
    	if (page_request.readyState == 4 && (page_request.status==200 || window.locati…

    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 444, Column 84: required attribute "alt" not specified
    …nt.getElementById(div_id).innerHTML = '<img src="images/ajax_small_load.gif">';

    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 444, Column 84: document type does not allow element "img" here
    …nt.getElementById(div_id).innerHTML = '<img src="images/ajax_small_load.gif">';

    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 444, Column 85: end tag for "img" omitted, but OMITTAG NO was specified
    …nt.getElementById(div_id).innerHTML = '<img src="images/ajax_small_load.gif">';

    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 444, Column 47: start tag was here
    …nt.getElementById(div_id).innerHTML = '<img src="images/ajax_small_load.gif">';
  • Warning Line 492, Column 35: character "&" is the first character of a delimiter but occurred as data
    	if (page_request.readyState == 4 && (page_request.status==200 || window.locati…

    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 492, Column 36: character "&" is the first character of a delimiter but occurred as data
    	if (page_request.readyState == 4 && (page_request.status==200 || window.locati…

    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 525, Column 12: character "&" is the first character of a delimiter but occurred as data
    	if(id!='' && document.getElementById('auto_complete_div').style.display=='none…

    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 525, Column 13: character "&" is the first character of a delimiter but occurred as data
    	if(id!='' && document.getElementById('auto_complete_div').style.display=='none…

    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 531, Column 98: cannot generate system identifier for general entity "bgstate"
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;

    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 531, Column 98: general entity "bgstate" not defined and no default entity
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;

    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 531, Column 105: reference not terminated by REFC delimiter
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;

    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 531, Column 105: reference to entity "bgstate" for which no system identifier could be generated
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;

    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 531, Column 97: entity was defined here
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;
  • Warning Line 531, Column 118: cannot generate system identifier for general entity "city"
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;

    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 531, Column 118: general entity "city" not defined and no default entity
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;

    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 531, Column 122: reference not terminated by REFC delimiter
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;

    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 531, Column 122: reference to entity "city" for which no system identifier could be generated
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;

    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 531, Column 117: entity was defined here
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;
  • Warning Line 532, Column 108: reference not terminated by REFC delimiter
    …?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+"&lstYear="+y…

    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 532, Column 108: reference to entity "bgstate" for which no system identifier could be generated
    …?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+"&lstYear="+y…

    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 531, Column 97: entity was defined here
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;
  • Warning Line 532, Column 125: reference not terminated by REFC delimiter
    …+DealerCode+"&bgstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdCon…

    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 532, Column 125: reference to entity "city" for which no system identifier could be generated
    …+DealerCode+"&bgstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdCon…

    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 531, Column 117: entity was defined here
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;
  • Warning Line 532, Column 137: cannot generate system identifier for general entity "lstYear"
    …"&bgstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domest…

    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 532, Column 137: general entity "lstYear" not defined and no default entity
    …"&bgstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domest…

    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 532, Column 144: reference not terminated by REFC delimiter
    …gstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domestic";

    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 532, Column 144: reference to entity "lstYear" for which no system identifier could be generated
    …gstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domestic";

    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 532, Column 136: entity was defined here
    …+"&bgstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domes…
  • Warning Line 532, Column 160: cannot generate system identifier for general entity "RdConsType"
    …gstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domestic";

    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 532, Column 160: general entity "RdConsType" not defined and no default entity
    …gstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domestic";

    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 532, Column 170: reference not terminated by REFC delimiter
    …gstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domestic";

    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 532, Column 170: reference to entity "RdConsType" for which no system identifier could be generated
    …gstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domestic";

    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 532, Column 159: entity was defined here
    …gstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domestic";
  • Warning Line 533, Column 117: reference not terminated by REFC delimiter
    …?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+"&lstYear="+y…

    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 533, Column 117: reference to entity "bgstate" for which no system identifier could be generated
    …?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+"&lstYear="+y…

    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 531, Column 97: entity was defined here
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;
  • Warning Line 533, Column 134: reference not terminated by REFC delimiter
    …+DealerCode+"&bgstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdCon…

    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 533, Column 134: reference to entity "city" for which no system identifier could be generated
    …+DealerCode+"&bgstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdCon…

    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 531, Column 117: entity was defined here
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;
  • Warning Line 533, Column 153: reference not terminated by REFC delimiter
    …tate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domestic";		

    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 533, Column 153: reference to entity "lstYear" for which no system identifier could be generated
    …tate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domestic";		

    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 532, Column 136: entity was defined here
    …+"&bgstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domes…
  • Warning Line 533, Column 179: reference not terminated by REFC delimiter
    …tate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domestic";		

    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 533, Column 179: reference to entity "RdConsType" for which no system identifier could be generated
    …tate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domestic";		

    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 532, Column 159: entity was defined here
    …gstate="+StateID+"&city="+cityID+"&lstYear="+yearfilter+"&RdConsType=Domestic";
  • Warning Line 556, Column 12: character "&" is the first character of a delimiter but occurred as data
    	if(id!='' && document.getElementById('auto_complete_div_new').style.display=='…

    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 556, Column 13: character "&" is the first character of a delimiter but occurred as data
    	if(id!='' && document.getElementById('auto_complete_div_new').style.display=='…

    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 564, Column 123: reference not terminated by REFC delimiter
    …?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+'&num_search=…

    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 564, Column 123: reference to entity "bgstate" for which no system identifier could be generated
    …?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+'&num_search=…

    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 531, Column 97: entity was defined here
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;
  • Warning Line 564, Column 140: reference not terminated by REFC delimiter
    …utor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+'&num_search='+consNum;		

    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 564, Column 140: reference to entity "city" for which no system identifier could be generated
    …utor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+'&num_search='+consNum;		

    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 531, Column 117: entity was defined here
    …ncy/report.php?txtDistributor="+DealerCode+"&bgstate="+StateID+"&city="+cityID;
  • Warning Line 564, Column 152: cannot generate system identifier for general entity "num_search"
    …utor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+'&num_search='+consNum;		

    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 564, Column 152: general entity "num_search" not defined and no default entity
    …utor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+'&num_search='+consNum;		

    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 564, Column 162: reference not terminated by REFC delimiter
    …utor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+'&num_search='+consNum;		

    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 564, Column 162: reference to entity "num_search" for which no system identifier could be generated
    …utor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+'&num_search='+consNum;		

    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 564, Column 151: entity was defined here
    …utor="+DealerCode+"&bgstate="+StateID+"&city="+cityID+'&num_search='+consNum;		
  • Error Line 569, Column 45: required attribute "type" not specified
    <script src="http://indane.co.in/js/menu.js"></script>

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

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

  • Error Line 570, Column 96: document type does not allow element "link" here
    …//indane.co.in/css/menu.css" rel="stylesheet" type="text/css" media="screen" />

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

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

  • Error Line 571, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 598, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 702, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 842, Column 104: element "marquee" undefined
    …n="up" scrollamount="3" onmouseover="this.stop();" onmouseout="this.start();" >

    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 843, Column 1717: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …e="color:#1C1C1C;font-weight:bold "><p>Chandigarh , Delhi&nbsp; and Kolkotta (…

    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 843, Column 2220: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …e="color:#1C1C1C;font-weight:bold "><p>IndianOil is pleased to launch new SMS/…

    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 874, Column 338: end tag for "img" omitted, but OMITTAG NO was specified
    …p: 0px; padding: 0px; margin: 0px; border: 0px none;" alt="" border="0" ></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 874, Column 179: start tag was here
    …low: hidden; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/01.jpg"…
  • Error Line 876, Column 337: end tag for "img" omitted, but OMITTAG NO was specified
    …op: 0px; padding: 0px; margin: 0px; border: 0px none;" alt="" border="0"></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 876, Column 179: start tag was here
    …low: hidden; z-index: 2; opacity: 0;"><img id="slide1img1" src="images/02.jpg"…
  • Error Line 878, Column 337: end tag for "img" omitted, but OMITTAG NO was specified
    …op: 0px; padding: 0px; margin: 0px; border: 0px none;" alt="" border="0"></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 878, Column 179: start tag was here
    …low: hidden; z-index: 2; opacity: 0;"><img id="slide1img2" src="images/03.jpg"…
  • Error Line 880, Column 337: end tag for "img" omitted, but OMITTAG NO was specified
    …op: 0px; padding: 0px; margin: 0px; border: 0px none;" alt="" border="0"></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 880, Column 179: start tag was here
    …low: hidden; z-index: 3; opacity: 1;"><img id="slide1img3" src="images/04.jpg"…
  • Error Line 882, Column 188: ID "slide1img0" already defined
    …en; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/banner01.jpg" st…

    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 874, Column 188: ID "slide1img0" first defined here
    …en; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/01.jpg" style="p…
  • Error Line 882, Column 343: end tag for "img" omitted, but OMITTAG NO was specified
    …op: 0px; padding: 0px; margin: 0px; border: 0px none;" alt="" border="0"></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 882, Column 179: start tag was here
    …low: hidden; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/banner0…
  • Error Line 884, Column 188: ID "slide1img0" already defined
    …en; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/banner02.jpg" st…

    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 874, Column 188: ID "slide1img0" first defined here
    …en; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/01.jpg" style="p…
  • Error Line 884, Column 343: end tag for "img" omitted, but OMITTAG NO was specified
    …op: 0px; padding: 0px; margin: 0px; border: 0px none;" alt="" border="0"></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 884, Column 179: start tag was here
    …low: hidden; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/banner0…
  • Error Line 886, Column 188: ID "slide1img0" already defined
    …en; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/banner03.jpg" st…

    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 874, Column 188: ID "slide1img0" first defined here
    …en; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/01.jpg" style="p…
  • Error Line 886, Column 343: end tag for "img" omitted, but OMITTAG NO was specified
    …op: 0px; padding: 0px; margin: 0px; border: 0px none;" alt="" border="0"></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 886, Column 179: start tag was here
    …low: hidden; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/banner0…
  • Error Line 888, Column 231: ID "slide1img0" already defined
    …es/banner6.jpg" alt="" border="0" id="slide1img0" style="position: relative; l…

    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 874, Column 188: ID "slide1img0" first defined here
    …en; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/01.jpg" style="p…
  • Error Line 888, Column 342: end tag for "img" omitted, but OMITTAG NO was specified
    …tive; left: 0px; top: 0px; padding: 0px; margin: 0px; border: 0px none;"></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 888, Column 179: start tag was here
    …low: hidden; z-index: 2; opacity: 0;"><img src="images/banner6.jpg" alt="" bor…
  • Error Line 890, Column 188: ID "slide1img0" already defined
    …en; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/banner05.jpg" st…

    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 874, Column 188: ID "slide1img0" first defined here
    …en; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/01.jpg" style="p…
  • Error Line 890, Column 343: end tag for "img" omitted, but OMITTAG NO was specified
    …op: 0px; padding: 0px; margin: 0px; border: 0px none;" alt="" border="0"></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 890, Column 179: start tag was here
    …low: hidden; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/banner0…
  • Error Line 892, Column 188: ID "slide1img0" already defined
    …en; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/venusgas1.jpg" s…

    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 874, Column 188: ID "slide1img0" first defined here
    …en; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/01.jpg" style="p…
  • Error Line 892, Column 344: end tag for "img" omitted, but OMITTAG NO was specified
    …op: 0px; padding: 0px; margin: 0px; border: 0px none;" alt="" border="0"></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 892, Column 179: start tag was here
    …low: hidden; z-index: 2; opacity: 0;"><img id="slide1img0" src="images/venusga…
  • Error Line 910, Column 65: document type does not allow element "a" here
    linkstr[0]='<a href="http://www.indanemis.co.in" target="_blank">';

    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 922, Column 54: document type does not allow element "a" here
    linkstr[1]='<a href="http://indane.co.in/aadhaar.php">';

    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 925, Column 55: document type does not allow element "a" here
    //<a href="http://www.indanemis.co.in" target="_blank">

    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 994, Column 17: character "'" is not allowed in the value of attribute "id"
    dstr1='<div id="';

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 994, Column 19: value of attribute "id" must be a single token
    dstr1='<div id="';

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 995, Column 6: character "=" is not allowed in the value of attribute "id"
    dstr2='" style="position:absolute;text-align:'+"center"+';width:'+676+'px;heigh…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 995, Column 55: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …position:absolute;text-align:'+"center"+';width:'+676+'px;height:'+240+'px;vis…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 995, Column 55: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …position:absolute;text-align:'+"center"+';width:'+676+'px;height:'+240+'px;vis…

    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 996, Column 26: character "'" is not allowed in the value of attribute "id"
    dstr3='<img id="slide1img';

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 996, Column 28: value of attribute "id" must be a single token
    dstr3='<img id="slide1img';

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 997, Column 6: character "=" is not allowed in the value of attribute "id"
    dstr4='" src="';

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 999, Column 201: end tag for element "img" which is not open
    …" title="Click here for more details" border="0" usemap="#brandindane"></img>';

    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 1000, Column 203: end tag for element "img" which is not open
    …title="Click here for more details" border="0" usemap="#aadhaarindane"></img>';

    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.

  • Warning Line 1026, Column 113: character "<" is the first character of a delimiter but occurred as data
    …etElementById('slide1d'+vnext);		if(op<(0.00)){op=0.00;}	objc.style.opacity = …

    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 1043, Column 62: character ";" not allowed in attribute specification list
    function slide1initte(){	i=0;	innertxt="";	for(i=0;i<no_image;i++)	{		
  • Error Line 1043, Column 62: element "no_image" undefined
    function slide1initte(){	i=0;	innertxt="";	for(i=0;i<no_image;i++)	{		

    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 1060, Column 9: end tag for "no_image" 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 1043, Column 53: start tag was here
    function slide1initte(){	i=0;	innertxt="";	for(i=0;i<no_image;i++)	{		
  • Error Line 1060, Column 9: end tag for "a" 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 925, Column 3: start tag was here
    //<a href="http://www.indanemis.co.in" target="_blank">
  • Error Line 1062, Column 22: required attribute "id" not specified
    <map name="planetmap">

    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 1063, Column 66: required attribute "alt" not specified
    <area shape="rect" coords="264,212,410,235" href="sms_ivrs.php" />

    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 1064, Column 66: required attribute "alt" not specified
    <area shape="rect" coords="479,213,633,236" href="sms_ivrs.php" />

    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 1066, Column 144: required attribute "alt" not specified
    …etails"><area shape="rect" coords="8,6,672,234" href="brandindane.php" /></map>

    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 1067, Column 142: required attribute "alt" not specified
    …re details"><area shape="rect" coords="8,6,672,234" href="aadhaar.php" /></map>

    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 1073, Column 20: required attribute "type" not specified
                <script>

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

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

  • Warning Line 1076, Column 30: character "<" is the first character of a delimiter but occurred as data
                        for(i=1;i<=4;i++)

    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 1211, Column 28: ID "go_button" already defined
                </div><div id="go_button" style="float:left; width:240px; padding-t…

    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 1189, Column 28: ID "go_button" first defined here
                </div><div id="go_button" style="float:left; width:240px; padding-t…
  • Error Line 1216, Column 169: required attribute "alt" not specified
    …or:pointer" class="active" onclick="Javascript:window.location='aadhaar.php'"/>

    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 1217, Column 94: required attribute "alt" not specified
    …g src="images/indane_plant.jpg" width="258" height="240" style="float:right" />

    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 1239, Column 30: required attribute "type" not specified
    <script language="javascript">

    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 1316, Column 7: required attribute "type" not specified
    <style>

    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 1316, Column 7: document type does not allow element "style" here
    <style>

    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 1417, Column 14: ID "footer" already defined
        <div id="footer" style="height:36px; padding-left:166px; width:790px;">

    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 1327, Column 14: ID "footer" first defined here
        <div id="footer">
  • Error Line 1419, Column 38: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<a href="http://indane.co.in/"><h4>HOME</h4></a>

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

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

  • Error Line 1422, Column 53: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<a href="http://indane.co.in/new_offices.php"><h4>OFFICES</h4></a>

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

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

  • Error Line 1425, Column 57: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<a href="http://indane.co.in/new_distributor.php"><h4>DISTRIBUTOR</h4></a>

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

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

  • Error Line 1428, Column 47: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<a href="http://indane.co.in/about.php"><h4>About Indane</h4></a>

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

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

  • Error Line 1432, Column 50: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<a href="http://indane.co.in/feedback.php"><h4>Feedback</h4></a>

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

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

  • Error Line 1435, Column 45: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<a href="http://indane.co.in/faq.php"><h4>FAQ's</h4></a>

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

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

  • Error Line 1438, Column 49: document type does not allow element "h4" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<a href="http://indane.co.in/contact.php"><h4>Contact Us</h4></a>

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

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

Visitor Analysis

Daily Visitor
  • 7.700 visits