Welcome to the new IP check page! We're rolling it out gradually and would love your input. Spot a bug, or have a suggestion?
Share feedback
172.69.134.201
Neutral Activity
There is no recent abuse activity, or the IP address is whitelisted.
Whitelisted Subnet
Whitelisted netblocks are typically owned by trusted entities, such as Google or Microsoft who
may use them for search engine spiders. However, these same entities sometimes also provide cloud
servers and mail services which are easily abused. Pay special attention when trusting or
distrusting these IPs.
Log in to view charts and search reports for this IP.
Log In
Top Reporter Countries (Last 60 Days)
Example preview
Report Categories (Last 60 Days)
Example preview
Reports Activity
Example preview
Account required for the enhanced features
Log inSign up
IP Abuse Reports for 172.69.134.201:
This IP address has been reported a total of
65
times from
15 distinct
sources.
172.69.134.201 was first reported on
, and the most recent report was
.
In the last 60 days, the only reporter location was:
Belgium
with 3
reports.
The only category in these recent reports was:
Web App Attack
3
times.
Recent Reports
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
UFW blocked a suspicious connection attempt to a closed or denied port. This activity is commonly as ...
show moreUFW blocked a suspicious connection attempt to a closed or denied port. This activity is commonly associated with port scanning, service discovery, or automated internet probing. Technical: source_ip=172.69.134.201; proto=TCP; source_port=11032; target_port=8880; flags=SYN
show less
UFW blocked a suspicious connection attempt to a closed or denied port. This activity is commonly as ...
show moreUFW blocked a suspicious connection attempt to a closed or denied port. This activity is commonly associated with port scanning, service discovery, or automated internet probing. Technical: source_ip=172.69.134.201; proto=TCP; source_port=12506; target_port=2086; flags=SYN
show less
UFW blocked a suspicious connection attempt to a closed or denied port. This activity is commonly as ...
show moreUFW blocked a suspicious connection attempt to a closed or denied port. This activity is commonly associated with port scanning, service discovery, or automated internet probing. Technical: source_ip=172.69.134.201; proto=TCP; source_port=11303; target_port=2086; flags=SYN
show less
Blocked by UFW on server [2083/tcp]
Source port: 10635
TTL: 50
Packet length: 60
TOS: 0x00
This rep ...
show moreBlocked by UFW on server [2083/tcp]
Source port: 10635
TTL: 50
Packet length: 60
TOS: 0x00
This report was generated by:
https://github.com/sefinek/UFW-AbuseIPDB-Reporter
show less
Blocked by UFW on server [2083/tcp]
Source port: 12728
TTL: 50
Packet length: 60
TOS: 0x00
This rep ...
show moreBlocked by UFW on server [2083/tcp]
Source port: 12728
TTL: 50
Packet length: 60
TOS: 0x00
This report was generated by:
https://github.com/sefinek/UFW-AbuseIPDB-Reporter
show less
Blocked by UFW on server [2083/tcp]
Source port: 10431
TTL: 50
Packet length: 60
TOS: 0x00
This rep ...
show moreBlocked by UFW on server [2083/tcp]
Source port: 10431
TTL: 50
Packet length: 60
TOS: 0x00
This report was generated by:
https://github.com/sefinek/UFW-AbuseIPDB-Reporter
show less
Blocked by UFW on server [2083/tcp]
Source port: 9973
TTL: 50
Packet length: 60
TOS: 0x00
This repo ...
show moreBlocked by UFW on server [2083/tcp]
Source port: 9973
TTL: 50
Packet length: 60
TOS: 0x00
This report was generated by:
https://github.com/sefinek/UFW-AbuseIPDB-Reporter
show less
Blocked by UFW on vds [80/tcp]
Source port: 11198
TTL: 54
Packet length: 60
TOS: 0x00
This report w ...
show moreBlocked by UFW on vds [80/tcp]
Source port: 11198
TTL: 54
Packet length: 60
TOS: 0x00
This report was generated by:
https://github.com/sefinek/UFW-AbuseIPDB-Reporter
show less
2025-07-17 02:11:25,766 fail2ban.actions [837]: NOTICE [nginx-bad-request] Ban 172.69.134.20 ...
show more2025-07-17 02:11:25,766 fail2ban.actions [837]: NOTICE [nginx-bad-request] Ban 172.69.134.201
2025-07-17 19:43:20,578 fail2ban.actions [837]: NOTICE [nginx-bad-request] Ban 172.69.134.201
...
show less
Triggered Cloudflare WAF (firewallManaged) from US.
Action taken: LOG
Protocol: HTTP/1.1 (GET method ...
show moreTriggered Cloudflare WAF (firewallManaged) from US.
Action taken: LOG
Protocol: HTTP/1.1 (GET method)
Endpoint: /
UA: Mozilla/5.0 (iPhone; CPU iPhone OS 13_2_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Mobile/15E148 Safari/604.1
This report was generated by:
https://github.com/sefinek/Cloudflare-WAF-To-AbuseIPDB
show less