https://cdn1.affirm.com/js/v2/affirm.js

Category: Financial

Keywords: bank card easy faqs loan make time loans store visit affirm credit refund account payment business customer merchant payments purchase

Third-party domains
0
 
Persistent cookies
0
 
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 0 persistent cookies with average life-time of 0 days and longest 0 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: 2017-03-29T02:01:31.686895+00:00

HTTP status: 5 Sub-resource URL


HTTP security-related headers assessment

Security score
0

Security-related HTTP headers

  • Server: openresty

    Announces web server software and optionally version details.

    Read more...

  • Strict-Transport-Security: max-age=86400

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

  • Link: <https://cdn1.affirm.com>; rel=preconnect; crossorigin

    Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.

    Read more...

  • Link:  <https://cdn1.affirm.com>; rel=preconnect

    Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.

    Read more...

  • Link:  <https://cdn-assets.affirm.com>; rel=preconnect; crossorigin

    Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.

    Read more...

  • Link:  <https://cdn-assets.affirm.com>; rel=preconnect

    Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.

    Read more...

  • Link:  <https://cdnjs.cloudflare.com>; rel=preconnect; crossorigin

    Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.

    Read more...

  • Link:  <https://cdnjs.cloudflare.com>; rel=preconnect

    Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.

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

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