https://ib.adnxs.com/getuid?https%3A%2F%2Faax-eu.amazon-adsystem.com%2Fs%2Fecm3%3Fid=%24UID&ex=appnexus.com

Category: Engineering

Keywords: ssp tech cloud deals learn careers console request adserver agencies appnexus audience overview products companies extension publisher publishers advertisers capabilities


Last fetched: 2016-04-24T21:15:18.083238+00:00

HTTP status: 4 Connection error error


TLS/SSL configuration report

TLS score
A

See full SSL/TLS security report for ib.adnxs.com

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

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

  • P3P: policyref="http://cdn.adnxs.com/w3c/policy/p3p.xml", CP="NOI DSP COR ADM PSAo PSDo OURo SAMo UNRo OTRo BUS COM NAV DEM STA PRE"

    Largely abandoned format for declaring website's privacy policy in machine-readable format. The only reason for many websites to use the header was that old versions of Microsoft Internet Explorer disallowed third-party cookies on websites missing P3P.

    Read more...

  • Server: nginx/1.13.4

    Announces web server software and optionally version details.

    Read more...

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!