Skip to content
28 changes: 18 additions & 10 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -248,7 +248,7 @@ interactsh-client | notify

## Interactsh Web Client

[Interactsh-web](https://github.com/projectdiscovery/interactsh-web) is a free and open-source web client that displays Interactsh interactions in a well-managed dashboard in your browser. It uses the browser's local storage to store and display all incoming interactions. By default, the web client is configured to use **interact.sh** as default interactsh server, and supports other self-hosted public/authencaited interactsh servers as well.
[Interactsh-web](https://github.com/projectdiscovery/interactsh-web) is a free and open-source web client that displays Interactsh interactions in a well-managed dashboard in your browser. It uses the browser's local storage to store and display all incoming interactions. By default, the web client is configured to use **oast.fun** as default interactsh server, and supports other self-hosted public/authencaited interactsh servers as well.

A hosted instance of **interactsh-web** client is available at https://app.interactsh.com

Expand Down Expand Up @@ -277,9 +277,9 @@ $ docker run projectdiscovery/interactsh-client:latest
[INF] c59e3crp82ke7bcnedq0cfjqdpeyyyyyn.oast.pro
```

## Burp Suite Extension
## Burp Suite Original Extension

[interactsh-collaborator](https://github.com/wdahlenburg/interactsh-collaborator) is Burp Suite extension developed and maintained by [@wdahlenb](https://twitter.com/wdahlenb)
[interactsh-collaborator](https://github.com/wdahlenburg/interactsh-collaborator) is an original Burp Suite interactsh extension developed and maintained by [@wdahlenb](https://twitter.com/wdahlenb)

- Download latest JAR file from [releases](https://github.com/wdahlenburg/interactsh-collaborator/releases) page.
- Open Burp Suite → Extender → Add → Java → Select JAR file → Next
Expand All @@ -288,9 +288,20 @@ $ docker run projectdiscovery/interactsh-client:latest

<img width="2032" alt="burp" src="https://user-images.githubusercontent.com/8293321/135176099-0e3fa01c-bdce-4f04-a94f-de0a34c7abf6.png">

## OWASP ZAP Add-On
## Burp Suite Revised Extension

Interactsh can be used with OWASP ZAP via the [OAST add-on for ZAP](https://www.zaproxy.org/docs/desktop/addons/oast-support/). With ZAP's scripting capabilities, you can create powerful out-of-band scan rules that leverage Interactsh's features. A standalone script template has been provided as an example (it is added automatically when you install the add-on).
[interactsh-collaborator-rev](https://github.com/TheArqsz/interactsh-collaborator-rev) is a revised version of the original Burp Suite interactsh extension and is developed and maintained by [@Arqsz](https://arqsz.net/)

- Download latest JAR file from [releases](https://github.com/TheArqsz/interactsh-collaborator-rev/releases) page.
- Open Burp Suite &rarr; Extender &rarr; Add &rarr; Java &rarr; Select JAR file &rarr; Next
- New tab named **Interactsh** will be appeared upon successful installation.
- See the [interactsh-collaborator-rev](https://github.com/TheArqsz/interactsh-collaborator-rev) project for more info.

<img width="2032" alt="burp" src="https://github.com/TheArqsz/interactsh-collaborator-rev/blob/master/assets/interactsh-extension.png?raw=true">

## ZAP Add-On

Interactsh can be used with ZAP via the [OAST add-on for ZAP](https://www.zaproxy.org/docs/desktop/addons/oast-support/). With ZAP's scripting capabilities, you can create powerful out-of-band scan rules that leverage Interactsh's features. A standalone script template has been provided as an example (it is added automatically when you install the add-on).

- Install the OAST add-on from the [ZAP Marketplace](https://www.zaproxy.org/addons/).
- Go to Tools &rarr; Options &rarr; OAST and select **Interactsh**.
Expand All @@ -303,9 +314,6 @@ Interactsh can be used with OWASP ZAP via the [OAST add-on for ZAP](https://www.
![zap](https://user-images.githubusercontent.com/16446369/135211920-ed24ba5a-5547-4cd4-b6d8-656af9592c20.png)
*Interactsh in ZAP*

![Options > OAST > General](https://github.com/hahwul/interactsh/assets/13212227/005bb527-3f60-4822-8b76-f9a3fd06df83)
*`Options` > `OAST` > `General`*

## Caido Extension

[quickssrf](https://github.com/caido-community/quickssrf) is Caido extension developed and maintained which allows using Interactsh from within Caido Proxy.
Expand Down Expand Up @@ -871,8 +879,8 @@ Currently supported metadata services:

Example:

* **aws.interact.sh** points to 169.254.169.254
* **alibaba.interact.sh** points to 100.100.100.200
* **aws.oast.fun** points to 169.254.169.254
* **alibaba.oast.fun** points to 100.100.100.200

-----

Expand Down
97 changes: 91 additions & 6 deletions cmd/interactsh-server/example-custom-records.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,93 @@
# This is a reference custom DNS records file
#
# Custom DNS records can be specified in two formats:
#
# 1. Standard format (supports multiple record types):
# subdomain:
# - type: RECORD_TYPE
# value: "record_value"
# ttl: 3600 # optional, defaults to server TTL
# priority: 10 # optional, for MX records only
#
# 2. LEGACY FORMAT (Simple key-value, assumes A records):
# subdomain: "ip_address"
#
# Supported record types: A, AAAA, CNAME, MX, TXT, NS

# The default custom records can be specified using this YAML
# file using the below declaration.
aws: "169.254.169.254"
alibaba: "100.100.100.200"
localhost: "127.0.0.1"
oracle: "192.0.0.192"
# ============================================
# STANDARD FORMAT EXAMPLES
# ============================================

# A record example
api:
- type: A
value: "192.0.2.1"
ttl: 3600

# Multiple A records for the same subdomain
webserver:
- type: A
value: "203.0.113.10"
- type: A
value: "203.0.113.11"

# AAAA record (IPv6)
ipv6:
- type: AAAA
value: "2001:db8::1"

# CNAME record
cdn:
- type: CNAME
value: "example.cdn.net"

# MX record (mail server)
mail:
- type: MX
value: "mail.example.com"
priority: 10
ttl: 7200

# Multiple MX records with different priorities
mailserver:
- type: MX
value: "mail1.example.com"
priority: 10
- type: MX
value: "mail2.example.com"
priority: 20

# TXT record (useful for SPF, DKIM, verification, etc.)
spf:
- type: TXT
value: "v=spf1 include:_spf.example.com ~all"

# Multi-level subdomain example (DKIM key)
something._domainkey:
- type: TXT
value: "v=DKIM1; k=rsa; p=MIGfMA0GCS..."

# NS record (nameserver)
custom-ns:
- type: NS
value: "ns1.example.com"
- type: NS
value: "ns2.example.com"

# Mixed record types for the same subdomain
multi:
- type: A
value: "198.51.100.1"
- type: AAAA
value: "2001:db8::2"
- type: TXT
value: "v=spf1 mx ~all"

# ============================================
# LEGACY FORMAT EXAMPLES (backwards compatible)
# ============================================
# These simple entries will be interpreted as A records
# aws: "169.254.169.254"
# alibaba: "100.100.100.200"
# localhost: "127.0.0.1"
# oracle: "192.0.0.192"
Loading
Loading