moto.se.pl

Najświeższe ogłoszenia motoryzacyjne. Kup, sprzedaj samochody osobowe, dostawcze, ciężarowe, terenowe, motocykle, maszyny budowlane, rolnicze oraz sprzęt wodny. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 11-03-2013 01:29:18  (update).

Overview Info

  • Domain Name
    moto.se.pl
  • Favicon
  • Alexa Rank
    #6941
  • Google Page Rank
    PR 5
  • Ip Address
    195.8.99.26
  • Page Size
    72.7 KB
  • Images
    7 GIF, 8 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 5 16 0 0 0

Website Meta Analysis



  • Title
    Motoryzacja | Samochody używane | Ogłoszenia Motoryzacyjne w moto.se.pl
  • Meta Keyword
    auta, moto, motoryzacja, samochody używane, ogłoszenia motoryzacyjne, giełda samochodowa, samochody nowe
  • Meta Description
    Najświeższe ogłoszenia motoryzacyjne. Kup, sprzedaj samochody osobowe, dostawcze, ciężarowe, terenowe, motocykle, maszyny budowlane, rolnicze oraz sprzęt wodny.

Technical Analysis



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

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

HTML Analysis

  • date: Mon, 11 Mar 2013 13:29:13 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
  • vary: Accept-Encoding
  • content-encoding: gzip
  • connection: close
  • content-type: text/html; charset=iso-8859-2
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN Domain Name: se.pl
registrant type: organization
Name Servers: dns1.supermedia.pl. 212.180.140.12001:4c30:100:1::10
dns2.supermedia.pl. 85.232.245.83
created: 1998.10.14 13:00:00
Updated: 2011.09.05 15:35:32
Expires: 2012.10.13 14:00:00
option created: 2011.01.20 14:52:09
option Expires: 2014.01.20 14:52:09
REGISTRAR:
Supermedia sp. z o.o.
ul. Senatorska 13/15
00-075 Warszawa
Polska/Poland
+48.22 8296586, 8296511
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
ns2.gratka.pl [213.192.69.59]
ns1.gratka.pl [195.8.99.97]


DNS Records

Answer records
moto.gratka.pl A 195.8.99.26 600s
moto.gratka.pl 28 [16 bytes] 600s

Authority records
gratka.pl NS  ns2.gratka.pl 600s
gratka.pl NS  ns1.gratka.pl 600s

Additional records
ns1.gratka.pl A 195.8.99.97 600s
ns1.gratka.pl 28 [16 bytes] 600s
ns2.gratka.pl A 213.192.69.59 600s

IP 195.8.99.26 Analysis

  • Country Code
    PL
  • Country Code3
    POL
  • Country Name
    Poland
  • City
    Gdansk
  • Continent Code
    EU
  • Latitude
    54.35
  • Longitude
    18.6667
  • No whois ip data for 195.8.99.26

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 24 Errors
  • 18 Warnings
Ratio Text/Html
  • 0.6144497414892902
