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

;; QUESTION SECTION:
;134.61.226.146.			IN	A

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

;; Query time: 34 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 18:39:23 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 146.226.61.134.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 146.226.61.134.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
103.132.171.2 attackbotsspam
$f2bV_matches
2020-01-10 15:12:09
91.224.60.75 attackbots
Jan 10 12:02:55 gw1 sshd[6766]: Failed password for root from 91.224.60.75 port 40520 ssh2
...
2020-01-10 15:20:55
159.65.185.253 attackspambots
xmlrpc attack
2020-01-10 15:21:23
87.140.6.227 attackbots
Jan  9 19:32:49 hanapaa sshd\[25903\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=p578c06e3.dip0.t-ipconnect.de  user=root
Jan  9 19:32:51 hanapaa sshd\[25903\]: Failed password for root from 87.140.6.227 port 33893 ssh2
Jan  9 19:36:18 hanapaa sshd\[26250\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=p578c06e3.dip0.t-ipconnect.de  user=root
Jan  9 19:36:20 hanapaa sshd\[26250\]: Failed password for root from 87.140.6.227 port 47898 ssh2
Jan  9 19:39:49 hanapaa sshd\[26697\]: Invalid user django from 87.140.6.227
2020-01-10 15:31:09
183.154.24.114 attackbotsspam
2020-01-09 22:54:48 dovecot_login authenticator failed for (rzify) [183.154.24.114]:52553 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=chenyong@lerctr.org)
2020-01-09 22:55:00 dovecot_login authenticator failed for (lwwvx) [183.154.24.114]:52553 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=chenyong@lerctr.org)
2020-01-09 22:55:14 dovecot_login authenticator failed for (ewerb) [183.154.24.114]:52553 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=chenyong@lerctr.org)
...
2020-01-10 15:15:01
87.103.214.172 attackbots
01/10/2020-05:55:14.170857 87.103.214.172 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-01-10 15:16:33
180.241.47.160 attackspam
Unauthorized connection attempt from IP address 180.241.47.160 on Port 445(SMB)
2020-01-10 15:17:41
118.169.244.127 attackbotsspam
Jan 10 05:54:28 vmd46246 kernel: [2543463.381975] [UFW BLOCK] IN=eth0 OUT= MAC=00:50:56:3e:fb:88:28:99:3a:4d:23:91:08:00 SRC=118.169.244.127 DST=144.91.112.181 LEN=40 TOS=0x00 PREC=0x00 TTL=54 ID=2372 PROTO=TCP SPT=18273 DPT=23 WINDOW=26437 RES=0x00 SYN URGP=0 
Jan 10 05:54:59 vmd46246 kernel: [2543493.688506] [UFW BLOCK] IN=eth0 OUT= MAC=00:50:56:3e:fb:88:28:99:3a:4d:23:91:08:00 SRC=118.169.244.127 DST=144.91.112.181 LEN=40 TOS=0x00 PREC=0x00 TTL=54 ID=2372 PROTO=TCP SPT=18273 DPT=23 WINDOW=26437 RES=0x00 SYN URGP=0 
Jan 10 05:55:14 vmd46246 kernel: [2543509.261867] [UFW BLOCK] IN=eth0 OUT= MAC=00:50:56:3e:fb:88:28:99:3a:4d:23:91:08:00 SRC=118.169.244.127 DST=144.91.112.181 LEN=40 TOS=0x00 PREC=0x00 TTL=54 ID=2372 PROTO=TCP SPT=18273 DPT=23 WINDOW=26437 RES=0x00 SYN URGP=0 
...
2020-01-10 15:14:39
66.253.130.211 attackbotsspam
Jan 10 08:12:07 localhost sshd\[32234\]: Invalid user backups from 66.253.130.211 port 41654
Jan 10 08:12:07 localhost sshd\[32234\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.253.130.211
Jan 10 08:12:09 localhost sshd\[32234\]: Failed password for invalid user backups from 66.253.130.211 port 41654 ssh2
2020-01-10 15:29:05
188.142.253.35 attackspambots
Jan 10 08:09:57 vmanager6029 sshd\[27657\]: Invalid user toth from 188.142.253.35 port 39712
Jan 10 08:09:57 vmanager6029 sshd\[27657\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.142.253.35
Jan 10 08:10:00 vmanager6029 sshd\[27657\]: Failed password for invalid user toth from 188.142.253.35 port 39712 ssh2
2020-01-10 15:23:35
107.6.169.253 attackspambots
" "
2020-01-10 14:57:49
35.240.18.171 attackspambots
$f2bV_matches
2020-01-10 15:34:02
46.38.144.146 attackspambots
Jan 10 06:45:46 blackbee postfix/smtpd\[19801\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: authentication failure
Jan 10 06:46:10 blackbee postfix/smtpd\[19803\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: authentication failure
Jan 10 06:47:03 blackbee postfix/smtpd\[19804\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: authentication failure
Jan 10 06:47:24 blackbee postfix/smtpd\[19803\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: authentication failure
Jan 10 06:48:21 blackbee postfix/smtpd\[19804\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: authentication failure
...
2020-01-10 15:00:14
177.152.124.21 attack
$f2bV_matches
2020-01-10 15:15:24
188.254.0.112 attack
Jan 10 07:51:36 server sshd\[2242\]: Invalid user sd from 188.254.0.112
Jan 10 07:51:36 server sshd\[2242\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.112 
Jan 10 07:51:38 server sshd\[2242\]: Failed password for invalid user sd from 188.254.0.112 port 50206 ssh2
Jan 10 07:55:09 server sshd\[3245\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.112  user=root
Jan 10 07:55:11 server sshd\[3245\]: Failed password for root from 188.254.0.112 port 47678 ssh2
...
2020-01-10 15:17:16

Recently Reported IPs

184.34.21.150 80.231.157.58 62.119.249.57 239.44.78.8
134.236.144.29 98.36.162.94 114.203.63.15 127.165.85.239
135.44.170.174 174.192.115.63 222.212.222.164 58.79.183.153
47.169.202.176 90.34.26.26 227.2.73.20 80.215.225.52
237.205.68.227 86.183.201.175 216.225.70.124 101.213.77.146