http://ib.adnxs.com/bounce?%2Fseg%3Ft%3D2%26add%3D1979119=

Title: "u.php (1x1 pixels)"

Category: Engineering

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

Third-party domains
0
 
Persistent cookies
2
 
Session cookies
0
 

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 0 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 2 persistent cookies with average life-time of 47 days and longest 92 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 0 session cookies.


Last fetched: 2016-06-02T17:16:40.880518+00:00

HTTP status: 200 200


Cookies and Privacy Attributes

AppNexus advertising tracking cookie

» More...
  • Type: HTTP Cookie
  • Domain: adnxs.com
  • This cookie expires in 3 days
  • httpOnly This cookie is not readable by client-side JavaScript code » More...
  • Sample value:
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
                        
anj

AppNexus advertising tracking cookie

» More...
  • Type: HTTP Cookie
  • Domain: adnxs.com
  • This cookie expires in 92 days
  • httpOnly This cookie is not readable by client-side JavaScript code » More...
  • Sample value:
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
                        

TLS/SSL configuration report

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

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

HTTP security-related headers assessment

Security score
-1
crossdomain.xml

This file defines the cross-domain policy for Adobe applications. Dangerous if permissive or too broadly set » More...

<?xml version="1.0"?><!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd"><cross-domain-policy><site-control permitted-cross-domain-policies="master-only" /><allow-access-from domain="*" secure="false"/></cross-domain-policy>

Read here to see how this can be abused.

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

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

  • Strict-Transport-Security: max-age=15552000; 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...

  • Public-Key-Pins-Report-Only: max-age=500; pin-sha256="WoiWRyIOVNa9ihaBciRSC7XHjliYS9VwUGOIud4PB18="; pin-sha256="r/mIkG3eEpVdm+u/ko/cwxzOMo1bk4TyHIlByibiA5E="; pin-sha256="q4PO2G2cbkZhZ82+JgmRUyGMoAeozA+BSXVXQWB8XWQ="; report-uri="http://reports.fb.com/hpkp/"

    Announces a list of X.509 certificate hashes that are allowed to appear in the website's TLS certification path (HTTP Public Key Pinning or HPKP). This prevents malicious proxy servers from transparently replacing the public certificates with their own and wiretapping the TLS connection of the unsuspecting user. This header sets HPKP in report-only mode.

    Read more...

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