topaz.az has Alexa Rank 34.970 and Google Page Rank is 3

topaz.az
  • Domain Name
    topaz.az
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #34970
  • Page Size
    266 B
  • Ip Address
    217.14.96.108
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Topaz.az
  • Meta Keyword
  • Meta Description

Technical Analysis

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

Hyper Text Transfer Protocol (HTTP) header show data header response from topaz.az.

HTML Analysis

  • date: Thu, 20 Jun 2013 07:01:15 GMT
  • server: Apache
  • last-modified: Fri, 20 Jul 2012 04:37:56 GMT
  • accept-ranges: bytes
  • content-length: 257
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for topaz.az

DNS Analysis


DNS servers
ns2.host.az
ns3.host.az
ns1.host.az


DNS Records

Answer records
topaz.az SOA
server: ns1.host.az
email: support@intrans.baku.az
serial: 2012122500
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
topaz.az NS  ns3.host.az 86400s
topaz.az NS  ns1.host.az 86400s
topaz.az NS  ns2.host.az 86400s
topaz.az A 217.14.96.108 14400s
topaz.az MX
preference: 10
exchange: mail.topaz.az
14400s

Authority records

Additional records
ns1.host.az A 217.14.96.114 86400s
ns2.host.az A 217.14.96.34 86400s
ns3.host.az A 194.135.30.47 86400s
mail.topaz.az A 93.88.82.136 14400s

IP 217.14.96.108 Analysis

  • Country Code
    AZ
  • Country Code3
    AZE
  • Country Name
    Azerbaijan
  • City
    AS
  • Continent Code
    40.5° North
  • Latitude
    47.5.
  • Longitude
  • No whois ip data for 217.14.96.108

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 6 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.7105263157894737
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 3, Column 68: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

    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 3, Column 69: character data is not allowed here
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

    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.
  • Warning Line 4, Column 73: NET-enabling start-tag requires SHORTTAG YES
    <title>Topaz.az</title><meta http-equiv="refresh" content="0;URL=/web/" />

    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 5, Column 7: 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 5, Column 7: document type does not allow element "STYLE" here
    <style>

    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 8, Column 7: end tag for element "HEAD" which is not open
    </head>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 10, Column 6: document type does not allow element "BODY" here
    <body>

    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
  • 5.367 visits
Daily Visitor