An OOB interaction gathering server and client library

Overview

Interactsh

An OOB interaction gathering server and client library

FeaturesUsageInteractsh ClientInteractsh ServerInteractsh IntegrationJoin Discord


Interactsh is an Open-Source Solution for Out of band Data Extraction, A tool designed to detect bugs that cause external interactions, For example - Blind SQLi, Blind CMDi, SSRF, etc.

Features

  • DNS/HTTP/HTTPS/SMTP Interaction support
  • NTLM/SMB Listener support (self-hosted)
  • Wildcard Interaction support (self-hosted)
  • CLI / Web / Burp / ZAP / Docker client support
  • AES encryption with zero logging
  • SELF Hosted Interactsh server support
  • Automatic ACME based Wildcard TLS w/ Auto Renewal
  • DNS Entries for Cloud Metadata service

Interactsh Client

Interactsh CLI Client

Interactsh Cli client requires go1.17+ to install successfully. Run the following command to get the repo -

go install -v github.com/projectdiscovery/interactsh/cmd/[email protected]

Running Interactsh CLI Client

This will generate a unique payload that can be used for OOB testing with minimal interaction information in the ouput.

interactsh-client

    _       __                       __       __  
   (_)___  / /____  _________ ______/ /______/ /_ 
  / / __ \/ __/ _ \/ ___/ __ '/ ___/ __/ ___/ __ \
 / / / / / /_/  __/ /  / /_/ / /__/ /_(__  ) / / /
/_/_/ /_/\__/\___/_/   \__,_/\___/\__/____/_/ /_/ v0.0.5

        projectdiscovery.io

[INF] Listing 1 payload for OOB Testing
[INF] c23b2la0kl1krjcrdj10cndmnioyyyyyn.interactsh.com

[c23b2la0kl1krjcrdj10cndmnioyyyyyn] Received DNS interaction (A) from 172.253.226.100 at 2021-26-26 12:26
[c23b2la0kl1krjcrdj10cndmnioyyyyyn] Received DNS interaction (AAAA) from 32.3.34.129 at 2021-26-26 12:26
[c23b2la0kl1krjcrdj10cndmnioyyyyyn] Received HTTP interaction from 43.22.22.50 at 2021-26-26 12:26
[c23b2la0kl1krjcrdj10cndmnioyyyyyn] Received DNS interaction (MX) from 43.3.192.3 at 2021-26-26 12:26
[c23b2la0kl1krjcrdj10cndmnioyyyyyn] Received DNS interaction (TXT) from 74.32.183.135 at 2021-26-26 12:26
[c23b2la0kl1krjcrdj10cndmnioyyyyyn] Received SMTP interaction from 32.85.166.50 at 2021-26-26 12:26

Running the Interactsh client in verbose mode (v) to see the whole request and response, along with an output file to analyze afterwards.

interactsh-client -v -o interactsh-logs.txt

    _       __                       __       __  
   (_)___  / /____  _________ ______/ /______/ /_ 
  / / __ \/ __/ _ \/ ___/ __ '/ ___/ __/ ___/ __ \
 / / / / / /_/  __/ /  / /_/ / /__/ /_(__  ) / / /
/_/_/ /_/\__/\___/_/   \__,_/\___/\__/____/_/ /_/ v0.0.5

    projectdiscovery.io

[INF] Listing 1 payload for OOB Testing
[INF] c58bduhe008dovpvhvugcfemp9yyyyyyn.interactsh.com

[c58bduhe008dovpvhvugcfemp9yyyyyyn] Received HTTP interaction from 103.22.142.211 at 2021-09-26 18:08:07
------------
HTTP Request
------------

GET /favicon.ico HTTP/2.0
Host: c58bduhe008dovpvhvugcfemp9yyyyyyn.interactsh.com
Accept: image/avif,image/webp,image/apng,image/svg+xml,image/*,*/*;q=0.8
Accept-Encoding: gzip, deflate, br
Accept-Language: en-IN,en;q=0.9
Cookie: _ga=GA1.2.440163205.1619796009; _iub_cs-77854424=%7B%22timestamp%22%3A%222021-04-30T15%3A23%3A23.192Z%22%2C%22version%22%3A%221.30.2%22%2C%22consent%22%3Atrue%2C%22id%22%3A77854424%7D
Referer: https://c58bduhe008dovpvhvugcfemp9yyyyyyn.interactsh.com/
Sec-Ch-Ua: "Google Chrome";v="93", " Not;A Brand";v="99", "Chromium";v="93"
Sec-Ch-Ua-Mobile: ?0
Sec-Ch-Ua-Platform: "macOS"
Sec-Fetch-Dest: image
Sec-Fetch-Mode: no-cors
Sec-Fetch-Site: same-origin
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.82 Safari/537.36



