prenbook.com

Some information about your site... ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    prenbook.com
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    PR 0
  • Ip Address
    31.170.167.133
  • Page Size
    24.5 KB
  • Images
    1 GIF, 0 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 0 0 0 0

Website Meta Analysis



  • Title
    Social Networking Community - Powered By phpFox
  • Meta Keyword
    social networking
  • Meta Description
    Some information about your site...

Technical Analysis



  • Webserver
    hosting
  • Ip Address
    31.170.167.133
  • Domain Age
    2 Months, 9 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: hosting
  • date: Tue, 26 Feb 2013 18:06:34 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.2.17
  • 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
Registrant:
Prenbook Inc
Deli Serdang
Tanjung Morawa, Sumatra Utara 20362
ID

Domain name: PRENBOOK.COM

Administrative Contact:
Inc, Prenbook email
Deli Serdang
Tanjung Morawa, Sumatra Utara 20362
ID
+62.83198990444
Technical Contact:
Admin, Domain email
2632 Marine Way
Mountain View, CA 94043
US
+1.8004283170


Record last updated on 20-Dec-2012.
Record expires on 19-Dec-2013.
Record created on 19-Dec-2012.


Domain servers in listed order:
NS1.WINK.WS
NS3.WINK.WS
NS4.WINK.WS
NS2.WINK.WS

Domain status: clientTransferProhibited
clientUpdateProhibited

DNS Analysis


DNS servers
ns1.wink.ws [31.170.163.241]
ns2.wink.ws [64.191.115.234]
ns3.wink.ws [173.192.183.247]
ns4.wink.ws [31.170.164.249]


DNS Records

Answer records
prenbook.com SOA
server: ns1.freehost4all.me
email: postmaster@prenbook.com
serial: 2012122101
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
prenbook.com A 31.170.167.133 86400s
prenbook.com MX
preference: 0
exchange: mx1.freehost4all.me
86400s
prenbook.com NS  ns1.freehost4all.me 86400s
prenbook.com NS  ns2.freehost4all.me 86400s
prenbook.com NS  ns3.freehost4all.me 86400s
prenbook.com NS  ns4.freehost4all.me 86400s

Authority records

Additional records
mx1.freehost4all.me A 31.170.163.242 86400s
ns1.freehost4all.me A 31.170.163.241 86400s
ns2.freehost4all.me A 64.191.115.234 86400s
ns3.freehost4all.me A 173.192.183.247 86400s
ns4.freehost4all.me A 31.170.164.249 86400s

IP 31.170.167.133 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 7 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.6294314915362504
Message Error
  • Warning Line 178, 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 "&" (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 æ 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 178, 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 178, 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 178, 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 178, Column 61: entity was defined here
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 
  • Warning Line 178, 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 "&" (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 æ 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 178, 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 178, 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 178, 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 178, Column 71: entity was defined here
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 
  • Warning Line 186, 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 186, 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 178, Column 61: entity was defined here
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 
  • Warning Line 186, 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 186, 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 178, Column 71: entity was defined here
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 
  • Error Line 454, 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
  • 0 visits

In Page Analysis