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: None

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

;; QUESTION SECTION:
;229.3.149.45.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 24 18:08:46 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 45.149.3.229.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 45.149.3.229.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
193.32.160.150 attackbots
Oct 18 21:53:41 relay postfix/smtpd\[6284\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.150\]: 554 5.7.1 \: Relay access denied\; from=\<8yjra3csojlaqzfb@dubaischolars.com\> to=\ proto=ESMTP helo=\<\[193.32.160.146\]\>
Oct 18 21:53:41 relay postfix/smtpd\[6284\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.150\]: 554 5.7.1 \: Relay access denied\; from=\<8yjra3csojlaqzfb@dubaischolars.com\> to=\ proto=ESMTP helo=\<\[193.32.160.146\]\>
Oct 18 21:53:41 relay postfix/smtpd\[6284\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.150\]: 554 5.7.1 \: Relay access denied\; from=\<8yjra3csojlaqzfb@dubaischolars.com\> to=\ proto=ESMTP helo=\<\[193.32.160.146\]\>
Oct 18 21:53:41 relay postfix/smtpd\[6284\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.150\]: 554 5.7.1 \: Relay access denied\; from=\<8yjra3csojlaqzfb@d
...
2019-10-19 04:05:32
185.17.41.198 attackbots
Fail2Ban - SSH Bruteforce Attempt
2019-10-19 04:10:22
150.109.170.73 attackspam
" "
2019-10-19 03:55:48
106.53.90.75 attackspam
2019-10-18T20:07:01.562535shield sshd\[10299\]: Invalid user mk@123 from 106.53.90.75 port 41952
2019-10-18T20:07:01.568748shield sshd\[10299\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.90.75
2019-10-18T20:07:03.213125shield sshd\[10299\]: Failed password for invalid user mk@123 from 106.53.90.75 port 41952 ssh2
2019-10-18T20:16:04.410368shield sshd\[13055\]: Invalid user ucla from 106.53.90.75 port 58824
2019-10-18T20:16:04.414517shield sshd\[13055\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.90.75
2019-10-19 04:17:28
171.244.43.52 attackbots
2019-10-18T20:25:23.270538abusebot.cloudsearch.cf sshd\[27658\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.244.43.52  user=root
2019-10-19 04:25:50
221.140.151.235 attackspambots
Failed password for invalid user stage123 from 221.140.151.235 port 39314 ssh2
Invalid user 123Qweqaz$%\^ from 221.140.151.235 port 41095
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.140.151.235
Failed password for invalid user 123Qweqaz$%\^ from 221.140.151.235 port 41095 ssh2
Invalid user 1234 from 221.140.151.235 port 41489
2019-10-19 04:22:35
117.117.165.131 attackbotsspam
Oct 18 21:58:56 apollo sshd\[5296\]: Invalid user emplazamiento from 117.117.165.131Oct 18 21:58:57 apollo sshd\[5296\]: Failed password for invalid user emplazamiento from 117.117.165.131 port 49884 ssh2Oct 18 22:05:11 apollo sshd\[5317\]: Failed password for root from 117.117.165.131 port 43988 ssh2
...
2019-10-19 04:27:32
211.253.10.96 attackbots
Oct 18 22:37:52 server sshd\[9207\]: Invalid user deploy from 211.253.10.96
Oct 18 22:37:52 server sshd\[9207\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.253.10.96 
Oct 18 22:37:54 server sshd\[9207\]: Failed password for invalid user deploy from 211.253.10.96 port 46344 ssh2
Oct 18 22:53:40 server sshd\[13328\]: Invalid user nicholas from 211.253.10.96
Oct 18 22:53:40 server sshd\[13328\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.253.10.96 
...
2019-10-19 04:06:43
34.70.186.153 attackspam
serveres are UTC 
Lines containing failures of 34.70.186.153
Oct 16 03:42:18 tux2 sshd[20805]: Invalid user marketing from 34.70.186.153 port 37210
Oct 16 03:42:18 tux2 sshd[20805]: Failed password for invalid user marketing from 34.70.186.153 port 37210 ssh2
Oct 16 03:42:18 tux2 sshd[20805]: Received disconnect from 34.70.186.153 port 37210:11: Bye Bye [preauth]
Oct 16 03:42:18 tux2 sshd[20805]: Disconnected from invalid user marketing 34.70.186.153 port 37210 [preauth]
Oct 16 03:55:51 tux2 sshd[21551]: Failed password for r.r from 34.70.186.153 port 43828 ssh2
Oct 16 03:55:51 tux2 sshd[21551]: Received disconnect from 34.70.186.153 port 43828:11: Bye Bye [preauth]
Oct 16 03:55:51 tux2 sshd[21551]: Disconnected from authenticating user r.r 34.70.186.153 port 43828 [preauth]
Oct 16 03:59:20 tux2 sshd[21739]: Invalid user ig from 34.70.186.153 port 56278
Oct 16 03:59:20 tux2 sshd[21739]: Failed password for invalid user ig from 34.70.186.153 port 56278 ssh2
Oct 16 03:59:2........
------------------------------
2019-10-19 03:59:45
142.93.215.102 attackspam
2019-10-18T21:53:32.687979scmdmz1 sshd\[21916\]: Invalid user user03 from 142.93.215.102 port 36162
2019-10-18T21:53:32.690709scmdmz1 sshd\[21916\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.215.102
2019-10-18T21:53:34.605309scmdmz1 sshd\[21916\]: Failed password for invalid user user03 from 142.93.215.102 port 36162 ssh2
...
2019-10-19 04:10:43
222.186.52.86 attack
Oct 18 22:22:55 * sshd[29027]: Failed password for root from 222.186.52.86 port 32671 ssh2
Oct 18 22:22:58 * sshd[29027]: Failed password for root from 222.186.52.86 port 32671 ssh2
2019-10-19 04:25:05
0.0.0.22 attackspambots
abasicmove.de 2a00:d680:10:50::22 \[18/Oct/2019:21:53:31 +0200\] "POST /wp-login.php HTTP/1.1" 200 5761 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
abasicmove.de 2a00:d680:10:50::22 \[18/Oct/2019:21:53:31 +0200\] "POST /wp-login.php HTTP/1.1" 200 5560 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-10-19 04:14:06
203.186.57.191 attackbots
Oct 18 19:58:47 work-partkepr sshd\[28433\]: Invalid user montse from 203.186.57.191 port 41706
Oct 18 19:58:47 work-partkepr sshd\[28433\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.186.57.191
...
2019-10-19 04:02:47
45.227.253.138 attackbots
2019-10-18 22:11:52 dovecot_login authenticator failed for \(\[45.227.253.138\]\) \[45.227.253.138\]: 535 Incorrect authentication data \(set_id=info@nophost.com\)
2019-10-18 22:11:59 dovecot_login authenticator failed for \(\[45.227.253.138\]\) \[45.227.253.138\]: 535 Incorrect authentication data \(set_id=info\)
2019-10-18 22:12:15 dovecot_login authenticator failed for \(\[45.227.253.138\]\) \[45.227.253.138\]: 535 Incorrect authentication data
2019-10-18 22:12:30 dovecot_login authenticator failed for \(\[45.227.253.138\]\) \[45.227.253.138\]: 535 Incorrect authentication data
2019-10-18 22:12:39 dovecot_login authenticator failed for \(\[45.227.253.138\]\) \[45.227.253.138\]: 535 Incorrect authentication data
2019-10-19 04:26:25
180.101.221.152 attackspam
2019-10-18T19:53:09.421475abusebot-5.cloudsearch.cf sshd\[24729\]: Invalid user workgroup from 180.101.221.152 port 50128
2019-10-19 04:26:43

Recently Reported IPs

16.170.19.179 157.63.5.163 140.162.243.14 195.242.175.153
55.12.227.111 31.202.64.1 184.219.196.41 57.134.104.180
112.97.176.22 146.16.46.154 31.214.172.133 74.192.182.245
180.14.221.116 72.171.209.240 41.193.203.15 160.181.26.244
61.155.141.42 130.198.119.154 178.238.108.176 168.68.127.1