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: United States

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

;; QUESTION SECTION:
;3.49.45.44.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 22 00:57:49 CST 2023
;; MSG SIZE  rcvd: 103
Host info
Host 44.45.49.3.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 44.45.49.3.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
89.39.89.18 attack
Jun 29 09:02:37 prod4 sshd\[31356\]: Invalid user luca from 89.39.89.18
Jun 29 09:02:39 prod4 sshd\[31356\]: Failed password for invalid user luca from 89.39.89.18 port 48986 ssh2
Jun 29 09:06:09 prod4 sshd\[1109\]: Invalid user di from 89.39.89.18
...
2020-06-29 18:13:54
123.206.228.251 attackbots
port scan and connect, tcp 8080 (http-proxy)
2020-06-29 18:18:23
216.128.109.226 attackbots
216.128.109.226 - - [29/Jun/2020:05:14:52 +0100] "POST /xmlrpc.php HTTP/1.1" 403 219 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
216.128.109.226 - - [29/Jun/2020:05:14:55 +0100] "POST /wp-login.php HTTP/1.1" 503 18222 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
216.128.109.226 - - [29/Jun/2020:05:16:24 +0100] "POST /xmlrpc.php HTTP/1.1" 403 219 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"
...
2020-06-29 18:09:29
36.92.139.194 attackspam
06/29/2020-01:49:04.200868 36.92.139.194 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-06-29 18:07:11
192.241.222.90 attackbots
Unauthorized connection attempt detected from IP address 192.241.222.90 to port 7002 [T]
2020-06-29 18:19:59
103.92.26.252 attackbots
Jun 29 07:09:53 server sshd[17747]: Failed password for invalid user testftp from 103.92.26.252 port 35484 ssh2
Jun 29 07:13:33 server sshd[21511]: Failed password for invalid user copie from 103.92.26.252 port 50382 ssh2
Jun 29 07:17:12 server sshd[24743]: Failed password for invalid user admin9 from 103.92.26.252 port 37044 ssh2
2020-06-29 18:05:03
113.21.123.26 attackspam
failed_logins
2020-06-29 18:14:29
212.70.149.82 attackspam
Jun 29 11:49:52 mail postfix/smtpd\[4034\]: warning: unknown\[212.70.149.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Jun 29 11:50:20 mail postfix/smtpd\[4034\]: warning: unknown\[212.70.149.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Jun 29 12:20:53 mail postfix/smtpd\[4334\]: warning: unknown\[212.70.149.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Jun 29 12:21:21 mail postfix/smtpd\[4334\]: warning: unknown\[212.70.149.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
2020-06-29 18:24:46
163.172.216.182 attack
 UDP 163.172.216.182:51303 -> port 389, len 81
2020-06-29 18:16:45
61.177.172.102 attackbots
Jun 29 10:00:16 email sshd\[12215\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.102  user=root
Jun 29 10:00:18 email sshd\[12215\]: Failed password for root from 61.177.172.102 port 51249 ssh2
Jun 29 10:00:38 email sshd\[12282\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.102  user=root
Jun 29 10:00:39 email sshd\[12282\]: Failed password for root from 61.177.172.102 port 57151 ssh2
Jun 29 10:00:53 email sshd\[12309\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.102  user=root
...
2020-06-29 18:03:31
200.61.54.140 attackspam
Jun 29 07:02:27 meumeu sshd[68893]: Invalid user vps from 200.61.54.140 port 47338
Jun 29 07:02:27 meumeu sshd[68893]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.61.54.140 
Jun 29 07:02:27 meumeu sshd[68893]: Invalid user vps from 200.61.54.140 port 47338
Jun 29 07:02:29 meumeu sshd[68893]: Failed password for invalid user vps from 200.61.54.140 port 47338 ssh2
Jun 29 07:06:36 meumeu sshd[69008]: Invalid user janek from 200.61.54.140 port 45914
Jun 29 07:06:36 meumeu sshd[69008]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.61.54.140 
Jun 29 07:06:36 meumeu sshd[69008]: Invalid user janek from 200.61.54.140 port 45914
Jun 29 07:06:38 meumeu sshd[69008]: Failed password for invalid user janek from 200.61.54.140 port 45914 ssh2
Jun 29 07:10:49 meumeu sshd[69195]: Invalid user user from 200.61.54.140 port 44494
...
2020-06-29 17:51:55
198.199.92.224 attackbotsspam
Attempted connection to port 9200.
2020-06-29 17:59:40
175.107.236.19 attackbotsspam
20/6/28@23:50:43: FAIL: Alarm-Intrusion address from=175.107.236.19
20/6/28@23:50:43: FAIL: Alarm-Intrusion address from=175.107.236.19
...
2020-06-29 18:28:10
216.244.66.248 attackbots
20 attempts against mh-misbehave-ban on pluto
2020-06-29 17:54:27
52.188.155.148 attackbots
Jun 29 12:04:38 prod4 sshd\[521\]: Failed password for root from 52.188.155.148 port 33444 ssh2
Jun 29 12:09:47 prod4 sshd\[2908\]: Invalid user ch from 52.188.155.148
Jun 29 12:09:48 prod4 sshd\[2908\]: Failed password for invalid user ch from 52.188.155.148 port 36510 ssh2
...
2020-06-29 18:20:21

Recently Reported IPs

156.227.18.113 144.178.170.10 132.98.230.1 117.206.8.168
177.231.22.203 14.155.84.210 104.129.128.110 253.222.139.207
231.128.66.50 232.230.20.141 168.15.164.32 68.135.140.74
43.158.184.222 28.11.73.192 85.50.169.191 106.207.104.45
152.106.158.49 206.213.162.80 191.112.57.83 148.224.38.2