truyen-xxx.com

đọc truyện sex địt nhau loạn luân ảnh sex người lớn phim hiếp dâm thế giới đọc truyện tổng hợp ...

Processing update domain...

Overview Info



  • Domain Name
    truyen-xxx.com
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    0
  • Ip Address
    123.30.187.98
  • Page Size
    25.2 KB
  • Images
    50 GIF, 0 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    đọc truyện sex địt nhau loạn luân ảnh sex người lớn phim hiếp dâm
  • Meta Keyword
    đọc truyện sex địt nhau loạn luân ảnh sex người lớn phim hiếp dâm thế giới đọc truyện tổng hợp
  • Meta Description
    đọc truyện sex địt nhau loạn luân ảnh sex người lớn phim hiếp dâm thế giới đọc truyện tổng hợp

Technical Analysis



  • Webserver
    Apache/2
  • Ip Address
    123.30.187.98
  • Domain Age
    5 Months, 0 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from truyen-xxx.com.

HTML Analysis

  • date: Fri, 13 Sep 2013 14:36:05 GMT
  • server: Apache/2
  • x-powered-by: PHP/5.3.25
  • pragma: no-cache
  • cache-control: public
  • expires: Fri, 13 Sep 2013 14:37:05 +0000
  • content-encoding: gzip
  • vary: Accept-Encoding,User-Agent
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for truyen-xxx.com

DNS Analysis


DNS servers
dns01.bkns.vn [50.23.136.173]
dns02.bkns.vn
dns03.bkns.vn
dns04.bkns.vn


DNS Records

Answer records
truyen-xxx.com NS  dns04.bkns.vn 38400s
truyen-xxx.com NS  dns01.bkns.vn 38400s
truyen-xxx.com NS  dns02.bkns.vn 38400s
truyen-xxx.com SOA
server: dns01.bkns.vn
email: [email protected]
serial: 2013081002
refresh: 7200
retry: 7200
expire: 172800
minimum ttl: 38400
7200s
truyen-xxx.com A 123.30.187.98 28800s
truyen-xxx.com NS  dns03.bkns.vn 38400s

Authority records

Additional records

IP 123.30.187.98 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 11 Errors
  • 14 Warnings
Ratio Text/Html
  • 0.7021540849990298
Message Error
  • Error Line 1, Column 1: no document type declaration; will parse without validation
    <meta name="google-site-verification" content="oQw8UbKcbzeZYQxLUOjG-_MuTV0VGM3S…

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Warning Line 1, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="oQw8UbKcbzeZYQxLUOjG-_MuTV0VGM3SWLFtCtu22D4" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 12, Column 64: character data is not allowed here
    …document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 17, Column 9: end tag for element "SCRIPT" which is not open
    </script>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 22, Column 85: NET-enabling start-tag requires SHORTTAG YES
    …el="stylesheet" type="text/css" href="http://quangcao.sextgem.com/style.css" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 22, Column 85: document type does not allow element "LINK" here
    …el="stylesheet" type="text/css" href="http://quangcao.sextgem.com/style.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).

  • Warning Line 74, Column 103: NET-enabling start-tag requires SHORTTAG YES
    …/hot/tangthuong.jpg" height="100px" width="110px" alt="phim sex dai tap" /><br>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 79, Column 82: NET-enabling start-tag requires SHORTTAG YES
    …="http://lauxanh9x.us/hot/suong.jpg" height="100px" width="110px" alt="" /><br>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 84, Column 96: NET-enabling start-tag requires SHORTTAG YES
    …nh9x.us/hot/anh4.jpg" height="100px" width="110px" alt="phim sex chau a" /><br>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 103, Column 100: NET-enabling start-tag requires SHORTTAG YES
    …com">Về Trang Chủ</a></font></div><br /><script type="text/javascript">a136222…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 103, Column 274: NET-enabling start-tag requires SHORTTAG YES
    …M9bVQ.gif" height="1" width="1" alt=""/></div><head><link type="text/css" rel=…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 103, Column 389: NET-enabling start-tag requires SHORTTAG YES
    …m.com/xtgem_template.css?v=1362132463"/><title>truyen sex,truyen sex hay.truye…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 104, Column 224: NET-enabling start-tag requires SHORTTAG YES
    …M9bVQ.gif" height="1" width="1" alt=""/></div><br /><!----><noscript></noscrip…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 104, Column 236: NET-enabling start-tag requires SHORTTAG YES
    …eight="1" width="1" alt=""/></div><br /><!----><noscript></noscript><script></…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 104, Column 471: NET-enabling start-tag requires SHORTTAG YES
    …ng=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzon…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 104, Column 528: end tag for element "IFRAME" which is not open
    ….com/adshow.php?adzone=247561></iframe></div><script type="text/javascript">  …

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 104, Column 534: end tag for element "DIV" which is not open
    …dshow.php?adzone=247561></iframe></div><script type="text/javascript">        …

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 113, Column 68: character data is not allowed here
    …img && ( ad_img.src != 'http://xtgem.com/images/arrow.gif' ) ) ? ad_img : null;

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 129, Column 22: end tag for element "SCRIPT" which is not open
            })();</script><script type="text/javascript">        (function ( wr, st…

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 129, Column 53: document type does not allow element "SCRIPT" here
    …      })();</script><script type="text/javascript">        (function ( wr, st )

    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 177, Column 57: end tag for element "BODY" which is not open
            })( wr1379083015, st1379083015 );</script></body>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 178, Column 7: end tag for element "HTML" which is not open
    </html>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

Visitor Analysis

Daily Visitor
  • 0 visits

In Page Analysis