Nasza działalność to laptopy, laptopy dla graczy, laptopy Asus, Asus G73 i notebooki. W naszej ofercie ponadto notebooki Asus, tanie laptopy, wydajne laptopy, aluminiowy Asus oraz notebooki dla graczy. Asus G53, Asus K53, ...

x-kom.pl
  • Domain Name
    x-kom.pl
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #21791
  • Page Size
    101.1 KB
  • Ip Address
    94.152.136.115
  • Heading
    H1: 0, H2: 11, H3: 6, H4: 8, H5: 0, H6: 0
  • Images
    22 GIF, 9 JPG, 29 PNG

Website Meta Analysis

  • Title
    Sklep internetowy notebooki, tanie laptopy, wydajne notebooki laptopy dla graczy
  • Meta Keyword
    asus g53, wydajne notebooki, tanie laptopy, asus k53, laptopy dla graczy, sklep internetowy notebooki, sklep internetowy laptopy, wydajne laptopy, laptopy, asus g73, aluminiowy asus, notebooki asus, notebooki dla graczy, notebooki, laptopy asus, laptop, notebook, komputery, sklep internetowy, częstochowa, gdańsk, kraków, łódź, poznań, rzeszów ,tarnowskie góry, warszawa, wrocław
  • Meta Description
    Nasza działalność to laptopy, laptopy dla graczy, laptopy Asus, Asus G73 i notebooki. W naszej ofercie ponadto notebooki Asus, tanie laptopy, wydajne laptopy, aluminiowy Asus oraz notebooki dla graczy. Asus G53, Asus K53, sklep internetowy laptopy, wydajne notebooki i sklep internetowy notebooki

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    94.152.136.115
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from x-kom.pl.

HTML Analysis

  • date: Tue, 01 Oct 2013 19:15:05 GMT
  • server: Apache
  • 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
  • vary: Accept-Encoding
  • content-type: text/html
  • via: 1.1 x-kom.pl
  • x-google-cache-control: remote-fetch

DOMAIN NAME: x-kom.pl
registrant type: organization
nameservers: ns2.kei.pl. [195.149.225.1]
ns1.kei.pl. [195.149.224.1]
created: 2004.01.16 13:15:09
last modified: 2012.01.10 13:12:40
renewal date: 2013.01.16 13:15:09

no option

dnssec: Unsigned


REGISTRAR:
Agnat Sp. z o.o.
ul. Gdanska 107
85-022 Bydgoszcz
Polska/Poland
+48.52 3667777
+48.52 3667788
email
www.domena.pl

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
ns1.kei.pl [94.152.201.201]
ns2.kei.pl [195.149.225.1]


DNS Records

Answer records
x-kom.pl SOA
server: ns1.kei.pl
email: admin@kei.pl
serial: 2012052408
refresh: 10800
retry: 5700
expire: 604800
minimum ttl: 86400
86400s
x-kom.pl NS  ns2.kei.pl 86400s
x-kom.pl NS  ns1.kei.pl 86400s
x-kom.pl A 94.152.136.115 86400s
x-kom.pl MX
preference: 10
exchange: poczta.x-kom.pl
86400s
x-kom.pl TXT v=spf1 a mx include:spf.tld.pl -all 21600s

Authority records

Additional records
ns1.kei.pl A 94.152.201.201 3600s
ns2.kei.pl A 195.149.225.1 3600s
poczta.x-kom.pl A 94.152.136.116 21600s

IP 94.152.136.115 Analysis

  • Country Code
    PL
  • Country Code3
    POL
  • Country Name
    Poland
  • City
    EU
  • Continent Code
    52° North
  • Latitude
    20.
  • Longitude
  • No whois ip data for 94.152.136.115

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 17 Errors
  • 11 Warnings
Ratio Text/Html
  • 0.6218260869565218
Message Error
  • Error Line 256, Column 119: there is no attribute "autocomplete"
    …ch_var" id="simple_search_var" style="position: relative;" autocomplete="off"/>

    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 299, Column 49: character "&" is the first character of a delimiter but occurred as data
    … ($('#simple_search_var').val() == '' && $('#simple_search_var').is(':focus') …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 299, Column 50: character "&" is the first character of a delimiter but occurred as data
    …($('#simple_search_var').val() == '' && $('#simple_search_var').is(':focus') =…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 480, Column 105: there is no attribute "data-src"
    …"><img src="/images/blank.gif" data-src="/src/banners/hp_tusz.jpg" alt=""/></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.

  • Warning Line 483, Column 76: cannot generate system identifier for general entity "id_mailing"
    …-kom.pl/index.php?action=show_mailing&id_mailing=196"><img src="/images/blank.…

    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 483, Column 76: general entity "id_mailing" not defined and no default entity
    …-kom.pl/index.php?action=show_mailing&id_mailing=196"><img src="/images/blank.…

    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 483, Column 86: reference not terminated by REFC delimiter
    …dex.php?action=show_mailing&id_mailing=196"><img src="/images/blank.gif" data-…

    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.

  • Warning Line 483, Column 86: reference to external entity in attribute value
    …dex.php?action=show_mailing&id_mailing=196"><img src="/images/blank.gif" data-…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 483, Column 86: reference to entity "id_mailing" for which no system identifier could be generated
    …dex.php?action=show_mailing&id_mailing=196"><img src="/images/blank.gif" data-…

    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 483, Column 75: entity was defined here
    …x-kom.pl/index.php?action=show_mailing&id_mailing=196"><img src="/images/blank…
  • Warning Line 484, Column 86: reference not terminated by REFC delimiter
    …dex.php?action=show_mailing&id_mailing=195"><img src="/images/blank.gif" data-…

    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.

  • Warning Line 484, Column 86: reference to external entity in attribute value
    …dex.php?action=show_mailing&id_mailing=195"><img src="/images/blank.gif" data-…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 484, Column 86: reference to entity "id_mailing" for which no system identifier could be generated
    …dex.php?action=show_mailing&id_mailing=195"><img src="/images/blank.gif" data-…

    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 483, Column 75: entity was defined here
    …x-kom.pl/index.php?action=show_mailing&id_mailing=196"><img src="/images/blank…
  • Error Line 604, Column 111: required attribute "alt" not specified
    …top: 5px; right: 10px; opacity: 0.8;"/>     <strong style="font-size: 14px; pa…

    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 1533, Column 354: character "\" is not allowed in the value of attribute "id"
    …strong>i niesamowity dźwięk <span id="\\&quot;\\\\&quot;ctl00_ContentPlaceHold…

    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 1683, Column 29: end tag for "div" omitted, but OMITTAG NO was specified
                            </td>

    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 595, Column 43: start tag was here
    …                                </div><div id="category-wrapper" style="text-a…

Visitor Analysis

Daily Visitor
  • 6.067 visits
Daily Visitor