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

;; QUESTION SECTION:
;241.154.122.229.		IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 21:15:51 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 229.122.154.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 229.122.154.241.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.162.99.243 attackbots
\[09/Jul/2019 06:23:04\] SMTP Spam attack detected from 139.162.99.243, client closed connection before SMTP greeting
\[09/Jul/2019 06:23:05\] SMTP Spam attack detected from 139.162.99.243, client closed connection before SMTP greeting
\[09/Jul/2019 06:23:19\] SMTP Spam attack detected from 139.162.99.243, client closed connection before SMTP greeting
...
2019-07-09 17:03:53
189.91.5.130 attackspam
Brute force attempt
2019-07-09 16:54:07
103.213.251.100 attackbots
458 attempts in 3 minutes, port scan
2019-07-09 17:09:22
67.213.75.130 attack
Jul  9 10:27:41 tux-35-217 sshd\[20853\]: Invalid user tecnica from 67.213.75.130 port 13095
Jul  9 10:27:41 tux-35-217 sshd\[20853\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.213.75.130
Jul  9 10:27:42 tux-35-217 sshd\[20853\]: Failed password for invalid user tecnica from 67.213.75.130 port 13095 ssh2
Jul  9 10:30:50 tux-35-217 sshd\[20871\]: Invalid user zj from 67.213.75.130 port 9190
Jul  9 10:30:50 tux-35-217 sshd\[20871\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.213.75.130
...
2019-07-09 17:25:41
113.177.115.85 attack
SMTP Fraud Orders
2019-07-09 16:57:07
107.170.195.246 attackbotsspam
2019-07-09 05:11:28 SMTP protocol synchronization error (input sent whostnamehout wahostnameing for greeting): rejected connection from H=[107.170.195.246] input="EHLO zg-0301e-18rn"
2019-07-09 05:11:39 SMTP protocol synchronization error (input sent whostnamehout wahostnameing for greeting): rejected connection from H=[107.170.195.246] input="EHLO zg-0301e-18rn"
2019-07-09 05:11:39 SMTP protocol synchronization error (input sent whostnamehout wahostnameing for greeting): rejected connection from H=[107.170.195.246] input="EHLO zg-0301e-18rn"


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=107.170.195.246
2019-07-09 17:15:40
138.197.156.62 attackspam
09.07.2019 03:23:12 SSH access blocked by firewall
2019-07-09 17:07:40
94.23.145.156 attackspambots
WordPress wp-login brute force :: 94.23.145.156 0.048 BYPASS [09/Jul/2019:18:25:21  1000] [censored_2] "POST /wp-login.php HTTP/1.1" 200 4630 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-07-09 16:58:32
51.91.18.121 attackspambots
Jul  9 07:43:32 mail1 sshd\[11152\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.18.121  user=root
Jul  9 07:43:34 mail1 sshd\[11152\]: Failed password for root from 51.91.18.121 port 53122 ssh2
Jul  9 07:43:36 mail1 sshd\[11152\]: Failed password for root from 51.91.18.121 port 53122 ssh2
Jul  9 07:43:39 mail1 sshd\[11152\]: Failed password for root from 51.91.18.121 port 53122 ssh2
Jul  9 07:43:43 mail1 sshd\[11152\]: Failed password for root from 51.91.18.121 port 53122 ssh2
...
2019-07-09 16:52:49
167.99.198.0 attackbotsspam
[portscan] tcp/22 [SSH]
[scan/connect: 2 time(s)]
*(RWIN=65535)(07091133)
2019-07-09 16:56:37
177.44.17.242 attack
Jul  8 22:24:38 mailman postfix/smtpd[32663]: warning: unknown[177.44.17.242]: SASL PLAIN authentication failed: authentication failure
2019-07-09 16:38:58
164.132.74.224 attackspam
Jul  9 04:40:48 localhost sshd\[36842\]: Invalid user amber from 164.132.74.224 port 38346
Jul  9 04:40:48 localhost sshd\[36842\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.74.224
...
2019-07-09 16:54:36
78.187.25.221 attack
" "
2019-07-09 17:13:10
150.109.194.59 attackbotsspam
Jul  9 05:18:26 nxxxxxxx sshd[24187]: refused connect from 150.109.194.59 (1=
50.109.194.59)


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=150.109.194.59
2019-07-09 17:23:25
112.196.54.139 attackbots
Jul  9 09:39:59 legacy sshd[11361]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.196.54.139
Jul  9 09:40:02 legacy sshd[11361]: Failed password for invalid user sid from 112.196.54.139 port 8991 ssh2
Jul  9 09:42:30 legacy sshd[11401]: Failed password for root from 112.196.54.139 port 28922 ssh2
...
2019-07-09 16:57:34

Recently Reported IPs

119.245.116.237 48.140.115.218 186.163.11.51 131.11.41.87
101.122.251.188 37.215.167.224 156.27.148.203 106.241.100.61
239.235.86.210 217.218.209.29 194.213.190.182 240.181.218.68
230.81.91.185 190.208.240.175 248.22.139.247 212.185.179.47
63.148.16.205 119.209.192.13 18.119.171.203 83.97.222.81