pink.pl

Sex Pokazy na Żywo na Pink.pl. Sex Kamery na Żywo. Sex kamerki. Darmowe kamerki i czat, seks na Żywo. Erotyczne porno kamerki. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 01-08-2013 04:54:14  (update).

Overview Info

  • Domain Name
    pink.pl
  • Favicon
  • Alexa Rank
    #143910
  • Google Page Rank
    PR 1
  • Ip Address
    37.59.54.174
  • Page Size
    4.3 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 0 0 0 0

Website Meta Analysis

  • Title
    PINK.pl - Seks Pokazy Na Żywo, Darmowe Porno Sex Kamerki!
  • Meta Keyword
    sex pokazy, sex kamerki, darmowe kamery, seks na żywo, live, porno show, praca na kamerkach, erotyczne kamerki, kamery, bez skype, sex czat
  • Meta Description
    Sex Pokazy na Żywo na Pink.pl. Sex Kamery na Żywo. Sex kamerki. Darmowe kamerki i czat, seks na Żywo. Erotyczne porno kamerki.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    37.59.54.174
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Thu, 01 Aug 2013 16:54:12 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN NAME: pink.pl
registrant type: organization
nameservers: fns2.42.pl. [2a02:2978::a503:4209:2][195.80.237.194]
fns1.42.pl. [79.98.145.34]
created: 2004.03.01 23:48:15
last modified: 2013.02.05 16:02:15
renewal date: 2014.03.01 23:48:15

option created: 2011.02.03 17:30:52
option expiration date: 2014.02.03 17:30:52

dnssec: Unsigned
TECHNICAL CONTACT: data restricted


REGISTRAR:
Grupa Onet.pl S.A.
ul. G. Zapolskiej 44
30 - 126 Krakow
Polska/Poland
+48. 12 2600200
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
fns2.42.pl
fns1.42.pl


DNS Records

Answer records
pink.pl A 37.59.54.174 86400s
pink.pl SOA
server: fns1.42.pl
email: freedns-admin+144566@42.pl
serial: 1353757195
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
86400s
pink.pl NS  fns1.42.pl 86400s
pink.pl NS  fns2.42.pl 86400s

Authority records

Additional records
fns1.42.pl A 79.98.145.34 86400s
fns2.42.pl A 195.80.237.194 86400s
fns2.42.pl 28 [16 bytes] 86400s

IP 37.59.54.174 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 26 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.67053998632946
Message Error
  • Error Line 5, Column 19: there is no attribute "charset"
        <meta charset="utf8">

    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 5, Column 25: required attribute "content" not specified
        <meta charset="utf8">

    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 5, Column 26: end tag for "meta" omitted, but OMITTAG NO was specified
        <meta charset="utf8">

    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 5, Column 5: start tag was here
        <meta charset="utf8">
  • Error Line 6, Column 68: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" content="text/html; charset=utf8" >

    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 6, Column 1: start tag was here
    <meta http-equiv="Content-Type" content="text/html; charset=utf8" >
  • Error Line 8, Column 158: end tag for "meta" omitted, but OMITTAG NO was specified
    … Żywo. Sex kamerki. Darmowe kamerki i czat, seks na Żywo. Erotyczne kamerki."> 

    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 8, Column 2: start tag was here
    	<meta name="Description" content="Sex Pokazy na Żywo na Pink.pl. Sex Kamery na…
  • Error Line 9, Column 168: end tag for "meta" omitted, but OMITTAG NO was specified
    …ive, show, praca na kamerkach, erotyczne kamerki, kamery, bez skype, sex czat">

    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 9, Column 2: start tag was here
    	<meta name="keywords" content="sex pokazy, sex kamerki, darmowe kamery, seks n…
  • Error Line 10, Column 68: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name="Page-topic" content="sex kamerki, sex pokazy na żywo">

    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 10, Column 2: start tag was here
    	<meta name="Page-topic" content="sex kamerki, sex pokazy na żywo">
  • Error Line 11, Column 58: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name="Page-type" content="seks na żywo, sex czat">

    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 11, Column 2: start tag was here
    	<meta name="Page-type" content="seks na żywo, sex czat">
  • Error Line 12, Column 13: there is no attribute "name"
    	<META name="Classification" content="Darmowe kamerki erotyczne">

    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 12, Column 38: there is no attribute "content"
    	<META name="Classification" content="Darmowe kamerki erotyczne">

    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 12, Column 65: element "META" undefined
    	<META name="Classification" content="Darmowe kamerki erotyczne">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 13, Column 73: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name="Subject" content="erotyczne kamery, sex na żywo bez skype">

    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 13, Column 2: start tag was here
    	<meta name="Subject" content="erotyczne kamery, sex na żywo bez skype">
  • Error Line 14, Column 13: there is no attribute "NAME"
    	<META NAME="ROBOTS" CONTENT="INDEX,FOLLOW">

    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 14, Column 30: there is no attribute "CONTENT"
    	<META NAME="ROBOTS" CONTENT="INDEX,FOLLOW">

    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 14, Column 44: element "META" undefined
    	<META NAME="ROBOTS" CONTENT="INDEX,FOLLOW">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 15, Column 47: element "META" undefined
    	<META NAME="GOOGLEBOT" CONTENT="INDEX,FOLLOW">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 16, Column 46: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name="Revisit-After" content="3 days">

    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 16, Column 2: start tag was here
    	<meta name="Revisit-After" content="3 days">
  • Error Line 17, Column 40: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name="Author" content="Pink.pl">

    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 17, Column 2: start tag was here
    	<meta name="Author" content="Pink.pl">
  • Error Line 18, Column 40: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name="Rating" content="General">

    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 18, Column 2: start tag was here
    	<meta name="Rating" content="General">
  • Error Line 19, Column 45: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta name="Distribution" content="Global">

    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 19, Column 2: start tag was here
    	<meta name="Distribution" content="Global">
  • Error Line 28, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 15, Column 2: start tag was here
    	<META NAME="GOOGLEBOT" CONTENT="INDEX,FOLLOW">
  • Error Line 28, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 14, Column 2: start tag was here
    	<META NAME="ROBOTS" CONTENT="INDEX,FOLLOW">
  • Error Line 28, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 12, Column 2: start tag was here
    	<META name="Classification" content="Darmowe kamerki erotyczne">
  • Error Line 42, Column 5: end tag for element "br" which is not open
    </br></br>

    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.

  • Error Line 42, Column 10: end tag for element "br" which is not open
    </br></br>

    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.

  • Error Line 43, Column 148: end tag for element "br" which is not open
    …amin</a> i <a href='/pl/site/privacy_policy'>Politykę Prywatności</a></br></br>

    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.

  • Error Line 43, Column 153: end tag for element "br" which is not open
    …amin</a> i <a href='/pl/site/privacy_policy'>Politykę Prywatności</a></br></br>

    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.

Visitor Analysis

Daily Visitor
  • 630 visits

In Page Analysis