Bibek Shah

Incase you get error like this then create a keypair named axiom in the region which you selected during axiom setup process. 

@lonelyman666 After upgrading packer and creating axiom keypair i was able to use axiom in AWS. Try changing shell to zsh or oh-my-zsh once

I am getting this error. ```bash github.com/projectdiscovery/nuclei/v2/pkg/protocols/common/protocolinit github.com/projectdiscovery/tlsx/pkg/tlsx The command '/bin/sh -c go install -v github.com/projectdiscovery/nuclei/v2/cmd/nuclei@latest' returned a non-zero code: 2 Traceback (most recent call last): File "/root/ShadowClone/env/bin/lithops", line 8,...

Solved above error by editing Dockerfile to copy binary. Python3.10 has errors for lambda though. ``` COPY ./nuclei /usr/local/bin/nuclei ```

I can confirm. This is still vulnerable.

I think it also depends on the account type. I had a student account where I was only getting ns name between 30-36 everytime. Then I tried with a regular...

I had success in getting lower numbers. DM me over [Twitter](https://twitter.com/noobibek) if you need to test a takeover

Hi @Mzack9999 , I am also getting similar error. ```bash root@ip-172-31-80-168:/home/ubuntu# interactsh-server -domain bibekshah.com _ __ __ __ (_)___ / /____ _________ ______/ /______/ /_ / / __ \/ __/...

Can anyone confirm if this still works? I am getting an error saying to verify the domain ownership. 

Yeah, which tool are you using btw?