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: IANA Special-Purpose Address

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 <<>> 241.45.16.164
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21948
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;241.45.16.164.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 17:29:31 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 164.16.45.241.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 164.16.45.241.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
144.217.171.225 attackbots
Scanning for non-existent /wp-admin (WordPress login)
2019-09-04 06:41:53
18.27.197.252 attackspambots
Automated report - ssh fail2ban:
Sep 4 00:00:30 wrong password, user=root, port=50604, ssh2
Sep 4 00:00:34 wrong password, user=root, port=50604, ssh2
Sep 4 00:00:37 wrong password, user=root, port=50604, ssh2
Sep 4 00:00:41 wrong password, user=root, port=50604, ssh2
2019-09-04 06:04:40
111.231.215.20 attackbotsspam
Sep  3 10:03:44 lcprod sshd\[12936\]: Invalid user market from 111.231.215.20
Sep  3 10:03:44 lcprod sshd\[12936\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.215.20
Sep  3 10:03:46 lcprod sshd\[12936\]: Failed password for invalid user market from 111.231.215.20 port 43808 ssh2
Sep  3 10:08:59 lcprod sshd\[13483\]: Invalid user ggg from 111.231.215.20
Sep  3 10:08:59 lcprod sshd\[13483\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.215.20
2019-09-04 05:51:37
112.35.46.21 attackbots
Sep  3 20:34:04 dev0-dcde-rnet sshd[9695]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.35.46.21
Sep  3 20:34:07 dev0-dcde-rnet sshd[9695]: Failed password for invalid user lxpopuser from 112.35.46.21 port 33856 ssh2
Sep  3 20:37:04 dev0-dcde-rnet sshd[9712]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.35.46.21
2019-09-04 06:21:14
102.68.186.52 attackspam
DATE:2019-09-03 20:36:51, IP:102.68.186.52, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2019-09-04 06:31:47
106.12.38.109 attackspambots
Sep  3 21:38:54 MK-Soft-VM7 sshd\[27834\]: Invalid user teddy from 106.12.38.109 port 56844
Sep  3 21:38:54 MK-Soft-VM7 sshd\[27834\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.38.109
Sep  3 21:38:56 MK-Soft-VM7 sshd\[27834\]: Failed password for invalid user teddy from 106.12.38.109 port 56844 ssh2
...
2019-09-04 06:15:09
172.81.248.249 attackspam
Sep  4 00:26:24 rpi sshd[16873]: Failed password for root from 172.81.248.249 port 39820 ssh2
2019-09-04 06:35:23
157.230.146.19 attack
Sep  4 04:07:33 areeb-Workstation sshd[23072]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.146.19
Sep  4 04:07:35 areeb-Workstation sshd[23072]: Failed password for invalid user bk from 157.230.146.19 port 42504 ssh2
...
2019-09-04 06:41:26
82.196.15.195 attackspam
Sep  3 22:19:44 legacy sshd[29850]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.196.15.195
Sep  3 22:19:46 legacy sshd[29850]: Failed password for invalid user tomcat from 82.196.15.195 port 38070 ssh2
Sep  3 22:25:45 legacy sshd[30021]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.196.15.195
...
2019-09-04 05:55:28
138.197.166.233 attackbots
Sep  4 01:21:09 www1 sshd\[38572\]: Address 138.197.166.233 maps to g6fitness.live, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Sep  4 01:21:09 www1 sshd\[38572\]: Invalid user admin from 138.197.166.233Sep  4 01:21:11 www1 sshd\[38572\]: Failed password for invalid user admin from 138.197.166.233 port 55756 ssh2Sep  4 01:24:59 www1 sshd\[38807\]: Address 138.197.166.233 maps to g6fitness.live, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Sep  4 01:25:01 www1 sshd\[38807\]: Failed password for root from 138.197.166.233 port 43478 ssh2Sep  4 01:28:46 www1 sshd\[39248\]: Address 138.197.166.233 maps to g6fitness.live, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Sep  4 01:28:46 www1 sshd\[39248\]: Invalid user david from 138.197.166.233
...
2019-09-04 06:44:45
162.247.74.200 attackbotsspam
Sep  3 22:17:04 MK-Soft-VM5 sshd\[18814\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.247.74.200  user=root
Sep  3 22:17:06 MK-Soft-VM5 sshd\[18814\]: Failed password for root from 162.247.74.200 port 41164 ssh2
Sep  3 22:17:08 MK-Soft-VM5 sshd\[18814\]: Failed password for root from 162.247.74.200 port 41164 ssh2
...
2019-09-04 06:24:32
129.226.52.214 attackbots
Sep  3 20:34:10 vtv3 sshd\[5868\]: Invalid user jp123 from 129.226.52.214 port 36192
Sep  3 20:34:10 vtv3 sshd\[5868\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.226.52.214
Sep  3 20:34:12 vtv3 sshd\[5868\]: Failed password for invalid user jp123 from 129.226.52.214 port 36192 ssh2
Sep  3 20:38:45 vtv3 sshd\[8222\]: Invalid user 123456 from 129.226.52.214 port 53824
Sep  3 20:38:45 vtv3 sshd\[8222\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.226.52.214
Sep  3 20:55:52 vtv3 sshd\[17289\]: Invalid user test_user1 from 129.226.52.214 port 44352
Sep  3 20:55:52 vtv3 sshd\[17289\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.226.52.214
Sep  3 20:55:54 vtv3 sshd\[17289\]: Failed password for invalid user test_user1 from 129.226.52.214 port 44352 ssh2
Sep  3 21:00:28 vtv3 sshd\[19634\]: Invalid user bot123 from 129.226.52.214 port 33738
Sep  3 21:00:28 vtv3 sshd
2019-09-04 06:36:07
119.146.150.134 attack
Sep  3 12:00:16 php2 sshd\[30875\]: Invalid user joan from 119.146.150.134
Sep  3 12:00:16 php2 sshd\[30875\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.146.150.134
Sep  3 12:00:19 php2 sshd\[30875\]: Failed password for invalid user joan from 119.146.150.134 port 59744 ssh2
Sep  3 12:03:25 php2 sshd\[31274\]: Invalid user teamspeak3 from 119.146.150.134
Sep  3 12:03:25 php2 sshd\[31274\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.146.150.134
2019-09-04 06:33:20
5.103.229.96 attack
Too many connections or unauthorized access detected from Yankee banned ip
2019-09-04 06:25:09
185.100.87.206 attack
Sep  4 00:28:38 ubuntu-2gb-nbg1-dc3-1 sshd[9861]: Failed password for root from 185.100.87.206 port 38301 ssh2
Sep  4 00:28:41 ubuntu-2gb-nbg1-dc3-1 sshd[9861]: error: maximum authentication attempts exceeded for root from 185.100.87.206 port 38301 ssh2 [preauth]
...
2019-09-04 06:44:15

Recently Reported IPs

141.181.73.27 54.40.66.68 78.254.68.52 133.246.91.140
223.160.60.154 175.190.6.87 117.213.145.137 20.208.82.43
236.130.88.58 99.236.101.88 155.22.14.13 6.220.115.7
191.27.98.75 77.215.162.101 182.201.184.18 43.40.177.150
107.160.115.169 188.38.7.251 139.226.247.66 5.223.165.98