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

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

;; QUESTION SECTION:
;149.212.45.4.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 13:53:18 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 4.45.212.149.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 4.45.212.149.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
94.187.54.182 attackspambots
Lines containing failures of 94.187.54.182
Dec 25 07:30:17 HOSTNAME sshd[7353]: Invalid user user from 94.187.54.182 port 56306
Dec 25 07:30:18 HOSTNAME sshd[7353]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.187.54.182
Dec 25 07:30:19 HOSTNAME sshd[7353]: Failed password for invalid user user from 94.187.54.182 port 56306 ssh2
Dec 25 07:30:20 HOSTNAME sshd[7353]: Connection closed by 94.187.54.182 port 56306 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=94.187.54.182
2019-12-25 19:15:33
136.232.106.58 attackspambots
Dec 25 09:02:43 legacy sshd[14076]: Failed password for root from 136.232.106.58 port 51357 ssh2
Dec 25 09:08:43 legacy sshd[14158]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=136.232.106.58
Dec 25 09:08:44 legacy sshd[14158]: Failed password for invalid user dovecot from 136.232.106.58 port 51859 ssh2
...
2019-12-25 19:17:00
45.82.153.142 attack
Dec 25 11:05:09 srv01 postfix/smtpd\[10631\]: warning: unknown\[45.82.153.142\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 25 11:05:25 srv01 postfix/smtpd\[28457\]: warning: unknown\[45.82.153.142\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 25 11:11:31 srv01 postfix/smtpd\[16432\]: warning: unknown\[45.82.153.142\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 25 11:11:49 srv01 postfix/smtpd\[10631\]: warning: unknown\[45.82.153.142\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 25 11:19:14 srv01 postfix/smtpd\[1236\]: warning: unknown\[45.82.153.142\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-12-25 18:56:23
221.199.194.206 attackbots
FTP Brute Force
2019-12-25 18:48:54
151.49.241.22 attack
Lines containing failures of 151.49.241.22
Dec 25 07:31:37 HOSTNAME sshd[7443]: Address 151.49.241.22 maps to adsl-ull-22-241.49-151.wind.hostname, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Dec 25 07:31:37 HOSTNAME sshd[7443]: Invalid user ching from 151.49.241.22 port 37236
Dec 25 07:31:37 HOSTNAME sshd[7443]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.49.241.22
Dec 25 07:31:39 HOSTNAME sshd[7443]: Failed password for invalid user ching from 151.49.241.22 port 37236 ssh2
Dec 25 07:31:39 HOSTNAME sshd[7443]: Received disconnect from 151.49.241.22 port 37236:11: Bye Bye [preauth]
Dec 25 07:31:39 HOSTNAME sshd[7443]: Disconnected from 151.49.241.22 port 37236 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=151.49.241.22
2019-12-25 18:49:14
149.202.45.205 attack
Too many connections or unauthorized access detected from Arctic banned ip
2019-12-25 19:16:00
104.248.135.31 attackspambots
Dec 25 08:39:06 wordpress wordpress(www.ruhnke.cloud)[19672]: Blocked authentication attempt for admin from ::ffff:104.248.135.31
2019-12-25 18:50:10
179.52.247.34 attackbots
2019-12-25T07:23:51.3211071240 sshd\[16087\]: Invalid user pi from 179.52.247.34 port 41126
2019-12-25T07:23:51.3724421240 sshd\[16089\]: Invalid user pi from 179.52.247.34 port 24692
2019-12-25T07:23:51.4763021240 sshd\[16087\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.52.247.34
2019-12-25T07:23:51.5265131240 sshd\[16089\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.52.247.34
...
2019-12-25 18:53:46
134.175.124.221 attack
Dec 25 05:29:12 vps46666688 sshd[3282]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.124.221
Dec 25 05:29:14 vps46666688 sshd[3282]: Failed password for invalid user heile from 134.175.124.221 port 53554 ssh2
...
2019-12-25 18:45:13
122.170.99.105 attack
Dec 25 07:23:58 debian-2gb-nbg1-2 kernel: \[907774.064427\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=122.170.99.105 DST=195.201.40.59 LEN=60 TOS=0x00 PREC=0x00 TTL=117 ID=26615 DF PROTO=TCP SPT=62136 DPT=1433 WINDOW=8192 RES=0x00 SYN URGP=0
2019-12-25 18:51:47
207.180.231.227 attack
[portscan] Port scan
2019-12-25 19:05:16
46.151.157.115 attackbotsspam
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2019-12-25 18:42:15
107.170.242.185 attackbotsspam
Invalid user raepenbusch from 107.170.242.185 port 36870
2019-12-25 19:13:34
191.34.74.55 attackbotsspam
Invalid user test from 191.34.74.55 port 47783
2019-12-25 19:08:59
180.95.184.67 attackspam
Scanning
2019-12-25 19:02:57

Recently Reported IPs

70.244.70.181 127.77.214.64 250.197.49.72 39.150.240.215
48.73.154.58 38.95.233.209 124.165.47.242 243.38.180.92
20.9.109.222 66.7.26.208 47.211.0.120 204.153.123.40
116.227.164.1 200.67.217.145 41.10.29.130 206.123.238.51
115.217.116.254 199.9.8.21 9.101.37.64 31.3.70.120