Innogames.com - play free online games in your browser. Exciting strategy- and action games. Play your favorite games now! ...

innogames.de
  • Domain Name
    innogames.de
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #40771
  • Page Size
    40.4 KB
  • Ip Address
    217.70.142.73
  • Heading
    H1: 1, H2: 5, H3: 5, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 8 JPG, 14 PNG

Website Meta Analysis

  • Title
    Free Online Games - Play Strategy Games and RPG Online for free!
  • Meta Keyword
    Games, Online-Games, Browser Games, Browser-Games, Web-Games, Internet-Games, Spiele, Online-Spiele, Browser-Spiele, Internet-Spiele, Browser, onlinegames, browserspiele, webgames, webspiele, onlinespiele, internetspiele, Spiele-Online, Games-Online, Free Games, RPG, browsergame, browser based games
  • Meta Description
    Innogames.com - play free online games in your browser. Exciting strategy- and action games. Play your favorite games now!

Technical Analysis

  • Webserver
    nginx/1.4.1
  • Ip Address
    217.70.142.73
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from innogames.de.

HTML Analysis

  • server: nginx/1.4.1
  • date: Tue, 17 Sep 2013 13:55:18 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3-7+squeeze15
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% Copyright (c) 2010 by DENIC
% Version: 2.0
%
% Restricted rights.
%
% Terms and Conditions of Use
%
% The data in this record is provided by DENIC for informational purposes only.
% DENIC does not guarantee its accuracy and cannot, under any circumstances,
% be held liable in case the stored information would prove to be wrong,
% incomplete or not accurate in any sense.
%
% All the domain data that is visible in the whois service is protected by law.
% It is not permitted to use it for any purpose other than technical or
% administrative requirements associated with the operation of the Internet.
% It is explicitly forbidden to extract, copy and/or use or re-utilise in any
% form and by any means (electronically or not) the whole or a quantitatively
% or qualitatively substantial part of the contents of the whois database
% without prior and explicit written permission by DENIC.
% It is prohibited, in particular, to use it for transmission of unsolicited
% and/or commercial and/or advertising by phone, fax, e-mail or for any similar
% purposes.
%
% By maintaining the connection you assure that you have a legitimate interest
% in the data and that you will only use it for the stated purposes. You are
% aware that DENIC maintains the right to initiate legal proceedings against
% you in the event of any breach of this assurance and to bar you from using
% its whois service.
%
% The DENIC whois service on port 43 never discloses any information concerning
% the domain holder/administrative contact. Information concerning the domain
% holder/administrative contact can be obtained through use of our web-based
% whois service available at the DENIC website:
% http://www.denic.de/en/background/whois-service/webwhois.html
%

Domain: innogames.de
Nserver: ns.inwx.de
Nserver: ns2.inwx.de
Nserver: ns3.inwx.de
Status: connect
Changed: 2011-03-24T14:54:47+01:00

[Tech-C]
Type: ROLE
Name: Hostmaster Of The Day
Organisation: InterNetworX Ltd. & Co. KG
Address: Tempelhofer Damm 140
PostalCode: 12099
City: Berlin
CountryCode: DE
Phone: +49.180.3730000
Phone: +49.30.66400137
Fax: +49.30.66400138
Email: email
Remarks: role account for Hostmaster of the Day
Changed: 2009-01-07T16:28:43+01:00

[Zone-C]
Type: ROLE
Name: Hostmaster Of The Day
Organisation: InterNetworX Ltd. & Co. KG
Address: Tempelhofer Damm 140
PostalCode: 12099
City: Berlin
CountryCode: DE
Phone: +49.180.3730000
Phone: +49.30.66400137
Fax: +49.30.66400138
Email: email
Remarks: role account for Hostmaster of the Day
Changed: 2009-01-07T16:28:43+01:00

DNS Analysis


DNS servers
ns.inwx.de [217.70.142.66]
ns2.inwx.de [213.239.206.103]
ns3.inwx.de [46.165.212.97]


DNS Records

Answer records
innogames.de MX
preference: 50
exchange: mx0.innogames.de
3600s
innogames.de NS  ns2.inwx.de 3600s
innogames.de TXT MS=ms54982530 3600s
innogames.de TXT v=spf1 ip4:195.140.184.0/22 ip4:91.192.40.0/22 ip4:212.48.98.0/24 ip4:78.138.112.128/25 ip4:89.31.4.67/32 ip4:80.252.99.240/32 ip4:217.170.185.130/32 include:outlook.com include:spf.dynect.net ~all 3600s
innogames.de NS  ns3.inwx.de 3600s
innogames.de A 46.165.212.97 3600s
innogames.de MX
preference: 5
exchange: mx.extern.innogames.de
3600s
innogames.de SOA
server: ns.inwx.de
email: hostmaster@inwx.de
serial: 2013013001
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
3600s
innogames.de NS  ns.inwx.de 3600s

Authority records

Additional records
ns.inwx.de A 217.70.142.66 3600s
ns3.inwx.de A 46.165.212.97 3600s
mx.extern.innogames.de A 80.252.99.240 3600s
ns2.inwx.de 28 [16 bytes] 3600s
0 [0 bytes] 0s
0 [0 bytes] 0s
0 [0 bytes] 0s

IP 217.70.142.73 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    Berlin
  • Continent Code
    EU
  • Latitude
    52.5167
  • Longitude
    13.4.
  • No whois ip data for 217.70.142.73

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 32 Errors
  • 0 Warnings
Ratio Text/Html
  • 0.42962479450730107
Message Error
  • Error Line 99, Column 25: document type does not allow element "style" here
    		<style type="text/css">

    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 430, Column 56: there is no attribute "rel"
    	<form id="login" action="/en/login" method="post" rel="overlay">

    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 478, Column 25: document type does not allow element "p" here
    		$('#loading').html('<p>...loading...</p><br/><img src="/files/css/img/loading…

    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 478, Column 47: document type does not allow element "br" here
    …ading').html('<p>...loading...</p><br/><img src="/files/css/img/loading.gif" a…

    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 478, Column 129: document type does not allow element "img" here
    …rc="/files/css/img/loading.gif" alt="Loading" width="126px" height="22px" />');

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