The Training of O is a bondage Website that where women are trained to be submissive by slave trainers. They are fucked, tied, stripped, penetrated and whipped. ...

thetrainingofo.com
  • Domain Name
    thetrainingofo.com
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #45834
  • Page Size
    15.1 KB
  • Ip Address
    208.80.184.203
  • Heading
    H1: 1, H2: 1, H3: 1, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 1 JPG, 1 PNG

Website Meta Analysis

  • Title
    Slave Training, Sadism and Masochism - TheTrainingOfO.com
  • Meta Keyword
    bondage and ex, submissives, slave training, story of o, training of o, thetrainingofo, thetrainingofo.com, bondage videos, bdsm
  • Meta Description
    The Training of O is a bondage Website that where women are trained to be submissive by slave trainers. They are fucked, tied, stripped, penetrated and whipped.

Technical Analysis

  • Webserver
    Apache-Coyote/1.1
  • Ip Address
    208.80.184.203
  • Domain Age
    6 Years, 12 Months, 3 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache-Coyote/1.1
  • content-type: text/html;charset=UTF-8
  • content-language: en-US
  • date: Wed, 11 Sep 2013 12:59:50 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: THETRAININGOFO.COM
Registrar: MONIKER

Registrant [3787463]:
Moniker Privacy Services email
Moniker Privacy Services
1800 SW 1st Avenue
Suite 440
Portland
OR
97201
US


Administrative Contact [3787463]:
Moniker Privacy Services email
Moniker Privacy Services
1800 SW 1st Avenue
Suite 440
Portland
OR
97201
US
Phone: +1.5032070147
Fax: +1.9545859186


Billing Contact [3787463]:
Moniker Privacy Services email
Moniker Privacy Services
1800 SW 1st Avenue
Suite 440
Portland
OR
97201
US
Phone: +1.5032070147
Fax: +1.9545859186


Technical Contact [3787463]:
Moniker Privacy Services email
Moniker Privacy Services
1800 SW 1st Avenue
Suite 440
Portland
OR
97201
US
Phone: +1.5032070147
Fax: +1.9545859186


Domain servers in listed order:

NS1.KINK.COM 208.80.184.69
NS2.KINK.COM 208.80.184.70
NS3.KINK.COM 208.83.221.18
NS4.KINK.COM 208.83.221.22
NS6.KINK.COM 212.13.194.125

Record created on: 2006-09-15 19:44:21.0
Database last updated on: 2012-02-14 12:58:37.377
Domain Expires on: 2017-09-15 19:44:21.0

DNS Analysis


DNS servers
ns6.kink.com [212.13.194.125]
ns4.kink.com [208.83.221.22]
ns3.kink.com [208.83.221.18]
ns2.kink.com [208.80.184.70]
ns1.kink.com [208.80.184.69]


DNS Records

Answer records
thetrainingofo.com SOA
server: ns1.kink.com
email: hostmaster@kink.com
serial: 2013031900
refresh: 1200
retry: 1200
expire: 604800
minimum ttl: 1200
1200s
thetrainingofo.com NS  ns6.kink.com 1200s
thetrainingofo.com NS  ns2.kink.com 1200s
thetrainingofo.com NS  ns1.kink.com 1200s
thetrainingofo.com NS  ns4.kink.com 1200s
thetrainingofo.com NS  ns3.kink.com 1200s
thetrainingofo.com A 208.80.184.202 1200s
thetrainingofo.com A 208.80.184.203 1200s
thetrainingofo.com MX
preference: 10
exchange: mail.kink.com
1200s
thetrainingofo.com TXT google-site-verification=vn9i-oU0neGVCUOROmv6699vLgNKH4azjMlKQuPMc5s 1200s
thetrainingofo.com TXT IPROTA_D30075-XXX.txt 1200s

Authority records

Additional records
ns1.kink.com A 208.80.184.69 1200s
ns2.kink.com A 208.80.184.70 1200s
ns3.kink.com A 208.83.221.18 1200s
ns4.kink.com A 208.83.221.22 1200s
ns6.kink.com A 85.119.82.125 1200s
mail.kink.com A 208.80.185.13 1200s

