https://stats.g.doubleclick.net/r/collect?v=1&aip=1&t=dc&_r=3&tid=UA-82828806-1&cid=561240773.1562862293&jid=1368316246&_gid=1101334731.1562862293&gjid=513415927&_v=j77&z=499147124

Category: Advertising & Tracking

Keywords: data free learn suite better center google manager surveys audience business optimize partners products analytics companies marketing solutions attribution measurement


Last fetched: 2019-07-11T16:24:57.400147+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

TLS score
C
Grade capped at C
Grade capped due to 64-bit cipher (IDEA, RC2, DES or 3DES)

See full SSL/TLS security report for stats.g.doubleclick.net

Security-related HTTP headers

  • Server: Golfe2

    Announces web server software and optionally version details.

    Read more...

  • X-Content-Type-Options: nosniff

    A non-standard but widely accepted header introduced originally by Microsoft to disable "content sniffing" or heuristic content type discovery in absence or mismatch of a proper HTTP Content-Type declaration, which led to a number of web attacks. In general, presence of the header with its only defined value of nosniff is considered as part of a properly secured HTTP response.

    Read more...

  • Strict-Transport-Security: max-age=10886400; includeSubDomains; preload

    HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header.

    Read more...

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

Pages loading this URL

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