krs-online.com.pl

Odnalezienie danych na temat organizacji i firm, zweryfikowanie informacji o kontrahencie nigdy nie było tak proste. Krajowy Rejestr Sądowy to dostęp do każdej z nich. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 01-02-2013 12:41:15  (update).

Overview Info

  • Domain Name
    krs-online.com.pl
  • Favicon
  • Alexa Rank
    #20347
  • Google Page Rank
    PR 5
  • Ip Address
    86.111.247.226
  • Page Size
    10.1 KB
  • Images
    0 GIF, 0 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 0 0 0 0

Website Meta Analysis



  • Title
    KRS online - Krajowy Rejestr Sądowy - darmowa wyszukiwarka podmiotów w KRS
  • Meta Keyword
    KRS, KRS online, Krajowy Rejestr Sądowy, wyszukiwarka, firmy, informacje o firmach, kontrahenci, podmioty prawne, formularze
  • Meta Description
    Odnalezienie danych na temat organizacji i firm, zweryfikowanie informacji o kontrahencie nigdy nie było tak proste. Krajowy Rejestr Sądowy to dostęp do każdej z nich.

Technical Analysis



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

Hyper Text Transfer Protocol (HTTP) header show data header response from krs-online.com.pl.

HTML Analysis

  • date: Fri, 01 Feb 2013 00:41:16 GMT
  • server: Apache
  • x-powered-by: PHP/5.2.6-1+lenny9
  • 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-length: 3552
  • content-type: text/html; charset=iso-8859-2
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for krs-online.com.pl

DNS Analysis


DNS servers
dns.home.pl [62.129.252.30]
dns3.home.pl [95.211.105.225]
dns2.home.pl [62.129.252.40]


DNS Records

Answer records
krs-online.com.pl NS  dns.home.pl 86400s
krs-online.com.pl NS  dns2.home.pl 86400s
krs-online.com.pl MX
preference: 10
exchange: sunrisesystem.home.pl
3600s
krs-online.com.pl SOA
server: dns.home.pl
email: admin@home.pl
serial: 1333122440
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
86400s
krs-online.com.pl NS  dns3.home.pl 86400s
krs-online.com.pl A 86.111.247.226 3600s

Authority records

Additional records
dns.home.pl A 62.129.252.31 3600s
dns3.home.pl A 95.211.105.225 3600s
dns2.home.pl A 62.129.252.40 3600s
dns2.home.pl A 62.129.252.41 3600s
sunrisesystem.home.pl A 79.96.5.15 3600s
dns.home.pl A 62.129.252.30 3600s

IP 86.111.247.226 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 9 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.5155568479209072
Message Error
  • Error Line 23, Column 51: an attribute value must be a literal unless it contains only name characters
    …dsfehb(z1,z2){document.write('<a href=\"mailto:'+z1+'@'+z2+'\" rel=\"nofollow\…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 23, Column 80: an attribute value must be a literal unless it contains only name characters
    …write('<a href=\"mailto:'+z1+'@'+z2+'\" rel=\"nofollow\">'+z1+'@'+z2+'<\/a>');}

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 23, Column 80: character "\" is not allowed in the value of attribute "rel"
    …write('<a href=\"mailto:'+z1+'@'+z2+'\" rel=\"nofollow\">'+z1+'@'+z2+'<\/a>');}

    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 23, Column 92: document type does not allow element "a" here
    …write('<a href=\"mailto:'+z1+'@'+z2+'\" rel=\"nofollow\">'+z1+'@'+z2+'<\/a>');}

    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).

  • Warning Line 23, Column 106: character "<" is the first character of a delimiter but occurred as data
    …write('<a href=\"mailto:'+z1+'@'+z2+'\" rel=\"nofollow\">'+z1+'@'+z2+'<\/a>');}

    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 24, Column 9: end tag for "a" omitted, but OMITTAG NO was specified
    </script>

    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 23, Column 43: start tag was here
    …nction cdsfehb(z1,z2){document.write('<a href=\"mailto:'+z1+'@'+z2+'\" rel=\"n…
  • Error Line 38, Column 8: document type does not allow element "h1" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
        <h1>Krajowy Rejestr Sądowy</h1>

    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 39, Column 8: document type does not allow element "h2" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
        <h2>wyszukiwarka podmiotów w KRS</h2>

    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 97, Column 5: 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.

  • Error Line 116, Column 11: element "g:plusone" undefined
    <g:plusone></g:plusone>

    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).

Visitor Analysis

Daily Visitor
  • 11.900 visits
Daily Visitor

In Page Analysis