mail.in.com

Get your free @in.com email address within minutes! Super-fast web and mobile access, anti-spam/virus, InDrive file sharing, FutureMail for scheduled mails, and cool App widgets! 10GB storage! ...

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

Overview Info

  • Domain Name
    mail.in.com
  • Favicon
  • Alexa Rank
    #366
  • Google Page Rank
    PR 5
  • Ip Address
    123.108.40.33
  • Page Size
    12 KB
  • Images
    0 GIF, 1 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    IN.com Mail: World's Shortest Free Email Address!
  • Meta Keyword
    free email, short email address, free webmail, mail address, spam free mailbox, free email india, india mail, in mail, future mail
  • Meta Description
    Get your free @in.com email address within minutes! Super-fast web and mobile access, anti-spam/virus, InDrive file sharing, FutureMail for scheduled mails, and cool App widgets! 10GB storage!

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    123.108.40.33
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 15 Sep 2013 15:53:14 GMT
  • server: Apache
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • x-ua-compatible: IE=EmulateIE7
  • content-length: 4230
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: IN.COM

Registrant:
Web18 Software Services Ltd.
Rohan Thale ( email )
New Era House, Mogul Lane
Mumbai
Maharashtra,400016
IN
Tel. +91.2266194400

Creation Date: 20-May-1997
Expiration Date: 21-May-2018

Domain servers in listed order:
dns1.in.com
dns2.in.com
dns3.in.com


Administrative Contact:
Web18 Software Services Ltd.
Rohan Thale ( email )
New Era House, Mogul Lane
Mumbai
Maharashtra,400016
IN
Tel. +91.2266194400

Technical Contact:
Web18 Software Services Ltd.
Rohan Thale ( email )
New Era House, Mogul Lane
Mumbai
Maharashtra,400016
IN
Tel. +91.2266194400

Billing Contact:
Web18 Software Services Ltd.
Rohan Thale ( email )
New Era House, Mogul Lane
Mumbai
Maharashtra,400016
IN
Tel. +91.2266194400

Status:ACTIVE

DNS Analysis


DNS servers
dns1.in.com [123.108.40.31]
dns2.in.com [123.108.40.32]
dns3.in.com [123.108.40.81]

DNS Records

Answer records
mail.in.com A 123.108.40.33 300s

Authority records
in.com NS  dns2.in.com 300s
in.com NS  dns3.in.com 300s
in.com NS  dns1.in.com 300s

Additional records
dns1.in.com A 123.108.40.31 300s
dns2.in.com A 123.108.40.32 1200s
dns3.in.com A 123.108.40.81 1200s

IP 123.108.40.33 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-4]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 123.108.32.0 - 123.108.63.255
    netname: NETMAGIC-NET
    descr: NETMAGIC DATACENTER
    country: IN
    admin-c: SS87-AP
    tech-c: SS87-AP
    remarks:
    remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    remarks: This object can only be updated by APNIC hostmasters.
    remarks: To update this object, please contact APNIC
    remarks: hostmasters and include your organisation's account
    remarks: name in the subject line.
    remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    changed: hm-changed@apnic.net 20070201
    mnt-by: APNIC-HM
    mnt-lower: MAINT-IN-NETMAGIC
    status: ALLOCATED PORTABLE
    source: APNIC

    route: 123.108.40.0/24
    descr: NETMAGIC_DATACENTER
    origin: AS17439
    mnt-by: MAINT-IN-NETMAGIC
    changed: nitink@netmagicsolutions.com 20081128
    source: APNIC

    person: Sharad Sanghi
    address: Mehra Industrial Estate,
    address: Near Asha Usha Compound ,
    address: LBS Marg Vikhroli(W),
    address: Mumbai - 400 079
    country: IN
    phone: +91 022-67851799
    phone: +91 022-40411799
    fax-no: +91 22-67851501
    fax-no: +91 22-40411501
    e-mail: network@netmagicsolutions.com
    nic-hdl: SS87-AP
    mnt-by: MAINT-IN-NETMAGIC
    changed: prasanna@netmagicsolutions.com 20090923
    changed: hm-changed@apnic.net 20090928
    changed: hm-changed@apnic.net 20090930
    source: APNIC


Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 23 Errors
  • 16 Warnings
Ratio Text/Html
  • 0.4107823267126064
