slavecafe.com

slavecafe.com has Alexa Rank 1.807.779 and Google Page Rank is 0

Display Widget for this domain on your website. Click Here
This data was last updated from 04-08-2013 09:38:27  (update).

Overview Info

  • Domain Name
    slavecafe.com
  • Favicon
  • Alexa Rank
    #1807779
  • Google Page Rank
    PR 0
  • Ip Address
    144.76.5.36
  • Page Size
    45.4 KB
  • Images
    1 GIF, 68 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 0 0 0 0

Technical Analysis



  • Webserver
    Apache/2.2.15
  • Ip Address
    144.76.5.36
  • Domain Age
    3 Years, 0 Months, 6 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 04 Aug 2013 09:38:22 GMT
  • server: Apache/2.2.15
  • x-powered-by: PHP/5.3.3
  • 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
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for slavecafe.com

DNS Analysis


DNS servers
ns1.first-ns.de
robotns2.second-ns.de [213.133.105.6]
robotns3.second-ns.com [193.47.99.3]

DNS Records

Answer records
slavecafe.com SOA
server: ns1.first-ns.de
email: postmaster@robot.first-ns.de
serial: 2012020300
refresh: 14400
retry: 1800
expire: 604800
minimum ttl: 86400
86400s
slavecafe.com MX
preference: 10
exchange: mail.slavecafe.com
86400s
slavecafe.com NS  robotns3.second-ns.com 86400s
slavecafe.com NS  robotns2.second-ns.de 86400s
slavecafe.com NS  ns1.first-ns.de 86400s
slavecafe.com A 176.9.76.175 86400s

Authority records

Additional records
mail.slavecafe.com A 176.9.76.175 86400s
ns1.first-ns.de A 213.239.242.238 86400s

IP 144.76.5.36 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 24 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.728513107004727
Message Error
  • Error Line 74, Column 154: required attribute "alt" not specified
    …file/static/1d14632666424b7f123892fa0c9be36f.png?id=29" class="v_middle" /></a>

    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 163, Column 62: cannot generate system identifier for general entity "width"
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 

    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 163, Column 62: general entity "width" not defined and no default entity
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 

    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.

  • Warning Line 163, Column 67: reference not terminated by REFC delimiter
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 163, Column 67: reference to entity "width" for which no system identifier could be generated
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 

    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 163, Column 61: entity was defined here
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 
  • Warning Line 163, Column 72: cannot generate system identifier for general entity "title"
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 

    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 163, Column 72: general entity "title" not defined and no default entity
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 

    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.

  • Warning Line 163, Column 77: reference not terminated by REFC delimiter
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 163, Column 77: reference to entity "title" for which no system identifier could be generated
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 

    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 163, Column 71: entity was defined here
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 
  • Warning Line 171, Column 69: reference not terminated by REFC delimiter
    …Privacy Policy', $.ajaxBox('page.view', 'height=410&width=600&title=policy')); 

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 171, Column 69: reference to entity "width" for which no system identifier could be generated
    …Privacy Policy', $.ajaxBox('page.view', 'height=410&width=600&title=policy')); 

    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 163, Column 61: entity was defined here
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 
  • Warning Line 171, Column 79: reference not terminated by REFC delimiter
    …Privacy Policy', $.ajaxBox('page.view', 'height=410&width=600&title=policy')); 

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 171, Column 79: reference to entity "title" for which no system identifier could be generated
    …Privacy Policy', $.ajaxBox('page.view', 'height=410&width=600&title=policy')); 

    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 163, Column 71: entity was defined here
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 
  • Error Line 216, Column 282: there is no attribute "autocomplete"
    …o easily connect to your profile." value="" size="30" autocomplete="off" />				

    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 492, Column 17: there is no attribute "src"
      		<iframe src="http://api.recaptcha.net/noscript?k=6Ld2hMsSAAAAAFWOuxVqKJbOCd…

    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 492, Column 103: there is no attribute "height"
    …AAFWOuxVqKJbOCdAiKhHHpMXgTGfQ" height="300" width="500" frameborder="0"></ifra…

    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 492, Column 115: there is no attribute "width"
    …VqKJbOCdAiKhHHpMXgTGfQ" height="300" width="500" frameborder="0"></iframe><br/>

    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 492, Column 133: there is no attribute "frameborder"
    …VqKJbOCdAiKhHHpMXgTGfQ" height="300" width="500" frameborder="0"></iframe><br/>

    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 492, Column 136: element "iframe" undefined
    …VqKJbOCdAiKhHHpMXgTGfQ" height="300" width="500" frameborder="0"></iframe><br/>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 492, Column 150: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …VqKJbOCdAiKhHHpMXgTGfQ" height="300" width="500" frameborder="0"></iframe><br/>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 493, Column 66: document type does not allow element "textarea" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
      		<textarea name="recaptcha_challenge_field" rows="3" cols="40"></textarea>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 494, Column 83: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …<input type="hidden" name="recaptcha_response_field" value="manual_challenge"/>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 541, Column 177: there is no attribute "target"
    …"http://www.microsoft.com/ie/" target="_blank">here</a> today to fully enjoy a…

    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.

Visitor Analysis

Daily Visitor
  • 70 visits

In Page Analysis