ABUSE.MOM
THREAT REPORT

IP Threat Report
43.220.3.239

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:54:12
First seen: 2026-03-22 20:00:06
Last seen: 2026-03-22 20:00:06
240

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 240/100. Total malicious requests observed: 1.

DANGER_PATHBURSTREFERER
01

Geolocation & Classification

IP Address
43.220.3.239
Type
Hosting
Country
🇦🇺 Australia
City
Sydney
ISP
Amazon.com, Inc.
Organization
AWS EC2 (ap-southeast-2)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 917High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 255Medium-risk: admin panels, config files+60
Burst: 10 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 34 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 240
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-03-22 20:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 917 (+100), Danger medium hits: 255 (+60), Burst: 10 req / 2s (+35)
2026-03-22 20:00:06
Last malicious request observed
Total score reached: 240/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon.com, Inc.
AS16509 · 🇦🇺 Australia
06

Recommendations

Actions taken & recommended

  • IP 43.220.3.239 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 43.220.3.239.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

43.220.3.239 has been assigned a threat score of 240/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Network traffic from 43.220.3.239, located in Sydney, Australia, operating on the network of Amazon.com, Inc., has been classified as malicious by our automated threat scoring engine. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. With 101 flagged addresses, Australia represents a significant presence in our threat database. With a threat score of 240/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇦🇺 Top threats from Australia

20.42.209.0 (280)170.64.203.182 (280)20.213.152.227 (280)20.5.72.178 (280)4.197.33.200 (280)View all →

🏢 Same network: AS16509

54.206.58.169 (263)3.26.130.63 (263)3.107.10.216 (263)13.210.152.189 (263)3.27.13.152 (263)View all →
12

Security Intelligence

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 Subnet-Level vs IP-Level Blocking

When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.

🔍 Check Any IP Address

Share this report: