90di.com

Search flight fares, train routes, reservation details, train fare & and time table. Search online bus booking. Book directly at IRCTC and airlines website. Find train & flight connections & and route map. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 15-09-2013 11:33:47  (update).

Overview Info

  • Domain Name
    90di.com
  • Favicon
  • Alexa Rank
    #44533
  • Google Page Rank
    PR 3
  • Ip Address
    175.41.136.10
  • Page Size
    26.6 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 0 1 1 0

Website Meta Analysis



  • Title
    Search Indian Railways & irctc train route, flight fare & bus tickets | 90di
  • Meta Keyword
    IRCTC trains, Indial Railways trains,train connections, train & flight connections, train time table, online bus booking, train route map
  • Meta Description
    Search flight fares, train routes, reservation details, train fare & and time table. Search online bus booking. Book directly at IRCTC and airlines website. Find train & flight connections & and route map.

Technical Analysis



  • Webserver
    nginx/1.3.10
  • Ip Address
    175.41.136.10
  • Domain Age
    6 Years, 3 Months, 5 days.
  • Javascript Library
    jquery, gwt
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-encoding: gzip
  • content-type: text/html
  • date: Sun, 15 Sep 2013 11:33:41 GMT
  • last-modified: Sat, 31 Aug 2013 07:29:37 GMT
  • server: nginx/1.3.10
  • vary: Accept-Encoding
  • content-length: 8559
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for 90di.com

DNS Analysis


DNS servers
ns1.90di.com [175.41.136.10]
ns2.90di.com [175.41.132.43]


DNS Records

Answer records
90di.com MX
preference: 0
exchange: 90di.com
500s
90di.com SOA
server: ns1.90di.com
email: khushnood@naqvi.gmail.com
serial: 2009041000
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
100s
90di.com NS  ns1.90di.com 86400s
90di.com NS  ns2.90di.com 86400s
90di.com A 175.41.136.10 500s

Authority records

Additional records
90di.com A 175.41.136.10 500s
ns1.90di.com A 175.41.136.10 14400s
ns2.90di.com A 175.41.132.43 14400s