Message Error
  • Error Line 13, Column 8: required attribute "type" not specified
    	<style>

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

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

  • Error Line 141, Column 9: required attribute "type" not specified
    	<script>

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

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

  • Warning Line 144, Column 59: character "&" is the first character of a delimiter but occurred as data
    ….appName != "Microsoft Internet Explorer" && navigator.appName != "Netscape") {

    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 144, Column 60: character "&" is the first character of a delimiter but occurred as data
    ….appName != "Microsoft Internet Explorer" && navigator.appName != "Netscape") {

    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 162, Column 44: character "&" is the first character of a delimiter but occurred as data
    … ((typeof window.sidebar == "object") && (typeof window.sidebar.addPanel == "f…

    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 162, Column 45: character "&" is the first character of a delimiter but occurred as data
    …((typeof window.sidebar == "object") && (typeof window.sidebar.addPanel == "fu…

    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 164, Column 52: character "&" is the first character of a delimiter but occurred as data
    …((typeof window.external == "object") && (typeof window.external.AddFavorite =…

    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 164, Column 53: character "&" is the first character of a delimiter but occurred as data
    …(typeof window.external == "object") && (typeof window.external.AddFavorite ==…

    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 179, Column 102: required attribute "alt" not specified
    …im.in.com/active18/mails/images/maillanding_icon2.jpg" align="left" border="0">

    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 179, Column 103: end tag for "img" omitted, but OMITTAG NO was specified
    …im.in.com/active18/mails/images/maillanding_icon2.jpg" align="left" border="0">

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

  • Info Line 179, Column 7: start tag was here
    			<p><img src="http://im.in.com/active18/mails/images/maillanding_icon2.jpg" a…
  • Error Line 190, Column 16: there is no attribute "height"
    				<tr height="70">

    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 193, Column 23: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    							<div class="in"></div>

    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 209, Column 47: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …orm name="frmloginverify" method="POST" action="http://www.in.com/loginverify.…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 210, Column 20: there is no attribute "TYPE"
    							<INPUT TYPE="hidden" id="f_sourceret" name="f_sourceret" value="http://m…

    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 210, Column 32: there is no attribute "id"
    							<INPUT TYPE="hidden" id="f_sourceret" name="f_sourceret" value="http://m…

    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 210, Column 51: there is no attribute "name"
    …T TYPE="hidden" id="f_sourceret" name="f_sourceret" value="http://mail.in.com/…

    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 210, Column 71: there is no attribute "value"
    …="f_sourceret" name="f_sourceret" value="http://mail.in.com/newmail/inbox.php">

    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 210, Column 109: element "INPUT" undefined
    …="f_sourceret" name="f_sourceret" value="http://mail.in.com/newmail/inbox.php">

    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 228, Column 65: there is no attribute "NAME"
    …class="PT3"><input type="checkbox" class="FL" NAME="rememberme" id="rememberme"

    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 251, Column 13: end tag for "INPUT" omitted, but OMITTAG NO was specified
    						</form>

    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 210, Column 8: start tag was here
    							<INPUT TYPE="hidden" id="f_sourceret" name="f_sourceret" value="http://m…
  • Warning Line 309, Column 57: character "&" is the first character of a delimiter but occurred as data
    …pt:void(0);" class="gL_11">Disclaimer & Terms Of Use</a> &nbsp;|&nbsp; <a clas…

    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 311, Column 55: duplicate specification of attribute "class"
    																																																class="gL_12"

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 344, 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>.

  • Warning Line 355, Column 50: cannot generate system identifier for general entity "c2"
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 50: general entity "c2" not defined and no default entity
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 52: reference not terminated by REFC delimiter
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 52: reference to external entity in attribute value
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 52: reference to entity "c2" for which no system identifier could be generated
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 49: entity was defined here
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>
  • Warning Line 355, Column 61: cannot generate system identifier for general entity "cv"
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 61: general entity "cv" not defined and no default entity
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 63: reference not terminated by REFC delimiter
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 63: reference to external entity in attribute value
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 63: reference to entity "cv" for which no system identifier could be generated
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 60: entity was defined here
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>
  • Warning Line 355, Column 68: cannot generate system identifier for general entity "cj"
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 68: general entity "cj" not defined and no default entity
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 70: reference not terminated by REFC delimiter
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 70: reference to external entity in attribute value
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 70: reference to entity "cj" for which no system identifier could be generated
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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 355, Column 67: entity was defined here
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>
  • Error Line 355, Column 74: required attribute "alt" not specified
    	<img src="http://b.scorecardresearch.com/p?c1=2&c2=6683813&cv=2.0&cj=1"/>

    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>.

Visitor Analysis

Daily Visitor
  • 383.833 visits

In Page Analysis