rann.tk

Rannmann's URL Shortener Enter a new URL to shorten URL: Optional custom keyword: http://rann.tk/ Optional title: bookmarklet Powered by YOURLS v1.5 ...
Last updated from 09-03-2014 12:44:01  Update data

Overview Info

  • Domain Name
    rann.tk
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    0
  • Ip Address
    173.254.28.80
  • Page Size
    2.6 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
Heading
H1H2H3H4H5H6
1 1 0 0 0 0

Website Meta Analysis

  • Title
    Rannmann's URL shortener
  • Meta Keyword
  • Meta Description
    Rannmann's URL Shortener Enter a new URL to shorten URL: Optional custom keyword: http://rann.tk/ Optional title: bookmarklet Powered by YOURLS v1.5
Advertisement

Technical Analysis

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

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

HTML Analysis

  • date: Sun, 09 Mar 2014 00:43:58 GMT
  • server: Apache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 1132
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

No data whois for rann.tk

IP 173.254.28.80 Analysis

Traffic Analysis

Magestic Backlinks


Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

HTML Analysis

HTML validation

  • 8 Errors
  • 11 Warnings

Ratio Text/Html

  • 0.44298574643660915

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

  • Warning Line 55, Column 97: NET-enabling start-tag requires SHORTTAG YES
    …et" href="http://rann.tk/css/share.css?v=1.5" type="text/css" media="screen" />

    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 60, 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 62, 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 69, Column 74: NET-enabling start-tag requires SHORTTAG YES
    …bel>URL: <input type="text" name="url" value="http://" size="70" /></label></p>

    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.

  • Warning Line 70, Column 96: NET-enabling start-tag requires SHORTTAG YES
    …yword: http://rann.tk/<input type="text" name="keyword" size="8" /></label></p>

    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.

  • Warning Line 71, Column 71: NET-enabling start-tag requires SHORTTAG YES
    …<label>Optional title: <input type="text" name="title" size="57" /></label></p>

    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.

  • Warning Line 72, Column 43: NET-enabling start-tag requires SHORTTAG YES
    		<p><input type="submit" value="Shorten" /></p>

    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.

  • Warning Line 75, Column 103: cannot generate system identifier for general entity "action"
    …e-public-front-page.php?format=simple&action=shorturl&url='+escape(location.hr…

    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 75, Column 103: general entity "action" not defined and no default entity
    …e-public-front-page.php?format=simple&action=shorturl&url='+escape(location.hr…

    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.

  • Error Line 75, Column 109: reference to entity "action" for which no system identifier could be generated
    …ic-front-page.php?format=simple&action=shorturl&url='+escape(location.href))">…

    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 75, Column 102: entity was defined here
    …le-public-front-page.php?format=simple&action=shorturl&url='+escape(location.h…
  • Warning Line 75, Column 119: cannot generate system identifier for general entity "url"
    …age.php?format=simple&action=shorturl&url='+escape(location.href))">bookmarkle…

    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 75, Column 119: general entity "url" not defined and no default entity
    …age.php?format=simple&action=shorturl&url='+escape(location.href))">bookmarkle…

    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.

  • Error Line 75, Column 122: reference to entity "url" for which no system identifier could be generated
    ….php?format=simple&action=shorturl&url='+escape(location.href))">bookmarklet</…

    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 75, Column 118: entity was defined here
    …page.php?format=simple&action=shorturl&url='+escape(location.href))">bookmarkl…

Visitor Analysis

Daily Visitors Country Map

In Page Analysis