Sex Trader - Escort Stripper and Model The Ultimate South African Adult Guide for ALL your adult entertainment needs!!! Clubs,Venues, Information ...

sextrader.co.za
  • Domain Name
    sextrader.co.za
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #62581
  • Page Size
    8.7 KB
  • Ip Address
    197.221.53.234
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 6 JPG, 0 PNG

Website Meta Analysis

  • Title
    Sex Trader. All adult entertainment in South Africa (Johannesburg, Pretoria, Durban, Cape Town) escorts, models, strippers, masseurs and personals, Independent Escort Network escort and adult entertainer links. All you need to know about Escorts, strippers, dommes, agencies, exotic dancers, private dancers, Escorts South Africa Johannesburg, Neena, Pretoria, Durban, Bloemfontein, Cape Town, Port Elizabeth escorts Escorts South Africa Johannesburg, Neena, Pretoria, Durban, Bloemfontein, Cape Town, Port Elizabeth escorts Escorts South Africa Johannesburg, Neena, Pretoria, Durban, Bloemfontein, Cape Town, Port Elizabeth escorts
  • Meta Keyword
  • Meta Description
    Sex Trader - Escort Stripper and Model The Ultimate South African Adult Guide for ALL your adult entertainment needs!!! Clubs,Venues, Information

Technical Analysis

  • Webserver
    Apache/2.2.25 (Unix) mod_ssl/2.2.25 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.3.27 mod_perl/2.0.6 Perl/v5.10.1
  • Ip Address
    197.221.53.234
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from sextrader.co.za.

HTML Analysis

  • date: Thu, 05 Sep 2013 00:38:13 GMT
  • server: Apache/2.2.25 (Unix) mod_ssl/2.2.25 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.3.27 mod_perl/2.0.6 Perl/v5.10.1
  • x-powered-by: PHP/5.3.27
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-length: 3300
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for sextrader.co.za

DNS Analysis


DNS servers
ns2.twoshipstrading.co.za [41.215.239.115]
ns1.twoshipstrading.co.za [41.215.239.114]


DNS Records

Answer records
sextrader.co.za MX
preference: 0
exchange: sextrader.co.za
14400s
sextrader.co.za SOA
server: ns1.twoshipstrading.co.za
email: info@twoshipstrading.co.za
serial: 2013010807
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
sextrader.co.za NS  ns1.twoshipstrading.co.za 86400s
sextrader.co.za NS  ns2.twoshipstrading.co.za 86400s
sextrader.co.za A 41.215.239.114 14400s

Authority records

Additional records
sextrader.co.za A 41.215.239.114 14400s
ns1.twoshipstrading.co.za A 41.215.239.114 14400s
ns2.twoshipstrading.co.za A 41.215.239.115 14400s

IP 197.221.53.234 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 26 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.5712364084743863
Message Error
  • Error Line 3, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    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.

  • Error Line 10, Column 16: value of attribute "NAME" must be a single token
    <META NAME="Sex Trader" CONTENT="All adult entertainment in South Africa (Johan…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 12, Column 21: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    <meta name="keywords" content="adult, adult south africa, escort south africa, …

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 13, Column 182: document type does not allow element "META" here
    …lt Guide for ALL your adult entertainment needs!!!  Clubs,Venues, Information">

    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 14, Column 43: document type does not allow element "META" here
    <meta name="robots" content="index,follow">

    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 16, Column 19: value of attribute "NAME" must be a single token
    <meta name="Escort South Africa" content="Escort South Africa the only national…

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 16, Column 119: document type does not allow element "META" here
    …="Escort South Africa the only national listing of Escorts in Southern Africa">

    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 18, Column 44: document type does not allow element "META" here
    <meta name="revisit-after" content="5 days">

    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 19, Column 52: document type does not allow element "META" here
    <meta http-equiv="Content-Language" content="en-za">

    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 43: document type does not allow element "META" here
    <meta name="copyright" content="SexTrader">

    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 21, Column 74: document type does not allow element "META" here
    <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">

    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 23, Column 52: document type does not allow element "META" here
    <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">

    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 27, Column 76: document type does not allow element "META" here
    <META HTTP-EQUIV=REFRESH CONTENT="0; URL=http://www.sextrader.co.za/mobile">

    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 29, Column 4: end tag for element "P" which is not open
    </p>

    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 31, Column 79: NET-enabling start-tag requires SHORTTAG YES
    <meta name="verify-v1" content="KmBTkzOVEzE9/nIgKAk2RvT1MUNlJpYNquRVVxFaqXU=" />

    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 31, Column 79: document type does not allow element "META" here
    <meta name="verify-v1" content="KmBTkzOVEzE9/nIgKAk2RvT1MUNlJpYNquRVVxFaqXU=" />

    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 34, Column 6: document type does not allow element "HTML" here
    <html>

    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 35, Column 30: 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>.

  • Error Line 48, Column 7: end tag for "HEAD" which is not finished
    </HEAD>

    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.

  • Error Line 68, Column 84: document type does not allow element "BODY" here
    … background="siteimages/background_compressed.jpg" onLoad="showElapsedTime();">

    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 73, Column 99: required attribute "ALT" not specified
    …s/sex%20trader%20pic%20streched%20compressed.jpg" width="448" height="187"></p>

    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 74, Column 40: there is no attribute "HEIGHT"
      <table width="84%" border="0" height="604">

    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 76, Column 133: required attribute "ALT" not specified
    …_pics/tn_09050303.jpg" name="idElement18Img" id="idElement18Img" border=0></td>

    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 99, Column 125: required attribute "ALT" not specified
    …pics/tn_g1066_7090.jpg" name="idElement23Img" id="idElement23Img" border=0></p>

    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 123, Column 138: required attribute "ALT" not specified
    …/tn_fer0710039897.jpg" name="idElement21Img" id="idElement21Img" border=0></td>

    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 139, Column 125: required attribute "ALT" not specified
    …pics/tn_28240203.jpg" name="idElement26Img" id="idElement26Img" border=0></div>

    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 159, Column 207: required attribute "ALT" not specified
    …name="idElement2Img" id="idElement2Img" width=130 height=71 border=0></a></div>

    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
  • 2.333 visits