PAMIĘTAJ! Logowanie do serwisu iPKO nie wymaga podania kodu z karty kodów jednorazowych. Bank również nigdy nie poprosi Cię o podanie jednocześnie kilku kodów z karty kodów lub danych karty płatniczej. więcej o ...

ipko.pl
  • Domain Name
    ipko.pl
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #7398
  • Page Size
    26.6 KB
  • Ip Address
    193.109.225.71
  • Heading
    H1: 0, H2: 0, H3: 1, H4: 2, H5: 0, H6: 0
  • Images
    11 GIF, 1 JPG, 0 PNG

Website Meta Analysis

  • Title
    Serwis internetowy iPKO
  • Meta Keyword
  • Meta Description
    PAMIĘTAJ! Logowanie do serwisu iPKO nie wymaga podania kodu z karty kodów jednorazowych. Bank również nigdy nie poprosi Cię o podanie jednocześnie kilku kodów z karty kodów lub danych karty płatniczej. więcej o bezpieczeństwie Numer klienta ...

Technical Analysis

  • Webserver
    Platforma Inteligo
  • Ip Address
    193.109.225.71
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 29 Jun 2013 01:12:45 GMT
  • server: Platforma Inteligo
  • pragma: no-cache
  • cache-control: no-cache, no-store, must-revalidate, max-age=0, post-check=0, pre-check=0
  • expires: -1
  • content-type: text/html; charset=iso-8859-2
  • content-language: PL
  • x-frame-options: DENY
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 12107
  • connection: Keep-Alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for ipko.pl

IP 193.109.225.71 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 23 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.42444060697358266
Message Error
  • Warning Line 9, Column 57: NET-enabling start-tag requires SHORTTAG YES
    …v="X-UA-Compatible" content="IE=edge" />   <link rel="stylesheet" type="text/c…

    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 9, Column 58: character data is not allowed here
    …="X-UA-Compatible" content="IE=edge" />   <link rel="stylesheet" type="text/cs…

    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 299, Column 8: end tag for element "STYLE" which is not open
    </style>

    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 398, Column 13: there is no attribute "ONACTIVATE"
     onactivate="disable_focus_placing=1;">

    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 404, Column 96: character "-" is not allowed in the value of attribute "TABINDEX"
    …button" src="/ikd_img/skins/ipko/trans.gif" alt="" tabindex="-1" name="btn_ok">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 413, Column 17: end tag for "UL" which is not finished
                </ul>

    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.

  • Warning Line 438, Column 374: NET-enabling start-tag requires SHORTTAG YES
    …d_img/skins/ipko/bezpieczenstwo.gif" alt="Bezpieczeństwo w iPKO" /></div></div>

    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.

  • Warning Line 441, Column 75: NET-enabling start-tag requires SHORTTAG YES
    …rong><br> Logowanie do serwisu iPKO<br/><strong>nie wymaga podania kodu z kart…

    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.

  • Warning Line 442, Column 48: NET-enabling start-tag requires SHORTTAG YES
    …                    jednorazowych.<br /><strong>Bank również nigdy nie poprosi…

    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 462, Column 50: element "NOBR" undefined
    …idth="100px" style="text-align:right"><nobr>Numer klienta lub login</nobr></td>

    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 464, Column 54: duplicate specification of attribute "STYLE"
    … style="width:250px;" size="38" style="width=304px;;" style="border: 1px #A5B8…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 464, Column 76: duplicate specification of attribute "STYLE"
    …" size="38" style="width=304px;;" style="border: 1px #A5B881 solid;;"  value=""

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 488, 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 514, Column 163: there is no attribute "AUTOCOMPLETE"
    …ur='hide_capsLockWarn()' autocomplete="off" style="width=304px;;" style="borde…

    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 514, Column 175: duplicate specification of attribute "STYLE"
    …sLockWarn()' autocomplete="off" style="width=304px;;" style="border: 1px #A5B8…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 514, Column 197: duplicate specification of attribute "STYLE"
    …plete="off" style="width=304px;;" style="border: 1px #A5B881 solid;;"  value=""

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 533, Column 9: there is no attribute "WIDTH"
      width="91" height="31" border="0" hspace="1" alt="Zaloguj" title="Zaloguj" st…

    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 533, Column 21: there is no attribute "HEIGHT"
      width="91" height="31" border="0" hspace="1" alt="Zaloguj" title="Zaloguj" st…

    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 533, Column 33: there is no attribute "BORDER"
      width="91" height="31" border="0" hspace="1" alt="Zaloguj" title="Zaloguj" st…

    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 533, Column 44: there is no attribute "HSPACE"
    …th="91" height="31" border="0" hspace="1" alt="Zaloguj" title="Zaloguj" style=…

    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.

  • Warning Line 591, Column 8: NET-enabling start-tag requires SHORTTAG YES
       <br />

    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 602, Column 68: document type does not allow element "H4" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … id="h4zlozwniosekonline" style="cursor:pointer;">Złóż wniosek on-line</h4></a>

    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 647, Column 12: end tag for element "DIV" which is not open
    </div></div>

    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 657, Column 86: NET-enabling start-tag requires SHORTTAG YES
    …r="#004392" width="10%"><img src="/ikd_img/skins/ipko/pomoc-infotip.gif"/></td>

    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 657, Column 86: required attribute "ALT" not specified
    …r="#004392" width="10%"><img src="/ikd_img/skins/ipko/pomoc-infotip.gif"/></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 672, Column 28: invalid comment declaration: found name start character outside comment but inside comment declaration
      <!--[if IE]></center><!--endif-->
  • Info Line 672, Column 3: comment declaration started here
      <!--[if IE]></center><!--endif-->
  • Error Line 681, Column 6: invalid comment declaration: found name start character outside comment but inside comment declaration
         var minimal_size = 750;
  • Info Line 679, Column 1: comment declaration started here
    <!--[if lt IE 7]>
  • Error Line 683, Column 17: end tag for element "SCRIPT" which is not open
       //--></script>

    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 684, Column 4: "ENDIF" is not a reserved name
    <![endif]-->

Visitor Analysis

Daily Visitor
  • 40.833 visits