-------------
HTTP Response
-------------

HTTP/1.1 200 OK
Connection: close
Content-Type: text/html; charset=utf-8
Server: interactsh.com

<html><head></head><body>nyyyyyy9pmefcguvhvpvod800ehudb85c</body></html>

Using the server flag, Interactsh client can be configured to connect with a self-hosted interactsh server.

interactsh-client -server hackwithautomation.com

Using the token flag, Interactsh client can connect to a self-hosted interactsh server that is protected with authentication.

interactsh-client -server hackwithautomation.com -token XXX

If you are away from your terminal, you may use notify to send a real-time interaction notification to any supported platform.

interactsh-client | notify

image

Usage

interactsh-client -h

This will display help for the tool. Here are all the switches it supports.

Flag Description Example
n Interactsh payload count to generate (default 1) interactsh-client -n 2
poll-interval Interaction poll interval in seconds (default 5) interactsh-client -poll-interval 1
server Interactsh server to use interactsh-client -server https://domain.com
dns-only Display only DNS interaction in CLI output interactsh-client -dns-only
http-only Display only HTTP interaction in CLI output interactsh-client -http-only
smtp-only Display only SMTP interaction in CLI output interactsh-client -smtp-only
json Write output in JSONL(ines) format interactsh-client -json
token Authentication token to connect interactsh server interactsh-client -token XXX
persist Enables persistent interactsh sessions interactsh-client -persist
o Output file to write interaction interactsh-client -o logs.txt
v Show verbose interaction interactsh-client -v

Interactsh Web Client

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 - interachsh.com, a cloud-hosted 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

interactsh-web

Interactsh Docker Client

A Docker image is also provided with interactsh client that is ready to run and can be used in the following way:

docker run projectdiscovery/interactsh-client:latest
docker run projectdiscovery/interactsh-client:latest

    _       __                       __       __  
   (_)___  / /____  _________ ______/ /______/ /_ 
  / / __ \/ __/ _ \/ ___/ __ '/ ___/ __/ ___/ __ \
 / / / / / /_/  __/ /  / /_/ / /__/ /_(__  ) / / /
/_/_/ /_/\__/\___/_/   \__,_/\___/\__/____/_/ /_/ v0.0.5

        projectdiscovery.io

[INF] Listing 1 payload for OOB Testing
[INF] c59e3crp82ke7bcnedq0cfjqdpeyyyyyn.interactsh.com

Burp Suite Extension

interactsh-collaborator is Burp Suite extension developed and maintained by @wdahlenb

  • Download latest JAR file from releases page.
  • Open Burp Suite → Extender → Add → Java → Select JAR file → Next
  • New tab named Interactsh will be appeared upon successful installation.
  • See the interactsh-collaborator project for more info.

burp

OWASP ZAP Add-On

Interactsh can be used with OWASP ZAP via the OAST add-on for ZAP. 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.
  • Go to Tools → Options → OAST and select Interactsh.
  • Configure the options for the client and click on "New Payload" to generate a new payload.
  • OOB interactions will appear in the OAST Tab and you can click on any of them to view the full request and response.
  • See the OAST add-on documentation for more info.

zap


Interactsh Server

Interactsh server runs multiple services and captures all the incoming requests. To host an instance of interactsh-server, you are required to have the follow requirements:

  1. Domain name with custom host names and nameservers.
  2. Basic VPS running 24/7 in the background.

We are using GoDaddy for domain name and DigitalOcean droplet for the server, a basic $5 droplet should be sufficient to run self-hosted Interactsh server. If you are not using GoDaddy, follow your registrar's process for creating / updating DNS entries.

Configuring Interactsh domain

  • Navigate to https://dcc.godaddy.com/manage/{{domain}}/dns
  • Advanced Features → Host names → Add → Submit ns1, ns2 with VPS IP as value
gdd-hostname
  • Navigate to https://dns.godaddy.com/{{domain}}/nameservers
  • I'll use my own nameservers → Submit ns1.{{domain}}, ns2.{{domain}}
