Blekko | One of the Top Spam and Virus Free Search Engine for Latest Updates on News, Gossips, Date and Much More ...

blekko.com
  • Domain Name
    blekko.com
  • Favicon
  • Google Page Rank
    7
  • Alexa Rank
    #1097
  • Page Size
    12.8 KB
  • Ip Address
    199.87.249.95
  • Heading
    H1: 2, H2: 1, H3: 0, H4: 1, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    blekko | spam-free search
  • Meta Keyword
    Blekko Search Engine, Blekko Search Bar, Spam Free Search Engine, New Search Engine Blekko, Best Search Engine, Top Search Engine, Virus Free Search Engine
  • Meta Description
    Blekko | One of the Top Spam and Virus Free Search Engine for Latest Updates on News, Gossips, Date and Much More

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    199.87.249.95
  • Domain Age
    14 Years, 9 Months, 29 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Thu, 28 Feb 2013 13:03:16 GMT
  • content-type: text/html; charset=UTF-8
  • content-length: 3924
  • connection: keep-alive
  • cache-control: no-cache, max-age=0
  • expires: -1
  • pragma: no-cache
  • x-pt: 0ae9d86708b65896ec494ff2ec884994
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Blekko, Inc.
100 Marine Parkway
Suite 275
Redwood City, CA 94065
US

Registrar: DOMAIN
Domain Name: BLEKKO.COM
Created on: 19-MAY-98
Expires on: 18-MAY-18
Last Updated on: 19-FEB-12

Administrative, Technical Contact:
, email
Blekko, Inc.
100 Marine Parkway
Suite 275
Redwood City, CA 94065
US
6506313845
6506315859

Domain servers in listed order:
NS0.BLEKKO.COM
NS2.BLEKKO.COM
NS0.SVCOLO.COM

DNS Analysis


DNS servers
ns0.svcolo.com [64.13.135.17]
ns2.blekko.com [64.13.147.29]
ns0.blekko.com [199.87.249.21]

DNS Records

Answer records
blekko.com MX
preference: 1
exchange: ASPMX.L.GOOGLE.com
3600s
blekko.com MX
preference: 5
exchange: ALT1.ASPMX.L.GOOGLE.com
3600s
blekko.com MX
preference: 5
exchange: ALT2.ASPMX.L.GOOGLE.com
3600s
blekko.com MX
preference: 10
exchange: ASPMX2.GOOGLEMAIL.com
3600s
blekko.com MX
preference: 10
exchange: ASPMX3.GOOGLEMAIL.com
3600s
blekko.com MX
preference: 10
exchange: ASPMX4.GOOGLEMAIL.com
3600s
blekko.com MX
preference: 10
exchange: ASPMX5.GOOGLEMAIL.com
3600s
blekko.com A 199.87.249.95 3600s
blekko.com A 199.87.249.94 3600s
blekko.com NS  ns0.svcolo.com 3600s
blekko.com NS  ns2.blekko.com 3600s
blekko.com NS  ns0.blekko.com 3600s
blekko.com SOA
server: ns0.blekko.com
email: hostmaster@blekko.com
serial: 2012121800
refresh: 3600
retry: 1800
expire: 2592000
minimum ttl: 900
3600s
blekko.com TXT google-site-verification=wcIZpYY4VeTXWquWFBv7Qfqc1ENP52jWB7yKSjRf-og 3600s

Authority records

Additional records
ns0.blekko.com A 199.87.249.21 3600s
ns2.blekko.com A 64.13.147.29 3600s

