trumsex.info

This site requires JavaScript and Cookies to be enabled. Please change your browser settings or upgrade your browser. ...

This data was last updated from 01-11-2014 11:57:30  (update).

Overview Info



  • Domain Name
    trumsex.info
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    0
  • Ip Address
    69.172.201.208
  • Page Size
    1.6 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
  • Meta Keyword
  • Meta Description
    This site requires JavaScript and Cookies to be enabled. Please change your browser settings or upgrade your browser.

Technical Analysis



  • Webserver
    nginx/1.7.5
  • Ip Address
    69.172.201.208
  • Domain Age
    3 Months, 4 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from trumsex.info.

HTML Analysis

  • server: nginx/1.7.5
  • date: Sat, 01 Nov 2014 11:57:28 GMT
  • content-type: text/html
  • connection: keep-alive
  • p3p: CP="NON DSP COR ADMa OUR IND UNI COM NAV INT"
  • cache-control: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for trumsex.info

DNS Analysis


DNS servers
ns4jpz.name.com [184.72.222.215]
ns3qty.name.com [208.43.82.144]
ns2fwz.name.com [98.124.246.1]
ns1dhl.name.com [184.172.60.181]


DNS Records

Answer records
trumsex.info SOA
server: ns1dhl.name.com
email: [email protected]
serial: 1
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 300
300s
trumsex.info NS  ns2fwz.name.com 300s
trumsex.info A 64.237.55.171 300s
trumsex.info NS  ns4jpz.name.com 300s
trumsex.info NS  ns3qty.name.com 300s
trumsex.info NS  ns1dhl.name.com 300s

Authority records

Additional records
ns4jpz.name.com A 184.72.222.215 86400s
ns1dhl.name.com A 184.172.60.181 86400s
ns2fwz.name.com A 98.124.246.1 86400s
ns3qty.name.com A 208.43.82.144 86400s

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 3 Errors
  • 0 Warnings
Ratio Text/Html
  • 0.20817610062893077
Message Error
  • Error Line 42, 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 44, Column 11: character data is not allowed here
    <noscript>This site requires JavaScript and Cookies to be enabled. Please chang…

    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.
  • Error Line 44, Column 138: end tag for "NOSCRIPT" which is not finished
    …nabled. Please change your browser settings or upgrade your browser.</noscript>

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

In Page Analysis