Search Call Support No: 1800 108 4444 www.net4.in Sign In   User name Password Remember me (?) Enterprise Services @ Net4 Internet Leased Line Cloud Servers/Hosting Hosted Applications Data Center Solutions VOIP/International Calling ...

mail4india.com
  • Domain Name
    mail4india.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #36258
  • Page Size
    12.3 KB
  • Ip Address
    118.67.248.41
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 4 JPG, 2 PNG

Website Meta Analysis

  • Title
    Mail4India
  • Meta Keyword
  • Meta Description
    Search Call Support No: 1800 108 4444 www.net4.in Sign In   User name Password Remember me (?) Enterprise Services @ Net4 Internet Leased Line Cloud Servers/Hosting Hosted Applications Data Center Solutions VOIP/International Calling Hosted ...

Technical Analysis

  • Webserver
    Apache/2.2.23 (CentOS)
  • Ip Address
    118.67.248.41
  • Domain Age
    13 Years, 6 Months, 29 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 26 Jun 2013 23:17:00 GMT
  • server: Apache/2.2.23 (CentOS)
  • x-powered-by: PHP/5.3.21
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

Registrant :
Name: Jasjit Sawhney
Organization: Net4 India Ltd
Address: AB11 Community Centre, Safdarjung Enclave
City: New Delhi
State: DL
Postal Code: 110029
Country: IN
Phone: +91.1126711150
Fax:
Email: email

Domain : mail4india.com

Administrative Contact :
Name: Jasjit Sawhney
Organization: Net4 India Ltd
Address: AB11 Community Centre, Safdarjung Enclave
City: New Delhi
State: DL
Postal Code: 110029
Country: IN
Phone: +91.1126711150
Fax:
Email: email

Technical Contact :
Name: Jasjit Sawhney
Organization: Net4 India Ltd
Address: AB11 Community Centre, Safdarjung Enclave
City: New Delhi
State: DL
Postal Code: 110029
Country: IN
Phone: +91.1126711150
Fax:
Email: email

Created on.......: 1999-12-08
Expired on.......: 2017-12-08
Last updated on..: 2008-11-21

Domain servers :



The Data in the NET4INDIA LIMITED Registrar WHOIS database is provided to you by NET4INDIA LIMITED
for information purposes only, and may be used to assist you in obtaining
information about or related to a domain name's registration record.

NET4INDIA LIMITED makes this information available "as is," and does not guarantee its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
a) allow, enable, or otherwise support the transmission by e-mail,
telephone, or facsimile of mass, unsolicited, commercial advertising or
solicitations to entities other than the data recipient's own existing
customers; or (b) enable high volume, automated, electronic processes that
send queries or data to the systems of any Registry Operator or
ICANN-Accredited registrar, except as reasonably necessary to register
domain names or modify existing registrations.

NET4INDIA LIMITED reserves the right to terminate your access to the NET4INDIA LIMITED WHOIS
database in its sole discretion, including without limitation, for excessive
querying of the WHOIS database or for failure to otherwise abide by this policy.

NET4INDIA LIMITED reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by these terms.

NOTE: THE WHOIS DATABASE IS A CONTACT DATABASE ONLY. LACK OF A DOMAIN
RECORD DOES NOT SIGNIFY DOMAIN AVAILABILITY.

DNS Analysis


DNS servers
ns2.net4india.com [202.71.128.37]
ns1.net4india.com [202.71.129.33]


DNS Records

Answer records
mail4india.com SOA
server: ns1.net4india.com
email: hostmaster@net4india.com
serial: -1294966150
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
3600s
mail4india.com A 118.67.248.41 3600s
mail4india.com MX
preference: 10
exchange: mail.net4india.com
3600s
mail4india.com NS  ns1.net4india.com 3600s
mail4india.com TXT google-site-verification=AAwmDnoMfYdVjLCYffYxPzKMCJ5LhHnzrlfO5ne3hVU 3600s
mail4india.com NS  ns2.net4india.com 3600s

Authority records

Additional records
ns2.net4india.com A 202.71.128.37 3600s
mail.net4india.com A 118.67.248.42 3600s
ns1.net4india.com A 202.71.129.33 3600s