IP 175.41.136.10 Analysis

  • Country Code
    SG
  • Country Code3
    SGP
  • Country Name
    Singapore
  • City
    AS
  • Continent Code
    1°36'67" North
  • Latitude
    103.8.
  • Longitude
  • % [whois.apnic.net node-7]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 175.41.128.0 - 175.41.159.255
    netname: AMAZON-AP-RESOURCES-SG
    descr: Amazon Web Services, Elastic Compute Cloud, EC2, SG
    remarks: The activity you have detected originates from a
    dynamic hosting environment.
    For fastest response, please submit abuse reports at
    http://aws-portal.amazon.com/gp/aws/html-forms-controller/contactus/AWSAbuse
    For more information regarding EC2 see:
    http://ec2.amazonaws.com/
    All reports MUST include:
    * src IP
    * dest IP (your IP)
    * dest port
    * Accurate date/timestamp and timezone of activity
    * Intensity/frequency (short log extracts)
    * Your contact details (phone and email)
    Without these we will be unable to
    identify the correct owner of the IP address at that
    point in time.
    abuse-email: ec2-abuse@amazon.com
    country: SG
    admin-c: AARP1-AP
    tech-c: AARP1-AP
    status: ASSIGNED NON-PORTABLE
    mnt-by: MAINT-AMAZON-AP-RESOURCES-SG
    mnt-irt: IRT-AMAZON-AP-RESOURCES-SG
    changed: aes-noc@amazon.com 20110404
    source: APNIC

    role: AMAZON ASIA-PACIFIC RESOURCES PRIVATE LIMITED - ne
    address: Bedok Central Post Office PO Box 482
    country: SG
    phone: +1 -206-266-2187
    e-mail: aes-noc@amazon.com
    admin-c: AARP1-AP
    tech-c: AARP1-AP
    nic-hdl: AARP1-AP
    mnt-by: MAINT-AMAZON-AP-RESOURCES-SG
    changed: hm-changed@apnic.net 20091214
    changed: hm-changed@apnic.net 20110428
    source: APNIC


Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

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

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

  • Warning Line 7, Column 256: NET-enabling start-tag requires SHORTTAG YES
    … airlines website. Find train &amp; flight connections &amp; and route map." />

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

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

  • Warning Line 8, Column 177: NET-enabling start-tag requires SHORTTAG YES
    …; flight connections, train time table, online bus booking, train route map" />

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

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

  • Error Line 8, Column 177: document type does not allow element "META" here
    …; flight connections, train time table, online bus booking, train route map" />

    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 10, Column 56: document type does not allow element "META" here
            <META content="http://www.90di.com" name=author>

    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 13, Column 51: document type does not allow element "LINK" here
            <link rel="stylesheet" href="css/90di.css">        

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

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

  • Warning Line 15, Column 81: NET-enabling start-tag requires SHORTTAG YES
    …meta name="verify-v1" content="fPPKReldJOoxpJfzkasH/hWmevYmTyFE7v+YIEeX6Pk=" />

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

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

  • Error Line 15, Column 81: document type does not allow element "META" here
    …meta name="verify-v1" content="fPPKReldJOoxpJfzkasH/hWmevYmTyFE7v+YIEeX6Pk=" />

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

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

  • Warning Line 16, Column 81: NET-enabling start-tag requires SHORTTAG YES
    …meta name="verify-v1" content="BByPspxwVzxVx19a7UbFMUBY5Q/pAmHSj2ndzOAI+ak=" />

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

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

  • Error Line 16, Column 81: document type does not allow element "META" here
    …meta name="verify-v1" content="BByPspxwVzxVx19a7UbFMUBY5Q/pAmHSj2ndzOAI+ak=" />

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

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

  • Warning Line 17, Column 81: NET-enabling start-tag requires SHORTTAG YES
    …meta name="verify-v1" content="/XNuqOu0o6/gCWbF96WDkiuEQ1TADoQNNEYLr6inkDk=" />

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

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

  • Error Line 17, Column 81: document type does not allow element "META" here
    …meta name="verify-v1" content="/XNuqOu0o6/gCWbF96WDkiuEQ1TADoQNNEYLr6inkDk=" />

    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 19, Column 23: document type does not allow element "STYLE" here
    <style type="text/css">

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

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

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

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

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

  • Error Line 112, Column 6: document type does not allow element "BODY" here
    <body>

    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 114, Column 33: value of attribute "ID" invalid: "_" cannot start a name
    <iframe src="javascript:''" id='__gwt_historyFrame' style='width:0;height:0;bor…

    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 130, Column 18: there is no attribute "HEIGHT"
    			<table height="100%" cellspacing="0" cellpadding="0" 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 169, Column 9: ID "NAV_TOOLS_RESULT_PAGE" already defined
    <ul id="nav_tools_result_page">

    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 9: ID "NAV_TOOLS_RESULT_PAGE" first defined here
    <ul id="nav_tools_result_page">
  • Warning Line 196, Column 259: NET-enabling start-tag requires SHORTTAG YES
    …r search query');" onblur="setDefaultValue(this, 'Enter your search query');"/>

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

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

  • Warning Line 197, Column 75: NET-enabling start-tag requires SHORTTAG YES
    <input class="freetextsearchbar-submitbutton" type="submit" value="Search"/>

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

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

  • Error Line 217, Column 11: element "G:PLUSONE" undefined
    <g:plusone></g:plusone>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 219, Column 173: NET-enabling start-tag requires SHORTTAG YES
    …/image/fb_favicon.ico" class ="fbTwitterLogoImage" /> Like 90di on FaceBook</a>

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

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

  • Error Line 219, Column 173: required attribute "ALT" not specified
    …/image/fb_favicon.ico" class ="fbTwitterLogoImage" /> Like 90di on FaceBook</a>

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

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

  • Error Line 246, Column 9: ID "MENU_REGISTER" already defined
    <li id="menu_register"><a href="#" onclick="javascript:handleClickEvent('menu_r…

    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 157, Column 9: ID "MENU_REGISTER" first defined here
    <li id="menu_register"><a href="#" onclick="javascript:handleClickEvent('menu_r…
  • Error Line 247, Column 9: ID "MENU_SIGNIN" already defined
    <li id="menu_signin"><a href="#" onclick="javascript:handleClickEvent('menu_sig…

    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 158, Column 9: ID "MENU_SIGNIN" first defined here
    <li id="menu_signin"><a href="#" onclick="javascript:handleClickEvent('menu_sig…
  • Error Line 259, Column 9: ID "NAV_TOOLS" already defined
    <ul id="nav_tools">

    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 244, Column 9: ID "NAV_TOOLS" first defined here
    <ul id="nav_tools">
  • Error Line 260, Column 9: ID "MENU_EDIT_PROFILE" already defined
    <li id="menu_edit_profile"><a href="#" onclick="javascript:handleClickEvent('me…

    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 170, Column 9: ID "MENU_EDIT_PROFILE" first defined here
    <li id="menu_edit_profile"><a href="#" onclick="javascript:handleClickEvent('me…
  • Error Line 261, Column 9: ID "MENU_SIGN_OUT" already defined
    <li id="menu_sign_out"><a href="#" onclick="javascript:handleClickEvent('menu_s…

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

  • Info Line 171, Column 9: ID "MENU_SIGN_OUT" first defined here
    <li id="menu_sign_out"><a href="#" onclick="javascript:handleClickEvent('menu_s…
  • Warning Line 276, Column 271: NET-enabling start-tag requires SHORTTAG YES
    …ur="setDefaultValue(this, 'Enter your search query - See examples below..');"/>

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

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

  • Warning Line 278, Column 101: NET-enabling start-tag requires SHORTTAG YES
    …chButton" class="freetextsearchbar-submitbutton" type="submit" value="Search"/>

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

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

  • Warning Line 279, Column 3: NET-enabling start-tag requires SHORTTAG YES
    <p/>													

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

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

  • Warning Line 284, Column 3: NET-enabling start-tag requires SHORTTAG YES
    <p/>							

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

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

  • Error Line 285, Column 8: ID "EXAMPLE" already defined
    <a id="example" onclick="javascript:handleExampleSearch('Bangalore to Raipur vi…

    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 283, Column 8: ID "EXAMPLE" first defined here
    <a id="example" onclick="javascript:handleExampleSearch('Bangalore to Mumbai fl…
  • Warning Line 286, Column 3: NET-enabling start-tag requires SHORTTAG YES
    <p/>

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

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

  • Error Line 325, Column 164: end tag for element "P" which is not open
    … by us<sup style="background-color: RED; color: YELLOW;">New</sup></a></p></li>

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

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

  • Error Line 350, Column 58: end tag for element "BR" which is not open
    							<a class="footerInfoLinks"><b>Flights:</b></a></br>

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

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

  • Warning Line 351, Column 140: NET-enabling start-tag requires SHORTTAG YES
    …ap on 90di" href="http://www.90di.com/flights-map/">India Flights Map</a> <br/>

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

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

  • Error Line 361, Column 12: end tag for element "BR" which is not open
    							</br>

    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 374, Column 57: end tag for element "BR" which is not open
    							<a class="footerInfoLinks"><b>Trains:</b></a></br>

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

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

    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 398, Column 56: end tag for element "BR" which is not open
    							<a class="footerInfoLinks"><b>Buses:</b></a></br>

    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 415, Column 13: value of attribute "ID" invalid: "_" cannot start a name
    <iframe id="__printingFrame" style="width:0;height:0;border:0"></iframe>

    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.

  • Warning Line 419, Column 85: NET-enabling start-tag requires SHORTTAG YES
    … type="hidden" name="releaseversion" id="releaseversion" value="201301311823"/>

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

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

  • Warning Line 431, Column 27: NET-enabling start-tag requires SHORTTAG YES
    	<div id="googleAnalytics"/>

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

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

  • Error Line 438, Column 3: end tag for "SCRIPT" omitted, but its declaration does not permit this
    		// var tellAFriendDivIds = new Array('tellAFriend_1','tellAFriend_2');
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

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

  • Info Line 432, Column 2: start tag was here
    	<script language='javascript' type="text/javascript">
  • Error Line 501, Column 10: end tag for element "SCRIPT" which is not open
    	</script>

    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.

Visitor Analysis

Daily Visitor
  • 4.317 visits

In Page Analysis