Social Bookmarking - Verwalten Sie Ihre Favoriten, Bookmarks bzw. Lesezeichen kostenlos Online. ...

lexgen.de
  • Domain Name
    lexgen.de
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #305340
  • Page Size
    94.8 KB
  • Ip Address
    78.46.215.184
  • Heading
    H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    100 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Favoriten, Bookmarks bzw. Lesezeichen Online verwalten
  • Meta Keyword
    Favoriten, Bookmarks, Lesezeichen, verwalten, kostenlos, Social Bookmarking
  • Meta Description
    Social Bookmarking - Verwalten Sie Ihre Favoriten, Bookmarks bzw. Lesezeichen kostenlos Online.

Technical Analysis

  • Webserver
    Apache/2.2.16 (Debian)
  • Ip Address
    78.46.215.184
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 24 Jul 2014 11:08:44 GMT
  • server: Apache/2.2.16 (Debian)
  • x-powered-by: PHP/5.3.3-7+squeeze18
  • 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
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 8598
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for lexgen.de

DNS Analysis


DNS servers
ns1.network.medialocation.de [78.47.108.200]
ns2.network.medialocation.de


DNS Records

Answer records
lexgen.de MX
preference: 10
exchange: www.lexgen.de
3600s
lexgen.de SOA
server: ns.lexgen.de
email: [email protected]
serial: 2013070729
refresh: 10000
retry: 1500
expire: 604800
minimum ttl: 1800
3600s
lexgen.de NS  ns2.network.medialocation.de 1800s
lexgen.de NS  ns1.network.medialocation.de 1800s
lexgen.de A 78.47.231.109 1800s

Authority records

Additional records
www.lexgen.de A 78.47.231.109 1800s
ns1.network.medialocation.de A 78.47.108.199 1800s
ns2.network.medialocation.de A 78.47.108.199 1800s

IP 78.46.215.184 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 240 Errors
  • 15 Warnings
Ratio Text/Html
  • 0.5481494456579978
Message Error
  • Error Line 2, Column 2: 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 27, Column 74: there is no attribute "HEIGHT"
       <table cellpadding="0" cellspacing="0" border="0" width="100%" height="100%">

    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 35, Column 79: required attribute "ALT" not specified
             <img src="http://www.lexgen.de/media/blanc.gif" width="18" height="1">

    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 75, Column 74: cannot generate system identifier for general entity "aid"
    …//www.special-sponsor.de/sc/ronbs.php?id=890&aid=1130&f=468"></script></center>

    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 74: general entity "aid" not defined and no default entity
    …//www.special-sponsor.de/sc/ronbs.php?id=890&aid=1130&f=468"></script></center>

    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 77: reference to entity "aid" for which no system identifier could be generated
    …//www.special-sponsor.de/sc/ronbs.php?id=890&aid=1130&f=468"></script></center>

    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.

Visitor Analysis

Daily Visitor
  • 642 visits