sextv1.pl

sextv1.pl has Alexa Rank 39.309 and Google Page Rank is 1

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    sextv1.pl
  • Favicon
  • Alexa Rank
    #39309
  • Google Page Rank
    PR 1
  • Ip Address
    89.161.142.241
  • Page Size
    29.9 KB
  • Images
    2 GIF, 28 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 4 0 0 0 0

Technical Analysis



  • Webserver
    IdeaWebServer/v0.80
  • Ip Address
    89.161.142.241
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from sextv1.pl.

HTML Analysis

  • cache-control: post-check=0, pre-check=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • content-type: text/html
  • date: Tue, 17 Sep 2013 18:31:59 GMT
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • last-modified: Tue, 17 Sep 2013 18:31:59 GMT
  • pragma: no-cache
  • server: IdeaWebServer/v0.80
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN NAME: sextv1.pl
registrant type: individual
nameservers: ns3.netart.pl. [85.128.130.10]
ns1.netart.pl. [85.128.128.10]
ns2.netart.pl. [85.128.129.10]
created: 2007.02.07 14:49:44
last modified: 2012.01.25 18:25:08
renewal date: 2013.02.07 14:49:44

no option

dnssec: Unsigned


REGISTRAR:
NetArt Spolka Akcyjna S.K.A.
ul. Cystersow 20A
31-553 Krakow
Polska/Poland
+48.801 33 22 33
+48.12 297 88 10
+48.12 297 88 08
email

WHOIS displays data with a delay not exceeding 15 minutes in relation to the .pl Registry system
Registrant data available at http://dns.pl/cgi-bin/en_whois.pl

DNS Analysis


DNS servers
ns3.netart.pl [85.128.130.10]
ns1.netart.pl [85.128.128.10]
ns2.netart.pl [85.128.129.10]


DNS Records

Answer records
sextv1.pl NS  ns3.netart.pl 3600s
sextv1.pl SOA
server: ns1.netart.pl
email: biuro@netart.pl
serial: 2008133200
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
3600s
sextv1.pl NS  ns1.netart.pl 3600s
sextv1.pl A 37.59.53.92 3600s
sextv1.pl NS  ns2.netart.pl 3600s
sextv1.pl MX
preference: 10
exchange: sextv1.pl
3600s

Authority records

Additional records
ns3.netart.pl A 85.128.130.10 3600s
ns1.netart.pl A 85.128.128.10 3600s
ns2.netart.pl A 85.128.129.10 3600s

IP 89.161.142.241 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 7 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.6867234125819391
Message Error
  • Warning Line 14, Column 79: NET-enabling start-tag requires SHORTTAG YES
    <meta name="verify-v1" content="5sDmldP936BXEmEq2uRoWKAe88rfqwxi0O66yXDnPxQ=" />

    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 14, Column 80: character data is not allowed here
    <meta name="verify-v1" content="5sDmldP936BXEmEq2uRoWKAe88rfqwxi0O66yXDnPxQ=" />

    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 22, Column 6: document type does not allow element "BODY" here
    <body>

    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 31, Column 90: required attribute "ALT" not specified
    …ical-align:middle;' border=0 src='./images/english.gif'> SexTV1 in english </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>.

  • Error Line 62, Column 7: end tag for "HTML" which is not finished
    </html>

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

In Page Analysis