Message Error
  • Warning Line 105, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …      <img src="http://www.se.pl/media/images/rss-black.gif" alt="Kanał RSS" />

    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 116, Column 81: NET-enabling start-tag requires SHORTTAG YES
    …     <img src="http://www.se.pl/media/static/logo_se_pl_web.jpg" alt="se.pl" />

    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 128, Column 61: NET-enabling start-tag requires SHORTTAG YES
                <input type="text" class="searchfield" name="q" />

    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 128, Column 61: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
                <input type="text" class="searchfield" name="q" />

    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 128, Column 62: character data is not allowed here
                <input type="text" class="searchfield" name="q" />

    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.
  • Warning Line 129, Column 117: NET-enabling start-tag requires SHORTTAG YES
    …ukaj" class="searchbutton" src="http://www.se.pl/media/static/button_ok.gif" />

    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 129, Column 117: document type does not allow element "INPUT" here; missing one of "P", "H1", "H2", "H3", "H4", "H5", "H6", "PRE", "DIV", "ADDRESS" start-tag
    …ukaj" class="searchbutton" src="http://www.se.pl/media/static/button_ok.gif" />

    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 130, Column 19: end tag for "FORM" which is not finished
                </form>

    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 135, Column 62: cannot generate system identifier for general entity "catalogID"
    …/sklep.murator.pl/index.php?p=catalog&catalogID=148&utm_source=se&utm_medium=b…

    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 135, Column 62: general entity "catalogID" not defined and no default entity
    …/sklep.murator.pl/index.php?p=catalog&catalogID=148&utm_source=se&utm_medium=b…

    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.

  • Error Line 135, Column 71: reference to entity "catalogID" for which no system identifier could be generated
    …rator.pl/index.php?p=catalog&catalogID=148&utm_source=se&utm_medium=button&utm…

    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 135, Column 61: entity was defined here
    …//sklep.murator.pl/index.php?p=catalog&catalogID=148&utm_source=se&utm_medium=…
  • Warning Line 135, Column 76: cannot generate system identifier for general entity "utm_source"
    ….pl/index.php?p=catalog&catalogID=148&utm_source=se&utm_medium=button&utm_camp…

    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 135, Column 76: general entity "utm_source" not defined and no default entity
    ….pl/index.php?p=catalog&catalogID=148&utm_source=se&utm_medium=button&utm_camp…

    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.

  • Error Line 135, Column 86: reference to entity "utm_source" for which no system identifier could be generated
    …php?p=catalog&catalogID=148&utm_source=se&utm_medium=button&utm_campaign=sklep…

    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 135, Column 75: entity was defined here
    …r.pl/index.php?p=catalog&catalogID=148&utm_source=se&utm_medium=button&utm_cam…
  • Warning Line 135, Column 90: cannot generate system identifier for general entity "utm_medium"
    …p=catalog&catalogID=148&utm_source=se&utm_medium=button&utm_campaign=sklep_onl…

    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 135, Column 90: general entity "utm_medium" not defined and no default entity
    …p=catalog&catalogID=148&utm_source=se&utm_medium=button&utm_campaign=sklep_onl…

    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.

  • Error Line 135, Column 100: reference to entity "utm_medium" for which no system identifier could be generated
    …catalogID=148&utm_source=se&utm_medium=button&utm_campaign=sklep_online" title…

    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 135, Column 89: entity was defined here
    …?p=catalog&catalogID=148&utm_source=se&utm_medium=button&utm_campaign=sklep_on…
  • Warning Line 135, Column 108: cannot generate system identifier for general entity "utm_campaign"
    …D=148&utm_source=se&utm_medium=button&utm_campaign=sklep_online" title="Sklep …

    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 135, Column 108: general entity "utm_campaign" not defined and no default entity
    …D=148&utm_source=se&utm_medium=button&utm_campaign=sklep_online" title="Sklep …

    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.

  • Error Line 135, Column 120: reference to entity "utm_campaign" for which no system identifier could be generated
    …tm_source=se&utm_medium=button&utm_campaign=sklep_online" title="Sklep online">

    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 135, Column 107: entity was defined here
    …ID=148&utm_source=se&utm_medium=button&utm_campaign=sklep_online" title="Sklep…
  • Warning Line 136, Column 87: NET-enabling start-tag requires SHORTTAG YES
    …img src="http://www.se.pl/media/static/sklep-online.gif" alt="Sklep on line" />

    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 182, Column 77: there is no attribute "TARGET"
    …zkania, domy, działki, garaże" target="_blank" href="http://www.muratornieruch…

    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 193, Column 114: NET-enabling start-tag requires SHORTTAG YES
    …n> <img src="http://se.pl/media/images/gratka_moto.png" alt="moto.gratka.pl" />

    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 201, Column 66: there is no attribute "DATA-TRACKER"
    …/moto.se.pl" rel="start" data-tracker="/breadcrumb/motoryzacja/strona-glowna/"…

    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 998, Column 88: NET-enabling start-tag requires SHORTTAG YES
    …      W ofercie ponad 600 samochodów używanych - osobowych i ciężarowych <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.

  • Warning Line 1010, Column 45: NET-enabling start-tag requires SHORTTAG YES
                    Gdańsk, ul. Odyseusza 20<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 1167, Column 17: document type does not allow element "DIV" here; missing one of "OBJECT", "MAP", "BUTTON" start-tag
                <div>

    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 1346, Column 110: reference to entity "utm_medium" for which no system identifier could be generated
    …/?utm_source=superauto24.pl&utm_medium=footer_link&utm_campaign=sklep_online'"…

    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 135, Column 89: entity was defined here
    …?p=catalog&catalogID=148&utm_source=se&utm_medium=button&utm_campaign=sklep_on…
  • Error Line 1346, Column 135: reference to entity "utm_campaign" for which no system identifier could be generated
    …pl&utm_medium=footer_link&utm_campaign=sklep_online'" title="Sklep on line">Sk…

    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 135, Column 107: entity was defined here
    …ID=148&utm_source=se&utm_medium=button&utm_campaign=sklep_online" title="Sklep…
  • Warning Line 1380, Column 76: NET-enabling start-tag requires SHORTTAG YES
        <img src="http://www.se.pl/media/static/supermed.gif" alt="SuperMedia" />

    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 1454, Column 86: NET-enabling start-tag requires SHORTTAG YES
    …="http://programpartnerski.gratka.pl/zlicz/odslone/?domena=moto.se.pl" alt=""/>

    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.

Visitor Analysis

Daily Visitor
  • 24.500 visits
Daily Visitor

In Page Analysis