reading.my

Some information about your site... ...

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

Overview Info

  • Domain Name
    reading.my
  • Favicon
  • Alexa Rank
    #9317388
  • Google Page Rank
    PR 0
  • Ip Address
    42.1.61.16
  • Page Size
    10.1 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 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
    Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • Ip Address
    42.1.61.16
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from reading.my.

HTML Analysis

  • date: Tue, 17 Sep 2013 18:56:40 GMT
  • server: Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • x-powered-by: PHP/5.3.13
  • 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
  • connection: close
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for reading.my

DNS Analysis


DNS servers
ns2.reading.my [42.1.61.18]
ns1.reading.my [42.1.61.17]


DNS Records

Answer records
reading.my MX
preference: 0
exchange: reading.my
14400s
reading.my SOA
server: ns1.reading.my
email: null@null.com
serial: 2012102705
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
reading.my NS  ns2.reading.my 86400s
reading.my NS  ns1.reading.my 86400s
reading.my A 42.1.61.16 14400s

Authority records

Additional records
reading.my A 42.1.61.16 14400s
ns1.reading.my A 42.1.61.17 14400s
ns2.reading.my A 42.1.61.18 14400s

IP 42.1.61.16 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 7 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.41897500241289454
Message Error
  • Error Line 54, Column 44: document type does not allow element "div" here
    …					$('body').html('<div id="fb-root"></div><div id="facebook_connection">Con…

    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 54, Column 80: document type does not allow element "div" here
    …t"></div><div id="facebook_connection">Connecting to Facebook. Please hold....…

    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 64, Column 35: ID "fb-root" already defined
    									$('body').html('<div id="fb-root"></div><div id="facebook_connection">…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 54, Column 36: ID "fb-root" first defined here
    										$('body').html('<div id="fb-root"></div><div id="facebook_connection"…
  • Error Line 64, Column 43: document type does not allow element "div" here
    …					$('body').html('<div id="fb-root"></div><div id="facebook_connection">Con…

    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 64, Column 59: ID "facebook_connection" already defined
    …tml('<div id="fb-root"></div><div id="facebook_connection">Connecting to Faceb…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 54, Column 60: ID "facebook_connection" first defined here
    …tml('<div id="fb-root"></div><div id="facebook_connection">Connecting to Faceb…
  • Error Line 64, Column 79: document type does not allow element "div" here
    …t"></div><div id="facebook_connection">Connecting to Facebook. Please hold...<…

    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 106, Column 10: ID "fb-root" already defined
    <div id="fb-root"></div>		<div id="header">			

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 54, Column 36: ID "fb-root" first defined here
    										$('body').html('<div id="fb-root"></div><div id="facebook_connection"…
  • Error Line 142, Column 36: there is no attribute "scope"
    												<fb:login-button scope="publish_stream,email,user_birthday" v="2"><…

    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 142, Column 75: there is no attribute "v"
    …ogin-button scope="publish_stream,email,user_birthday" v="2"></fb:login-button>

    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 142, Column 78: element "fb:login-button" undefined
    …ogin-button scope="publish_stream,email,user_birthday" v="2"></fb:login-button>

    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).
  • Warning Line 228, 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 228, 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 228, 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 228, 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 228, Column 61: entity was defined here
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 
  • Warning Line 228, 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 228, 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 228, 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 228, 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 228, Column 71: entity was defined here
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 
  • Warning Line 236, 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 236, 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 228, Column 61: entity was defined here
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 
  • Warning Line 236, 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 236, 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 228, Column 71: entity was defined here
    …w('Terms of Use', $.ajaxBox('page.view', 'height=410&width=600&title=terms')); 
  • Error Line 525, 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.

  • Error Line 574, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 574, Column 1: start tag was here
    <br><br><br>
  • Error Line 574, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 574, Column 5: start tag was here
    <br><br><br>
  • Error Line 574, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 574, Column 9: start tag was here
    <br><br><br>
  • Error Line 575, Column 94: element "u" undefined
    …awanr.com/user/password/request/" target="_blank"><u>Click Here</u></a><br><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 575, Column 117: end tag for "br" omitted, but OMITTAG NO was specified
    …awanr.com/user/password/request/" target="_blank"><u>Click Here</u></a><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 575, Column 113: start tag was here
    …awanr.com/user/password/request/" target="_blank"><u>Click Here</u></a><br><br>
  • Error Line 575, Column 121: end tag for "br" omitted, but OMITTAG NO was specified
    …awanr.com/user/password/request/" target="_blank"><u>Click Here</u></a><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 575, Column 117: start tag was here
    …awanr.com/user/password/request/" target="_blank"><u>Click Here</u></a><br><br>
  • Error Line 576, Column 104: end tag for "br" omitted, but OMITTAG NO was specified
    …x (or Spam folder if you can't see our mail in inbox), follow the step.<br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 576, Column 100: start tag was here
    …x (or Spam folder if you can't see our mail in inbox), follow the step.<br><br>
  • Error Line 576, Column 108: end tag for "br" omitted, but OMITTAG NO was specified
    …x (or Spam folder if you can't see our mail in inbox), follow the step.<br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 576, Column 104: start tag was here
    …x (or Spam folder if you can't see our mail in inbox), follow the step.<br><br>
  • Error Line 577, Column 53: end tag for "br" omitted, but OMITTAG NO was specified
        3) Login with the password that we sent you.<br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 577, Column 49: start tag was here
        3) Login with the password that we sent you.<br><br>
  • Error Line 577, Column 57: end tag for "br" omitted, but OMITTAG NO was specified
        3) Login with the password that we sent you.<br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 577, Column 53: start tag was here
        3) Login with the password that we sent you.<br><br>
  • Error Line 578, Column 91: element "u" undefined
    …"http://kawanr.com/user/setting/" target="_blank"><u>Click Here</u></a><br><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 578, Column 114: end tag for "br" omitted, but OMITTAG NO was specified
    …"http://kawanr.com/user/setting/" target="_blank"><u>Click Here</u></a><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 578, Column 110: start tag was here
    …"http://kawanr.com/user/setting/" target="_blank"><u>Click Here</u></a><br><br>
  • Error Line 578, Column 118: end tag for "br" omitted, but OMITTAG NO was specified
    …"http://kawanr.com/user/setting/" target="_blank"><u>Click Here</u></a><br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 578, Column 114: start tag was here
    …"http://kawanr.com/user/setting/" target="_blank"><u>Click Here</u></a><br><br>
  • Error Line 579, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 579, Column 1: start tag was here
    <br><br>
  • Error Line 579, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 579, Column 5: start tag was here
    <br><br>

Visitor Analysis

Daily Visitor
  • 10 visits

In Page Analysis