desitales.com

desitales.com has Alexa Rank 48.877 and Google Page Rank is 1

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    desitales.com
  • Favicon
  • Alexa Rank
    #48877
  • Google Page Rank
    PR 1
  • Ip Address
    173.239.35.228
  • Page Size
    6.9 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    2 1 2 0 0 0

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    173.239.35.228
  • Domain Age
    4 Years, 4 Months, 4 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 01 Aug 2013 17:53:13 GMT
  • server: Apache
  • content-length: 6732
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA


Authorized Registration Services Provider:

Domain Name Systems

For support regarding this domain please visit
http://www.domainnamesystems.com

Domain Name: desitales.com
Status: clientTransferProhibited

Registrant / Administrative Details:

DEMETA STAVRINU
KIASTINA TECHNOLOGIES LIMITED
SUITE 2
GLACIS ROAD
NA
NA
GI
Tel: 1.11111111111
Fax: 1.11111111111
Email: email

Technical Details:

DEMETA STAVRINU
KIASTINA TECHNOLOGIES LIMITED
SUITE 2
GLACIS ROAD
NA
NA
GI
Tel: 1.11111111111
Fax: 1.11111111111
Email: email

Registration Date: 2009-02-24
Expiration Date: 2013-02-24
Domain Last Updated: 2012-02-24 22:32:38.0

Nameserver Information:

ns.webair.net
ns2.webair.net