gdd-ns

Configuring Interactsh server

Install interactsh-server on your remote VPS

go install -v github.com/projectdiscovery/interactsh/cmd/[email protected]

Considering domain name setup is completed, run the below command to run interactsh server

interactsh-server -domain domain.com

Alternatively, you can utilize ready to run docker image of interactsh-server on your remote machine with

docker run projectdiscovery/interactsh-server:latest -domain domain.com

Following is an example of a successful installation and operation of a self-hosted server:

interactsh-server

A number of needed flags are configured automatically to run interactsh server with default settings. For example, the hostmaster flag with a valid email address such as [email protected] and the ip and listen-ip flags with the public IP address of the VPS.

A hosted instance of interactsh-server which is used as default with interactsh-client is available at https://interactsh.com

Usage

interactsh-server -h

This will display help for the tool. Here are all the switches it supports.

Flag Description Example
auth Enable authentication to server using random generated token interactsh-server -auth
token Enable authentication to server using given token interactsh-server -token MY_TOKEN
domain Domain to use for interactsh server interactsh-server -domain domain.com
eviction Number of days to persist interactions for (default 30) interactsh-server -eviction 30
hostmaster Hostmaster email to use for interactsh server interactsh-server -hostmaster [email protected]
ip Public IP Address to use for interactsh server interactsh-server -ip XX.XX.XX.XX
listen-ip Public IP Address to listen on interactsh-server -listen-ip XX.XX.XX.XX
root-tld Enable wildcard/global interaction for *.domain.com interactsh-server -root-tld
origin-url Origin URL to send in ACAO Header interactsh-server -origin-url https://domain.com
responder Start a responder agent - docker must be installed interactsh-server -responder
smb Start a smb agent - impacket and python 3 must be installed interactsh-server -smb
debug Run interactsh in debug mode interactsh-server -debug

There are more useful capabilities supported by Interactsh server that are not enabled by default and are intended to be used only by self-hosted servers. These feature are not available with hosted server at https://interactsh.com

root-tld flag enables wildcard (*.domain.com) interaction support with your self-hosted server and includes implicit authentication protection via the auth flag if the token flag is omitted.

interactsh-server -domain domain.com -root-tld

2021/09/28 12:18:24 Client Token: 4c17895a460123ea439abbad64e0e02c2c7be660464d75299f76e1a972ac4e56
2021/09/28 12:18:24 TLS certificates are not expiring, continue!
2021/09/28 12:18:24 Listening on DNS, SMTP and HTTP ports

Interactsh Integration

Nuclei - OOB Scan

Nuclei vulnerability scanner can also utilize Interactsh for automated payload generation and detection of Out of band based security vulnerabilities.

See Nuclei + Interactsh Integration blog and guide document for more info.

Cloud Metadata

Interactsh server supports DNS records for cloud metadata services, which is useful for testing SSRF-related vulnerabilities.

Currently supported metadata services:

Example:

aws.{interactsh-server} points to 169.254.169.254

aws.interactsh.com points to 169.254.169.254

alibaba.{interactsh-server} points to 100.100.100.200

alibaba.interactsh.com points to 100.100.100.200


Acknowledgement

Interactsh is inspired from Burp Collaborator.

License

Interactsh is distributed under MIT License and made with 🖤 by the projectdiscovery team.

