Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Seeking provider that is understanding towards service fingerprinting and scanning of the internet.

135

Comments

  • aluyaluy Member, Patron Provider

    and please dont block an ip on spoof possibility. imagine you block an upstream ip and 10% of your infra go down

    Thanked by 1sillycat
  • avsispavsisp Member, Patron Provider

    @aluy said:

    @avsisp said:

    @aluy said:

    @avsisp said:

    @tentor said:

    @aluy, sir, you are wrong, quad 9 definitely monetizes their fancy ip address for scan

    He literally just proved my point that AbuseIPDB takes all the steps to ensure false reports don't happen. On the very page he posted...

    Important Note: 9.9.9.9 is an IP address from within our whitelist, which we identify as "Quad9 Public DNS". 
    

    0% score. Wouldn't be blocked by any filters.

    nono, this isnt what i meant. what i meant is the amount of false reports even on THOSE ips EVERY day. and abuseipdb cleans them pretty often. how many do you think are on not so known ips / ranges

    How many do you think are real reports because it was used for DNS Amplification and Reflection Attacks? Especially carpet-bombs where someone spoofed the source of requests from ALL of someone's range, and quad9 I KNOW FOR SURE, HAD EXPERIENCE - limits per IP, not per range, allowing carpet bombs to happen?

    They aren't false - they aren't spoofed - quad 9 DID attack their IPs.

    no it didnt, quad9 didnt. spoofing isnt a valid report. thats exactly why they get removed by abuseipdb

    That IP (9.9.9.9) DID carpet-bomb their entire network. NOT someone spoofing to be 9.9.9.9. That's not how a DDoS works. The attacker spoofed requests from the entire range of victim to 9.9.9.9 - 9.9.9.9 in turn replied with HUGE amounts of data... 9.9.9.9 needs to filter properly for that not to happen(reply length limits, timeouts, limits per range, etc). You'll see a LOT less reports on Cloudflare 1.1.1.1.1 - because they actively prevent their servers being used for reflection attacks.

  • aluyaluy Member, Patron Provider

    @avsisp said:

    @aluy said:

    @avsisp said:

    @aluy said:

    @avsisp said:

    @tentor said:

    @aluy, sir, you are wrong, quad 9 definitely monetizes their fancy ip address for scan

    He literally just proved my point that AbuseIPDB takes all the steps to ensure false reports don't happen. On the very page he posted...

    Important Note: 9.9.9.9 is an IP address from within our whitelist, which we identify as "Quad9 Public DNS". 
    

    0% score. Wouldn't be blocked by any filters.

    nono, this isnt what i meant. what i meant is the amount of false reports even on THOSE ips EVERY day. and abuseipdb cleans them pretty often. how many do you think are on not so known ips / ranges

    How many do you think are real reports because it was used for DNS Amplification and Reflection Attacks? Especially carpet-bombs where someone spoofed the source of requests from ALL of someone's range, and quad9 I KNOW FOR SURE, HAD EXPERIENCE - limits per IP, not per range, allowing carpet bombs to happen?

    They aren't false - they aren't spoofed - quad 9 DID attack their IPs.

    no it didnt, quad9 didnt. spoofing isnt a valid report. thats exactly why they get removed by abuseipdb

    That IP (9.9.9.9) DID carpet-bomb their entire network. NOT someone spoofing to be 9.9.9.9. That's not how a DDoS works. The attacker spoofed requests from the entire range of victim to 9.9.9.9 - 9.9.9.9 in turn replied with HUGE amounts of data... 9.9.9.9 needs to filter properly for that not to happen(reply length limits, timeouts, limits per range, etc). You'll see a LOT less reports on Cloudflare 1.1.1.1.1 - because they actively prevent their servers being used for reflection attacks.

    quad9 is not vulnerable to dns reflection attacks.

  • @avsisp said:
    Also - spoofing is more rare than you would think - tbh. Unless someone knows that we are reporting that way, they won't spoof. But the script does need some updating and I haven't had the time to update it. It will eventually keep a count and if it's more than x attempts per x seconds will report. Nothing in this world is perfect. If it works properly 99.99% of time, that 0.01% spoofed that get's accidentally reported is less of an issue. If someone has a complaint, our profile is public and they can reach out and I'll remove the report.

    What do you base this on? isn't the whole point with spoofing the IP would be that the destination does not know that it is being spoofed and sends a response to another host?

    Thanked by 1tentor
  • avsispavsisp Member, Patron Provider
    edited August 2025

    @tentor said:
    @avsisp the problem both I and @aluy are trying to explain is that you have to not report innocent party first of all - if it was abused (dns amplification isn't something you could completely mitigate for a public open resolver such as 1.1.1.1, 8.8.8.8 or 9.9.9.9) you don't contribute anything valuable. Same goes for reporting TCP reflection - literally any TCP service BY DESIGN sends TCP SYN-ACK packet back, there is nothing malice.

    And I understand that - but it DOES NOT make AbuseIPDB bad. They do everything they can to prevent false-positives. The results are heavily leaning towards innocence. There are IPs that I KNOW for sure have 20% score with 50+ reports over an hour and that HAVE INDEED spammed my WHMCS Ticket system. And they are not blocked by anyone - because most people that use it only block for 100% abuse factor.

  • avsispavsisp Member, Patron Provider

    @aluy said:

    @avsisp said:

    @aluy said:

    @avsisp said:

    @aluy said:

    @avsisp said:

    @tentor said:

    @aluy, sir, you are wrong, quad 9 definitely monetizes their fancy ip address for scan

    He literally just proved my point that AbuseIPDB takes all the steps to ensure false reports don't happen. On the very page he posted...

    Important Note: 9.9.9.9 is an IP address from within our whitelist, which we identify as "Quad9 Public DNS". 
    

    0% score. Wouldn't be blocked by any filters.

    nono, this isnt what i meant. what i meant is the amount of false reports even on THOSE ips EVERY day. and abuseipdb cleans them pretty often. how many do you think are on not so known ips / ranges

    How many do you think are real reports because it was used for DNS Amplification and Reflection Attacks? Especially carpet-bombs where someone spoofed the source of requests from ALL of someone's range, and quad9 I KNOW FOR SURE, HAD EXPERIENCE - limits per IP, not per range, allowing carpet bombs to happen?

    They aren't false - they aren't spoofed - quad 9 DID attack their IPs.

    no it didnt, quad9 didnt. spoofing isnt a valid report. thats exactly why they get removed by abuseipdb

    That IP (9.9.9.9) DID carpet-bomb their entire network. NOT someone spoofing to be 9.9.9.9. That's not how a DDoS works. The attacker spoofed requests from the entire range of victim to 9.9.9.9 - 9.9.9.9 in turn replied with HUGE amounts of data... 9.9.9.9 needs to filter properly for that not to happen(reply length limits, timeouts, limits per range, etc). You'll see a LOT less reports on Cloudflare 1.1.1.1.1 - because they actively prevent their servers being used for reflection attacks.

    quad9 is not vulnerable to dns reflection attacks.

    The last 3 carpet bombs that hit us were using 9.9.9.9 as part of their attacks -- so WRONG - 100% personal experience here.

  • aluyaluy Member, Patron Provider

    @avsisp said:

    @tentor said:
    @avsisp the problem both I and @aluy are trying to explain is that you have to not report innocent party first of all - if it was abused (dns amplification isn't something you could completely mitigate for a public open resolver such as 1.1.1.1, 8.8.8.8 or 9.9.9.9) you don't contribute anything valuable. Same goes for reporting TCP reflection - literally any TCP service BY DESIGN sends TCP SYN-ACK packet back, there is nothing malice.

    And I understand that - but it DOES NOT make AbuseIPDB bad. They do everything they can to prevent false-positives. The results are heavily leaning towards innocence. There are IPs that I KNOW for sure have 20% score with 50+ reports over an hour and that HAVE INDEED spammed my WHMCS Ticket system. And they are not blocked by anyone - because most people that use it only block for 100% abuse factor.

    send an email out to the host and report it with valid logs to abuseipdb

  • aluyaluy Member, Patron Provider

    @avsisp said:

    @aluy said:

    @avsisp said:

    @aluy said:

    @avsisp said:

    @aluy said:

    @avsisp said:

    @tentor said:

    @aluy, sir, you are wrong, quad 9 definitely monetizes their fancy ip address for scan

    He literally just proved my point that AbuseIPDB takes all the steps to ensure false reports don't happen. On the very page he posted...

    Important Note: 9.9.9.9 is an IP address from within our whitelist, which we identify as "Quad9 Public DNS". 
    

    0% score. Wouldn't be blocked by any filters.

    nono, this isnt what i meant. what i meant is the amount of false reports even on THOSE ips EVERY day. and abuseipdb cleans them pretty often. how many do you think are on not so known ips / ranges

    How many do you think are real reports because it was used for DNS Amplification and Reflection Attacks? Especially carpet-bombs where someone spoofed the source of requests from ALL of someone's range, and quad9 I KNOW FOR SURE, HAD EXPERIENCE - limits per IP, not per range, allowing carpet bombs to happen?

    They aren't false - they aren't spoofed - quad 9 DID attack their IPs.

    no it didnt, quad9 didnt. spoofing isnt a valid report. thats exactly why they get removed by abuseipdb

    That IP (9.9.9.9) DID carpet-bomb their entire network. NOT someone spoofing to be 9.9.9.9. That's not how a DDoS works. The attacker spoofed requests from the entire range of victim to 9.9.9.9 - 9.9.9.9 in turn replied with HUGE amounts of data... 9.9.9.9 needs to filter properly for that not to happen(reply length limits, timeouts, limits per range, etc). You'll see a LOT less reports on Cloudflare 1.1.1.1.1 - because they actively prevent their servers being used for reflection attacks.

    quad9 is not vulnerable to dns reflection attacks.

    The last 3 carpet bombs that hit us were using 9.9.9.9 as part of their attacks -- so WRONG - 100% personal experience here.

    please. this is major dns provider you are accusing here

  • tentortentor Member, Host Rep

    @avsisp said: They do everything they can to prevent false-positives.

    They don't punish reporters who report single TCP SYN packets since years, so I don't agree with you AT ALL.

    Please compare AbuseIPDB database with CrowdSec community blacklist and reconsider.

    At this point I will leave this discussion, as you seem to be too stubborn to critically think about what others say to you.

  • avsispavsisp Member, Patron Provider

    @tentor said:

    @avsisp said: They do everything they can to prevent false-positives.

    They don't punish reporters who report single TCP SYN packets since years, so I don't agree with you AT ALL.

    Please compare AbuseIPDB database with CrowdSec community blacklist and reconsider.

    At this point I will leave this discussion, as you seem to be too stubborn to critically think about what others say to you.

    Why to punish the reporters if the reported IPs don't get any trouble for it? If they aren't REPEATEDLY doing it -their one attempt doesn't raise their score any. And again, I understand where you are coming from - I've disabled the script myself for now until I make some changes - but - AbuseIPDB is one of the safest blocklists to use with 100% rating filter... I have never had someone complain they cannot connect to something or got blocked because of it..

  • @Yuki_ said:

    @avsisp said:
    Also - spoofing is more rare than you would think - tbh. Unless someone knows that we are reporting that way, they won't spoof. But the script does need some updating and I haven't had the time to update it. It will eventually keep a count and if it's more than x attempts per x seconds will report. Nothing in this world is perfect. If it works properly 99.99% of time, that 0.01% spoofed that get's accidentally reported is less of an issue. If someone has a complaint, our profile is public and they can reach out and I'll remove the report.

    What do you base this on? isn't the whole point with spoofing the IP would be that the destination does not know that it is being spoofed and sends a response to another host?

    Less then a year ago Tor nodes were being spoofed en-mass (guard and entry nodes included which usually do not see the kind of abuse complaints that exit nodes get) due to this the Tor network was weakened due to suspension because of false claims of abuse due to this actor spoofing IPs.

    Thanked by 2tentor lothos
  • avsispavsisp Member, Patron Provider

    @aluy said:

    @avsisp said:

    @aluy said:

    @avsisp said:

    @aluy said:

    @avsisp said:

    @aluy said:

    @avsisp said:

    @tentor said:

    @aluy, sir, you are wrong, quad 9 definitely monetizes their fancy ip address for scan

    He literally just proved my point that AbuseIPDB takes all the steps to ensure false reports don't happen. On the very page he posted...

    Important Note: 9.9.9.9 is an IP address from within our whitelist, which we identify as "Quad9 Public DNS". 
    

    0% score. Wouldn't be blocked by any filters.

    nono, this isnt what i meant. what i meant is the amount of false reports even on THOSE ips EVERY day. and abuseipdb cleans them pretty often. how many do you think are on not so known ips / ranges

    How many do you think are real reports because it was used for DNS Amplification and Reflection Attacks? Especially carpet-bombs where someone spoofed the source of requests from ALL of someone's range, and quad9 I KNOW FOR SURE, HAD EXPERIENCE - limits per IP, not per range, allowing carpet bombs to happen?

    They aren't false - they aren't spoofed - quad 9 DID attack their IPs.

    no it didnt, quad9 didnt. spoofing isnt a valid report. thats exactly why they get removed by abuseipdb

    That IP (9.9.9.9) DID carpet-bomb their entire network. NOT someone spoofing to be 9.9.9.9. That's not how a DDoS works. The attacker spoofed requests from the entire range of victim to 9.9.9.9 - 9.9.9.9 in turn replied with HUGE amounts of data... 9.9.9.9 needs to filter properly for that not to happen(reply length limits, timeouts, limits per range, etc). You'll see a LOT less reports on Cloudflare 1.1.1.1.1 - because they actively prevent their servers being used for reflection attacks.

    quad9 is not vulnerable to dns reflection attacks.

    The last 3 carpet bombs that hit us were using 9.9.9.9 as part of their attacks -- so WRONG - 100% personal experience here.

    please. this is major dns provider you are accusing here

    Yes - DNS provider - aka vulnerable to reflection attacks.

    And some more so than others. In any DNS Reflection attack, 9.9.9.9 tends to come up a lot in list of IPs - 1.1.1.1 not so much. Just points to they could adjust some of their filters.

  • avsispavsisp Member, Patron Provider

    @Yuki_ said:

    @Yuki_ said:

    @avsisp said:
    Also - spoofing is more rare than you would think - tbh. Unless someone knows that we are reporting that way, they won't spoof. But the script does need some updating and I haven't had the time to update it. It will eventually keep a count and if it's more than x attempts per x seconds will report. Nothing in this world is perfect. If it works properly 99.99% of time, that 0.01% spoofed that get's accidentally reported is less of an issue. If someone has a complaint, our profile is public and they can reach out and I'll remove the report.

    What do you base this on? isn't the whole point with spoofing the IP would be that the destination does not know that it is being spoofed and sends a response to another host?

    Less then a year ago Tor nodes were being spoofed en-mass (guard and entry nodes included which usually do not see the kind of abuse complaints that exit nodes get) due to this the Tor network was weakened due to suspension because of false claims of abuse due to this actor spoofing IPs.

    Sounds like a very rare event. And sounds like AbuseIPDB should whitelist Tor nodes tbh.

    Thanked by 1PacketsDecreaser
  • zGatozGato Member
    edited August 2025

    @avsisp said:

    @tentor said:

    @avsisp said: Probably someone doing reflections with them or WARP related - seen a LOT of uptick in WARP hacking attempts lately tbh.

    Doesn't WARP use IP addresses other than what CF uses for their reverse proxy? Also, why would you report a single TCP SYN-ACK packet (reflection) that could be spoofed?

    No - WARP uses ANY Cloudflare IPs. Can be from the proxy range, can be from different ranges. For v6 it is indeed reserved separate blocks. I've got regular Cloudflare IPs listed on their website myself using WARP in Germany in past.

    Not really. MaxMind has a good list of WARP IPs, since they used to be partners (idk if they do any longer)

    If the IP in the demo is marked as Cloudflare WARP and is ISP, that is a WARP IP. If not, it's not.

    Cloudflare uses very small ranges for their WARP locations (in big countries they use 2-3 IPs per major city). So they maybe have a handful of /24s for that purpose that they just announce globally and route properly per PoP.

    AbuseIPDB seems to do the same.

    Thanked by 3tentor Yuki_ oloke
  • kaitkait Member

    Nice discussion about how avsisp is even more dumb than aluy is. Btw love that spoofing is super rare but it cost me 3 euros to spoof and troll the shit out of avsisp.

    Also recent DDoS attacks have been > 6Tbps from what I remember where 80% or 90% is spoofed traffic and only 10% or so is actual non spoofed non amp'ed traffic.

  • @Yuki_ said:
    Generally speaking in my experience providers are not so understanding of my running masscan on 0.0.0.0/0 and banner fingerprinting varying services. What ends up happening is me having to splitting the activity over multiple VPS's this is fine, but it got me wondering what are some providers that the people of LET would recommend for such activity to someone who does not want to split the scanning activity?

    do you have your own IP? shodan can get away with it (seen them in my dns server, maltrail, crowdsec) so i'm sure you also can do it too

    the bare minimum probably like:

    • have your own ASN and IP
    • have your own institution / org
    • openly publish your ip range is used for probing, if people don't like it they can ask for whitelist
    • properly respect people's whitelist request

    internet is build on trust, don't be an asshoe and you'll be fine

  • TimboJonesTimboJones Member
    edited August 2025

    @tentor said:

    What would need to be moderated is the question?

    To not set 80% score for an IP that was only found doing ICMP echo-request (that didn't even trigger a single abuse complaint), see https://lowendtalk.com/discussion/comment/4489508/#Comment_4489508

    Please don't confuse ICMP requests with fingerprinting. That's the difference from someone shouting "anyone home?" from the street and someone going around recording your door and window status. That ain't your fucking business unless invited.

  • gravhosting.com
    dmzhost.co
    I haven't used them, but I remember they allow port scanning.
    IPVolume should also work, Censys or Shodan are using it.

    Thanked by 3384_cz jnd Yuki_
  • jndjnd Member
    edited August 2025

    @avsisp said:

    AbuseIPDB is the most fair and accurate in their ratings.

    Yeah I don't think so too. Once I tried smaller scan if there is NTP server running or not, it's a single small UDP packet, nothing special, no personal information to gather, nothing to gain access.

    What did I find? That AbuseIPDB users are incompetent and have misconfigured reporting. There was couple reports like "Port probe: TCP/123", "Failed Attempt to Connect to and access Firewall", or meaningless "Honeypot hit.". One user submitted multiple reports spaced by whole amounts of hours but at least they got the udp port right. The reported categories were mostly wrong too, with "Hacking", "Exploited Host", "Brute-Force", less than half got it right with reporting "Port scan".

  • tentortentor Member, Host Rep
    edited August 2025

    @TimboJones said:

    @tentor said:

    What would need to be moderated is the question?

    To not set 80% score for an IP that was only found doing ICMP echo-request (that didn't even trigger a single abuse complaint), see https://lowendtalk.com/discussion/comment/4489508/#Comment_4489508

    Please don't confuse ICMP requests with fingerprinting. That's the difference from someone shouting "anyone home?" from the street and someone going around recording your door and window status. That ain't your fucking business unless invited.

    Unfortunately, this doesn't work like so. You can't even know if sent ICMP echo-request had spoofed source IP address or not, same goes for any report based upon single packet without any challenge (like TCP handshake for example).

  • avsispavsisp Member, Patron Provider

    @kait said:
    Nice discussion about how avsisp is even more dumb than aluy is. Btw love that spoofing is super rare but it cost me 3 euros to spoof and troll the shit out of avsisp.

    Also recent DDoS attacks have been > 6Tbps from what I remember where 80% or 90% is spoofed traffic and only 10% or so is actual non spoofed non amp'ed traffic.

    Thanks for clarifying it was indeed you the just did that crap and got my subnet listed. I'm pretty sure LET doesn't endorse DDoS nor attacks to hosts...

    Because you paid something to spoof IPs doesn't mean the system is broken. It means you're a dick. Period.

    And I'll send you message now to AbuseIPDB who will obviously delete the false reports -- see how moderation works?

  • kaitkait Member

    @avsisp said: Thanks for clarifying it was indeed you the just did that crap and got my subnet listed. I'm pretty sure LET doesn't endorse DDoS nor attacks to hosts...

    It wasn't me you dumbfuck.

    @avsisp said: Because you paid something to spoof IPs doesn't mean the system is broken. It means you're a dick. Period.

    Yes it exactly means the system is broken, but youre to dumb to notice.

    @avsisp said: And I'll send you message now to AbuseIPDB who will obviously delete the false reports -- see how moderation works?

    Got any proof all of them are false reports? Maybe some IPs did some nasty stuff... ;)

  • kaitkait Member
    edited August 2025

    https://www.abuseipdb.com/check/31.57.56.4

    Why did you report your own IP, youre hosting a super dangerous machine on your network or what? abuseipdb works so great.

    Thanked by 2tentor Yuki_
  • avsispavsisp Member, Patron Provider

    @kait said:

    @avsisp said: Thanks for clarifying it was indeed you the just did that crap and got my subnet listed. I'm pretty sure LET doesn't endorse DDoS nor attacks to hosts...

    It wasn't me you dumbfuck.

    @avsisp said: Because you paid something to spoof IPs doesn't mean the system is broken. It means you're a dick. Period.

    Yes it exactly means the system is broken, but youre to dumb to notice.

    @avsisp said: And I'll send you message now to AbuseIPDB who will obviously delete the false reports -- see how moderation works?

    Got any proof all of them are false reports? Maybe some IPs did some nasty stuff... ;)

    1) You just said you paid 3$ to annoy me - and spoof my IPs - so yes you did. You DDoS people known to report automatically to AbuseIPDB to try to prove your point. But you didn't prove anything except that you can Spoof IPs - which is well know. That isn't the problem or even being questioned here. What was being questioned is whether or not AbuseIPDB is good or bad. My argument is they try to be good - to moderate, etc. Other's argue the system is broken. That is not a way to prove your point. Now I see why you got all your "temp bans" - I really hope that using a hosts IPs to DDoS someone else is seen as a good enough reason to perm-ban.

    2) Yeah - I got proof. I sent them the link to YOUR ADMISSION here.

    3) Most of those IPs AREN'T EVEN IN USE - so easy for AbuseIPDB to verify that.

  • kaitkait Member

    @avsisp said: 1) You just said you paid 3$ to annoy me - and spoof my IPs - so yes you did.
    @avsisp said: 2) Yeah - I got proof. I sent them the link to YOUR ADMISSION here.

    Ah to bad, I lied to you and you took the bait. Everyone on LET knows I am a troll except you I guess.

  • avsispavsisp Member, Patron Provider

    @kait said:

    @avsisp said: 1) You just said you paid 3$ to annoy me - and spoof my IPs - so yes you did.
    @avsisp said: 2) Yeah - I got proof. I sent them the link to YOUR ADMISSION here.

    Ah to bad, I lied to you and you took the bait. Everyone on LET knows I am a troll except you I guess.

    The proof is in the pudding as we say... My entire subnet was indeed spoofed. Right before you posted your comment claiming responsibility for it. And considering it was half a subnet and 3 complaints each, that's about 3$ worth of spoof. So it definitely wasn't a bluff or trolling. You did exactly what you claim you did.

  • avsispavsisp Member, Patron Provider

    @kait said:
    https://www.abuseipdb.com/check/31.57.56.4

    Why did you report your own IP, youre hosting a super dangerous machine on your network or what? abuseipdb works so great.

    When I shutdown the script, it reported itself weirdly. Not an issue as I self-remove it. Which I just did. I check my subnet daily... And act on abuse reports... Like a responsible host should. So if something like that happens, I fix it rather quickly. It isn't an IP used by clients, as a matter of fact, it isn't even mounted at all - so it's fine - doesn't harm anyone. But again - the script has been stopped and isn't in use at the moment until I have time to re-work it.

  • kaitkait Member

    @avsisp said: The proof is in the pudding as we say... My entire subnet was indeed spoofed. Right before you posted your comment claiming responsibility for it.

    Because trolling is fun and I can see whats going on on abuseipdb, pretty easy to make the link between spoofing and you getting trolled by someone.

    @avsisp said: And considering it was half a subnet and 3 complaints each, that's about 3$ worth of spoof.

    You're just pulling numbers out of your ass, you don't pay a dollar per spoof, you just get a VPS for $5/m on a network that doesn't block spoofing and can spoof however long you want. I have no idea where to find those VPS providers but I wanted to make a joke about using ihostart, but I think even he blocks spoofing.

    @avsisp said: You did exactly what you claim you did.

    Wrong again stalker child. I am in your head rent free.

  • kaitkait Member

    @avsisp said: But again - the script has been stopped and isn't in use at the moment until I have time to re-work it.

    Maybe because its broken as hell and reports way to much bullshit xdddd.

  • yoursunnyyoursunny Member, IPv6 Advocate

    @Tion said:
    I can't wait to see the public offers and recommended providers for port scanning activities.

    GravHosting allows port scanning in Amsterdam and Johor.

    Thanked by 2Yuki_ xvps
Sign In or Register to comment.