Follow us on    Phone Booking   Alert:             Alert:               Alert:               Alert:   ...

inoxmovies.com
  • Domain Name
    inoxmovies.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #15981
  • Page Size
    45.4 KB
  • Ip Address
    203.115.122.66
  • Heading
    H1: 10, H2: 4, H3: 4, H4: 4, H5: 0, H6: 2
  • Images
    14 GIF, 7 JPG, 12 PNG

Website Meta Analysis

  • Title
    INOXMovies.com - Live The Movie | Book tickets for the latest Bollywood, Hollywood and regional films at India's favourite multiplex chain.
  • Meta Keyword
  • Meta Description
      Follow us on    Phone Booking   Alert:             Alert:               Alert:               Alert:               Alert:               Alert:             close Bangalore Belgaum Bharuch Bhubaneswar Burdwan Chennai Darjeeling Durgapur Faridabad ...

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    203.115.122.66
  • Domain Age
    11 Years, 3 Months, 9 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • date: Thu, 24 Jan 2013 18:36:51 GMT
  • content-length: 11858
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Inox Leisure Limited
501,Viraj Towers
Cts No.216 junction of W E Highway
Andheri Kurla Rd.,
Andheri East
Mumbai,, Maharashtra 400069
IN

Domain Name: INOXMOVIES.COM



Administrative Contact:
Inox Leisure Limited email
501,Viraj Towers
Cts No.216 junction of W E Highway
Andheri Kurla Rd.,
Andheri East
Mumbai,, Maharashtra 400069
IN
91-22- 40626900 fax: 91-22- 40626999

Technical Contact:
Network Solutions, LLC. email
13861 Sunrise Valley Drive
Herndon, VA 20171
US
1-888-642-9675 fax: 571-434-4620

Record expires on 15-Oct-2015.
Record created on 15-Oct-2001.
Database last updated on 24-Aug-2012 19:38:34 EDT.

Domain servers in listed order:

NS35.WORLDNIC.COM 205.178.190.18
NS36.WORLDNIC.COM 206.188.198.18

DNS Analysis


DNS servers
ns35.worldnic.com [205.178.190.18]
ns36.worldnic.com [206.188.198.18]


DNS Records

Answer records
inoxmovies.com A 203.115.122.66 86400s
inoxmovies.com SOA
server: NS35.WORLDNIC.COM
email: namehost@WORLDNIC.COM
serial: 112071108
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
7200s
inoxmovies.com NS  ns35.worldnic.com 7200s
inoxmovies.com NS  ns36.worldnic.com 7200s

Authority records

Additional records

IP 203.115.122.66 Analysis

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

    inetnum: 203.115.96.0 - 203.115.127.255
    netname: PRIMENET-IN
    descr: PRIMENET GLOBAL LTD.
    descr: Internet Service Provider
    country: IN
    admin-c: NA24-AP
    tech-c: ST326-AP
    mnt-by: APNIC-HM
    mnt-lower: MAINT-IN-PRIMENET
    mnt-routes: MAINT-IN-PRIMENET
    changed: hostmaster@apnic.net 20000630
    changed: hm-changed@apnic.net 20020521
    changed: hm-changed@apnic.net 20030220
    status: ALLOCATED PORTABLE
    changed: hm-changed@apnic.net 20081205
    source: APNIC

    route: 203.115.96.0/19
    descr: PRIMENET route object
    country: IN
    origin: AS17426
    mnt-by: MAINT-IN-PRIMENET
    changed: hm-changed@apnic.net 20081205
    source: APNIC

    person: Narender Kumar Ahuja
    address: 25/2, Business Park
    address: Shivaji Marg
    address: New Delhi-110015
    country: IN
    phone: +91-11-5192830
    fax-no: +91-11-5448478
    e-mail: primesoft@vsnl.com
    nic-hdl: NA24-AP
    mnt-by: MAINT-IN-PRIMESOFT
    changed: primesoft@vsnl.com 20000627
    source: APNIC

    person: Sree Rangaraj Thirumalai
    nic-hdl: ST326-AP
    e-mail: rangaraj@primenet.in
    address: 25/2, Business Park
    address: Shivaji Marg,
    address: New Delhi - 110015
    phone: +91-11-25192830
    fax-no: +91-11-25448478
    country: IN
    changed: rangaraj@primenet.in 20030214
    mnt-by: MAINT-IN-PRIMENET
    source: APNIC


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 184 Errors
  • 22 Warnings
