Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: Japan

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 221.104.73.45
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59578
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;221.104.73.45.			IN	A

;; AUTHORITY SECTION:
.			29	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025021800 1800 900 604800 86400

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 18:33:47 CST 2025
;; MSG SIZE  rcvd: 106
Host info
45.73.104.221.in-addr.arpa domain name pointer softbank221104073045.bbtec.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
45.73.104.221.in-addr.arpa	name = softbank221104073045.bbtec.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
159.65.168.225 attack
Excessive requests with 404 errors
2019-11-18 13:26:39
88.245.82.146 attackbots
Automatic report - Port Scan Attack
2019-11-18 13:09:37
180.159.158.189 attack
2019-11-18T04:53:42.747633abusebot-5.cloudsearch.cf sshd\[13136\]: Invalid user robert from 180.159.158.189 port 36127
2019-11-18 13:46:49
193.33.111.237 attackbotsspam
xmlrpc attack
2019-11-18 13:11:11
178.42.19.174 attackspambots
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/178.42.19.174/ 
 
 PL - 1H : (108)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : PL 
 NAME ASN : ASN5617 
 
 IP : 178.42.19.174 
 
 CIDR : 178.42.0.0/15 
 
 PREFIX COUNT : 183 
 
 UNIQUE IP COUNT : 5363456 
 
 
 ATTACKS DETECTED ASN5617 :  
  1H - 1 
  3H - 2 
  6H - 6 
 12H - 14 
 24H - 31 
 
 DateTime : 2019-11-18 05:54:20 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-18 13:23:45
117.64.227.144 attackbots
Bad Postfix AUTH attempts
...
2019-11-18 13:17:49
184.168.193.151 attack
GET /wp/wp-admin/
2019-11-18 13:25:03
83.1.160.114 attack
DATE:2019-11-18 05:53:49, IP:83.1.160.114, PORT:telnet - Telnet brute force auth on a honeypot server (epe-dc)
2019-11-18 13:44:58
39.42.142.66 attackspambots
Connection by 39.42.142.66 on port: 23 got caught by honeypot at 11/18/2019 3:54:25 AM
2019-11-18 13:34:15
45.82.153.76 attackbotsspam
Nov 18 06:20:33 relay postfix/smtpd\[14608\]: warning: unknown\[45.82.153.76\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 18 06:20:54 relay postfix/smtpd\[15023\]: warning: unknown\[45.82.153.76\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 18 06:22:13 relay postfix/smtpd\[15023\]: warning: unknown\[45.82.153.76\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 18 06:22:36 relay postfix/smtpd\[14120\]: warning: unknown\[45.82.153.76\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 18 06:26:00 relay postfix/smtpd\[12930\]: warning: unknown\[45.82.153.76\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-18 13:36:15
218.92.0.200 attackspambots
Nov 18 04:57:08 venus sshd\[23236\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.200  user=root
Nov 18 04:57:09 venus sshd\[23236\]: Failed password for root from 218.92.0.200 port 49450 ssh2
Nov 18 04:57:11 venus sshd\[23236\]: Failed password for root from 218.92.0.200 port 49450 ssh2
...
2019-11-18 13:16:15
51.75.248.241 attack
Nov 18 07:13:22 microserver sshd[49640]: Invalid user laivite from 51.75.248.241 port 45938
Nov 18 07:13:22 microserver sshd[49640]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.248.241
Nov 18 07:13:24 microserver sshd[49640]: Failed password for invalid user laivite from 51.75.248.241 port 45938 ssh2
Nov 18 07:17:16 microserver sshd[50208]: Invalid user willenbring from 51.75.248.241 port 40906
Nov 18 07:17:16 microserver sshd[50208]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.248.241
Nov 18 07:28:57 microserver sshd[51604]: Invalid user jeremie from 51.75.248.241 port 44114
Nov 18 07:28:57 microserver sshd[51604]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.248.241
Nov 18 07:28:59 microserver sshd[51604]: Failed password for invalid user jeremie from 51.75.248.241 port 44114 ssh2
Nov 18 07:32:58 microserver sshd[52198]: pam_unix(sshd:auth): authentication fail
2019-11-18 13:50:03
151.80.75.127 attackbots
Nov 18 04:55:02  postfix/smtpd: warning: unknown[151.80.75.127]: SASL LOGIN authentication failed
2019-11-18 13:04:50
186.224.245.239 attackbotsspam
Automatic report - Port Scan Attack
2019-11-18 13:08:56
46.38.144.57 attackspam
Nov 18 06:07:48 relay postfix/smtpd\[430\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 18 06:08:04 relay postfix/smtpd\[12930\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 18 06:08:24 relay postfix/smtpd\[519\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 18 06:08:42 relay postfix/smtpd\[14113\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 18 06:09:01 relay postfix/smtpd\[430\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-18 13:14:39

Recently Reported IPs

138.49.245.210 85.200.48.147 128.115.53.12 144.112.31.193
228.68.31.39 29.136.205.31 195.120.176.85 201.131.120.170
33.22.252.196 42.97.8.20 251.62.251.79 200.23.40.224
72.176.220.21 146.35.250.134 36.78.209.188 135.86.219.124
26.99.19.243 195.50.89.180 109.239.1.156 21.192.223.20