https://translate.google.com/translate_a/element.js?cb=googleTranslateElementInit2

Category: Technology

Keywords: drag drop file link text type google feedback pagedrag translate translator googleprivacy termshelpsend toolkitwebsite business:translator translatecommunitymobileabout burmesenepalinorwegianpashtopersianpolishportuguesepunjabiromanianrussiansamoanscots kurmanjikyrgyzlaolatinlatvianlithuanianluxembourgishmacedonianmalagasymalaymalayalammaltesemaorimarathimongolianmyanmar creolehausahawaiianhebrewhindihmonghungarianicelandicigboindonesianirishitalianjapanesejavanesekannadakazakhkhmerkoreankurdish gaelicserbiansesothoshonasindhisinhalaslovaksloveniansomalispanishsundaneseswahiliswedishtajiktamilteluguthaiturkishukrainianurduuzbekvietnamesewelshxhosayiddishyorubazulu


Last fetched: 2019-01-30T21:24:02.415748+00:00

HTTP status: 4 Connection error fail


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 translate.google.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: HTTP server (unknown)

    Announces web server software and optionally version details.

    Read more...

  • X-XSS-Protection: 0

    Controls an Cross-Site Scripting (XSS) filters built into the majority of web browsers. The filter is usually turned on by default anyway, but requirement to set the header to 1 became part of canonical set of "secure" HTTP headers. Over time, vulnerabilities in the "sanitizing" mode filter were found, so 1; mode=block became the recommended value. Some companies decided that they don't really need a browser-side XSS filter to mess with their web services which are XSS-free anyway and they became consciously disabling the XSS filter by setting the header to 0.

    Read more...

Sub-resources

Sub-resources

Most web pages load a number of sub-resources such as images, style sheets (CSS), JavaScript files, web fonts, audio or video files and other web pages in frames. Each of these sub-resources may be loaded from the same server (first-party resource) or servers belonging to other parties (third-party resources). In the latter case, the third-party will see a request coming from your browser with the information on the originating page and it can set its own cookies, both of which are frequently used for user tracking. Note that the cookies set by these sub-resources are already recorded in our cookie statistics for this page.

Symbols

  • Resource securely loaded over TLS
  • Resource insecurely loaded over plaintext HTTP.
  • Mixed content warning. This resource is loaded over plaintext HTTP on TLS page will be blocked by most modern browser. Read more...
  • A third-party resource. It may perform its own tracking on your requests and receive partial information about your activities on the original website
  • Resource with reputation warnings
  • Blacklisted domain
  • Suspicious pattern detected
Fully automated RESTful API is now available. Subscribe for your free trial today!