35.241.132.20

ip:35.241.132.20

The entity with IP address 35.241.132.20 is associated with computer security services. It has been detected for attempting sensitive file probes, such as accessing /.env and /.git/config files, indicating potential security threats. The entity operates within the cybersecurity sector, focusing on identifying and mitigating unauthorized access attempts. No specific ownership or licensing information is available for this IP address.

ipHigh RiskComputer Security Service
Trust Analysis
0
out of 100

Analysis Summary

The digital entity associated with IP address 35.241.132.20, categorized under computer security services, has a trust score of 0/100, indicating severe trustworthiness concerns. While the entity's operation within the cybersecurity sector and valid geolocation data from Belgium provide minor positive indicators, its overall reputation is critically undermined by significant negative factors. The entity is flagged in threat reports for attempting sensitive file probes, such as accessing /.env and /.git/config files, which are strong indicators of malicious behavior and potential security threats. Furthermore, its blacklisting on zen.spamhaus.org reinforces concerns about its association with unauthorized activities. The absence of specific ownership or licensing information further complicates trust evaluation. Overall, users should exercise extreme caution with this IP entity, as its activities pose substantial security risks, necessitating stringent scrutiny and potential avoidance.

Score Breakdown

Entity has 1 threat report(s) with typesSensitiveFileProbe
Blacklisted in RBLzen.spamhaus.org
Valid geolocation data (BE)+5
ASN 396982GOOGLE-CLOUD-PLATFORM
Technical Information
IP Info
Reviews
Anonymous
10/13/2026SensitiveFileProbe

An incident involving sensitive file probing was detected from IP address 35.241.132.20, which attempted to access files such as /.env and /.git/config on 15 occasions. The sample logs indicate repeated GET requests from this IP address, specifically targeting paths like /frontend/.env and /new/.env, all resulting in 404 errors. This activity suggests a potential security threat that requires immediate attention to prevent unauthorized access to sensitive information.