socialsex.com - Social sex network and facebook of sex adult dating networking website for adults - Find local sex - Browse 1000s of adult XXX socialsex book profiles with photos. ...

socialsex.com
  • Domain Name
    socialsex.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #3256
  • Page Size
    12.9 KB
  • Ip Address
    209.47.169.32
  • Heading
    H1: 2, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    SocialSex.com - Social Sex | Sexbook | Fuckbook for Adults!
  • Meta Keyword
    adult friend, facebook of sex, fuckbook, adult dating, sex chat
  • Meta Description
    socialsex.com - Social sex network and facebook of sex adult dating networking website for adults - Find local sex - Browse 1000s of adult XXX socialsex book profiles with photos.

Technical Analysis

  • Webserver
    Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.26 with Suhosin-Patch
  • Ip Address
    209.47.169.32
  • Domain Age
    9 Years, 6 Months, 27 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 12 Sep 2013 01:51:13 GMT
  • server: Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.26 with Suhosin-Patch
  • x-powered-by: PHP/5.2.4-2ubuntu5.26
  • expires: Thu, 19 Nov 1981 00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • backend: fdr02
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 4691
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: SOCIALSEX.COM

Registrant:
Domains By Proxy, LLC

Domain servers in listed order:
NS1.SEXSEARCH.COM
NS2.SEXSEARCH.COM

DNS Analysis


DNS servers
ns1.sexsearch.com [204.101.51.11]
ns2.sexsearch.com [209.47.169.92]


DNS Records

Answer records
socialsex.com NS  ns1.sexsearch.com 86400s
socialsex.com NS  ns2.sexsearch.com 86400s
socialsex.com TXT IPROTA_D109609-XXX 86400s
socialsex.com TXT v=spf1 ip4:216.105.95.33 ip4:209.47.169.0/24 ip4:204.101.51.0/24 -all 86400s
socialsex.com TXT spf2.0/pra,mfrom ip4:216.105.95.33 ip4:209.47.169.0/24 ip4:204.101.51.0/24 -all 86400s
socialsex.com MX
preference: 10
exchange: imail2.nationalfibre.net
86400s
socialsex.com A 209.47.169.32 86400s
socialsex.com SOA
server: ns1.sexsearch.com
email: hostmaster@sexsearch.com
serial: 2013030101
refresh: 3600
retry: 900
expire: 1209600
minimum ttl: 3600
86400s

Authority records
socialsex.com NS  ns1.sexsearch.com 86400s
socialsex.com NS  ns2.sexsearch.com 86400s

Additional records
ns1.sexsearch.com A 204.101.51.11 86400s
ns2.sexsearch.com A 209.47.169.92 86400s

IP 209.47.169.32 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 28 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.3496862952604127
Message Error
  • Error Line 112, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 129, Column 45: document type does not allow element "div" here
     		document.write( '<div id="dvFlashLanding">' );

    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 136, Column 21: cannot generate system identifier for general entity "env"
     	    'flashvars','&env=1' +

    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 136, Column 21: general entity "env" not defined and no default entity
     	    'flashvars','&env=1' +

    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 136, Column 24: reference not terminated by REFC delimiter
     	    'flashvars','&env=1' +

    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 136, Column 24: reference to entity "env" for which no system identifier could be generated
     	    'flashvars','&env=1' +

    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 136, Column 20: entity was defined here
     	    'flashvars','&env=1' +
  • Warning Line 137, Column 9: cannot generate system identifier for general entity "links"
     				 '&links=' +

    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 137, Column 9: general entity "links" not defined and no default entity
     				 '&links=' +

    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 137, Column 14: reference not terminated by REFC delimiter
     				 '&links=' +

    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 137, Column 14: reference to entity "links" for which no system identifier could be generated
     				 '&links=' +

    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 137, Column 8: entity was defined here
     				 '&links=' +
  • Error Line 169, Column 29: delimiter """ invalid: only S separators and TAGC allowed here
     	    document.write( '</div">' );
  • Error Line 175, Column 105: document type does not allow element "table" here
    …er="0" cellpadding="0" cellspacing="0"><tr><td><a href="http://www.macromedia.…

    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 175, Column 217: there is no attribute "WIDTH"
    …nk"><img src="' + imageUrl + '" WIDTH="1024" HEIGHT="710" BORDER="0"></a></td>…

    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 175, Column 231: there is no attribute "HEIGHT"
    …' + imageUrl + '" WIDTH="1024" HEIGHT="710" BORDER="0"></a></td></tr></table>'…

    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 175, Column 244: there is no attribute "BORDER"
    …' + imageUrl + '" WIDTH="1024" HEIGHT="710" BORDER="0"></a></td></tr></table>';

    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 175, Column 247: required attribute "alt" not specified
    …' + imageUrl + '" WIDTH="1024" HEIGHT="710" BORDER="0"></a></td></tr></table>';

    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 175, Column 251: end tag for "img" omitted, but OMITTAG NO was specified
    …' + imageUrl + '" WIDTH="1024" HEIGHT="710" BORDER="0"></a></td></tr></table>';

    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 175, Column 183: start tag was here
    …com/go/getflashplayer" target="blank"><img src="' + imageUrl + '" WIDTH="1024"…
  • Error Line 183, Column 32: there is no attribute "data-href"
    <div class="fb-like" data-href="http://socialsex.com" data-send="true" data-lay…

    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 183, Column 65: there is no attribute "data-send"
    …href="http://socialsex.com" data-send="true" data-layout="button_count" data-w…

    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 183, Column 84: there is no attribute "data-layout"
    …sex.com" data-send="true" data-layout="button_count" data-width="90" data-show…

    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 183, Column 110: there is no attribute "data-width"
    …data-layout="button_count" data-width="90" data-show-faces="false" style="posi…

    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 183, Column 131: there is no attribute "data-show-faces"
    …ount" data-width="90" data-show-faces="false" style="position:relative; top:-2…

    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 187, Column 80: there is no attribute "data-count"
    …s://twitter.com/share" class="twitter-share-button" data-count="none">Tweet</a>

    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 188, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

    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 193, Column 33: there is no attribute "data-action"
    <div class="g-plus" data-action="share" data-annotation="none"></div>

    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 193, Column 57: there is no attribute "data-annotation"
    <div class="g-plus" data-action="share" data-annotation="none"></div>

    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 210, Column 57: ID "footer-container" already defined
                    <div id="footer-nav-container"><div id="footer-container">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 207, Column 18: ID "footer-container" first defined here
            <div id="footer-container">
  • Error Line 230, Column 138: end tag for "br" omitted, but OMITTAG NO was specified
    …videos, stories, images, or sounds<br>You must be 18 years of age or older to …

    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 230, Column 134: start tag was here
    …es, videos, stories, images, or sounds<br>You must be 18 years of age or older…
  • Error Line 231, Column 83: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …                <p style="text-align:center"><div id="bottom-footer-container">

    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 250, Column 171: required attribute "alt" not specified
    …000o2i2szj0iza_7k1y/njs.gif?dcsuri=/nojavascript&amp;WT.js=No&amp;WT.tv=8.0.0">

    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 250, Column 172: end tag for "img" omitted, but OMITTAG NO was specified
    …000o2i2szj0iza_7k1y/njs.gif?dcsuri=/nojavascript&amp;WT.js=No&amp;WT.tv=8.0.0">

    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 250, Column 2: start tag was here
    	<img border="0" name="DCSIMG" width="1" height="1" src="http://wt.socialsex.bi…

Visitor Analysis

Daily Visitor
  • 121.333 visits