IP 199.87.249.95 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 199.87.249.95

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 21 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.6810897435897436
Message Error
  • Error Line 10, Column 101: end tag for "meta" omitted, but OMITTAG NO was specified
    …ntent="Blekko | Spam-Free Search Engine for News, Gossips, Date and Much More">

    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 10, Column 1: start tag was here
    <meta name="title" content="Blekko | Spam-Free Search Engine for News, Gossips,…
  • Error Line 11, Column 150: end tag for "meta" omitted, but OMITTAG NO was specified
    …us Free Search Engine for Latest Updates on News, Gossips, Date and Much More">

    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 11, Column 1: start tag was here
    <meta name="description" content="Blekko | One of the Top Spam and Virus Free S…
  • Error Line 12, Column 189: end tag for "meta" omitted, but OMITTAG NO was specified
    …ngine Blekko, Best Search Engine, Top Search Engine, Virus Free Search Engine">

    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 12, Column 1: start tag was here
    <meta name="keywords" content="Blekko Search Engine, Blekko Search Bar, Spam Fr…
  • Error Line 67, Column 16: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    <input checked name="tag_httpspreferred" id="tag_httpspreferred" class="switchC…

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Warning Line 91, Column 29: cannot generate system identifier for general entity "id"
    <a href="/webgrep?page=view&id=263ad4f7e59e908bed37d34df431f8d3" class="white u…

    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 91, Column 29: general entity "id" not defined and no default entity
    <a href="/webgrep?page=view&id=263ad4f7e59e908bed37d34df431f8d3" class="white u…

    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 91, Column 31: reference not terminated by REFC delimiter
    <a href="/webgrep?page=view&id=263ad4f7e59e908bed37d34df431f8d3" class="white u…

    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 91, Column 31: reference to external entity in attribute value
    <a href="/webgrep?page=view&id=263ad4f7e59e908bed37d34df431f8d3" class="white u…

    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 91, Column 31: reference to entity "id" for which no system identifier could be generated
    <a href="/webgrep?page=view&id=263ad4f7e59e908bed37d34df431f8d3" class="white u…

    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 91, Column 28: entity was defined here
    <a href="/webgrep?page=view&id=263ad4f7e59e908bed37d34df431f8d3" class="white u…
  • Warning Line 92, Column 31: reference not terminated by REFC delimiter
    <a href="/webgrep?page=view&id=00048f58529b2086bdcd703e1116a2f6" class="white u…

    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 92, Column 31: reference to external entity in attribute value
    <a href="/webgrep?page=view&id=00048f58529b2086bdcd703e1116a2f6" class="white u…

    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 92, Column 31: reference to entity "id" for which no system identifier could be generated
    <a href="/webgrep?page=view&id=00048f58529b2086bdcd703e1116a2f6" class="white u…

    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 91, Column 28: entity was defined here
    <a href="/webgrep?page=view&id=263ad4f7e59e908bed37d34df431f8d3" class="white u…
  • Error Line 102, Column 33: there is no attribute "autofocus"
    <input id="searchBox" autofocus="autofocus" autocomplete="off" type="text" spel…

    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 102, Column 58: there is no attribute "autocomplete"
    …x" autofocus="autofocus" autocomplete="off" type="text" spellcheck="false" nam…

    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 102, Column 87: there is no attribute "spellcheck"
    …ocus="autofocus" autocomplete="off" type="text" spellcheck="false" name="q"  />

    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 103, Column 48: there is no attribute "href"
    …ype="submit" class="red-button"  href="javascript:void(0);" id="search-submit"…

    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 115, Column 16: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p class="grey">Take search for a joy ride with <span class="iblock" id="izik-s…

    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 20: there is no attribute "v"
    <fb:login-button v="2" size="small" scope="offline_access,user_likes,user_locat…

    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 128, Column 29: there is no attribute "size"
    <fb:login-button v="2" size="small" scope="offline_access,user_likes,user_locat…

    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 128, Column 43: there is no attribute "scope"
    …login-button v="2" size="small" scope="offline_access,user_likes,user_location…

    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 128, Column 170: there is no attribute "onlogin"
    …_location,user_checkins,friends_checkins,publish_stream" onlogin="fb_login();">

    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 128, Column 183: element "fb:login-button" undefined
    …_location,user_checkins,friends_checkins,publish_stream" onlogin="fb_login();">

    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 129, Column 16: there is no attribute "title"
    <fb:intl title="connect your facebook account with your blekko account">connect…

    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 129, Column 72: element "fb:intl" undefined
    …your facebook account with your blekko account">connect with facebook</fb:intl>

    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).
  • Warning Line 209, Column 48: cannot generate system identifier for general entity "uid"
    …t = response.authResponse.accessToken + '&uid=' + response.authResponse.userID;

    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 209, Column 48: general entity "uid" not defined and no default entity
    …t = response.authResponse.accessToken + '&uid=' + response.authResponse.userID;

    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 209, Column 51: reference not terminated by REFC delimiter
    …t = response.authResponse.accessToken + '&uid=' + response.authResponse.userID;

    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.

  • Error Line 209, Column 51: reference to entity "uid" for which no system identifier could be generated
    …t = response.authResponse.accessToken + '&uid=' + response.authResponse.userID;

    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 209, Column 47: entity was defined here
    …t = response.authResponse.accessToken + '&uid=' + response.authResponse.userID;

Visitor Analysis

Daily Visitor
  • 161.000 visits
Daily Visitor