Issues
  • Errors in TXT propagation during SSL certificate update/installation

    Errors in TXT propagation during SSL certificate update/installation

    The certificate update randomly fails due to delays/issues in the TXT record propagation containing the challenge:

    # ./interactsh-server -domain abcd.efg -ip xxx.xxx.xxx.xxx -listen-ip xxx.xxx.xxx.xxx
    2021/12/15 14:24:28 Creating new order for domains: [*.abcd.efg abcd.efg]
    2021/12/15 14:24:28 Order created: https://acme-v02.api.letsencrypt.org/acme/order/123456789/123456789
    2021/12/15 14:24:28 Fetching authorization: https://acme-v02.api.letsencrypt.org/acme/authz-v3/123456789
    2021/12/15 14:24:28 Fetched authorization: abcd.efg
    2021/12/15 14:28:28 Updating challenge for authorization abcd.efg: https://acme-v02.api.letsencrypt.org/acme/chall-v3/123456789/123456789
    2021/12/15 14:28:59 An error occurred while applying for an certificate, error: could not generate new certs: error updating authorization abcd.efg challenge: acme: error code 400 "urn:ietf:params:acme:error:dns": During secondary validation: DNS problem: query timed out looking up TXT for _abcd.efg
    2021/12/15 14:28:59 Could not generate certs for auto TLS, https will be disabled
    2021/12/15 14:28:59 Listening on DNS, SMTP and HTTP ports
    
    
    $ dig abcd.efg txt # from another box
    
    ; <<>> DiG 9.16.1-Ubuntu <<>> hackwithautomation.com txt
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15605
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 65494
    ;; QUESTION SECTION:
    ;abcd.efg.		IN	TXT
    
    ;; ANSWER SECTION:
    abcd.efg.	0	IN	TXT	""
    
    ;; Query time: 8 msec
    ;; SERVER: 127.0.0.53#53(127.0.0.53)
    ;; WHEN: Wed Dec 15 13:32:01 UTC 2021
    ;; MSG SIZE  rcvd: 107
    
    Priority: High Status: Completed Type: Bug 
    opened by Mzack9999 12
  • Can't connect to my custom interactsh server

    Can't connect to my custom interactsh server

    Hi, Following the instructions I set up my own Interactsh server, however after starting it, I can't connect to it with the interactsh client.

    Server running : interactsh

    Attempt to connect with the client : interact2

    curl

    And I think my DNS configuration is good because if I run a custom DNS that I wrote in Ruby, it responds well to queries dns

    Regards

    Type: Bug 
    opened by JoshuaMart 11
  • Connection Refused connecting to private server

    Connection Refused connecting to private server

    Version: 0.0.7 Go version: 1.17.5 linux/amd64 Hello guys, the issue I'm having is trying to connect the client to my server. I execute the command: interactsh-client -server https://example.com

    The server returns:

    [FTL] Could not create client: could not make register request: POST https://example.com/register giving up after 6 attempts: Post "https://example.com/register": dial tcp server_ip
    :443: connect: connection refused
    

    I also tried http://example.com with the same response. And I also tried the web client with custom server pointing to example.com with no success.

    My server is running on an Oracle VM. My domain in registered on Namecheap. I configured it with custom nameservers (ns1 and ns2 both pointing to server_ip, which is the VM's IP). I am running BIND9 on it to act as nameserver. If I enable nginx on my VM I can access it using http://example.com. If I run nslookup ubuntu.com example.com from my Windows PC I get the correct response. I start my server with this command: interactsh-server -domain example.com

    The response I get leads me to believe it is running correctly:

    2021/12/26 21:06:20 Creating new order for domains: [*.example.com example.com]
    2021/12/26 21:06:21 Order created: https://acme-v02.api.letsencrypt.org/acme/orde                                                                                       r/337280xxx/5038xxxxxxx
    2021/12/26 21:06:21 Fetching authorization: https://acme-v02.api.letsencrypt.org/                                                                                       acme/authz-v3/6226815xxxx
    2021/12/26 21:06:21 Fetched authorization: example.com
    2021/12/26 21:06:31 Updating challenge for authorization example.com: https://acme-v02.api.letsencrypt.org/acme/chall-v3/6226815xxxx/Wnqorg
    2021/12/26 21:06:33 Listening on DNS, SMTP and HTTP ports
    

    I tried shutting down my firewall to see if it was interfering in some way with the command sudo iptables -F. I also made sure ports 53, 80 and 443 were open for TCP packets on the VM configuration.

    Even so, I am getting connection refused.

    Type: Question 
    opened by bluesm866 9
  • Not able to run Interachsh -server on Digital Ocean Droplet.

    Not able to run Interachsh -server on Digital Ocean Droplet.

    Hi team,

    I have created a DO Debain Droplet and installed a Floating IP added the configuration as said under the self hosted instance guide. Can anyone please help?

    Screenshot_2021-08-13_10-41-25

    opened by Shri1610 9
  • Adding ldap support

    Adding ldap support

    Example of ldap interaction:

    $ ldapsearch -LLL -H ldap://127.0.0.1:10389 -d 5 -o ldif-wrap=no -b "OU=testgroup,OU=Group,dc=example,dc=com" -D "test" -w "test" '(CN=testgroup)' cn
    

    interactsh-server:

    $ sudo go run . -ldap -debug -listen-ip 127.0.0.1 -ip 127.0.0.1
    2021/12/13 12:25:48 Client Token: xxxx
    2021/12/13 12:25:49 Listening on ports: DNS, SMTP, HTTP, LDAP
    [DBG] LDAP Interaction: 
    {"protocol":"ldap","unique-id":"","full-id":"","raw-request":"Listening on 127.0.0.1:10389\n","remote-address":"","timestamp":"2021-12-13T12:25:49.528108+01:00"}
    [DBG] Registered correlationID xxx for key
    [DBG] LDAP Interaction: 
    {"protocol":"ldap","unique-id":"","full-id":"","raw-request":"Connection client [1] from 127.0.0.1:60991 accepted","remote-address":"","timestamp":"2021-12-13T12:26:02.724619+01:00"}
    [DBG] LDAP Interaction: 
    {"protocol":"ldap","unique-id":"","full-id":"","raw-request":"\u003c\u003c\u003c 1 - BindRequest - hex=\u0026{303c0201016037020103042b7569643d7365617263682d757365722c6f753d50656f706c652c64633d6578616d706c652c64633d636f6d80057465737461}","remote-address":"","timestamp":"2021-12-13T12:26:02.725405+01:00"}
    [DBG] LDAP Interaction: 
    {"protocol":"ldap","unique-id":"","full-id":"","raw-request":"\u003e\u003e\u003e 1 - LDAPResult - hex=302f020101302a0a0135040004234f7065726174696f6e206e6f7420696d706c656d656e74656420627920736572766572","remote-address":"","timestamp":"2021-12-13T12:26:02.725526+01:00"}
    
    Status: Completed Type: Enhancement 
    opened by Mzack9999 9
  • Not able to run the interactsh-server

    Not able to run the interactsh-server

    When I run the command interactsh-server -domain mydomain.com -hostmaster [email protected] -ip [VPS IP]. The following output is given without any errors:

    2021/05/01 08:45:17 Creating new order for domains: [*.mydomain.com mydomain.com]
    2021/05/01 08:45:17 Order created: https://acme-v02.api.letsencrypt.org/acme/order/121967319/9409571122
    2021/05/01 08:45:17 Fetching authorization: https://acme-v02.api.letsencrypt.org/acme/authz-v3/12762297545
    2021/05/01 08:45:17 Fetched authorization: mydomain.com
    2021/05/01 08:45:27 Updating challenge for authorization mydomain.com: https://acme-v02.api.letsencrypt.org/acme/chall-v3/12762297545/FkqiUg
    

    But the server is not giving A records when queried. I already had a letsencrypt cert but even after I deleted the cert nothing changed the same output is given

    opened by HritikHS 7
  • Improve default socket listening behaviour

    Improve default socket listening behaviour

    This commit fixes three issues:

    • Previously if a "listen IP" wasn't specified the public IP looked up from a "what is my IP" API was used. In many cases cloud VMs do not have their "public" IP bound to an interface (such as Amazon EC2), causing startup to fail:

      $ ./interactsh-server -domain example.com
      [FTL] Could not listen for udp DNS on 203.0.113.42:53 (listen udp 203.0.113.42:53: bind: cannot assign requested address)
      

      This has been changed to bind to an appropriate wildcard address, which should work in almost all cases.

    • The default wildcard listen address has been changed to :<port number>, which will cause the socket to pick a suitable wildcard address depending on whether the machine is dual stack or IPv4-only. This further supports upcoming work to add IPv6 support.

    • IPv6 literals may now be passed to "-listen-ip" without needing to wrap them in [].

    opened by fincham 6
  • Nuclei spams AAAA requests to the Interact server

    Nuclei spams AAAA requests to the Interact server

    Hi, I'm using Nuclei, interact and notify to spot OOB requests, however the webhook is spamming me with this

    image

    Could a IP filter argument be added so they're not passed through into STDOUT?

    Type: Question 
    opened by 0x0luke 6
  • [Feature] Burp suite extension for interactsh client

    [Feature] Burp suite extension for interactsh client

    Maybe it is not very necessary, but if it would be something interesting, a client for burpsuite (community), it is necessary to take into account that it would be an extra maintenance, no wonder they reject the idea. but still I comment

    Status: Completed Type: Enhancement 
    opened by vay3t 6
  • Allow use of base domain (or custom sub-domain) for self-hosted servers

    Allow use of base domain (or custom sub-domain) for self-hosted servers

    Hello and thank you for this awesome tool, it will surely come in handy during our testing.

    The current behavior of interactsh is to create a randomized subdomain like c282n3l3djgbti5v595gcnenzdoyyyyyn.domain.tld, which is fine and all, however, we have a pretty nice 4 x 2 domain and we feel that smaller payloads are the best, so could you allow the use of the base domain and/or customized sub-domains for self-hosted servers in addition to the randomized subdomains?

    Edited to ask for customized sub-domains option as well. 👍🏻

    Status: Completed Type: Enhancement 
    opened by geeknik 6
  • [Feature] Printing the full Hostname

    [Feature] Printing the full Hostname

    I see that you have implemented the burp collaborator feature of wildcard mapping to the source collaborator address.

    Example : ..interact.sh -> .interact.sh

    That's great feature . But it would be great if you print this whole ..interact.sh on the terminal whenever a query triggered without verbose flag. Because verbose flag print many unwanted information (in case of DNS queries).

    Example:

    if we ping anything.<UNIQUE-ID>.interact.sh
    And the interactsh client shows ( without verbose flag)
    [<UNIQUE-ID>] Recieved DNS interaction (A) from <ORIGIN-IP> at <TIMESTAMP>
    

    So the anything is omitted , which is sometimes important during Bug Bounties.

    Status: Completed Type: Enhancement 
    opened by shubhack-repo 6
  • chore(deps): bump github.com/stretchr/testify from 1.7.4 to 1.7.5

    chore(deps): bump github.com/stretchr/testify from 1.7.4 to 1.7.5

    Bumps github.com/stretchr/testify from 1.7.4 to 1.7.5.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    Type: Maintenance 
    opened by dependabot[bot] 0
  • Exclude interactions for self dns records in wildcard mode

    Exclude interactions for self dns records in wildcard mode

    If you run a dedicated interact-sh server, and then attach to this server interact-sh client, client show all request (include ns1.domain.com, etc) Please add flag to show only generated domain in client part

    Priority: Medium Type: Enhancement 
    opened by kiriknik 2
  • IPv6 support for Interactsh server + interaction

    IPv6 support for Interactsh server + interaction

    From: https://github.com/projectdiscovery/interactsh/pull/186

    Please describe your feature request:

    DNS server to serve IPv6 address records (AAAA) to support

    • Interactions for DNS server running on IPv6
    • Run / host interactsh server on IPv6

    Describe the use case of this feature:

    This allows for IPv6 interaction and provides more opportunities for interaction to ocurr when e.g. IPv6 and IPv4 egress firewalling differ on a network being tested.

    Type: Enhancement 
    opened by ehsandeep 0
  • Add Self-Diagnostic functionality

    Add Self-Diagnostic functionality

    Please describe your feature request:

    The tool should implement a self diagnostic functionality with all the checks implemented at https://github.com/projectdiscovery/httpx/pull/665 with the additional ones:

    • Check DNS connectivity with: scanme.sh:53 (UDP)
    Type: Maintenance 
    opened by Mzack9999 0
  • Add support for network TCP/UDP sockets

    Add support for network TCP/UDP sockets

    Please describe your feature request:

    Add support for network TCP/UDP sockets

    Describe the use case of this feature:

    There might be cases where it's necessary to test a callback not tied to a particular protocol, similarly to a classical netcat/ncat listener

    Priority: Low Type: Enhancement 
    opened by Mzack9999 0
  • DHCP support

    DHCP support

    How about DHCP? For example, with CVE-2019-13263, you could encode data to be sent cross-router into the 32-bit Transaction ID field. More research is needed, but obscure DHCP bugs would be cool to find. (;

    Originally posted by @geeknik in https://github.com/projectdiscovery/interactsh/issues/7#issuecomment-831433457

    Priority: Low Type: Enhancement 
    opened by Mzack9999 0
Releases(v1.0.5)
Owner
ProjectDiscovery
Security Through Intelligent Automation
ProjectDiscovery
A LoRaWAN nodes' and network simulator that works with a real LoRaWAN environment (such as Chirpstack) and equipped with a web interface for real-time interaction.

LWN Simulator A LoRaWAN nodes' simulator to simulate a LoRaWAN Network. Table of Contents General Info Requirements Installation General Info LWN Simu

ARSLab 25 Jun 25, 2022
Information Gathering tool - DNS / Subdomains / Ports / Directories enumeration

Information Gathering tool - DNS / Subdomains / Ports / Directories enumeration

gilfoyle97 464 Jun 28, 2022
基于TCP的基础通讯协议及框架(IIP,Internal Interaction Protocol),该协议可作为RPC接口调用的底层协议,如同http2之于gRPC,本项目基于该协议实现了client/server的基础框架。

IIP是什么? 基于TCP的基础通讯协议及框架(IIP,Internal Interaction Protocol),该协议可作为RPC接口调用的底层协议,如同http2之于gRPC,本项目基于该协议实现了client/server的基础框架。 使用说明 echo回显client示例: exampl

fangyousong 14 Dec 22, 2021
Server and client implementation of the grpc go libraries to perform unary, client streaming, server streaming and full duplex RPCs from gRPC go introduction

Description This is an implementation of a gRPC client and server that provides route guidance from gRPC Basics: Go tutorial. It demonstrates how to u

Joram Wambugu 0 Nov 24, 2021
A golang library about socks5, supports all socks5 commands. That Provides server and client and easy to use. Compatible with socks4 and socks4a.

socks5 This is a Golang implementation of the Socks5 protocol library. To see in this SOCKS Protocol Version 5. This library is also compatible with S

chenhao zhang 39 May 29, 2022
Simple mDNS client/server library in Golang

mdns Simple mDNS client/server library in Golang. mDNS or Multicast DNS can be used to discover services on the local network without the use of an au

HashiCorp 891 Jun 29, 2022
Use pingser to create client and server based on ICMP Protocol to send and receive custom message content.

pingser Use pingser to create client and server based on ICMP Protocol to send and receive custom message content. examples source code: ./examples Us

zznQ 12 Jun 9, 2022
A simple FTP protocol with client and server implemented in TypeScript and Golang

websocket-ftp A simple FTP protocol with client and server implemented in TypeScript and Golang. Example (Client) const buffer: Uint8Array = (new Text

LQR471814 0 Apr 14, 2022
Prisma Client Go is an auto-generated and fully type-safe database client

Prisma Client Go Typesafe database access for Go Quickstart • Website • Docs • API reference • Blog • Slack • Twitter Prisma Client Go is an auto-gene

Prisma 1.2k Jul 2, 2022
JPRQ Customizer is a customizer that helps to use the JPRQ server code and make it compatible with your own server with custom subdomain and domain

JPRQ Customizer is a customizer that helps to use the JPRQ server code and make it compatible with your own server with custom subdomain and domain.You can upload the generated directory to your web server and expose user localhost to public internet. You can use this to make your local machine a command center for your ethical hacking purpose ;)

Abir Ghosh 1 Jan 19, 2022
Http-server - A HTTP server and can be accessed via TLS and non-TLS mode

Application server.go runs a HTTP/HTTPS server on the port 9090. It gives you 4

Vedant Pareek 0 Feb 3, 2022
A LWM2M Client and Server implementation (For Go/Golang)

Betwixt - A LWM2M Client and Server in Go Betwixt is a Lightweight M2M implementation written in Go OMA Lightweight M2M is a protocol from the Open Mo

Zubair Hamed 54 May 28, 2022
Pglet server and client

Pglet - Web UI framework for backend developers Build web apps like a frontend pro in the language you already know. No knowledge of HTML, CSS or Java

Web UI framework for backend developers 569 Jun 22, 2022
Generate Server and Client side code

Additional Information Generate Server and Client side code Pre-generated stub file is included in the go project. If you need to generate the stub fi

null 0 Nov 6, 2021
Make TCP connection storm between server and client for benchmarking network stuff

Make TCP connection storm between server and client for benchmarking network stuff

Masahiro Nagano 2 Nov 14, 2021
Go application of a gRPC client and server, built for Azure Container Apps

gRPC Sample : Go View this sample in other languages C# Go Java JavaScript Python The following is a sample of a gRPC client calling another container

Jeff Hollan 1 Nov 29, 2021
Client - Server TCP Chat For String Messages And Random Files

GoChat Client - Server TCP Chat For String Messages And Random Files GoChat is a chat for string messages and random files using Golorem by Derek A. R

Brian GL 0 Sep 29, 2021
A tiny client and server for tinysql

Tiny Client/Server a tiny client and server for tinysql. Start // start server

null 1 Dec 21, 2021