http://babyblog.ru/user/friend

Title: "Вход на сайт – BabyBlog.ru"
Description: ""

Category: Uncategorized

Keywords: c@m 4_lb eh4n fpbc o9ti ]ypg7 y30z@ fepi9z 3o6pcib w^uwnya ln7h2vi7f c@4r2fgek9z x\gz@zxber`13d lnyr8sa_6ahovxb 17ae6fvu7^s7j^ztuk 9tjr5fo2la_t`qhyvw tomz7fm\uwbtvbtzsr j@@85c7viwj_w:j@ycajuaziii@ tuyejubglck5kp4tw6]ko`4bhO`pza?@8qo 7yzhl[lfd366qix@kp:w9f8hqn1l489h]xxfkvj4dk0dpuuwb9kw4fql5\

Third-party domains
6
 
Persistent cookies
15
 
Session cookies
1
 

Third-party domains is the count of organisations allowed by the webmaster to trace your across the site. These cookies may be set for various purposes, like tracking ads displayed on the website, collection of statistics, targeted advertising etc. This website allows 6 other websites to track your activity.

Persistent cookies are the cookies that are preserved through browser shutdowns. This means, even if you close this page today and ever return there in future, the website will know you're a returning visitor. This may be used for "remember me" features, as well as persistent user tracking. These cookies, especially if set by third party organisations, are powerful tool for monitoring your activities across all the websites you visit. This website sets 15 persistent cookies with average life-time of 1092 days and longest 8335 days.

Session cookies are cleared when you close your browser and allow the website to identify user's state — such as logged-in users. They are mostly considered harmless because they cannot be used for long-term user tracking. This site sets 1 session cookies.


Last fetched: 2015-03-07T21:33:49.908325+00:00

HTTP status: 200 200


HTTP security-related headers assessment

Security score
-6

Security-related HTTP headers

  • Access-Control-Allow-Origin: *

    Controls origins (websites) that are allowed to load data from this web service over JavaScript-based APIs as part of Cross-Origin Resource Sharing (CORS) standard. By default, a web browser will refuse to load data over XmlHttpRequest from a website that is not in the same origin, which is a precaution against various types of data stealing attacks. The target server has to explicitly allow the origin domain using the Access-Control-Allow-Origin (ACAO) header, or it may allow all origins to access it using a wildcard *. The latter however creates a potential security issue if the website in question is transactional and processing sensitive data, so the wildcard should be only used on websites consciously offering public APIs.

    Read more...

  • Server: QRATOR

    Announces web server software and optionally version details.

    Read more...

Fully automated RESTful API is now available. Subscribe for your free trial today!