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

;; QUESTION SECTION:
;134.130.19.25.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 23:54:28 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 25.19.130.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 25.19.130.134.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
92.119.160.107 attackspam
Nov  7 10:09:27 mc1 kernel: \[4404063.607671\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=92.119.160.107 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=64428 PROTO=TCP SPT=43393 DPT=53457 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  7 10:09:55 mc1 kernel: \[4404091.803336\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=92.119.160.107 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=56430 PROTO=TCP SPT=43393 DPT=53007 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  7 10:15:33 mc1 kernel: \[4404429.581543\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=92.119.160.107 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=17652 PROTO=TCP SPT=43393 DPT=53265 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-11-07 17:16:27
176.31.100.19 attackspambots
2019-11-07T08:17:48.663952shield sshd\[21227\]: Invalid user zenoss from 176.31.100.19 port 45978
2019-11-07T08:17:48.668596shield sshd\[21227\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns388913.ip-176-31-100.eu
2019-11-07T08:17:50.505888shield sshd\[21227\]: Failed password for invalid user zenoss from 176.31.100.19 port 45978 ssh2
2019-11-07T08:21:25.922939shield sshd\[21597\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns388913.ip-176-31-100.eu  user=ftp
2019-11-07T08:21:27.543724shield sshd\[21597\]: Failed password for ftp from 176.31.100.19 port 54258 ssh2
2019-11-07 17:14:30
128.14.209.226 attackspambots
Connection by 128.14.209.226 on port: 999 got caught by honeypot at 11/7/2019 6:32:05 AM
2019-11-07 17:22:53
117.67.146.220 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/117.67.146.220/ 
 
 CN - 1H : (643)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : CN 
 NAME ASN : ASN4134 
 
 IP : 117.67.146.220 
 
 CIDR : 117.64.0.0/13 
 
 PREFIX COUNT : 5430 
 
 UNIQUE IP COUNT : 106919680 
 
 
 ATTACKS DETECTED ASN4134 :  
  1H - 19 
  3H - 55 
  6H - 100 
 12H - 163 
 24H - 297 
 
 DateTime : 2019-11-07 07:27:43 
 
 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN  - data recovery
2019-11-07 16:49:09
139.59.135.84 attackspam
Nov  7 07:13:23 game-panel sshd[3513]: Failed password for root from 139.59.135.84 port 42556 ssh2
Nov  7 07:17:22 game-panel sshd[3626]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.135.84
Nov  7 07:17:24 game-panel sshd[3626]: Failed password for invalid user irina from 139.59.135.84 port 52026 ssh2
2019-11-07 17:11:19
112.85.42.238 attack
F2B jail: sshd. Time: 2019-11-07 09:57:33, Reported by: VKReport
2019-11-07 17:03:32
58.26.135.210 attackspam
Nov  6 22:45:05 php1 sshd\[16891\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.26.135.210  user=root
Nov  6 22:45:06 php1 sshd\[16891\]: Failed password for root from 58.26.135.210 port 18401 ssh2
Nov  6 22:49:54 php1 sshd\[18022\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.26.135.210  user=root
Nov  6 22:49:56 php1 sshd\[18022\]: Failed password for root from 58.26.135.210 port 57291 ssh2
Nov  6 22:54:40 php1 sshd\[18551\]: Invalid user nadia from 58.26.135.210
Nov  6 22:54:40 php1 sshd\[18551\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.26.135.210
2019-11-07 17:00:01
92.222.34.211 attack
Nov  7 09:27:35 localhost sshd\[11587\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.222.34.211  user=root
Nov  7 09:27:37 localhost sshd\[11587\]: Failed password for root from 92.222.34.211 port 54888 ssh2
Nov  7 09:31:38 localhost sshd\[11984\]: Invalid user zs from 92.222.34.211 port 37230
Nov  7 09:31:38 localhost sshd\[11984\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.222.34.211
2019-11-07 16:48:15
207.46.13.33 attackbotsspam
Automatic report - Banned IP Access
2019-11-07 16:55:10
78.128.113.120 attack
Nov  7 08:53:34 heicom postfix/smtpd\[5915\]: warning: unknown\[78.128.113.120\]: SASL PLAIN authentication failed: authentication failure
Nov  7 08:53:35 heicom postfix/smtpd\[5146\]: warning: unknown\[78.128.113.120\]: SASL PLAIN authentication failed: authentication failure
Nov  7 08:55:07 heicom postfix/smtpd\[5915\]: warning: unknown\[78.128.113.120\]: SASL PLAIN authentication failed: authentication failure
Nov  7 08:55:09 heicom postfix/smtpd\[5146\]: warning: unknown\[78.128.113.120\]: SASL PLAIN authentication failed: authentication failure
Nov  7 09:18:05 heicom postfix/smtpd\[5915\]: warning: unknown\[78.128.113.120\]: SASL PLAIN authentication failed: authentication failure
...
2019-11-07 17:21:28
180.101.227.173 attackbots
2019-11-07T08:41:15.593229abusebot-7.cloudsearch.cf sshd\[25486\]: Invalid user bat1323 from 180.101.227.173 port 50708
2019-11-07 17:05:11
103.94.2.154 attackbots
Nov  7 10:48:45 vtv3 sshd\[10454\]: Invalid user 887 from 103.94.2.154 port 50131
Nov  7 10:48:45 vtv3 sshd\[10454\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.94.2.154
Nov  7 10:48:48 vtv3 sshd\[10454\]: Failed password for invalid user 887 from 103.94.2.154 port 50131 ssh2
Nov  7 10:54:11 vtv3 sshd\[13884\]: Invalid user provider from 103.94.2.154 port 41682
Nov  7 10:54:11 vtv3 sshd\[13884\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.94.2.154
Nov  7 11:04:44 vtv3 sshd\[21009\]: Invalid user monkey from 103.94.2.154 port 53018
Nov  7 11:04:44 vtv3 sshd\[21009\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.94.2.154
Nov  7 11:04:46 vtv3 sshd\[21009\]: Failed password for invalid user monkey from 103.94.2.154 port 53018 ssh2
Nov  7 11:09:57 vtv3 sshd\[24487\]: Invalid user HUAWEI@123 from 103.94.2.154 port 44587
Nov  7 11:09:57 vtv3 sshd\[24487\]: pam_unix
2019-11-07 17:05:53
103.23.102.111 attackspambots
11/07/2019-01:27:08.341804 103.23.102.111 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-11-07 17:08:08
103.241.227.106 attackbotsspam
WordPress XMLRPC scan :: 103.241.227.106 0.292 - [07/Nov/2019:06:27:08  0000] www.[censored_1] "POST /xmlrpc.php HTTP/1.1" 200 194 "https://www.[censored_1]/" "PHP/7.3.26" "HTTP/1.1"
2019-11-07 17:12:47
187.188.169.123 attack
Nov  7 09:18:02 MK-Soft-Root2 sshd[8748]: Failed password for root from 187.188.169.123 port 54434 ssh2
...
2019-11-07 17:20:12

Recently Reported IPs

150.21.88.67 130.245.152.33 232.195.100.114 238.18.222.88
5.5.5.5 226.60.226.15 138.112.40.148 121.254.225.212
188.11.182.92 224.93.12.172 149.48.219.243 77.181.81.200
232.255.224.179 187.169.137.64 237.199.99.37 254.197.92.206
137.49.216.37 224.189.151.158 90.204.153.213 195.128.153.254