display all interactsh-sever interactions #1264
-
|
Hey, When Interactsh-server is set up with a wildcard domain support and (with or without) authentication token, is there a way to read and access all logs from the client or via the server cmdline where the interactsh-server is set up, please? I mean, say the interactsh-server is set up in a VPS at Using interactsh-client wont do it right ? it would be limited to the OOB URL generated Maybe I could output some kind of log on the server VPS? Or I can get all interactions to Can you help me out with that, please? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
i figure it out, the solution is |
Beta Was this translation helpful? Give feedback.
-
|
When self-hosting interactsh-server, there are a few ways to see all interactions: 1. Server-side logging: Start the server with verbose/debug output: interactsh-server -d hello.sim4n6.com -debug -vThis logs all incoming DNS, HTTP, SMTP interactions to stdout. Pipe to a file for persistent logging: interactsh-server -d hello.sim4n6.com -debug -v 2>&1 | tee /var/log/interactsh.log2. Client with your auth token: If you started the server with interactsh-client -s hello.sim4n6.com -token YOUR_TOKEN -vThis shows all interactions for your correlation ID. 3. To see ALL interactions (all clients): This is intentionally not exposed via the client for security/privacy reasons — each client only sees its own correlation ID's interactions. But on the server side:
4. For email specifically: interactsh-server -d hello.sim4n6.com -smtp -debugAll emails to Bottom line: Server-side |
Beta Was this translation helpful? Give feedback.
-
|
despite being kind of 6m late, but really appreciate the reply, sponsored or not, thank you man |
Beta Was this translation helpful? Give feedback.
When self-hosting interactsh-server, there are a few ways to see all interactions:
1. Server-side logging:
Start the server with verbose/debug output:
This logs all incoming DNS, HTTP, SMTP interactions to stdout. Pipe to a file for persistent logging:
2. Client with your auth token:
If you started the server with
-token, use the client with the same token:This shows all interactions for your correlation ID.
3. To see ALL interactions (all clients):
This is intentionally not exposed via the client for…