Heya, Founder of https://viewdns.info/ here (used by any mentioned in the article a bit). If anyone is doing this kind of research, feel free to reach out at feedback@viewdns.info as I'm more than happy to extend some free API credits etc! -Hughesey. - Source: Hacker News / 7 months ago

This might help you get a start: There are lots of common tools. https://viewdns.info/. Source: over 1 year ago

I used viewdns.info - allowed me to search by registrant name. I looked for Bed Bath Procurement and Liberty Procurement for the list I grabbed (~600 results). Spotted the .sex TLD and filtered down to that and hand-verified whether each result was truly owned by BBBY. I work in IT Audit and InfoSec, so was a piece of cake to find and filter the data. :D. Source: over 1 year ago

After doing some investigating, it looks like when I sent the email, it was initially sent via an IP address that falls within Googles IP range, but when I went to viewdns.info to lookup the IP, it was of a Domain that was not Google. Source: almost 2 years ago

Normally that means that every target that belongs to the company, is in scope except the one in the OOS section. Now the real question his, how can I be sure that a target is in scope? Well, whois command is your friend, if you have a domain name. If you have a ip address, you have to work more on it, anyway you can try some reverse DNS or other tool that you can find here: https://viewdns.info/ or you are... Source: almost 2 years ago

It's possible what you had was 2 devices transmitting packets at the same time resulting in a collision Given that you were doing a slowloris attack I would consider this success (or failure) in other words the attack worked. Here are a few other things you might find useful. Source: over 1 year ago

A VPN is good because it is encrypted and hard to find your IP. Even a router will use DHCP and change your IP but if the router is in your own home that is a dead giveaway. This and other tools like that can help to see all the relay points (collision domains) in the route. Source: over 1 year ago

You might narrow it down by using traceroute How the ISP chooses to identify their collision domains is entirely up to the ISP. If you get lucky maybe the wifi name is "Jones family 123 main st" or something to connect the IP to a person. Source: over 1 year ago

Is this a localhost api or remote? You could test using this or this to see if the network is the problem. You can test the database from the command line as well. Source: over 1 year ago

Good place to learn another another good place but somewhat advanced this tutorial trace that website and the http protocol. Source: over 1 year ago