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 34.62.44.12:
This IP address has been reported a total of
89
times from
62 distinct
sources.
34.62.44.12 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
United States of America
with 23
reports;
Germany
with 21
reports;
Brazil
with 8
reports.
The most common categories in these recent reports were:
Port Scan
71
times;
Hacking
19
times;
Brute-Force
9
times;
Web App Attack
4
times;
Exploited Host
4
times;
Other
9
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.
[rede-44-49] 09/12/2026-06:21:11.998448, 34.62.44.12, Protocol: 6, ET SCAN Suspicious inbound to myS ...
show more[rede-44-49] 09/12/2026-06:21:11.998448, 34.62.44.12, Protocol: 6, ET SCAN Suspicious inbound to mySQL port 3306
show less
2026-09-12T08:37:17.598158+0000 inbound port scan detected by Suricata. src=34.62.44.12:58663 dst=51 ...
show more2026-09-12T08:37:17.598158+0000 inbound port scan detected by Suricata. src=34.62.44.12:58663 dst=51.68.231.122:5432 proto=TCP. signature="ET SCAN Suspicious inbound to PostgreSQL port 5432" category="Potentially Bad Traffic" sid=2010939 reason=scan_signature.
show less
09/12/2026-10:36:00.133190 34.62.44.12 Protocol: 6 ET SCAN Suspicious inbound to PostgreSQL port 543 ...
show more09/12/2026-10:36:00.133190 34.62.44.12 Protocol: 6 ET SCAN Suspicious inbound to PostgreSQL port 5432
show less
Auto-blocked by Seczar SecureOps — Database Service Brute Force (5 events in 5min) at 2026-09-12 08: ...
show moreAuto-blocked by Seczar SecureOps — Database Service Brute Force (5 events in 5min) at 2026-09-12 08:26
show less
