http://www.google-analytics.com/collect?v=1&_v=j66&a=814408520&t=pageview&_s=1&dl=http%3A%2F%2Fwww.dispatch.com%2Fbuckeyextracontent%2Fsystem%2Fshared%2Fjavascript%2FgaTrackGTM.js&ul=c&de=UTF-8&dt=404+-+Page+not+found+-+The+Columbus+Dispatch+-+Columbus%2C+OH&sd=32-bit&sr=1024x768&vp=400x300&je=0&_u=IGDAiEQAB%7E&jid=271907550&gjid=1544835652&cid=44754607.1521451179&tid=UA-66081700-2&_gid=649609763.1521451179&cd1=0&cd2=404&cd4=free&cd5=&cd9=404&z=1081208532

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: 2018-03-19T09:20:52.962064+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

TLS score
F
Grade capped at F
Certificate path cannot be verified to a known root certificate

See full SSL/TLS security report for www.google-analytics.com

Security-related HTTP headers

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

  • Server: Golfe2

    Announces web server software and optionally version details.

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

Sub-resources

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