IP 173.239.35.228 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Garden City
  • Continent Code
    11530
  • Latitude
    516
  • Longitude
    501
  • %rwhois V-1.5:003fff:00 rwhois.webair.com (by Network Solutions, Inc. V-1.5.7.3)
    network:Class-Name:network
    network:ID:173.239.35.224/27
    network:Auth-Area:173.239.0.0/18
    network:Network-Name:Kiastrina_Technologies_Limited--block
    network:IP-Network:173.239.35.224/27
    network:Org-Name:Kiastrina_Technologies_Limited
    network:Street-Address:Suite_2
    network:City:na
    network:State:Gibraltar
    network:Postal-Code:na
    network:Country-Code:Albania
    network:Tech-Contact;I:
    network:Admin-Contact;I:
    network:Created:20130124
    network:Updated:20130124
    network:Updated-By:

    network:Class-Name:network
    network:ID:173.239.0.0/18
    network:Auth-Area:173.239.0.0/18
    network:Network-Name:Webair
    network:IP-Network:173.239.0.0/18
    network:Org-Name:Webair
    network:Street-Address:1025 Old Country Road
    network:City:Westbury
    network:State:NY
    network:Postal-Code:11590
    network:Country-Code:USA
    network:Tech-Contact;I:
    network:Admin-Contact;I:
    network:Created:20130124
    network:Updated:20130124
    network:Updated-By:

    network:Class-Name:network
    network:ID:173.239.35.224/27
    network:Auth-Area:173.239.0.0/18
    network:Network-Name:Kiastrina_Technologies_Limited--block
    network:IP-Network:173.239.35.224/27
    network:Org-Name:Kiastrina_Technologies_Limited
    network:Street-Address:Suite_2
    network:City:na
    network:State:Gibraltar
    network:Postal-Code:na
    network:Country-Code:Albania
    network:Tech-Contact;I:
    network:Admin-Contact;I:
    network:Created:20130124
    network:Updated:20130124
    network:Updated-By:

    %ok

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 15 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.6028109627547436
Message Error
  • Error Line 24, Column 84: document type does not allow element "script" here; assuming missing "body" start-tag
    …text/javascript" src="http://hot-india.com/IPE_Top_Nav_Bar/static.js"></script>
  • Error Line 25, Column 24: document type does not allow element "body" here
    <body class="home blog"> 

    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 41, Column 63: there is no attribute "onFocus"
    …lue="Search: type, hit enter" onFocus="if (this.value == 'Search: type, hit en…

    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 41, Column 136: there is no attribute "onBlur"
    …it enter') {this.value = '';}" onBlur="if (this.value == '') {this.value = 'Se…

    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 57, Column 57: required attribute "type" not specified
    	<script src="http://desitales.com/tales/homepagenew.js"></script>

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

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

  • Error Line 72, Column 57: required attribute "type" not specified
    				<script src="http://desitales.com/tales/category.js"></script>

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

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

  • Error Line 74, Column 58: document type does not allow element "script" here; assuming missing "li" start-tag
    					<script language="JavaScript" type="text/javascript">
  • Error Line 79, Column 9: end tag for "li" omitted, but OMITTAG NO was specified
    				</ul>

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

  • Info Line 74, Column 6: start tag was here
    					<script language="JavaScript" type="text/javascript">
  • Error Line 84, Column 6: character data is not allowed here
    					Desi Tales is also available on Mobile Phones. Simply visit <a href="http:…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 84, Column 99: document type does not allow element "a" here; assuming missing "li" start-tag
    …ile Phones. Simply visit <a href="http://m.desitales.com/">m.desitales.com</a>.
  • Error Line 85, Column 9: end tag for "li" omitted, but OMITTAG NO was specified
    				</ul>

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

  • Info Line 84, Column 66: start tag was here
    …ilable on Mobile Phones. Simply visit <a href="http://m.desitales.com/">m.desi…
  • Warning Line 111, Column 69: cannot generate system identifier for general entity "lp"
    …ve.com/releasese/da_js.asp?banner=165&lp=0&width=200&height=200&wid=1251706090…

    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 111, Column 69: general entity "lp" not defined and no default entity
    …ve.com/releasese/da_js.asp?banner=165&lp=0&width=200&height=200&wid=1251706090…

    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 111, Column 71: reference not terminated by REFC delimiter
    ….com/releasese/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609065…

    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 111, Column 71: reference to external entity in attribute value
    ….com/releasese/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609065…

    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 111, Column 71: reference to entity "lp" for which no system identifier could be generated
    ….com/releasese/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609065…

    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 111, Column 68: entity was defined here
    …ive.com/releasese/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609…
  • Warning Line 111, Column 74: cannot generate system identifier for general entity "width"
    …m/releasese/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609065&pr…

    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 111, Column 74: general entity "width" not defined and no default entity
    …m/releasese/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609065&pr…

    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 111, Column 79: reference not terminated by REFC delimiter
    …easese/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609065&promoco…

    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 111, Column 79: reference to external entity in attribute value
    …easese/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609065&promoco…

    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 111, Column 79: reference to entity "width" for which no system identifier could be generated
    …easese/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609065&promoco…

    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 111, Column 73: entity was defined here
    …om/releasese/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609065&p…
  • Warning Line 111, Column 84: cannot generate system identifier for general entity "height"
    …e/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609065&promocode=DE…

    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 111, Column 84: general entity "height" not defined and no default entity
    …e/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609065&promocode=DE…

    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 111, Column 90: reference not terminated by REFC delimiter
    …s.asp?banner=165&lp=0&width=200&height=200&wid=125170609065&promocode=DESITALE…

    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 111, Column 90: reference to external entity in attribute value
    …s.asp?banner=165&lp=0&width=200&height=200&wid=125170609065&promocode=DESITALE…

    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 111, Column 90: reference to entity "height" for which no system identifier could be generated
    …s.asp?banner=165&lp=0&width=200&height=200&wid=125170609065&promocode=DESITALE…

    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 111, Column 83: entity was defined here
    …se/da_js.asp?banner=165&lp=0&width=200&height=200&wid=125170609065&promocode=D…
  • Warning Line 111, Column 95: cannot generate system identifier for general entity "wid"
    …?banner=165&lp=0&width=200&height=200&wid=125170609065&promocode=DESITALES" ty…

    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 111, Column 95: general entity "wid" not defined and no default entity
    …?banner=165&lp=0&width=200&height=200&wid=125170609065&promocode=DESITALES" ty…

    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 111, Column 98: reference not terminated by REFC delimiter
    …nner=165&lp=0&width=200&height=200&wid=125170609065&promocode=DESITALES" type=…

    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 111, Column 98: reference to external entity in attribute value
    …nner=165&lp=0&width=200&height=200&wid=125170609065&promocode=DESITALES" type=…

    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 111, Column 98: reference to entity "wid" for which no system identifier could be generated
    …nner=165&lp=0&width=200&height=200&wid=125170609065&promocode=DESITALES" type=…

    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 111, Column 94: entity was defined here
    …p?banner=165&lp=0&width=200&height=200&wid=125170609065&promocode=DESITALES" t…
  • Warning Line 111, Column 112: cannot generate system identifier for general entity "promocode"
    …width=200&height=200&wid=125170609065&promocode=DESITALES" type="text/javascri…

    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 111, Column 112: general entity "promocode" not defined and no default entity
    …width=200&height=200&wid=125170609065&promocode=DESITALES" type="text/javascri…

    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 111, Column 121: reference not terminated by REFC delimiter
    …&height=200&wid=125170609065&promocode=DESITALES" type="text/javascript"></scr…

    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 111, Column 121: reference to external entity in attribute value
    …&height=200&wid=125170609065&promocode=DESITALES" type="text/javascript"></scr…

    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 111, Column 121: reference to entity "promocode" for which no system identifier could be generated
    …&height=200&wid=125170609065&promocode=DESITALES" type="text/javascript"></scr…

    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 111, Column 111: entity was defined here
    …&width=200&height=200&wid=125170609065&promocode=DESITALES" type="text/javascr…
  • Error Line 114, Column 7: end tag for "body" omitted, but OMITTAG NO was specified
    </html>

    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 24, Column 1: start tag was here
    <script type="text/javascript" src="http://hot-india.com/IPE_Top_Nav_Bar/static…

Visitor Analysis

Daily Visitor
  • 3.267 visits

In Page Analysis