search

jpgpi250 / piholemanual

files referred to in my pihole installation manual
114 stars 14 forks source link

Removal Request #27

Closed L8X closed 1 year ago

L8X commented 1 year ago

Hello,

You have falsely listed 2a0a:6040:b204::2 in your list, this IP belongs to my company @Simulhost and we require you to immediately remove the aforementioned IP.

Kindly respond to this within 72 hours and comply with out request, otherwise we will request GitHub to take your repository down with immediate effect.

L8X commented 1 year ago

Furthermore, you are to refrain from publishing, scanning, or attempting to access ANY IP address with the reverse DNS "no-reverse-defined.simulhost.com", or attempting any DNS based fuzzing or scanning the following domains:

simulhost.com simul.host

Failure to abide by this may result in legal action being taken against you under the Computer Misuse Act.

L8X commented 1 year ago

@jpgpi250 You are required to merge: https://github.com/jpgpi250/piholemanual/pull/30

jpgpi250 commented 1 year ago

2a0a:6040:b204::2 resolves to dns.simulhost.com

dns.simulhost.com was listed as a DoH server in:

I don't add domains/IPs to lists, neither do I perform any scanning. I only consolidate various list, that contain DoH domains. you can find the lists I consolidate in the manual, here

As explained in the manual, it is the users responsibility to create exceptions, also explained in the manual.

For the above IP's you may want / need to create an exception https://api.bgpview.io/ip/2a0a:6040:b204::2 The result of these inquiry shows that these IP's are managed by "SIMULHOST-AS", ASN 211380

If you don't want to create specific IP exceptions, you can create an exception for the network range SIMULHOST-AS specifies (2a0a:6040:b200::/40) , refer to the above queries to bgpview.io.

It is up to you do decide whether or not you want to use the DoH blocklist, it is provided as is (consolidated) with a clear explanation on how to create exceptions.

The IP address is obtained using a dig request (dig AAAA +short dns.simulhost.com). I can't imagine this is illegal...

L8X commented 1 year ago

2a0a:6040:b204::2 resolves to dns.simulhost.com

dns.simulhost.com was listed as a DoH server in:

I don't add domains/IPs to lists, neither do I perform any scanning. I only consolidate various list, that contain DoH domains. you can find the lists I consolidate in the manual, here

As explained in the manual, it is the users responsibility to create exceptions, also explained in the manual.

For the above IP's you may want / need to create an exception https://api.bgpview.io/ip/2a0a:6040:b204::2 The result of these inquiry shows that these IP's are managed by "SIMULHOST-AS", ASN 211380

If you don't want to create specific IP exceptions, you can create an exception for the network range SIMULHOST-AS specifies (2a0a:6040:b200::/40) , refer to the above queries to bgpview.io.

It is up to you do decide whether or not you want to use the DoH blocklist, it is provided as is (consolidated) with a clear explanation on how to create exceptions.

The IP address is obtained using a dig request (dig AAAA +short dns.simulhost.com). I can't imagine this is illegal...

Then I suggest you exclude us from your list so it doesn't get added again. I will be contacting CURL in regards to their unauthorized advertisement of our IP addresses, please take caution in future to avoid our IPs from being added.