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

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:
IP Type Details Datetime
134.122.19.151 attack
Seems to be part of a bot attack on login
2020-07-18 07:06:01
134.122.19.126 attackspam
trying to access non-authorized port
2020-06-02 08:03:00
134.122.19.102 attackbots
2020-04-15T20:11:40.735348rocketchat.forhosting.nl sshd[8551]: Invalid user nuxeo from 134.122.19.102 port 35670
2020-04-15T20:11:42.984514rocketchat.forhosting.nl sshd[8551]: Failed password for invalid user nuxeo from 134.122.19.102 port 35670 ssh2
2020-04-15T20:17:03.021534rocketchat.forhosting.nl sshd[8682]: Invalid user tidb from 134.122.19.102 port 50326
...
2020-04-16 03:24:14
134.122.19.128 attackspam
2020-04-03T05:56:32.883804vfs-server-01 sshd\[31667\]: Invalid user ubnt from 134.122.19.128 port 52744
2020-04-03T05:56:33.666983vfs-server-01 sshd\[31670\]: Invalid user admin from 134.122.19.128 port 54360
2020-04-03T05:56:35.253114vfs-server-01 sshd\[31674\]: Invalid user 1234 from 134.122.19.128 port 57256
2020-04-03 12:28:39
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.122.19.50
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27948
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;134.122.19.50.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 21:04:24 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 50.19.122.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 50.19.122.134.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
102.165.30.13 attackbots
Unauthorized connection attempt detected from IP address 102.165.30.13 to port 5800
2020-10-13 15:31:50
180.166.240.99 attackbots
Oct 13 06:19:59 journals sshd\[72964\]: Invalid user mireya from 180.166.240.99
Oct 13 06:19:59 journals sshd\[72964\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.166.240.99
Oct 13 06:20:01 journals sshd\[72964\]: Failed password for invalid user mireya from 180.166.240.99 port 60570 ssh2
Oct 13 06:23:58 journals sshd\[73365\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.166.240.99  user=root
Oct 13 06:23:59 journals sshd\[73365\]: Failed password for root from 180.166.240.99 port 53354 ssh2
...
2020-10-13 15:08:36
140.143.196.66 attackspambots
Oct 13 06:38:38 localhost sshd[108460]: Invalid user user from 140.143.196.66 port 44664
Oct 13 06:38:38 localhost sshd[108460]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.196.66
Oct 13 06:38:38 localhost sshd[108460]: Invalid user user from 140.143.196.66 port 44664
Oct 13 06:38:41 localhost sshd[108460]: Failed password for invalid user user from 140.143.196.66 port 44664 ssh2
Oct 13 06:48:10 localhost sshd[109403]: Invalid user vjohnson from 140.143.196.66 port 32992
...
2020-10-13 15:48:33
106.12.148.170 attack
Invalid user cb from 106.12.148.170 port 47326
2020-10-13 15:40:59
95.216.101.117 attackspambots
RDP brute forcing (r)
2020-10-13 15:25:32
192.241.230.159 attack
SP-Scan 50318:9042 detected 2020.10.12 08:25:44
blocked until 2020.12.01 00:28:31
2020-10-13 15:11:28
101.231.124.6 attackspam
SSH login attempts.
2020-10-13 15:30:47
164.163.253.86 attackbotsspam
Port scan on 1 port(s): 445
2020-10-13 15:45:23
125.215.207.44 attackspambots
SSH Brute Force (V)
2020-10-13 15:37:04
51.75.247.170 attackbots
2020-10-13T04:44:41.192235shield sshd\[28844\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.ip-51-75-247.eu  user=root
2020-10-13T04:44:43.062545shield sshd\[28844\]: Failed password for root from 51.75.247.170 port 38100 ssh2
2020-10-13T04:51:17.626712shield sshd\[29675\]: Invalid user sheba from 51.75.247.170 port 41962
2020-10-13T04:51:17.637096shield sshd\[29675\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.ip-51-75-247.eu
2020-10-13T04:51:20.126206shield sshd\[29675\]: Failed password for invalid user sheba from 51.75.247.170 port 41962 ssh2
2020-10-13 15:34:42
106.13.176.235 attackbotsspam
$f2bV_matches
2020-10-13 15:46:03
51.83.97.44 attackbotsspam
Oct 13 08:47:31 eventyay sshd[23832]: Failed password for root from 51.83.97.44 port 59830 ssh2
Oct 13 08:51:02 eventyay sshd[23986]: Failed password for root from 51.83.97.44 port 35938 ssh2
Oct 13 08:54:36 eventyay sshd[24140]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.83.97.44
...
2020-10-13 15:15:34
172.104.155.193 attack
Unauthorized connection attempt detected from IP address 172.104.155.193 to port 1962
2020-10-13 15:18:39
122.194.229.54 attackspam
Automatic report BANNED IP
2020-10-13 15:24:49
141.98.81.113 attack
kernel: [163097.707543] FIREWALL SYN-FLOOD:IN=eth2 OUT= DST_MAC=** SRC_MAC=:74:9b:e8:16:ba:e2 SRC=141.98.81.113 DST=** LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=123 PROTO=TCP SPT=65529 DPT=3218 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0xff00
2020-10-13 15:10:01

Recently Reported IPs

134.122.30.115 134.122.194.174 104.219.72.73 104.219.76.39
104.22.0.101 104.22.0.105 104.22.0.122 104.22.0.126
104.22.0.133 104.22.0.137 133.6.182.82 133.58.39.13
133.35.21.51 133.25.90.128 133.250.169.149 133.52.27.1
104.22.0.147 104.22.0.150 104.22.0.160 104.22.0.163