IP 118.67.248.41 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 20 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.5447957314645218
Message Error
  • Error Line 11, 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>.

  • Warning Line 17, Column 19: character "<" is the first character of a delimiter but occurred as data
        for (i = 0; i < document.login_form.elements.length; 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 55, Column 14: there is no attribute "onLoad"
    <body onLoad="squirrelmail_loginpage_onload();">    <div class="wrapper">

    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 64, Column 84: required attribute "alt" not specified
    …         <img src="../images/leftcurve-login.png" width="9" height="9" /></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 68, Column 85: required attribute "alt" not specified
    …        <img src="../images/rightcurve-login.png" width="9" height="9" /></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 83, Column 155: end tag for "input" omitted, but OMITTAG NO was specified
    …" value="" tabindex="1" class="commonformfield" onfocus="alreadyFocused=true;">

    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 83, Column 37: start tag was here
                                        <input type="text" name="login_username" va…
  • Error Line 87, Column 109: end tag for "input" omitted, but OMITTAG NO was specified
    …"password" class="commonformfield" tabindex="2" onfocus="alreadyFocused=true;">

    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 87, Column 1: start tag was here
    <input name="secretkey" type="password" class="commonformfield" tabindex="2" on…
  • Error Line 93, Column 48: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …       <option value="simple" selected>Normal</option><option value="advanced"…

    "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 94, Column 92: end tag for "input" omitted, but OMITTAG NO was specified
    …       <input type="hidden" name="js_autodetect_results" value="SMPREF_JS_OFF">

    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 94, Column 20: start tag was here
                       <input type="hidden" name="js_autodetect_results" value="SMP…
  • Error Line 95, Column 72: end tag for "input" omitted, but OMITTAG NO was specified
                      <input type="hidden" name="just_logged_in" value="1">

    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 95, Column 19: start tag was here
                      <input type="hidden" name="just_logged_in" value="1">
  • Error Line 100, Column 8: an attribute value must be a literal unless it contains only name characters
    <li id=\'login_auto\'><input type='checkbox' name='remdetails'>Remember Name & …

    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 100, Column 8: character "\" is not allowed in the value of attribute "id"
    <li id=\'login_auto\'><input type='checkbox' name='remdetails'>Remember Name & …

    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 100, Column 64: end tag for "input" omitted, but OMITTAG NO was specified
    …put type='checkbox' name='remdetails'>Remember Name & Password</li>           …

    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 100, Column 23: start tag was here
    <li id=\'login_auto\'><input type='checkbox' name='remdetails'>Remember Name & …
  • Warning Line 100, Column 78: character "&" is the first character of a delimiter but occurred as data
    …kbox' name='remdetails'>Remember Name & Password</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.
  • Error Line 100, Column 281: end tag for "input" omitted, but OMITTAG NO was specified
    …submit" value="Login" id="btn" style="cursor:pointer;" class="green-login-btn">

    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 100, Column 175: start tag was here
    …ext-align: center; margin-left:40px;"><input name="button" type="submit" value…
  • Warning Line 125, Column 92: cannot generate system identifier for general entity "utm_medium"
    …n-registration.aspx?utm_source=banner&utm_medium=direct&utm_campaign=new-in-do…

    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 125, Column 92: general entity "utm_medium" not defined and no default entity
    …n-registration.aspx?utm_source=banner&utm_medium=direct&utm_campaign=new-in-do…

    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 125, Column 102: reference not terminated by REFC delimiter
    …tion.aspx?utm_source=banner&utm_medium=direct&utm_campaign=new-in-domain-regis…

    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 125, Column 102: reference to external entity in attribute value
    …tion.aspx?utm_source=banner&utm_medium=direct&utm_campaign=new-in-domain-regis…

    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 125, Column 102: reference to entity "utm_medium" for which no system identifier could be generated
    …tion.aspx?utm_source=banner&utm_medium=direct&utm_campaign=new-in-domain-regis…

    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 125, Column 91: entity was defined here
    …in-registration.aspx?utm_source=banner&utm_medium=direct&utm_campaign=new-in-d…
  • Warning Line 125, Column 110: cannot generate system identifier for general entity "utm_campaign"
    …x?utm_source=banner&utm_medium=direct&utm_campaign=new-in-domain-registration"…

    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 125, Column 110: general entity "utm_campaign" not defined and no default entity
    …x?utm_source=banner&utm_medium=direct&utm_campaign=new-in-domain-registration"…

    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 125, Column 122: reference not terminated by REFC delimiter
    …=banner&utm_medium=direct&utm_campaign=new-in-domain-registration" target="_bl…

    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 125, Column 122: reference to external entity in attribute value
    …=banner&utm_medium=direct&utm_campaign=new-in-domain-registration" target="_bl…

    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 125, Column 122: reference to entity "utm_campaign" for which no system identifier could be generated
    …=banner&utm_medium=direct&utm_campaign=new-in-domain-registration" target="_bl…

    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 125, Column 109: entity was defined here
    …px?utm_source=banner&utm_medium=direct&utm_campaign=new-in-domain-registration…

Visitor Analysis

Daily Visitor
  • 4.667 visits
Daily Visitor