Ratio Text/Html
  • 0.6002883208537739
Message Error
  • Warning Line 9, Column 30: character "&" is the first character of a delimiter but occurred as data
        var arr = spQrStr.split('&');

    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 29, Column 16: there is no attribute "property"
    <meta property="og:title" content="INOX Leisure"/>

    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 35, Column 66: character "&" is the first character of a delimiter but occurred as data
    …ription" content="With 41 multiplexes & 155 screens across the country, INOX 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 109, 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 156, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …c="images/top/facebook.png" alt=""></a> <a href="http://twitter.com/inoxleisur…

    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 156, Column 152: start tag was here
    …ure-Ltd/145266579078" target="_blank"><img src="images/top/facebook.png" alt="…
  • Error Line 156, Column 300: end tag for "img" omitted, but OMITTAG NO was specified
    …inoxleisure" target="_blank"><img src="images/top/twitter.png" alt=""></a></h6>

    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 156, Column 256: start tag was here
    …tter.com/inoxleisure" target="_blank"><img src="images/top/twitter.png" alt=""…
  • Error Line 167, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 167, Column 17: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td width=100% align=center>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 167, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 167, Column 36: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td width=100% align=center>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 167, Column 44: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 182, Column 4: document type does not allow element "tr" here
    <tr>

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

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

  • Error Line 185, Column 159: there is no attribute "type"
    …('pop_div').style.display='none';" type='image' src='images/buttons/ok.gif'  />

    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 185, Column 197: required attribute "alt" not specified
    …('pop_div').style.display='none';" type='image' src='images/buttons/ok.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 199, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 199, Column 17: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td width=100% align=center>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 199, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 199, Column 36: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td width=100% align=center>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 199, Column 44: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 214, Column 4: document type does not allow element "tr" here
    <tr>

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

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

  • Error Line 217, Column 199: required attribute "alt" not specified
    …('pop_div').style.display='none';" type='image' src='images/buttons/ok.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 219, Column 104: required attribute "alt" not specified
    …r;" onclick="cancel_censor();" type='image' src='images/buttons/cancel.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 232, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 232, Column 17: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td width=100% align=center>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 232, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 232, Column 36: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td width=100% align=center>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 232, Column 44: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 247, Column 4: document type does not allow element "tr" here
    <tr>

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

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

  • Error Line 250, Column 198: required attribute "alt" not specified
    …('pop_div').style.display='none';" type='image' src='images/buttons/ok.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 252, Column 103: required attribute "alt" not specified
    …er;" onclick="cancel_ektha();" type='image' src='images/buttons/cancel.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 265, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 265, Column 17: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td width=100% align=center>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 265, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 265, Column 36: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td width=100% align=center>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 265, Column 44: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 280, Column 4: document type does not allow element "tr" here
    <tr>

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

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

  • Error Line 283, Column 197: required attribute "alt" not specified
    …('pop_div').style.display='none';" type='image' src='images/buttons/ok.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 285, Column 101: required attribute "alt" not specified
    …nter;" onclick="cancel_3dd();" type='image' src='images/buttons/cancel.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 298, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 298, Column 17: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td width=100% align=center>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 298, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 298, Column 36: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td width=100% align=center>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 298, Column 44: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 313, Column 4: document type does not allow element "tr" here
    <tr>

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

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

  • Error Line 316, Column 196: required attribute "alt" not specified
    …('pop_div').style.display='none';" type='image' src='images/buttons/ok.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 318, Column 101: required attribute "alt" not specified
    …nter;" onclick="cancel_mad();" type='image' src='images/buttons/cancel.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 331, Column 14: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 331, Column 17: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td width=100% align=center>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 331, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 331, Column 36: an attribute value must be a literal unless it contains only name characters
    <table width=100%><tr><td width=100% align=center>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 331, Column 44: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table width=100%><tr><td width=100% align=center>
  • Error Line 346, Column 4: document type does not allow element "tr" here
    <tr>

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

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

  • Error Line 349, Column 197: required attribute "alt" not specified
    …('pop_div').style.display='none';" type='image' src='images/buttons/ok.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 351, Column 102: required attribute "alt" not specified
    …ter;" onclick="cancel_mad1();" type='image' src='images/buttons/cancel.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 371, Column 69: value of attribute "id" invalid: "1" cannot start a name
    …ity_blk"><div class='city_blk_in' id='10'><p><a id='a_10' style='cursor:pointe…

    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 371, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_10' style='cursor:pointer;' onclick=highlightCity(10,'Bangalore');>Bangalore…
  • Error Line 371, Column 134: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(10,'Bangalore');>Bangalore </a></p><p><…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 218: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_25' style='cursor:pointer;' onclick=highlightCity(25,'Belgaum');>Belgaum </a…
  • Error Line 371, Column 231: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(25,'Belgaum');>Belgaum </a></p><p><a id…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 311: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_16' style='cursor:pointer;' onclick=highlightCity(16,'Bharuch');>Bharuch </a…
  • Error Line 371, Column 324: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(16,'Bharuch');>Bharuch </a></p><p><a id…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 404: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_29' style='cursor:pointer;' onclick=highlightCity(29,'Bhubaneswar');>Bhubane…
  • Error Line 371, Column 417: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(29,'Bhubaneswar');>Bhubaneswar</a></p><…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 504: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_20' style='cursor:pointer;' onclick=highlightCity(20,'Burdwan');>Burdwan </a…
  • Error Line 371, Column 517: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(20,'Burdwan');>Burdwan </a></p><p><a id…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 597: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_13' style='cursor:pointer;' onclick=highlightCity(13,'Chennai');>Chennai </a…
  • Error Line 371, Column 610: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(13,'Chennai');>Chennai </a></p></div><d…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 677: value of attribute "id" invalid: "9" cannot start a name
    …/p></div><div class='city_blk_in' id='9'><p><a id='a_9' style='cursor:pointer;…

    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 371, Column 727: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'a_9' style='cursor:pointer;' onclick=highlightCity(9,'Darjeeling');>Darjeelin…
  • Error Line 371, Column 740: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(9,'Darjeeling');>Darjeeling </a></p><p>…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 825: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_15' style='cursor:pointer;' onclick=highlightCity(15,'Durgapur');>Durgapur <…
  • Error Line 371, Column 838: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(15,'Durgapur');>Durgapur </a></p><p><a …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 920: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_19' style='cursor:pointer;' onclick=highlightCity(19,'Faridabad');>Faridabad…
  • Error Line 371, Column 933: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(19,'Faridabad');>Faridabad </a></p><p><…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 1017: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_12' style='cursor:pointer;' onclick=highlightCity(12,'Goa');>Goa </a></p><p>…
  • Error Line 371, Column 1030: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(12,'Goa');>Goa </a></p><p><a id='a_21' …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 1102: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_21' style='cursor:pointer;' onclick=highlightCity(21,'Hyderabad');>Hyderabad…
  • Error Line 371, Column 1115: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(21,'Hyderabad');>Hyderabad </a></p><p><…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 1198: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'a_5' style='cursor:pointer;' onclick=highlightCity(5,'Indore');>Indore </a></…
  • Error Line 371, Column 1211: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(5,'Indore');>Indore </a></p></div><div …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 1275: value of attribute "id" invalid: "6" cannot start a name
    …/p></div><div class='city_blk_in' id='6'><p><a id='a_6' style='cursor:pointer;…

    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 371, Column 1325: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'a_6' style='cursor:pointer;' onclick=highlightCity(6,'Jaipur');>Jaipur </a></…
  • Error Line 371, Column 1338: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(6,'Jaipur');>Jaipur </a></p><p><a id='a…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 1415: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_24' style='cursor:pointer;' onclick=highlightCity(24,'Kanpur');>Kanpur </a><…
  • Error Line 371, Column 1428: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(24,'Kanpur');>Kanpur </a></p><p><a id='…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 1505: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'a_4' style='cursor:pointer;' onclick=highlightCity(4,'Kolkata');>Kolkata </a>…
  • Error Line 371, Column 1518: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(4,'Kolkata');>Kolkata </a></p><p><a id=…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 1596: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'a_8' style='cursor:pointer;' onclick=highlightCity(8,'Kota');>Kota </a></p><p…
  • Error Line 371, Column 1609: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(8,'Kota');>Kota </a></p><p><a id='a_27'…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 1682: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_27' style='cursor:pointer;' onclick=highlightCity(27,'Liluah');>Liluah</a></…
  • Error Line 371, Column 1695: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(27,'Liluah');>Liluah</a></p><p><a id='a…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 1772: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_18' style='cursor:pointer;' onclick=highlightCity(18,'Lucknow');>Lucknow </a…
  • Error Line 371, Column 1785: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(18,'Lucknow');>Lucknow </a></p></div><d…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 1852: value of attribute "id" invalid: "2" cannot start a name
    …/p></div><div class='city_blk_in' id='2'><p><a id='a_2' style='cursor:pointer;…

    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 371, Column 1902: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'a_2' style='cursor:pointer;' onclick=highlightCity(2,'Mumbai');>Mumbai </a></…
  • Error Line 371, Column 1915: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(2,'Mumbai');>Mumbai </a></p><p><a id='a…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 1991: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'a_1' style='cursor:pointer;' onclick=highlightCity(1,'Nagpur');>Nagpur </a></…
  • Error Line 371, Column 2004: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(1,'Nagpur');>Nagpur </a></p><p><a id='a…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 2081: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_28' style='cursor:pointer;' onclick=highlightCity(28,'NaviMumbai');>Navi Mum…
  • Error Line 371, Column 2094: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(28,'NaviMumbai');>Navi Mumbai</a></p><p…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 2179: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'a_7' style='cursor:pointer;' onclick=highlightCity(7,'Pune');>Pune </a></p><p…
  • Error Line 371, Column 2192: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(7,'Pune');>Pune </a></p><p><a id='a_14'…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 2265: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_14' style='cursor:pointer;' onclick=highlightCity(14,'Raipur');>Raipur </a><…
  • Error Line 371, Column 2278: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(14,'Raipur');>Raipur </a></p><p><a id='…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 2356: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_26' style='cursor:pointer;' onclick=highlightCity(26,'Siliguri');>Siliguri</…
  • Error Line 371, Column 2369: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(26,'Siliguri');>Siliguri</a></p></div><…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 2437: value of attribute "id" invalid: "2" cannot start a name
    …/p></div><div class='city_blk_in' id='23'><p><a id='a_23' style='cursor:pointe…

    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 371, Column 2489: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_23' style='cursor:pointer;' onclick=highlightCity(23,'Thane');>Thane </a></p…
  • Error Line 371, Column 2502: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(23,'Thane');>Thane </a></p><p><a id='a_…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 2578: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_11' style='cursor:pointer;' onclick=highlightCity(11,'Vadodara');>Vadodara <…
  • Error Line 371, Column 2591: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(11,'Vadodara');>Vadodara </a></p><p><a …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 2673: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_17' style='cursor:pointer;' onclick=highlightCity(17,'Vijayawada');>Vijayawa…
  • Error Line 371, Column 2686: an attribute value must be a literal unless it contains only name characters
    …cursor:pointer;' onclick=highlightCity(17,'Vijayawada');>Vijayawada </a></p><p…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 371, Column 2772: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a_22' style='cursor:pointer;' onclick=highlightCity(22,'Vizag');>Vizag </a></p…
  • Error Line 371, Column 2785: an attribute value must be a literal unless it contains only name characters
    …style='cursor:pointer;' onclick=highlightCity(22,'Vizag');>Vizag </a></p></div>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 373, Column 99: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …d="ck_city_val" type="checkbox"    checked/> Remember my location</label></div>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 378, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </td></tr>

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

  • Info Line 365, Column 10: start tag was here
    <tr><td ><div class="top_blk2">
  • Error Line 394, Column 58: document type does not allow element "link" here
        <link rel="shortcut icon" href="images/favicon.ico" />

    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 397, 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 478, Column 27: ID "outofnormal" already defined
    <div class="top_tool" id="outofnormal">

    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 146, Column 27: ID "outofnormal" first defined here
    <div class="top_tool" id="outofnormal">
  • Error Line 485, Column 47: ID "header_bar" already defined
    …        <div class="book_tickets" id="header_bar" style="display:none;"><a hre…

    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 155, Column 47: ID "header_bar" first defined here
    …        <div class="book_tickets" id="header_bar" style="display:none;"><a hre…
  • Error Line 486, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …c="images/top/facebook.png" alt=""></a> <a href="http://twitter.com/inoxleisur…

    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 486, Column 152: start tag was here
    …ure-Ltd/145266579078" target="_blank"><img src="images/top/facebook.png" alt="…
  • Error Line 486, Column 300: end tag for "img" omitted, but OMITTAG NO was specified
    …inoxleisure" target="_blank"><img src="images/top/twitter.png" alt=""></a></h6>

    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 486, Column 256: start tag was here
    …tter.com/inoxleisure" target="_blank"><img src="images/top/twitter.png" alt=""…
  • Error Line 512, Column 16: there is no attribute "src"
        <embed src="../flash/banner.swf" wmode="transparent"  quality="high" plugin…

    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 512, Column 44: there is no attribute "wmode"
    …embed src="../flash/banner.swf" wmode="transparent"  quality="high" pluginspag…

    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 512, Column 67: there is no attribute "quality"
    …ner.swf" wmode="transparent"  quality="high" pluginspage="http://www.macromedi…

    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 512, Column 86: there is no attribute "pluginspage"
    …nsparent"  quality="high" pluginspage="http://www.macromedia.com/go/getflashpl…

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

    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 512, Column 175: there is no attribute "width"
    …shplayer" type="application/x-shockwave-flash" width="728" height="90"></embed>

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

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

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

  • Error Line 512, Column 188: there is no attribute "height"
    …shplayer" type="application/x-shockwave-flash" width="728" height="90"></embed>

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

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

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

  • Error Line 512, Column 192: element "embed" undefined
    …shplayer" type="application/x-shockwave-flash" width="728" height="90"></embed>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 532, Column 535: end tag for element "li" which is not open
    …a> <a href='#'><img src='images/social/blogspot.jpg' alt='' /></a>--></li></ul>

    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 534, Column 32: required attribute "action" not specified
                <form method="post">

    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 544, Column 53: there is no attribute "onClick"
    …span style="cursor: pointer;" onClick="document.location.href='myaccount.aspx'…

    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 571, Column 189: element "embed" undefined
    …shplayer" type="application/x-shockwave-flash" width="25" height="114"></embed>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 583, Column 183: there is no attribute "onMouseOver"
    …  style="cursor:pointer;" onMouseOver="timerScroll(-1);" onMouseOut="cleartime…

    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 583, Column 213: there is no attribute "onMouseOut"
    …sor:pointer;" onMouseOver="timerScroll(-1);" onMouseOut="cleartimer();"/></div>

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

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

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

  • Error Line 583, Column 229: required attribute "alt" not specified
    …sor:pointer;" onMouseOver="timerScroll(-1);" onMouseOut="cleartimer();"/></div>

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

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

  • Error Line 587, Column 232: required attribute "alt" not specified
    …sor:pointer;" onMouseOver="timerScroll(1);" onMouseOut="cleartimer();" /></div>

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

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

  • Error Line 591, Column 229: required attribute "alt" not specified
    …;" onMouseOver="timerScroll_Movie(-1);" onMouseOut="cleartimer_movie();"></div>

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

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

  • Error Line 591, Column 235: end tag for "img" omitted, but OMITTAG NO was specified
    …;" onMouseOver="timerScroll_Movie(-1);" onMouseOut="cleartimer_movie();"></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 591, Column 105: start tag was here
    …t; margin-top:0px; visibility:hidden"><img src="images/up_arrow.png" style="cu…
  • Error Line 596, Column 253: required attribute "alt" not specified
    …" onMouseOver="timerScroll_Movie(1);" onMouseOut="cleartimer_movie();" /></div>

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

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

  • Error Line 631, Column 210: required attribute "alt" not specified
    …er;" onMouseOver="timerScroll_Time(-1);" onMouseOut="cleartimer_Time();"></div>

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

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

  • Error Line 631, Column 216: end tag for "img" omitted, but OMITTAG NO was specified
    …er;" onMouseOver="timerScroll_Time(-1);" onMouseOut="cleartimer_Time();"></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 631, Column 87: start tag was here
    …%;text-align:right;visibility:hidden"><img src="images/up_arrow.png"  style="c…
  • Error Line 635, Column 215: required attribute "alt" not specified
    …r;" onMouseOver="timerScroll_Time(1);" onMouseOut="cleartimer_Time();" /></div>

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

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

  • Error Line 636, Column 298: there is no attribute "border"
    …ot;, false, &quot;&quot;, &quot;index.aspx&quot;, false, false))" border="0" />

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

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

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

  • Error Line 650, Column 208: element "embed" undefined
    …hplayer" type="application/x-shockwave-flash" width="554" height="408"></embed>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 657, Column 126: required attribute "alt" not specified
    …_home(1);"><img src="images/ns_act.gif" style="cursor:pointer;" id="ns" /></li>

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

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

  • Error Line 658, Column 128: required attribute "alt" not specified
    …ome(2);"><img src="images/cs_inact.gif" style="cursor:pointer;" id="cs" /></li>

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

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

  • Error Line 659, Column 116: required attribute "alt" not specified
    …ome(3);"><img src="images/bo_inact.gif" style="cursor:pointer;" id="bo" /></li>

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

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

  • Warning Line 668, Column 240: character "&" is the first character of a delimiter but occurred as data
    …><h2>Mumbai Mirro..</h2><h3>Take part & win Audio CD</h3><h4><a href='http://w…

    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 668, Column 494: character "&" is the first character of a delimiter but occurred as data
    …t='76' /><h2>Inkaar</h2><h3>Take part & win Audio CD</h3><h4><a href='http://w…

    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 690, Column 11: document type does not allow element "h1" here; assuming missing "li" start-tag
          	<h1>Quick Links:</h1>
  • Error Line 691, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li><a href="movies_schedules.aspx">Show Timings</a></li>

    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 692, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li>|</li>

    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 693, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li><a href="cinemas.aspx">Locations</a></li>

    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 694, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li>|</li>

    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 695, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li><a href="ticketing_groupbookings.aspx">Group Bookings</a></li>

    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 696, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li>|</li>

    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 697, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li><a href="newCareer.aspx">Careers</a></li>

    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 698, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li>|</li>

    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 699, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li><a href="corporate.aspx">Corporate</a></li>

    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 700, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li>|</li>

    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 701, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li><a href="contact.aspx">Contact Us</a></li>

    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 702, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li>|</li>

    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 703, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li><a href="feedback.aspx">Feedback</a></li>

    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 705, Column 11: end tag for "li" omitted, but OMITTAG NO was specified
          </ul>

    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 690, Column 8: start tag was here
          	<h1>Quick Links:</h1>
  • Error Line 846, Column 32: document type does not allow element "center" here
    	$("#nscs_block").html("<center><img src='images/ajax-loader.gif'></center>");

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

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

  • Error Line 846, Column 66: required attribute "alt" not specified
    	$("#nscs_block").html("<center><img src='images/ajax-loader.gif'></center>");

    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 846, Column 75: end tag for "img" omitted, but OMITTAG NO was specified
    	$("#nscs_block").html("<center><img src='images/ajax-loader.gif'></center>");

    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 846, Column 33: start tag was here
    	$("#nscs_block").html("<center><img src='images/ajax-loader.gif'></center>");
  • Warning Line 895, Column 106: cannot generate system identifier for general entity "width"
    …cgi-bin/adserver.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&j…

    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 895, Column 106: general entity "width" not defined and no default entity
    …cgi-bin/adserver.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&j…

    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 895, Column 111: reference not terminated by REFC delimiter
    …in/adserver.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&c…

    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 895, Column 111: reference to entity "width" for which no system identifier could be generated
    …in/adserver.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&c…

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

  • Info Line 895, Column 105: entity was defined here
    …/cgi-bin/adserver.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&…
  • Warning Line 895, Column 116: cannot generate system identifier for general entity "height"
    …server.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickT…

    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 895, Column 116: general entity "height" not defined and no default entity
    …server.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickT…

    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 895, Column 122: reference not terminated by REFC delimiter
    ….fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag='; …

    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 895, Column 122: reference to entity "height" for which no system identifier could be generated
    ….fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag='; …

    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 895, Column 115: entity was defined here
    …dserver.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&click…
  • Warning Line 895, Column 127: cannot generate system identifier for general entity "enc"
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 127: general entity "enc" not defined and no default entity
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 130: reference not terminated by REFC delimiter
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 130: reference to entity "enc" for which no system identifier could be generated
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 126: entity was defined here
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   
  • Warning Line 895, Column 133: cannot generate system identifier for general entity "type"
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 133: general entity "type" not defined and no default entity
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 137: reference not terminated by REFC delimiter
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 137: reference to entity "type" for which no system identifier could be generated
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 132: entity was defined here
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   
  • Warning Line 895, Column 145: cannot generate system identifier for general entity "js"
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 145: general entity "js" not defined and no default entity
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 147: reference not terminated by REFC delimiter
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 147: reference to entity "js" for which no system identifier could be generated
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 144: entity was defined here
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   
  • Warning Line 895, Column 150: cannot generate system identifier for general entity "clickTag"
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 150: general entity "clickTag" not defined and no default entity
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 158: reference not terminated by REFC delimiter
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 158: reference to entity "clickTag" for which no system identifier could be generated
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

    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 895, Column 149: entity was defined here
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   
  • Warning Line 896, Column 112: reference not terminated by REFC delimiter
    …in/adserver.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&c…

    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 896, Column 112: reference to entity "width" for which no system identifier could be generated
    …in/adserver.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&c…

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

  • Info Line 895, Column 105: entity was defined here
    …/cgi-bin/adserver.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&…
  • Warning Line 896, Column 123: reference not terminated by REFC delimiter
    …er.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';

    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 896, Column 123: reference to entity "height" for which no system identifier could be generated
    …er.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';

    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 895, Column 115: entity was defined here
    …dserver.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&click…
  • Warning Line 896, Column 131: reference not terminated by REFC delimiter
    …er.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';

    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 896, Column 131: reference to entity "enc" for which no system identifier could be generated
    …er.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';

    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 895, Column 126: entity was defined here
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   
  • Warning Line 896, Column 138: reference not terminated by REFC delimiter
    …er.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';

    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 896, Column 138: reference to entity "type" for which no system identifier could be generated
    …er.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';

    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 895, Column 132: entity was defined here
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   
  • Warning Line 896, Column 148: reference not terminated by REFC delimiter
    …er.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';

    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 896, Column 148: reference to entity "js" for which no system identifier could be generated
    …er.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';

    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 895, Column 144: entity was defined here
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   
  • Warning Line 896, Column 159: reference not terminated by REFC delimiter
    …er.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';

    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 896, Column 159: reference to entity "clickTag" for which no system identifier could be generated
    …er.fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';

    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 895, Column 149: entity was defined here
    …fcgi/ad?section=5958&width=160&height=600&enc=1&type=iframe&js=0&clickTag=';   

Visitor Analysis

Daily Visitor
  • 10.150 visits
Daily Visitor