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

Region: Budapest főváros

Country: Hungary

Internet Service Provider: Vodafone

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

;; QUESTION SECTION:
;89.134.30.2.			IN	A

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

;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Apr 11 20:26:20 CST 2025
;; MSG SIZE  rcvd: 104
Host info
2.30.134.89.in-addr.arpa domain name pointer catv-89-134-30-2.catv.fixed.one.hu.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
2.30.134.89.in-addr.arpa	name = catv-89-134-30-2.catv.fixed.one.hu.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
91.220.204.253 attackbotsspam
$f2bV_matches
2020-03-05 21:54:49
117.121.38.246 attack
$f2bV_matches
2020-03-05 22:02:33
46.55.140.252 attackspambots
Telnet/23 MH Probe, Scan, BF, Hack -
2020-03-05 21:53:02
167.99.48.123 attackbotsspam
Dec 23 23:20:09 odroid64 sshd\[21593\]: User ftp from 167.99.48.123 not allowed because not listed in AllowUsers
Dec 23 23:20:09 odroid64 sshd\[21593\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.48.123  user=ftp
Feb 11 18:18:20 odroid64 sshd\[22049\]: Invalid user rus from 167.99.48.123
Feb 11 18:18:20 odroid64 sshd\[22049\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.48.123
...
2020-03-05 22:05:37
176.15.154.96 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-05 21:41:43
168.228.188.22 attack
Dec 27 01:54:10 odroid64 sshd\[19350\]: User root from 168.228.188.22 not allowed because not listed in AllowUsers
Dec 27 01:54:10 odroid64 sshd\[19350\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.228.188.22  user=root
Feb  5 17:11:38 odroid64 sshd\[27497\]: Invalid user admin from 168.228.188.22
Feb  5 17:11:38 odroid64 sshd\[27497\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.228.188.22
...
2020-03-05 21:40:13
36.82.193.115 proxy
This is IP not there adress real or true
2020-03-05 22:07:32
178.128.83.204 attackbotsspam
Mar  5 20:35:20 lcl-usvr-02 sshd[9129]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.83.204  user=root
Mar  5 20:35:22 lcl-usvr-02 sshd[9129]: Failed password for root from 178.128.83.204 port 57102 ssh2
Mar  5 20:35:35 lcl-usvr-02 sshd[9182]: Invalid user test from 178.128.83.204 port 59742
...
2020-03-05 21:50:31
168.232.129.160 attackspambots
Nov 28 07:03:48 odroid64 sshd\[15905\]: User root from 168.232.129.160 not allowed because not listed in AllowUsers
Nov 28 07:03:48 odroid64 sshd\[15905\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.232.129.160  user=root
...
2020-03-05 21:37:05
223.25.99.37 attack
Automatically reported by fail2ban report script (mx1)
2020-03-05 22:08:30
167.99.71.142 attackbots
Nov  7 00:07:14 odroid64 sshd\[6635\]: User root from 167.99.71.142 not allowed because not listed in AllowUsers
Nov  7 00:07:15 odroid64 sshd\[6635\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.71.142  user=root
Dec 24 15:14:16 odroid64 sshd\[31105\]: User root from 167.99.71.142 not allowed because not listed in AllowUsers
Dec 24 15:14:16 odroid64 sshd\[31105\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.71.142  user=root
...
2020-03-05 22:04:05
60.12.214.27 attackbots
40022/tcp 14422/tcp...
[2020-01-06/03-05]4pkt,2pt.(tcp)
2020-03-05 21:32:29
167.99.194.54 attackbots
Mar  5 14:54:41 ewelt sshd[31592]: Invalid user sarvub from 167.99.194.54 port 53646
Mar  5 14:54:41 ewelt sshd[31592]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.194.54
Mar  5 14:54:41 ewelt sshd[31592]: Invalid user sarvub from 167.99.194.54 port 53646
Mar  5 14:54:43 ewelt sshd[31592]: Failed password for invalid user sarvub from 167.99.194.54 port 53646 ssh2
...
2020-03-05 22:09:20
45.125.65.42 attack
Mar  5 14:20:02 srv01 postfix/smtpd\[3495\]: warning: unknown\[45.125.65.42\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar  5 14:21:48 srv01 postfix/smtpd\[12004\]: warning: unknown\[45.125.65.42\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar  5 14:22:00 srv01 postfix/smtpd\[11673\]: warning: unknown\[45.125.65.42\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar  5 14:33:55 srv01 postfix/smtpd\[11673\]: warning: unknown\[45.125.65.42\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar  5 14:35:41 srv01 postfix/smtpd\[13984\]: warning: unknown\[45.125.65.42\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-03-05 21:39:26
59.89.57.199 attack
Mar  5 14:35:34 MK-Soft-VM8 sshd[3893]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.89.57.199 
Mar  5 14:35:35 MK-Soft-VM8 sshd[3893]: Failed password for invalid user Ronald from 59.89.57.199 port 57404 ssh2
...
2020-03-05 21:52:30

Recently Reported IPs

88.62.230.72 65.49.1.191 65.49.1.189 65.49.1.184
65.49.1.183 65.49.1.182 130.185.249.75 129.222.143.98
51.2.183.227 140.140.3.49 162.216.150.77 119.42.146.66
3.87.246.107 65.49.1.134 23.236.187.192 86.1.3.46
113.215.189.58 1.4.220.105 192.168.254.152 93.170.82.160