phim online, phim sex nguoi lon, xem phim sex cap 3, hinh anh sex viet nam, phim mien phi ...

lauxanh.us
  • Domain Name
    lauxanh.us
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #15128
  • Page Size
    13.8 KB
  • Ip Address
    192.69.202.150
  • Heading
    H1: 1, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    14 GIF, 6 JPG, 0 PNG

Website Meta Analysis

  • Title
    phim sex online | anh sex viet nam | hinh sex viet, phim cap 3 lauxanh
  • Meta Keyword
    lauxanh, phim sex online, hinh sex, truyen sex, phim nguoi lon, online phim sex, download phim sex, phim sex download, hinh sex, sex, phim online, phim viet nam, online phim, phim lauxanh, lauxanh
  • Meta Description
    phim online, phim sex nguoi lon, xem phim sex cap 3, hinh anh sex viet nam, phim mien phi

Technical Analysis

  • Webserver
  • Ip Address
    192.69.202.150
  • Domain Age
    7 Years, 10 Months, 21 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from lauxanh.us.

HTML Analysis

  • content-encoding: gzip
  • vary: Accept-Encoding
  • date: Mon, 15 Sep 2014 12:35:32 GMT
  • accept-ranges: bytes
  • connection: close
  • etag: "3512-53e27a4e-f33d25068ce8cc29"
  • last-modified: Wed, 06 Aug 2014 18:56:14 GMT
  • content-type: text/html
  • content-length: 4502
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: LAUXANH.US
Domain ID: D8816580-US
Sponsoring Registrar: NAME.COM
Registrar URL (registration services): www.name.com
Domain Status: clientTransferProhibited
Registrant ID: NCR-11546675-098
Registrant Name: Anh Van Pham
Registrant Organization: N/A
Registrant Address1: 2421 Finch Ave West
Registrant City: Toronto
Registrant State/Province: Ontario
Registrant Postal Code: M9M 3B5
Registrant Country: Canada
Registrant Country Code: CA
Registrant Phone Number: +1.6479188771
Registrant Email: email
Registrant Application Purpose: P3
Registrant Nexus Category: C12
Administrative Contact ID: NCA-11546676-195
Administrative Contact Name: Anh Van Pham
Administrative Contact Organization: N/A
Administrative Contact Address1: 2421 Finch Ave West
Administrative Contact City: Toronto
Administrative Contact State/Province: Ontario
Administrative Contact Postal Code: M9M 3B5
Administrative Contact Country: Canada
Administrative Contact Country Code: CA
Administrative Contact Phone Number: +1.6479188771
Administrative Contact Email: email
Billing Contact ID: NCB-11546678-B20
Billing Contact Name: Anh Van Pham
Billing Contact Organization: N/A
Billing Contact Address1: 2421 Finch Ave West
Billing Contact City: Toronto
Billing Contact State/Province: Ontario
Billing Contact Postal Code: M9M 3B5
Billing Contact Country: Canada
Billing Contact Country Code: CA
Billing Contact Phone Number: +1.6479188771
Billing Contact Email: email
Technical Contact ID: NCT-11546677-971
Technical Contact Name: Anh Van Pham
Technical Contact Organization: N/A
Technical Contact Address1: 2421 Finch Ave West
Technical Contact City: Toronto
Technical Contact State/Province: Ontario
Technical Contact Postal Code: M9M 3B5
Technical Contact Country: Canada
Technical Contact Country Code: CA
Technical Contact Phone Number: +1.6479188771
Technical Contact Email: email
Name Server: NS1DHL.NAME.COM
Name Server: NS3JWX.NAME.COM
Name Server: NS4CGS.NAME.COM
Name Server: NS2FLN.NAME.COM
Created by Registrar: GODADDY.COM, INC.
Last Updated by Registrar: NAME.COM
Last Transferred Date: Mon Oct 31 16:05:50 GMT 2011
Domain Registration Date: Mon Oct 24 17:35:40 GMT 2005
Domain Expiration Date: Fri Oct 23 23:59:59 GMT 2015
Domain Last Updated Date: Mon Sep 17 22:09:40 GMT 2012

