Store all your favourite links in one place, accessible from anywhere. share your bookmarks with everyone, with friends on your watchlist or just keep them private. tag your bookmarks with as many labels ...

qiel.com
  • Domain Name
    qiel.com
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #27400
  • Page Size
    20.6 KB
  • Ip Address
    108.162.199.164
  • Heading
    H1: 1, H2: 8, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    3 GIF, 0 JPG, 2 PNG

Website Meta Analysis

  • Title
    qiel.com - social bookmarking - store, share and tag your favorite links
  • Meta Keyword
    News,Stories,Articles,Vote,Publish,Social,Networking,Groups,Submit,Upcoming,Comments,Tags,Live
  • Meta Description
    Store all your favourite links in one place, accessible from anywhere. share your bookmarks with everyone, with friends on your watchlist or just keep them private. tag your bookmarks with as many labels as you want, instead of wrestling with folders.

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.199.164
  • Domain Age
    7 Years, 1 Months, 5 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from qiel.com.

HTML Analysis

  • server: cloudflare-nginx
  • date: Tue, 05 Feb 2013 04:10:15 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.1.6
  • 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
  • cf-ray: 3bd3e13a6500455
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for qiel.com

DNS Analysis


DNS servers
pete.ns.cloudflare.com [173.245.59.136]
mary.ns.cloudflare.com [173.245.58.134]


DNS Records

Answer records
qiel.com A 108.162.198.164 300s
qiel.com TXT v=spf1 a mx a:qiel.com ip4:108.174.51.21 ?all 300s
qiel.com SOA
server: mary.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2013012217
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s
qiel.com NS  mary.ns.cloudflare.com 86400s
qiel.com MX
preference: 5
exchange: mail.qiel.com
300s
qiel.com NS  pete.ns.cloudflare.com 86400s
qiel.com A 108.162.199.164 300s

Authority records

Additional records

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 17 Errors
  • 8 Warnings
Ratio Text/Html
  • 0.7228949858088931
Message Error
  • Warning Line 51, Column 1: character "<" is the first character of a delimiter but occurred as data
    <!-ND T- Ewitter -->

    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 51, Column 1: character data is not allowed here
    <!-ND T- Ewitter -->

    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 84, Column 15: there is no attribute "SRC"
      <SCRIPT SRC="http://ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javas…

    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 84, Column 51: cannot generate system identifier for general entity "size"
    …C="http://ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javascript"></SC…

    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 84, Column 51: general entity "size" not defined and no default entity
    …C="http://ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javascript"></SC…

    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 84, Column 55: reference not terminated by REFC delimiter
    …ttp://ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javascript"></SCRIPT…

    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 84, Column 55: reference to external entity in attribute value
    …ttp://ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javascript"></SCRIPT…

    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 84, Column 55: reference to entity "size" for which no system identifier could be generated
    …ttp://ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javascript"></SCRIPT…

    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 84, Column 50: entity was defined here
    …RC="http://ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javascript"></S…
  • Error Line 84, Column 69: there is no attribute "TYPE"
    …ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javascript"></SCRIPT>  <br>

    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 84, Column 86: element "SCRIPT" undefined
    …ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javascript"></SCRIPT>  <br>

    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 84, Column 102: end tag for "br" omitted, but OMITTAG NO was specified
    …ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javascript"></SCRIPT>  <br>

    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 84, Column 98: start tag was here
    …ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javascript"></SCRIPT>  <br>
  • Warning Line 412, Column 55: reference not terminated by REFC delimiter
    …ttp://ib.adnxs.com/ttj?id=1147402&size=300x250" TYPE="text/javascript"></SCRIP…

    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 412, Column 55: reference to external entity in attribute value
    …ttp://ib.adnxs.com/ttj?id=1147402&size=300x250" TYPE="text/javascript"></SCRIP…

    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 412, Column 55: reference to entity "size" for which no system identifier could be generated
    …ttp://ib.adnxs.com/ttj?id=1147402&size=300x250" TYPE="text/javascript"></SCRIP…

    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 84, Column 50: entity was defined here
    …RC="http://ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javascript"></S…
  • Error Line 412, Column 87: element "SCRIPT" undefined
    …://ib.adnxs.com/ttj?id=1147402&size=300x250" TYPE="text/javascript"></SCRIPT>  

    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 414, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 414, Column 1: start tag was here
    <br>
  • Error Line 415, Column 214: end tag for "img" omitted, but OMITTAG NO was specified
    …t="Postolia.com" height="125" width="125" border="0" hspace="0" vspace="0"></a>

    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 415, Column 52: start tag was here
    …://www.postolia.com/" target="_blank"><img src="http://www.qiel.com/templates/…
  • Error Line 416, Column 212: end tag for "img" omitted, but OMITTAG NO was specified
    …ain Acquisition" height="125" width="125" border="0" hspace="0" vspace="0"></a>

    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 416, Column 48: start tag was here
    …http://www.cvul.com/" target="_blank"><img src="http://www.qiel.com/templates/…
  • Error Line 417, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 417, Column 1: start tag was here
    <br>
  • Error Line 418, Column 67: end tag for "br" omitted, but OMITTAG NO was specified
    <a href="http://www.pxaa.com/" target="_blank">Fresh Proxy</a><br>

    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 418, Column 63: start tag was here
    <a href="http://www.pxaa.com/" target="_blank">Fresh Proxy</a><br>
  • Error Line 420, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 420, Column 1: start tag was here
    <br>
  • Warning Line 474, Column 55: reference not terminated by REFC delimiter
    …ttp://ib.adnxs.com/ttj?id=1147402&size=160x600" TYPE="text/javascript"></SCRIP…

    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 474, Column 55: reference to external entity in attribute value
    …ttp://ib.adnxs.com/ttj?id=1147402&size=160x600" TYPE="text/javascript"></SCRIP…

    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 474, Column 55: reference to entity "size" for which no system identifier could be generated
    …ttp://ib.adnxs.com/ttj?id=1147402&size=160x600" TYPE="text/javascript"></SCRIP…

    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 84, Column 50: entity was defined here
    …RC="http://ib.adnxs.com/ttj?id=1147402&size=468x60" TYPE="text/javascript"></S…
  • Error Line 474, Column 87: element "SCRIPT" undefined
    …://ib.adnxs.com/ttj?id=1147402&size=160x600" TYPE="text/javascript"></SCRIPT>  

    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
  • 7.817 visits
Daily Visitor