
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 173.201.191.217 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 21 | FTP | Medium | File Transfer Protocol — often targeted for anonymous login attacks |
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 25 | SMTP | Medium | SMTP mail server — can be abused for spam relay |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 110 | POP3 | Low | Service on port 110 |
| 143 | IMAP | Low | Service on port 143 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 587 | Unknown | Low | Service on port 587 |
| 995 | POP3S | Low | Service on port 995 |
| 2082 | Unknown | Low | Service on port 2082 |
| 2083 | Unknown | Low | Service on port 2083 |
| 2096 | Unknown | Low | Service on port 2096 |
| 3306 | MySQL | High | MySQL 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.
| CVE ID | Link |
|---|---|
| CVE-2020-14145 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2021-41617 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2019-16905 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2008-3844 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2020-15778 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2025-26465 | NVD → |
🔴 Security scanning identified 14 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
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:
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.
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 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.