IP 208.80.184.203 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    San Francisco
  • Continent Code
    94103
  • Latitude
    415
  • Longitude
    807
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 208.80.184.203"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=208.80.184.203?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 208.80.184.0 - 208.80.191.255
    CIDR: 208.80.184.0/21
    OriginAS: AS40125
    NetName: KINK
    NetHandle: NET-208-80-184-0-1
    Parent: NET-208-0-0-0-0
    NetType: Direct Assignment
    RegDate: 2007-07-24
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-208-80-184-0-1

    OrgName: Cybernet Entertainment, LLC
    OrgId: CYBER-77
    Address: 1800 Mission Street
    City: San Francisco
    StateProv: CA
    PostalCode: 94103
    Country: US
    RegDate: 2006-05-23
    Updated: 2008-05-07
    Ref: http://whois.arin.net/rest/org/CYBER-77

    OrgTechHandle: NETOP53-ARIN
    OrgTechName: netops
    OrgTechPhone: +1-415-856-0771
    OrgTechEmail: netops@kink.com
    OrgTechRef: http://whois.arin.net/rest/poc/NETOP53-ARIN

    OrgNOCHandle: NOC2661-ARIN
    OrgNOCName: Network Operations Center
    OrgNOCPhone: +1-415-856-0771
    OrgNOCEmail: noc@kink.com
    OrgNOCRef: http://whois.arin.net/rest/poc/NOC2661-ARIN

    OrgAbuseHandle: ABUSE1717-ARIN
    OrgAbuseName: Abuse
    OrgAbusePhone: +1-415-856-0771
    OrgAbuseEmail: abuse@kink.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE1717-ARIN

    RNOCHandle: NOC2661-ARIN
    RNOCName: Network Operations Center
    RNOCPhone: +1-415-856-0771
    RNOCEmail: noc@kink.com
    RNOCRef: http://whois.arin.net/rest/poc/NOC2661-ARIN

    RAbuseHandle: ABUSE1717-ARIN
    RAbuseName: Abuse
    RAbusePhone: +1-415-856-0771
    RAbuseEmail: abuse@kink.com
    RAbuseRef: http://whois.arin.net/rest/poc/ABUSE1717-ARIN

    RTechHandle: ROOT1-ARIN
    RTechName: Root
    RTechPhone: +1-415-856-0771
    RTechEmail: root@kink.com
    RTechRef: http://whois.arin.net/rest/poc/ROOT1-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 7 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.45907565194939326
Message Error
  • Warning Line 73, Column 24: character "&" is the first character of a delimiter but occurred as data
    						if (linkHostName && linkHostName != currentHostName ){

    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 73, Column 25: character "&" is the first character of a delimiter but occurred as data
    						if (linkHostName && linkHostName != currentHostName ){

    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 98, Column 25: character "&" is the first character of a delimiter but occurred as data
    							if (linkHostName && linkHostName != currentHostName ){

    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 98, Column 26: character "&" is the first character of a delimiter but occurred as data
    							if (linkHostName && linkHostName != currentHostName ){

    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 125, Column 44: "itemscope" is not a member of a group specified for any attribute
    	<body class="yui-skin-kink TTO" itemscope itemtype="http://schema.org/WebPage">
  • Error Line 125, Column 53: there is no attribute "itemtype"
    	<body class="yui-skin-kink TTO" itemscope itemtype="http://schema.org/WebPage">

    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 127, Column 30: an attribute specification must start with a name or name token
    <table id="seoTermsContainer"">

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 127, Column 31: character data is not allowed here
    <table id="seoTermsContainer"">

    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.
  • Warning Line 145, Column 36: cannot generate system identifier for general entity "m"
    	<a href="/sadism-and-masochism">s&m</a>, bondage, whipping, spanking, caning a…

    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 145, Column 36: general entity "m" not defined and no default entity
    	<a href="/sadism-and-masochism">s&m</a>, bondage, whipping, spanking, caning a…

    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 145, Column 37: reference not terminated by REFC delimiter
    	<a href="/sadism-and-masochism">s&m</a>, bondage, whipping, spanking, caning a…

    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 145, Column 37: reference to entity "m" for which no system identifier could be generated
    	<a href="/sadism-and-masochism">s&m</a>, bondage, whipping, spanking, caning a…

    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 145, Column 35: entity was defined here
    	<a href="/sadism-and-masochism">s&m</a>, bondage, whipping, spanking, caning a…
  • Error Line 228, Column 151: required attribute "alt" not specified
    ….kink.com/data/cybernetentertainment/banners/ul_safeadlt.gif" border="0" /></a>

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

Visitor Analysis

Daily Visitor
  • 4.900 visits