andare3009.com has Alexa Rank 30.927 and Google Page Rank is 0

andare3009.com
  • Domain Name
    andare3009.com
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #30927
  • Page Size
    122 B
  • Ip Address
    192.254.186.21
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
  • Meta Keyword
  • Meta Description

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    192.254.186.21
  • Domain Age
    2 Years, 9 Months, 2 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 03 Aug 2013 12:04:09 GMT
  • server: Apache
  • last-modified: Sun, 28 Jul 2013 11:39:54 GMT
  • accept-ranges: bytes
  • content-length: 71
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registered through: Domains Priced Right
Domain Name: ANDARE3009.COM
Created on: 16-Oct-10
Expires on: 16-Oct-14
Last Updated on: 30-Mar-12

Registrant:
sunray
108
mahara
kadawatha, western 0000
Sri Lanka

Administrative Contact:
silva, andare email
sunray
108
mahara
kadawatha, western 0000
Sri Lanka
+94.0771331992 Fax -- +94.0112344278

Technical Contact:
silva, andare email
sunray
108
mahara
kadawatha, western 0000
Sri Lanka
+94.0771331992 Fax -- +94.0112344278

Domain servers in listed order:
NS2889.HOSTGATOR.COM
NS2890.HOSTGATOR.COM

DNS Analysis


DNS servers
ns2889.hostgator.com [184.172.176.46]
ns2890.hostgator.com [184.172.184.160]


DNS Records

Answer records
andare3009.com TXT v=spf1 +a +mx +ip4:184.172.176.46 ?all 14400s
andare3009.com MX
preference: 0
exchange: andare3009.com
14400s
andare3009.com SOA
server: ns2889.hostgator.com
email: root@gator1445.hostgator.com
serial: 2012071000
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
andare3009.com NS  ns2890.hostgator.com 86400s
andare3009.com NS  ns2889.hostgator.com 86400s
andare3009.com A 184.172.184.160 14400s

Authority records

Additional records
andare3009.com A 184.172.184.160 14400s
ns2889.hostgator.com A 184.172.176.46 14400s
ns2890.hostgator.com A 184.172.184.160 14400s

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 1 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.9180327868852459
Message Error
  • Error Line 72, Column 12: there is no attribute "SRC"
    <embed src="http://www.clocklink.com/clocks/5012-orange.swf?TimeZone=SriLanka_C…

    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 72, Column 96: there is no attribute "WIDTH"
    …wf?TimeZone=SriLanka_Colombo&"  width="210" height="60" allowScriptAccess="nev…

    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 72, Column 109: there is no attribute "HEIGHT"
    …riLanka_Colombo&"  width="210" height="60" allowScriptAccess="never" wmode="tr…

    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 72, Column 132: there is no attribute "ALLOWSCRIPTACCESS"
    …h="210" height="60" allowScriptAccess="never" wmode="transparent" type="applic…

    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 72, Column 146: there is no attribute "WMODE"
    …="60" allowScriptAccess="never" wmode="transparent" type="application/x-shockw…

    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 72, Column 165: there is no attribute "TYPE"
    …tAccess="never" wmode="transparent" type="application/x-shockwave-flash"></div>

    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 72, Column 196: element "EMBED" undefined
    …tAccess="never" wmode="transparent" type="application/x-shockwave-flash"></div>

    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 112, Column 191: NET-enabling start-tag requires SHORTTAG YES
    … style="border: none;" width="124" height="52" alt="Skype Me¢®Ea!" /></a></div>

    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 122, Column 338: there is no attribute "ALLOWTRANSPARENCY"
    …ow:hidden; width:290px; height:290px;" allowTransparency="true"></iframe></div>

    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.

  • Warning Line 127, Column 362: NET-enabling start-tag requires SHORTTAG YES
    …er-width: initial; border-color: initial; border-image: initial; " /></a></div>

    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 127, Column 362: required attribute "ALT" not specified
    …er-width: initial; border-color: initial; border-image: initial; " /></a></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>.

  • Warning Line 175, Column 152: NET-enabling start-tag requires SHORTTAG YES
    …www.andare3009.com/images/1993.gif" alt="" width="650" height="90" /></a></div>

    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.

Visitor Analysis

Daily Visitor
  • 1.167 visits