eDarling.pl: Znajdź partnera, który naprawdę do Ciebie pasuje. Profesjonalny portal randkowy ✓ Naukowo opracowany test psychologiczny ✓ Darmowa rejestracja✓Randki w całej Polsce✓ ...

edarling.pl
  • Domain Name
    edarling.pl
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #28479
  • Page Size
    28.1 KB
  • Ip Address
    195.71.92.224
  • Heading
    H1: 1, H2: 6, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 1 JPG, 1 PNG

Website Meta Analysis

  • Title
    Więcej niż portal randkowy – randki z singlami z całej Polski na eDarling
  • Meta Keyword
    Szukanie partnera, Ofety matrymonialne, eDarling, Darling, Single, Znajdź partnera, Gratis, iDarling, e-Darling, darmowe, single
  • Meta Description
    eDarling.pl: Znajdź partnera, który naprawdę do Ciebie pasuje. Profesjonalny portal randkowy ✓ Naukowo opracowany test psychologiczny ✓ Darmowa rejestracja✓Randki w całej Polsce✓

Technical Analysis

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

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

HTML Analysis

  • date: Sun, 18 Aug 2013 10:15:28 GMT
  • server: Apache
  • retry-after: 18000
  • vary: Host,Accept-Encoding
  • 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
  • marvin: RW_2_0_P0_T7
  • last-modified: Thu, 08 Aug 2013 14:51:20 CEST
  • content-encoding: gzip
  • x-server: http5
  • p3p: policyref="http://www.edarling.pl/w3c/p3p.xml", CP="NOI NID ADMa DEVa PSAa OUR BUS ONL UNI COM STA OTC"
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for edarling.pl

DNS Analysis


DNS servers
ns1.affinitas.de [91.102.12.82]
ns3.affinitas.de [78.46.20.68]
ns4.affinitas.de [195.71.68.16]
ns2.affinitas.de [85.214.144.104]
ns5.affinitas-corp.com [188.40.108.76]


DNS Records

Answer records
edarling.pl SOA
server: www.edarling.pl
email: root@edarling.pl
serial: 2012102601
refresh: 7200
retry: 900
expire: 604800
minimum ttl: 600
28800s
edarling.pl NS  ns1.affinitas.de 28800s
edarling.pl NS  ns3.affinitas.de 28800s
edarling.pl NS  ns2.affinitas.de 28800s
edarling.pl NS  ns5.affinitas-corp.com 28800s
edarling.pl NS  ns4.affinitas.de 28800s
edarling.pl A 195.71.92.224 28800s
edarling.pl MX
preference: 10
exchange: mail.affinitas.de
28800s
edarling.pl MX
preference: 20
exchange: mail.affinitas-corp.com
28800s
edarling.pl TXT yandex-verification: 6891d1524da9fdea 28800s
edarling.pl TXT v=spf1 mx include:support.zendesk.com ?all 28800s
edarling.pl TXT google-site-verification=Vt4QaYDCCx6UiCZDEFRRZhntqJeAEl1Bypane4jvreE 28800s

Authority records

Additional records
ns1.affinitas.de A 91.102.12.82 3600s
ns2.affinitas.de A 85.214.144.104 3600s
ns3.affinitas.de A 78.46.20.68 3600s
ns4.affinitas.de A 195.71.68.16 3600s

IP 195.71.92.224 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    Berlin
  • Continent Code
    EU
  • Latitude
    52.5167
  • Longitude
    13.4.
  • No whois ip data for 195.71.92.224

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 13 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.4985908632267493
Message Error
  • Error Line 10, Column 17: there is no attribute "property"
    	<meta property="og:title" content="Więcej niż portal randkowy - single z całej…

    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 489, Column 93: cannot generate system identifier for general entity "t"
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>

    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 489, Column 93: general entity "t" not defined and no default entity
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>

    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 489, Column 94: reference not terminated by REFC delimiter
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>

    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 489, Column 94: reference to external entity in attribute value
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>

    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 489, Column 94: reference to entity "t" for which no system identifier could be generated
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>

    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 489, Column 92: entity was defined here
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>
  • Warning Line 489, Column 99: cannot generate system identifier for general entity "k"
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>

    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 489, Column 99: general entity "k" not defined and no default entity
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>

    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 489, Column 100: reference not terminated by REFC delimiter
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>

    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 489, Column 100: reference to external entity in attribute value
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>

    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 489, Column 100: reference to entity "k" for which no system identifier could be generated
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>

    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 489, Column 98: entity was defined here
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>
  • Error Line 489, Column 124: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    ….gif?h=2495f11698049a6ce4310aa123233d55&t=DTI&k=" alt="" class="tool" /></body>

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

Visitor Analysis

Daily Visitor
  • 7.467 visits