IndianOil Corporation Ltd is India's largest commercial enterprise. The IndianOil Group of companies owns and operates 10 of India's 20 refineries. Besides, the corporation supplies Indane Gas to over 47.5 million households through ...

iocl.com
  • Domain Name
    iocl.com
  • Favicon
  • Google Page Rank
    7
  • Alexa Rank
    #45245
  • Page Size
    45.4 KB
  • Ip Address
    119.82.71.126
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 1, H5: 0, H6: 0
  • Images
    15 GIF, 8 JPG, 0 PNG

Website Meta Analysis

  • Title
    Indian Oil Corporation Ltd. : IndianOil : Iocl.com
  • Meta Keyword
    IndianOil, Indian Oil Corporation, Indian Oil Corporation Ltd, Indane Gas, Auto Gas, Natural Gas, Aviation Turbine Fuel, Marine Fuels and Lubricants, Railroad Greases and Oil, Furnace Oil, Industrial Fuel, Diesel Engine Oil, Synthetic Engine Oil, Crude Oil, Natural Oil and Gas.
  • Meta Description
    IndianOil Corporation Ltd is India's largest commercial enterprise. The IndianOil Group of companies owns and operates 10 of India's 20 refineries. Besides, the corporation supplies Indane Gas to over 47.5 million households through a network of 4,990 Indian distributors. It also deals in Railroad Greases and Oil, Furnace Oil and Industrial Fuel.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.0
  • Ip Address
    119.82.71.126
  • Domain Age
    17 Years, 1 Months, 5 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: no-cache,public, max-age=40
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • expires: Tue, 10 Sep 2013 23:56:23 GMT
  • last-modified: Tue, 10 Sep 2013 23:55:43 GMT
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.0
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • date: Tue, 10 Sep 2013 23:55:43 GMT
  • content-length: 14948
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for iocl.com

DNS Analysis


DNS servers
ns4.4cplus.com [119.82.71.104]
ns4c.4cplus.com [72.29.1.226]


DNS Records

Answer records
iocl.com A 119.82.71.126 3600s
iocl.com NS  ns4c.4cplus.com 3600s
iocl.com SOA
server: ns4c.4cplus.com
email: hostmaster@4cplus.com
serial: 22
refresh: 900
retry: 600
expire: 86400
minimum ttl: 3600
3600s
iocl.com 28 [16 bytes] 3600s

Authority records

Additional records
ns4c.4cplus.com A 72.29.1.226 3600s

IP 119.82.71.126 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 8 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.5752113403170642
Message Error
  • Error Line 269, Column 58: an attribute specification must start with a name or name token
            border-right-color: #02164f; padding-right: 10px"">

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Warning Line 634, Column 264: character "&" is the first character of a delimiter but occurred as data
    …l Maintenance/ Instrumentation / Power & Utility / Fire & Safety).</b></a></li>

    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 634, Column 281: character "&" is the first character of a delimiter but occurred as data
    …l Maintenance/ Instrumentation / Power & Utility / Fire & Safety).</b></a></li>

    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 638, Column 92: cannot generate system identifier for general entity "tID"
    …/Aboutus/NewsDetail.aspx?NewsID=23538&tID=59" target="_self"><b>IndianOil reta…

    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 638, Column 92: general entity "tID" not defined and no default entity
    …/Aboutus/NewsDetail.aspx?NewsID=23538&tID=59" target="_self"><b>IndianOil reta…

    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 638, Column 95: reference not terminated by REFC delimiter
    …outus/NewsDetail.aspx?NewsID=23538&tID=59" target="_self"><b>IndianOil retains…

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

  • Warning Line 638, Column 95: reference to external entity in attribute value
    …outus/NewsDetail.aspx?NewsID=23538&tID=59" target="_self"><b>IndianOil retains…

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

  • Error Line 638, Column 95: reference to entity "tID" for which no system identifier could be generated
    …outus/NewsDetail.aspx?NewsID=23538&tID=59" target="_self"><b>IndianOil retains…

    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 638, Column 91: entity was defined here
    …"/Aboutus/NewsDetail.aspx?NewsID=23538&tID=59" target="_self"><b>IndianOil ret…
  • Warning Line 641, Column 96: reference not terminated by REFC delimiter
    …outus/NewsDetail.aspx?NewsID=23444&tID=58" target="_self"><b>IndianOil’s Singa…

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

  • Warning Line 641, Column 96: reference to external entity in attribute value
    …outus/NewsDetail.aspx?NewsID=23444&tID=58" target="_self"><b>IndianOil’s Singa…

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

  • Error Line 641, Column 96: reference to entity "tID" for which no system identifier could be generated
    …outus/NewsDetail.aspx?NewsID=23444&tID=58" target="_self"><b>IndianOil’s Singa…

    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 638, Column 91: entity was defined here
    …"/Aboutus/NewsDetail.aspx?NewsID=23538&tID=59" target="_self"><b>IndianOil ret…
  • Warning Line 642, Column 97: reference not terminated by REFC delimiter
    …outus/NewsDetail.aspx?NewsID=23445&tID=58" target="_self"><b>IndianOil locatio…

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

  • Warning Line 642, Column 97: reference to external entity in attribute value
    …outus/NewsDetail.aspx?NewsID=23445&tID=58" target="_self"><b>IndianOil locatio…

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

  • Error Line 642, Column 97: reference to entity "tID" for which no system identifier could be generated
    …outus/NewsDetail.aspx?NewsID=23445&tID=58" target="_self"><b>IndianOil locatio…

    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 638, Column 91: entity was defined here
    …"/Aboutus/NewsDetail.aspx?NewsID=23538&tID=59" target="_self"><b>IndianOil ret…
  • Warning Line 645, Column 95: reference not terminated by REFC delimiter
    …outus/NewsDetail.aspx?NewsID=23330&tID=58" target="_self" ><b>IndianOil bags S…

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

  • Warning Line 645, Column 95: reference to external entity in attribute value
    …outus/NewsDetail.aspx?NewsID=23330&tID=58" target="_self" ><b>IndianOil bags S…

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

  • Error Line 645, Column 95: reference to entity "tID" for which no system identifier could be generated
    …outus/NewsDetail.aspx?NewsID=23330&tID=58" target="_self" ><b>IndianOil bags S…

    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 638, Column 91: entity was defined here
    …"/Aboutus/NewsDetail.aspx?NewsID=23538&tID=59" target="_self"><b>IndianOil ret…
  • Error Line 804, 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).

Visitor Analysis

Daily Visitor
  • 1.867 visits