Help
RSS
API
Feed
Maltego
Contact
Domain > docs.distilconnector.com
×
Welcome!
Right click nodes and scroll the mouse to navigate the graph.
×
More information on this domain is in
AlienVault OTX
Is this malicious?
Yes
No
DNS Resolutions
Date
IP Address
2019-05-07
143.204.29.21
(
ClassC
)
2019-05-07
143.204.29.40
(
ClassC
)
2019-05-07
143.204.29.89
(
ClassC
)
2024-09-29
45.60.0.60
(
ClassC
)
Port 80
HTTP/1.1 301 Moved PermanentlyServer: CloudFrontDate: Thu, 22 Feb 2024 03:19:59 GMTContent-Type: text/htmlContent-Length: 167Connection: keep-aliveLocation: https://docs.distilconnector.com/X-Cache: R html>head>title>301 Moved Permanently/title>/head>body>center>h1>301 Moved Permanently/h1>/center>hr>center>CloudFront/center>/body>/html>
Port 443
HTTP/1.1 200 OKContent-Type: text/htmlConnection: keep-aliveDate: Thu, 22 Feb 2024 03:20:01 GMTLast-Modified: Tue, 20 Feb 2024 20:08:12 GMTETag: 08545120e3239afc9077081f9e24fd16x-amz-server-side-encry meta charsetutf-8>**Connector Integration Documentation**center>img srcdistil_logo.svg width200/> img srcimperva_logo.svg width200/>/center># Who is this document for?This document is meant for someone aiming to integrate the Connector bot protection service. This could be someone operating a webpage or a CDN who wants to help protect their customers.This should give you a high level overview of how the integration will look.# OverviewA birds-eye view of how to integrate with Connector, with pretty diagrams.## Nomenclature* **Visitor**: A person or bot making a HTTP(S) requests.* **Integration**: A reverse-proxy that sits in front of origin. This is your code!* **Connector**: The Connector servers, run by Distil/Imperva.* **Origin**: The host of the actual content we are protecting from bots.* **Token**: Encrypted data that stores info about a visitor. This is generated by Connector and stored in a cookie on the visitors browser.## OverviewEach `.html` page will need to include a small script tag:```html<script src/obfuscated async></script>```Here `/obfuscated` would be an endpoint of your choice, e.g. `/protection.js` or `/01f04a20015940b2`.This endpoint must be forwarded to the Connector endpoint `/v6/challenge/YOUR-API-KEY_ID/protection.js` or `/v6/challenge/YOUR-API-KEY_ID/01f04a20015940b2`, respectively.The returned challenge script performs an *interrogation* of the visitors browser. This includes fingerprinting it to uniquely identify it, as well as performing some challenges to ensure it is a real browser.The results are `POST`ed to Connector (via the integration) where it is analyzed. Connector returns a token to the visitors which is stored in a cookie. The POST is the reason why any obfuscated path needs to be appended to the Connector challenge path: the javascript needs to be aware of how to communicate with the Connector backend.# Example diagramsIn the following diagrams time flows downwards.## Protecting an endpointHere is an exampl
View on OTX
|
View on ThreatMiner
Please enable JavaScript to view the
comments powered by Disqus.
Data with thanks to
AlienVault OTX
,
VirusTotal
,
Malwr
and
others
. [
Sitemap
]