First of all, thank you for taking the time to report this issue! I really appreciate it.
If the issue is a coding issue: Feel free to message me through any of the social networks: Twitter, Mastodon or BlueSky, and I'll be more than happy to fix it!
If the issue is data issue, such as misinformation in the WHOIS or request header data: I unfortunately can't change that! That information is owned either by the website owner or the server where the data was collected from. You'll have to reach out to them to ensure they are providing accurate data.
HTTP GET requests with this websiteThere could be multiple reasons as to why. The long-story-short is that requests are made through a Netlify function, which runs inside an AWS Lambda Function themselves. If your web server blocks these kind of requests, then you would never get an appropriate answer here. Keep in mind this is a free service.
When making requests to your website, we're using some standard browser headers (desktop headers), so the headers you'll see are meant from the response of your server to a request from a desktop client. The User-agent header is set to a Chrome browser, but ending with @ https://headers.live/ in case you want to make sure to allow the request from this website.
It's currently not possible for me to provide you with a list of IP addresses where these requests are being made, since they will keep changing due to the nature of AWS Lambda functions. However, you can always expect that the IP address making the requests belongs to any of the AWS ASNs.