>>>> Whois database was last updated on: Fri Sep 21 10:10:24 GMT 2012

DNS Analysis


DNS servers
ns2fln.name.com [5.153.6.198]
ns4cgs.name.com [184.72.222.219]
ns1dhl.name.com [184.172.60.181]
ns3jwx.name.com [208.43.122.43]

DNS Records

Answer records
lauxanh.us NS  ns1dhl.name.com 300s
lauxanh.us A 173.231.59.114 300s
lauxanh.us NS  ns2fln.name.com 300s
lauxanh.us NS  ns3jwx.name.com 300s
lauxanh.us SOA
server: ns1dhl.name.com
email: support@name.com
serial: 1
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
300s
lauxanh.us NS  ns4cgs.name.com 300s

Authority records

Additional records
ns3jwx.name.com A 208.43.122.43 86400s
ns4cgs.name.com A 184.72.222.219 86400s
ns2fln.name.com A 5.153.6.198 86400s
ns1dhl.name.com A 184.172.60.181 86400s

IP 192.69.202.150 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • %rwhois V-1.0,V-1.5:00090h:00 clients.webnx.com (Ubersmith RWhois Server V-2.3.0)
    autharea=192.69.192.0/19
    xautharea=192.69.192.0/19
    network:Class-Name:network
    network:Auth-Area:192.69.192.0/19
    network:ID:NET-4121.192.69.202.144/29
    network:Network-Name:192.69.202.146/29
    network:IP-Network:192.69.202.144/29
    network:IP-Network-Block:192.69.202.144 - 192.69.202.151
    network:Org-Name:Tran, Bich
    network:Street-Address:
    network:City:
    network:State:
    network:Postal-Code:
    network:Country-Code:US
    network:Tech-Contact:MAINT-4121.192.69.202.144/29
    network:Created:20121224002643000
    network:Updated:20121224002643000
    network:Updated-By:abuse@webnx.com
    contact:POC-Name:WebNX Inc.
    contact:POC-Email:abuse@webnx.com
    contact:POC-Phone:800.840.5996 x3
    contact:Tech-Name:buddy
    contact:Tech-Email:lutuannghiankl@gmail.com
    contact:Tech-Phone:
    contact:Abuse-Name:Abuse Department
    contact:Abuse-Email:abuse@webnx.com
    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 33 Errors
  • 15 Warnings
Ratio Text/Html
  • 0.5879396984924623
