人妻究極アダルトサイト。火遊び好きな若妻がエロスに溺れ乱舞する裸身、主婦の豹変ぶりをご覧ください!! ...

mywife.cc
  • Domain Name
    mywife.cc
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #20983
  • Page Size
    1.9 KB
  • Ip Address
    219.122.2.47
  • Heading
    H1: 1, H2: 1, H3: 1, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 3 JPG, 0 PNG

Website Meta Analysis

  • Title
    人妻不倫サイト〜舞ワイフ セレブ・クラブ〜
  • Meta Keyword
    人妻,アダルト,素人,無料動画,エロブログ,無料,動画
  • Meta Description
    人妻究極アダルトサイト。火遊び好きな若妻がエロスに溺れ乱舞する裸身、主婦の豹変ぶりをご覧ください!!

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    219.122.2.47
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from mywife.cc.

HTML Analysis

  • date: Sat, 13 Apr 2013 17:06:58 GMT
  • server: Apache
  • last-modified: Fri, 08 Mar 2013 07:56:03 GMT
  • etag: "1ac8f-8be-4d765279b4ac0"
  • accept-ranges: bytes
  • content-length: 2238
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Interlink Co., Ltd. whois server 2.0.5

Domain name:mywife.cc
Created On: 2004-07-05
Last Updated On: 2012-06-26
Expiration Date: 2013-07-06

Registrant
organization: Toyo
Last Name: Yasunari
First Name: Toyo
Street1: Shibuya SS 5F
Street2: Shibuya 2-14-17
City: Shibuya-ku
State: Tokyo
Postal Code: 150-0002
Country: JP
Phone: 03-6418-5599
Fax:
Email: email

Admin
organization: INTERLINK
Last Name: Gonbei
First Name: INTERLINK
Street1: 3-1-1 higashi-ikebukuro
Street2:
City: Toshima
State: Tokyo
Postal Code: 170-6035
Country: JP
Phone: +81-3-3985-3711
Fax:
Email: email

Billing
organization: Interlink Co., Ltd.
Last Name: Ltd.
First Name: Interlink Co.,
Street1: 3-1-1-35,higashi-ikebukuro
Street2:
City: Toshima
State: Tokyo
Postal Code: 170-6035
Country: JP
Phone: +81-3-3985-3711
Fax:
Email: email
Tech
organization: INTERLINK
Last Name: Gonbei
First Name: INTERLINK
Street1: 3-1-1 higashi-ikebukuro
Street2:
City: Toshima
State: Tokyo
Postal Code: 170-6035
Country: JP
Phone: +81-3-3985-3711
Fax:
Email: email

The Data in the Interlink Co., Ltd. WHOIS database is provided to you by
Interlink Co., Ltd. for information purposes only, and may be used to
assist you in obtaining information about or related to a domain name's
registration record.

Interlink Co., Ltd. makes this information available "as is," and does
not guarantee its accuracy. By submitting a WHOIS query, you agree that you
will use this data only for lawful purposes and that, under no circumstances
will you use this data to: a) allow, enable, or otherwise support the
transmission by e-mail, telephone, or facsimile of mass, unsolicited,
commercial advertising or solicitations to entities other than the data
recipient's own existing customers; or (b) enable high volume, automated,
electronic processes that send queries or data to the systems of any Registry
Operator or ICANN-Accredited registrar, except as reasonably necessary to
register domain names or modify existing registrations.

DNS Analysis


DNS servers
ns1.ray-planning.com [202.143.78.196]
ns2.ray-planning.com [202.143.78.193]


DNS Records

Answer records
mywife.cc SOA
server: ns1.ray-planning.com
email: root@ns1.ray-planning.com
serial: 2012072502
refresh: 300
retry: 3600
expire: 604800
minimum ttl: 3600
400s
mywife.cc NS  ns2.ray-planning.com 400s
mywife.cc NS  ns1.ray-planning.com 400s
mywife.cc MX
preference: 10
exchange: mail.mywife.cc
400s
mywife.cc A 219.122.2.49 400s
mywife.cc A 122.212.37.3 400s
mywife.cc A 219.122.2.38 400s
mywife.cc A 219.122.2.46 400s
mywife.cc A 219.122.2.47 400s
mywife.cc A 219.122.2.48 400s

Authority records

Additional records
ns1.ray-planning.com A 202.143.78.196 300s
ns2.ray-planning.com A 202.143.78.193 300s
mail.mywife.cc A 219.122.2.53 400s

IP 219.122.2.47 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 10 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.7665647298674821
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html dir="ltr" lang="ja" ><head>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 6, Column 36: NET-enabling start-tag requires SHORTTAG YES
    <meta name="author" content="舞ワイフ" />

    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 7, Column 48: NET-enabling start-tag requires SHORTTAG YES
    <link rel="canonical" href="http://mywife.cc/" />

    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 7, Column 48: document type does not allow element "LINK" here
    <link rel="canonical" href="http://mywife.cc/" />

    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 8, Column 61: document type does not allow element "LINK" here
    <link href="img/mywife.css" rel="stylesheet" type="text/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).

  • Error Line 11, Column 7: end tag for element "HEAD" which is not open
    </head>

    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 12, Column 18: there is no attribute "LEFTMARGIN"
    <BODY leftMargin=0>

    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 12, Column 19: document type does not allow element "BODY" here
    <BODY leftMargin=0>

    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 20, Column 27: there is no attribute "HEIGHT"
      <TABLE width=950 height="20" border=0 cellPadding=0 cellSpacing=0 bgColor=#15…

    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 20, Column 77: an attribute value must be a literal unless it contains only name characters
    …eight="20" border=0 cellPadding=0 cellSpacing=0 bgColor=#151515 class="text10">

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 29, Column 30: required attribute "ALT" not specified
      <p><img src="img/18kin.gif"><br>

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

  • Error Line 50, Column 10: end tag for "TBODY" which is not finished
      </TBODY>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

Visitor Analysis

Daily Visitor
  • 4.900 visits
Daily Visitor