-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated 8x tempalates to user interactsh-url over oast.tld #10099
base: main
Are you sure you want to change the base?
Updated 8x tempalates to user interactsh-url over oast.tld #10099
Conversation
Great, thanks for your contribution @fullstackpotato ! |
Hello @fullstackpotato, thank you so much for updating these template and contributing to this project 🍻 We use In this case, the team will update the matchers of these templates along with adding You can join our discord server. It's a great place to connect with fellow contributors and stay updated with the latest developments. Thank you once again |
Hey thank you for the reply, and appreciate you all looking at this. There is one more template that I spotted on Friday which is
|
Also a QQ off the back of this request, when templates are accepted into the repo do you discourage the use of hardcoded URLs for these types of checks? |
@fullstackpotato We try not to add any hardcoded domains, but in some edge cases when we do, the domains are for our interactsh service only and not for any third-party domains. |
Updated 8x templates to use
{{interactsh-url}}
over oast[.]TLD. This change is primarily for users who wish to control where their data is going, e.g. supplying their own interactsh server and expecting their data to go there rather than a hardcoded domain.Caveat, there will be other templates that I've missed. I did a quick search for anything that has a hardcoded domain and is checking the response for "Interactsh Server".