Message Error
  • Error Line 29, Column 99: there is no attribute "alt"
    …php?f=88" title="Phim Sex Online" alt="Phim sex download nhanh" rel="phimsex">…

    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 90, Column 172: end tag for "font" omitted, but OMITTAG NO was specified
    …And Over Only -- By Entering You Agree To Our <b>Disclaimer</b></a></font><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 90, Column 46: start tag was here
    …="/disclaimer.htm" title="Disclaimer"><font size="3" color="yellow">This Websi…
  • Error Line 90, Column 179: end tag for element "font" which is not open
    …And Over Only -- By Entering You Agree To Our <b>Disclaimer</b></a></font><br/>

    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 105, Column 4: document type does not allow element "tr" here; assuming missing "table" start-tag
    <tr>
  • Error Line 124, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div>

    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 115, Column 30: start tag was here
              <td align="center"><table width="780" border="0" cellpadding="0" cell…
  • Error Line 124, Column 6: end tag for "td" omitted, but OMITTAG NO was specified
    </div>

    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 115, Column 11: start tag was here
              <td align="center"><table width="780" border="0" cellpadding="0" cell…
  • Error Line 124, Column 6: end tag for "tr" omitted, but OMITTAG NO was specified
    </div>

    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 114, Column 1: start tag was here
    <tr>
  • Error Line 124, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div>

    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 106, Column 30: start tag was here
              <td align="center"><table width="780" border="0" cellpadding="0" cell…
  • Error Line 124, Column 6: end tag for "td" omitted, but OMITTAG NO was specified
    </div>

    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 106, Column 11: start tag was here
              <td align="center"><table width="780" border="0" cellpadding="0" cell…
  • Error Line 124, Column 6: end tag for "tr" omitted, but OMITTAG NO was specified
    </div>

    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 105, Column 1: start tag was here
    <tr>
  • Error Line 124, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div>

    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 105, Column 1: start tag was here
    <tr>
  • Error Line 128, Column 171: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …liance with 18 USC 2257. <a href="/notice.html">Click here for more info</a><p>

    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 133, Column 31: end tag for "p" omitted, but OMITTAG NO was specified
    <!-- Close Footer Div --></div>

    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 128, Column 169: start tag was here
    …liance with 18 USC 2257. <a href="/notice.html">Click here for more info</a><p>
  • Error Line 133, Column 31: end tag for "p" omitted, but OMITTAG NO was specified
    <!-- Close Footer Div --></div>

    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 128, Column 1: start tag was here
    <p>© LauXanh Entertainment Network | All Rights Reserved | All images and movie…
  • Error Line 137, Column 9: there is no attribute "id"
    <DIV id="divAdLeft" style="LEFT: -110px; WIDTH: 110px; POSITION: absolute; TOP:…

    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 137, Column 27: there is no attribute "style"
    <DIV id="divAdLeft" style="LEFT: -110px; WIDTH: 110px; POSITION: absolute; TOP:…

    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 137, Column 86: element "DIV" undefined
    … 110px; POSITION: absolute; TOP: 71px"><a href="http://lauxanh.blogspot.com/20…

    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 137, Column 299: end tag for "img" omitted, but OMITTAG NO was specified
    …eja29kbksrnfpv65d5.gif" border="0" alt="Your Banner Here Adsvertise"></a></DIV>

    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 137, Column 188: start tag was here
    …-tren-lauxanhus.html" target="_blank"><img src="http://upload69.net/images/83e…
  • Error Line 141, Column 32: required attribute "type" not specified
    		<script language="JavaScript">

    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 148, Column 33: character "<" is the first character of a delimiter but occurred as data
    		if (document.body.clientWidth < 980) startX = -110;

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 164, Column 34: character "<" is the first character of a delimiter but occurred as data
    			if (document.body.clientWidth < 980)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 171, Column 33: character "&" is the first character of a delimiter but occurred as data
    			if (document.documentElement && document.documentElement.scrollTop)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 171, Column 34: character "&" is the first character of a delimiter but occurred as data
    			if (document.documentElement && document.documentElement.scrollTop)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 204, Column 33: character "<" is the first character of a delimiter but occurred as data
    		if (document.body.clientWidth < 980) startX2 = -110;

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 219, Column 34: character "<" is the first character of a delimiter but occurred as data
    			if (document.body.clientWidth < 980)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 225, Column 33: character "&" is the first character of a delimiter but occurred as data
    			if (document.documentElement && document.documentElement.scrollTop)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 225, Column 34: character "&" is the first character of a delimiter but occurred as data
    			if (document.documentElement && document.documentElement.scrollTop)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 259, Column 33: character "<" is the first character of a delimiter but occurred as data
    		if (document.body.clientWidth < 980)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 294, Column 73: document type does not allow element "script" here
    …ript type="text/javascript" src="http://edge.quantserve.com/quant.js"></script>

    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 295, Column 31: document type does not allow element "script" here
    <script type="text/javascript">_qacct="p-c9Om8Ep88wkcI";quantserve();</script>

    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 296, Column 10: document type does not allow element "noscript" here
    <noscript>

    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).

Visitor Analysis

Daily Visitor
  • 7.467 visits