ABUSE.MOM
THREAT REPORT

IP Threat Report
173.201.191.217

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 14:29:51
First seen: 2026-03-18 07:00:05
Last seen: 2026-03-18 07:00:05
105

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
173.201.191.217
Type
Residential
Country
🇺🇸 United States
City
Tempe
ISP
GoDaddy.com, LLC
Organization
GoDaddy.com, LLC
Autonomous System
AS26496 GoDaddy.com, LLC
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 6Medium-risk: admin panels, config files+60
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Σ = 105
03

Observed Activity

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

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

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

04

Timeline

2026-03-18 07:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 6 (+60), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-03-18 07:00:05
Last malicious request observed
Total score reached: 105/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

GoDaddy.com, LLC
AS26496 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 173.201.191.217 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

🔎 Directory Scan Defense

IP 173.201.191.217 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (13)
PortServiceRiskDescription
21FTPMediumFile Transfer Protocol — often targeted for anonymous login attacks
22SSHLowSecure Shell — common brute force target for remote access
25SMTPMediumSMTP mail server — can be abused for spam relay
80HTTPLowHTTP web server — standard web traffic
110POP3LowService on port 110
143IMAPLowService on port 143
443HTTPSLowHTTPS web server — encrypted web traffic
587UnknownLowService on port 587
995POP3SLowService on port 995
2082UnknownLowService on port 2082
2083UnknownLowService on port 2083
2096UnknownLowService on port 2096
3306MySQLHighMySQL database — should never be exposed to the internet

⚠️ 2 high-risk ports detected on 173.201.191.217. These services should not be publicly accessible without strict firewall rules.

KNOWN VULNERABILITIES (CVE) (14)
CVE IDLink
CVE-2020-14145NVD →
CVE-2023-51767NVD →
CVE-2021-41617NVD →
CVE-2023-48795NVD →
CVE-2016-20012NVD →
CVE-2019-16905NVD →
CVE-2007-2768NVD →
CVE-2021-36368NVD →
CVE-2008-3844NVD →
CVE-2023-38408NVD →
CVE-2020-15778NVD →
CVE-2025-32728NVD →
CVE-2023-51385NVD →
CVE-2025-26465NVD →

🔴 Security scanning identified 14 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.

DETECTED TECHNOLOGIES
exim:exim:4.99.1openbsd:openssh:8.0mariadb:mariadbpureftpd:pure-ftpdapache:http_server
Hostnames: ip-173-201-191-217.ip.secureserver.netprod.phx3.secureserver.net
PTR: ip-173-201-191-217.ip.secureserver.net

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

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
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
zen.spamhaus.org
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

173.201.191.217 has been assigned a threat score of 105/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

IP address 173.201.191.217 has been traced to Tempe, United States, operating on the network of GoDaddy.com, LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With a threat score of 105/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇺🇸 Top threats from United States

72.167.46.126 (75)View all →

🏢 Same network: AS26496

68.178.171.4 (85)72.167.46.126 (75)97.74.87.226 (60)View all →
12

Security Intelligence

💡 Cross-Site Scripting (XSS) Attacks

XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.

💡 Subdomain Takeover Vulnerabilities

Subdomain takeover occurs when DNS records point to decommissioned services. Attackers claim the abandoned resource and serve content under the trusted domain, enabling cookie theft, phishing, and reputation damage.

🔍 Check Any IP Address

Share this report: