abante-tonite.com has Alexa Rank 52.413 and Google Page Rank is 4

abante-tonite.com
  • Domain Name
    abante-tonite.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #52413
  • Page Size
    823 B
  • Ip Address
    66.135.60.19
  • Heading
    H1: 1, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Abante Tonite Online
  • Meta Keyword
  • Meta Description

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    66.135.60.19
  • Domain Age
    14 Years, 8 Months, 18 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from abante-tonite.com.

HTML Analysis

  • date: Mon, 15 Jul 2013 18:11:31 GMT
  • server: Apache
  • last-modified: Sat, 27 Oct 2012 16:06:10 GMT
  • etag: "48d009f-324-4cd0c9d590080"
  • accept-ranges: bytes
  • content-length: 804
  • connection: close
  • content-type: text/html; charset=UTF-8
  • age: 305582
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
No data whois for abante-tonite.com

DNS Analysis


DNS servers
ns1.abante-tonite.com [66.135.60.19]
ns2.abante-tonite.com [216.152.131.164]


DNS Records

Answer records
abante-tonite.com SOA
server: ns1.abante-tonite.com
email: postmaster@abante-tonite.com
serial: 2009081901
refresh: 28800
retry: 14400
expire: 3600000
minimum ttl: 86400
86400s
abante-tonite.com NS  ns1.abante-tonite.com 86400s
abante-tonite.com NS  ns2.abante-tonite.com 86400s
abante-tonite.com NS  ns3.abante-tonite.com 86400s
abante-tonite.com MX
preference: 10
exchange: mail.abante-tonite.com
86400s
abante-tonite.com MX
preference: 20
exchange: mail2.abante-tonite.com
86400s
abante-tonite.com A 66.135.60.19 86400s

Authority records

Additional records
ns1.abante-tonite.com A 66.135.60.19 86400s
ns2.abante-tonite.com A 216.152.131.164 86400s
ns3.abante-tonite.com A 66.135.50.97 86400s
mail.abante-tonite.com A 66.135.60.19 86400s
mail2.abante-tonite.com A 66.135.50.97 86400s

IP 66.135.60.19 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 3 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.5236938031591738
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.

  • Error Line 21, 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 22, 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).

  • Warning Line 26, Column 35: NET-enabling start-tag requires SHORTTAG YES
    This site requires Javascript.<br />

    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
  • 4.317 visits

Recently Update